Three years ago, every Tier 1 retailer’s transformation budget had a data lake line item. Twenty to fifty million dollars each. Same vendor parade. Same architectural diagrams. Same promise: unify the data, unlock the insights, modernize the stack.
Now the conversations have moved on. Agentic. GenAI. AI-native. Foundation models. The data lake has gone quiet.
It didn’t go away. It went underutilized.
The CDO trap
Most CDOs I talk to have a version of the same problem: they built the lake, they hit the milestones, they declared the project done — and then they never built the connective tissue from lake to decision to action.
The dashboards got built. Some of them even get viewed. But the lake itself — the actual asset — sits there as a passive repository that powers Monday-morning reports and very little else.
When the AI conversation showed up, most CDOs went straight to model selection. Which LLM. Which vendor. Which copilot. The lake — their largest single investment in the last cycle — never came up.
That’s the trap. The model isn’t the bottleneck. The lake’s readiness for agent consumption is.
What changed
AI agents need clean, queryable, contextually-tagged data more than your dashboards ever did.
A dashboard is forgiving. It surfaces a number, and a human applies judgment. If the underlying data is messy, the human notices and reaches for context.
An agent isn’t forgiving. An agent ingests, ranks, decides, and acts — often in a closed loop, often without a human in the path. If the underlying data is messy, the agent acts on the mess. At scale. Repeatedly.
The data lake you built for dashboard consumption is not, by default, ready for agent consumption. Three things break:
- Semantic context is missing. Your fields have names that made sense to the dashboard team. They don’t make sense to an agent that needs to reason about whether a SKU is promoted, returnable, age-restricted, or seasonally indexed.
- Latency assumptions are wrong. Batch refresh windows that were fine for weekly reports are not fine for closed-loop scoring agents that need to react inside the conversion window.
- Lineage is non-existent. Agents that act in a loop need to know which data is fresh, which is derived, which is canonical. Most lakes can’t answer that for any given field without an engineer.
The retrofit nobody is publishing about
The retailers compounding AI wins right now are the ones quietly retrofitting their lakes for agent consumption. Three moves, in roughly this order:
- A semantic abstraction layer on top of the lake. Not a new lake. Not a new vendor. A layer — usually built on dbt, sometimes on a metric store, sometimes hand-rolled — that gives every important entity and field a stable, agent-readable identity and definition.
- Latency tiering, not latency optimization. Most data doesn’t need to be real-time. The retrofit identifies which 5–10% does, isolates it, and routes agents to the right tier. The other 90% stays on its existing batch cadence.
- Lineage as a first-class artifact. Every field exposed to an agent has a freshness tag, a derivation history, and a confidence band. Agents that see this information make better decisions and recover from bad data more gracefully.
None of this is glamorous. None of it gets a vendor logo on the slide. It’s the unsexy retrofit work that makes every AI dollar that comes after it worth ten times what it would otherwise be worth.
The CODN angle
The cost of not closing this loop isn’t the price of the lake. It’s the multiplier on every AI initiative downstream.
A retailer with an unretrofitted lake spending $5M on agentic deployments in 2026 will get roughly half the value a peer with a retrofitted lake gets for the same spend. Not because the agents are different — they’re the same agents. Because the substrate is different.
The Cost of Doing Nothing on data lake retrofitting compounds with every new AI initiative the retailer launches. By the time the gap is visible in margin or share, it’s already two cycles too late to close cheaply.
If your lake doesn’t have a semantic layer, latency tiering, and first-class lineage today, you are underwater on every AI dollar that comes after it. That’s not a vendor problem. It’s a CDO problem. And the CDOs who treat it like one are the ones whose names will be on the case studies in 2027.