The Nekt mental model
Companies mature with data in four stages. The secret is to seek value and assertiveness first, and leave optimization for when it it really pays off.
- See the data journey as a maturity model
- Understand why value comes before optimization
- Recognize the setup that already delivers value on the first day
There is a classic temptation in data projects: start by modeling everything, arranging each table, putting together the perfect architecture before answer the first question. And then weeks pass, no one took it value of nothing, and enthusiasm cools. Nekt proposes the way contrary. First you gather the data and extract value. A Optimization comes later, when it makes sense.
The most honest way to look at this is as a maturity model. Every company follows the same four stages, in the same order, and each one delivers results per own account. You don't need to be last to start win.
The transformation comes later, when repetition justifies the effort
The four stages of maturity
1. Consolidate data in one place. It is the step that unlocks everything. While the data is spread across HubSpot, spreadsheets, a Postgres database and Meta Ads, no one can cross anything. Bring Everything for Nekt's Lakehouse is, in itself, a victory. For the first time there is a place where data is consolidated and structured in the same format.
2. Extract value with context and AI agents. With the data together and a little context (what each table means, what are the business rules), you plug in an AI agent and start literally talk to the data. No dashboard, no SQL, no wait weeks. Context, more agents already deliver assertiveness which surprises, and this happens before any heavy modeling.
3. Transform and model. When certain questions become routine and certain queries are repeated every day, so it is worth worth optimizing. You clean, type, add data sources and assemble ready-made tables for that use. And here's a facilitator: Nekt's own MCP creates the queries and notebooks of these transformations from language natural, so assembling the layers is much faster. The transformation is not the beginning of the journey, it is the consequence of having discovered what it really matters.
4. Apps and agents in production. With the stable model, you put applications and agents running in the team's daily life: a report that updates itself, an agent that responds on Slack, a app that consumes through the Data API. The value stops being punctual and becomes part of the operation.
Value and assertiveness above optimization.
It is
better answer an important question today, with just data
consolidated and a good context, than spending a month modeling for
reply in a few weeks. Optimize what has proven repetitive and
valuable, not what you imagine you might need one day.
The most impressive setup
The best way to get a feel for this model is to do the complete path of the zero until the first answer. It's short, and this is where the "aha" lives: in just a few steps you go from scattered data to an AI agent responding about your business.
- Create the workspace. Your space at Nekt, where data and resources will be brought together.
- Connect the sources. CRM, bank, spreadsheet, files, ad platforms, APIs, etc. Nekt brings the data and consolidates everything in one place.
- Configure MCP. At Nekt you connect the MCP server, the bridge that lets an AI agent see and query your data safely.
- Plug the MCP into your AI agent. You connect this MCP to its AI client (Claude, for example) and the agent starts have access to the context of your business.
- Extract value. Ask in natural language: "How much did we earn per channel last month?". The answer comes from your data, instantly. This is the moment when the journey stops being promise.
None of this required modeling tables. Consolidate sources and give context to an agent has already answered the question. Modeling only comes in later, when you figure out which questions are worth turning routine.
What about the Bronze, Silver and Gold tiers?
They continue to exist and are extremely useful. When you arrive In the transform step, the data is refined into layers: a raw layer that mirrors the data source, a clean and typed intermediate, and a ready for consumption. But note that this is a detail of step 3, not the point of departure. Many people get stuck precisely because they think they need to master the layers before taking any value. No need.
In this guide the focus is on the larger map: consolidate, give context, consume, and optimize by last. When you want to understand in depth how each layer works and the that lives in each, the lakehouse anatomy guide covers it with examples.
↗ Guide: Anatomy of the lakehouse, Bronze, Silver and GoldAn agency with 12 clients connected Meta Ads, Google Ads and CRM of each one. Instead of waiting months to assemble the architecture perfect, on the same day they consolidated everything on Nekt and plugged in an agent via MCP. In the first week I answered "which campaign yielded more this week" with just the consolidated data and a little context. Only later, when I saw that this question was repeated every day, modeled a consolidated table by customer, channel and day. Value first, optimization when it paid off.