Prashant AkhawatBuilding AI-Native Enterprises

The Economics of Enterprise AI  /  Issue Brief

The last moat isn't data.
It's your learning loop. Three Nobel economists explain the risk every enterprise runs when it buys intelligence. And the data shows the market already splitting into those who will pay it and those who won't.

The invoice is only the first payment. The second is not paid in leaked data, which contracts already handle. It is paid in dependency, and it does not stop even when the provider promises never to look.

In July 2026, Satya Nadella gave a name to a discomfort that enterprise leaders had felt for two years without being able to articulate it. He called it the Reverse Information Paradox. It is the sharpest framing yet of a real problem, and it deserves to be taken seriously because of who said it. It is also, in one crucial respect, not precise enough, and the imprecision is exactly where enterprises lose money. Read it as a diagnosis of symptoms, accurately observed. What it does not yet name is the mechanism, or the bill.

Three Nobel economists frame the whole question. In 1962, Kenneth Arrow described the original information paradox: the value of information cannot be known to a buyer until it is revealed, but once revealed it has effectively been acquired for free. The seller carries the risk. Artificial intelligence inverts that. To make a purchased model useful, an enterprise must feed it the knowledge that makes the enterprise distinctive: its prompts, its workflows, its evaluations, and above all its corrections. The buyer now carries the risk, and pays twice, once with money and again with knowledge.

The more important economist here is Oliver Williamson, who won the Nobel in 2009 for describing what happens next. Williamson showed that when a buyer makes investments valuable in one relationship but worthless outside it, a condition he called asset specificity, that buyer becomes vulnerable to being squeezed. He named it the hold-up problem. That is what the second payment actually buys: not the theft of your knowledge, but a growing dependency a supplier can later price against you.

THE SECOND PAYMENT  ·  The hidden cost of enterprise AI that contracts cannot prevent. The first payment is the invoice, and procurement already knows how to manage it. The second is paid in dependency: institutional judgment migrating, decision by decision, into a learning loop the firm does not own. Its mechanism is Loop Capture. Nadella named the symptom. What follows names the mechanism, prices the cost, and sets out the architecture that ends it.

The question of the decade is not who builds the best model. It is who owns the loop in which the model gets better at your work.

The argument in four lines
  • Training Leakage (your data trains their model) is real but largely solved by enterprise contracts and zero-retention terms.
  • Loop Capture is the real paradox: your prompts, evals, and memory become specific to one provider and lose value if moved.
  • That is asset specificity, and it invites Williamson's hold-up: once captured, you can be repriced with no exit.
  • The fix is not a better contract. It is owning the learning loop inside a trust boundary, while switching cost is still low.
The last moat isn't data. It's your learning loop.The Second Payment: the hidden cost of enterprise AI that contracts cannot prevent · the whole argument in one frameTODAY'S DEFAULT · THE CAPTURED LOOPTHE RESPONSE · THE OWNED LOOPPROVIDER'S TENANT1 · Prompt2 · Model responds3 · Human corrects4 · Memory + evalsthe loop compounds here, for themYOUR FIRMyour evaluations, corrections, and memory flow in, and stayYou pay twice: the invoice, then your judgmentSwitching cost compounds every monthThe vendor gains repricing power over youNo provable lineage when the regulator asksYOUR TRUST BOUNDARY1 · Prompt2 · Model responds3 · Human corrects4 · Memory + evalsthe loop compounds here, for youModel AModel BModel Cmodel-agnostic orchestration: swapping is configuration, not a projectEvals, memory, corrections are owned IPAny model underneath, none of them requiredThe compounding accrues to your accountProvable lineage, on demandWHY IT DECIDES THE DECADEAI adoptionLearning loopFaster learningBetter decisionsBetter executionDurable advantageThe loop is the firm's compounding mechanism. Break the chain at any link and no advantage forms. Own every link and it compounds.Prashant Akhawat · CXO Intelligence Series · akhawat.com/writing
The complete argument in one frame: the same loop, two locations for the boundary. Where the loop closes decides who owns the compounding. (Author's framework.)

That this warning came from the chief executive of the company that sells more enterprise AI than any other is worth pausing on. It is credible precisely because it runs against interest, and Nadella is explicit that the problem requires more than data protection. It is also fair to note that the firms naming the risk are positioned to sell the remedy, in sovereign tenancy and governance tooling. Neither observation makes the paradox less real. Both argue for understanding it on the buyer's terms, not the vendor's.

01  /  The mechanismIntelligence exhaust, and the loop it feeds

The knowledge that leaves is not the data enterprises already know how to protect. It is a subtler byproduct, what Nadella calls intelligence exhaust: the prompts people write, the tools agents invoke, and most valuably the corrections people make when a model is wrong. Every correction encodes a unit of institutional judgment, what an organization considers good and how it measures success, and it drains away one trace, one correction, one evaluation at a time. This is what Nadella, reaching for Hayek, calls a firm's particular knowledge: the understanding of time, place, and circumstance that no one else can hold. These corrections do not sit still. They feed a loop, and the loop is the thing that matters.

The learning loop Each turn makes the system better at your specific work 1 · Prompt 2 · Model responds 3 · Human corrects 4 · Memory + evalsaccumulate the loop compounds
The asset is not any single prompt or file. It is the compounding cycle. The only question that matters for the economics is where the boundary around this loop sits: inside the provider's environment, or inside yours. Author's framework.
PA
Author's view
Prashant Akhawat

This is cognition leakage, not data leakage

Calling this a data problem understates it. In the Cognition Stack framing, a firm's durable asset is not its documents but its layered cognition: how it perceives, decides, corrects, and remembers. The loop above is that cognition, operationalized. Data governance protects the file cabinet. What is at stake here is the reasoning that made the files worth having, and the uncomfortable corollary is that your best people feed the loop fastest, because their corrections carry the most judgment.

~528,000units / year
Consider a 2,000-person firm where 40 percent use AI daily, each making three substantive corrections that encode judgment. That is roughly half a million units of institutional judgment a year shaping a loop the firm may not own. Illustrative arithmetic on stated assumptions (800 users × 3 corrections × 220 working days), not a measurement. Change the inputs; the order of magnitude is the point.

02  /  The distinction"But they promise not to train on our data"

Here is where most treatments collapse, and where the argument must earn its keep. The strongest objection is factual and correct: on the major business and API tiers, from OpenAI and Anthropic to Microsoft and Google, customer inputs are contractually excluded from training, retention is short, and zero-data-retention terms exist for regulated workloads. For properly configured enterprise usage, "your data trains their model" is simply wrong.

Why learning compounds

Why does that flow matter more than the data it carries? Because data was never the scarce asset. Data tells you what happened. A model tells you what is probable. Organizational judgment decides what your company should do, and judgment is the one input on that list a competitor cannot buy.

Strategy research reached this conclusion long before AI made it urgent. Edith Penrose showed that firms grow on accumulated productive knowledge, not on the resources they happen to hold. Nelson and Winter showed where that knowledge lives: in routines, the half-tacit patterns of how work actually gets decided and corrected, which function as an organization's memory and are stubbornly hard to imitate. David Teece showed that advantage belongs not to the firm with the best assets but to the firm best able to keep reconfiguring them, what he called dynamic capabilities. Put the three together and the conclusion is uncomfortable for the way most enterprises now buy AI: knowledge is the growth engine, routines are where it accumulates, and the capacity to repeatedly improve decisions is the advantage itself.

The learning loop is exactly that capacity, made operational and accelerated. Each pass converts a correction into a routine, a routine into an evaluation, an evaluation into a better next decision. The causal chain is explicit and testable: AI adoption feeds the learning loop; the loop accelerates organizational learning; faster learning produces better decisions; better decisions produce better execution; and execution that improves faster than a rival's is what a durable advantage is. Break the chain at any link and no advantage forms. Own every link and it compounds.

One nuance keeps the claim honest. Owning the loop does not guarantee advantage; a firm can own its loop and still learn slowly. Ownership is the precondition, not the prize. It determines whose account the compounding accrues to, and a firm that rents its loop can execute brilliantly while building someone else's asset.

The pattern has a lineage every executive already knows. ERP captured transactions. CRM captured customers. Cloud captured infrastructure. AI captures organizational judgment, and judgment is the first captured layer that compounds with use. The earlier platforms took custody of your records. This one takes custody of your rate of learning. That is why this shift is different in kind, not merely in degree.

If the paradox were only about training, that objection would end it. It does not, for two reasons. Nadella himself points at the first: even where enterprise inputs are excluded, providers impose restrictive terms on distillation and reserve rights over usage and interaction data, so learning still flows one way at the ecosystem level. The second is deeper, and it survives even a perfect contract. Separating the two versions is the whole game.

The shallow version

Training Leakage

  • Raw data is absorbed into a shared model and could resurface elsewhere.
  • Occurs mainly on consumer tiers and shadow AI, not governed enterprise usage.
  • Addressable by contract: no-train terms, ZDR, tenant isolation, redaction.
Real, but largely solved by procurement.
The structural version

Loop Capture

  • Your prompts, evals, memory, and scaffolding become specific to one model.
  • Portable as files, but they lose value when moved. This is asset specificity.
  • Not fixable by contract. It is architecture, and it deepens with every use.
Survives every privacy promise. This is the real paradox.

A definition, stated so it can be tested and quoted: Loop Capture is the migration of an organization's learning, its evaluations, corrections, memory, and decision heuristics, into execution paths that depend on a single provider, so that the learning keeps compounding but the organization no longer owns the compounding. Lock-in describes the cost of leaving. Loop Capture describes what you lose by staying.

PA
Author's view
Prashant Akhawat

Loop Capture is Williamson's hold-up problem in a new suit

A provider can promise, truthfully, never to train on your data, and you can still be paying the Second Payment in full, because the mechanism is not theft. It is asset specificity. A prompt library tuned to one model's quirks, an evaluation harness calibrated to one model's behavior, two years of agent memory and scaffolding built for one stack: all of it is portable as text and worth far less the moment you move it. You can export the files. You cannot export the fit.

Once your investment is that specific, Williamson's hold-up follows automatically: the supplier can reprice, and you have no credible exit. No harvesting required. This is why the fix is not a better clause. It is a trust boundary you own, inside which the loop closes on your side of the line.

03  /  The evidenceBoth versions, in the data

The evidence splits cleanly. Training Leakage shows up as shadow AI on ungoverned tiers. Loop Capture shows up as the depth of dependency being accumulated. Here is the shallow version first, because it is the better-measured of the two.

Evidence for the shallow version: Training Leakage
FigureFindingWhat it meansSource
39.7%of employee AI interactions involve sensitive data; sensitive data entered once every three days per employee.The exhaust is a daily habit, not an incident.Cyberhaven, 2026
93%year-over-year rise in enterprise data moved into AI tools, roughly 18,000 TB in a year.Volume compounds faster than controls.Zscaler, 2026
47%of enterprise AI conversations run on personal, not corporate, identities.Half of usage sits outside governance.LayerX, 2026
~65%of technical uploads to AI tools are proprietary source code.What leaks is product logic.LangProtect, 2026
20%of 2025 breaches involved shadow AI.Ungoverned tools are now a breach vector.IBM, 2025
How much crosses the boundary unmanaged Interactions involving sensitive data 39.7% Conversations on personal identities 47% Top-100 GenAI tools rated medium-to-critical risk 82% Technical uploads that are proprietary code ~65%
The shallow version is real and measurable, but it is a governance problem with a known fix: move usage onto managed tiers with no-train terms. Cyberhaven 2026 AI Adoption & Risk Report (222 companies); LayerX; LangProtect (2026).

The deeper version is harder to measure, because it is newer and no one sells a dashboard for it. But its proxies are already loud: 76 to 81 percent of enterprises report concern over proprietary dependency in model, memory, and orchestration, and when a platform collapses, the migration bill arrives within weeks, as the Builder.ai case below shows. That is asset specificity presenting its bill.

04  /  The counter-caseWhy this thesis is falsifiable, and already contested

An argument that cannot be wrong is not worth making. So here is the strongest evidence against alarm: enterprises are not sleepwalking into capture. They are diversifying, fast. If that trend wins, Loop Capture recedes on its own.

The market is already reducing its specificity Enterprises deliberately spreading across models and providers Companies using 2+ LLM families (2026) 78% Companies using 3+ LLM families 36%59%in ~3 months Organizations running multiple providers 23%40%in one year earlier now Atlassian alone runs 20+ models behind one gateway.
The countertrend is genuine. Multi-model routing, open protocols such as MCP, and open-weight models all reduce asset specificity, and adoption is climbing steeply. Databricks State of AI Agents 2026; Portkey; Menlo Ventures (2026).

So why is this not already solved? Because diversification at the plumbing level does not automatically protect the loop. Routing a query to whichever model is cheapest is not the same as owning your evaluations, memory, and corrections independently of any model. A firm can run twenty models and still have its institutional judgment tuned to, and trapped inside, one provider's environment. The bifurcation is real, but the dividing line is not "how many models do you use." It is "where does your loop close."

Now run the counterargument all the way to its limit, because its endpoint is instructive. Suppose the optimists are entirely right. Suppose every frontier model converges in capability and price until intelligence is a pure commodity, as interchangeable as electricity. What, in that world, differentiates one enterprise from another? Not the model; everyone has the same ones. Not raw data, which is increasingly abundant rather than scarce. The only remaining differentiator is the rate at which an organization converts commodity intelligence into better decisions, which is precisely the learning loop. Commoditization does not weaken the thesis. It completes it: the cheaper and more interchangeable intelligence becomes, the more the loop is the only durable asset left standing.

The thesis, stated so it can be tested: firms that own the loop compound advantage; firms that merely diversify their models do not. The next three years will show which group grows faster.

05  /  The precedentWhat the casualty list actually teaches

The public cases split along the same line, and reading them correctly matters. The 2023 bans were the reflex to Training Leakage, and they were largely resolved: Samsung, Apple, and the banks now run governed enterprise AI. The unsolved cases are the 2026 ones, and they are all Loop Capture.

Samsung2023 · leakage · solved
Within 20 days of permitting ChatGPT, engineers leaked semiconductor source code and a meeting transcript across three incidents. Response: a ban, then a governed internal model. The shallow problem, correctly fixed.
Banks & Apple2023 · leakage · solved
JPMorgan, Bank of America, Citigroup, Deutsche Bank, Goldman Sachs and Apple restricted consumer tools, then adopted enterprise AI under contract. Procurement solved it.
Uber2026 · capture · unsolved
Confirmed by its CTO: exhausted its entire 2026 AI budget by April as Claude Code spread across ~5,000 engineers, at $150–$2,000 per engineer per month. Not a leak. Consumption pricing colliding with agentic workloads on a process the business now depends on; the fix was $1,500 monthly caps.
Builder.ai fallout2026 · capture · unsolved
$315,000 and three months to migrate 40 workflows after the platform's collapse, per one 2026 vendor analysis (orchestrator.dev). The cost of specificity with no portable exit.

06  /  The exposureFive risks on the board's desk

01

Moat erosion

Distinctive judgment accumulates inside a loop the firm rents. Invisible on any balance sheet until a rival deployment behaves like your best analyst.

~65% of tech uploads are proprietary code
02

Shadow AI

Half of enterprise AI runs on personal accounts. Legacy DLP was built for attachments, not chat, so the commonest leak is the most invisible.

20% of 2025 breaches involved shadow AI
03

Compounding lock-in

Specificity accrues across model, memory, orchestration, and expertise at once. Switching costs multiply, which is why early pricing is set aggressively.

76–81% cite dependency risk
04

Regulatory exposure

Regulated data in a third-party loop cedes control. Under the EU AI Act and India's DPDP, that is a compliance breach, not just a security gap.

Up to €35M or 7% of turnover
05

Cost volatility

Inference is ~85% of AI budgets (orchestrator.dev) and agentic workloads consume 5–30× the tokens of chat. Consumption pricing plus dependency leaves finance no forward visibility, as Uber's four-month burn shows.

~85% of AI budget is inference

07  /  The India lensWhy the Global South pays a steeper Second Payment

The paradox is universal, but the bill is not evenly split. For India and much of the Global South, three forces compound it.

First, regulation arrives as capability scales. India's Digital Personal Data Protection Act reaches full enforcement on 13 May 2027, with penalties up to ₹250 crore per violation, and roughly 83 percent of organizations have not begun comprehensive implementation. A regime that puts primary accountability on the data fiduciary, on a strict consent basis with no separate category for sensitive data, turns uncontrolled exhaust into direct legal liability.

Second, the sovereign build itself runs on rented foundations. The IndiaAI Mission has committed roughly $1.25 billion and deployed tens of thousands of GPUs. Yet the silicon is almost entirely foreign, and the frontier models most enterprises deploy are trained abroad. Sovereignty at the infrastructure layer can coexist with dependency at the model and loop layers. That is Loop Capture wearing a national flag.

PA
Author's view
Prashant Akhawat

Sovereignty is a loop question, not a location question

The Indian conversation has fixed on where data and compute physically sit. Necessary, but insufficient. A model can run on Indian soil, on Indian GPUs, and still capture the loop for a foreign provider if the orchestration, evaluations, and memory are theirs. Real sovereignty is the ability to run your loop, on your terms, against any model. When a global capability center in Bengaluru tunes two years of workflows to one foreign model, the moat being quietly exported is not one firm's. It is a national one.


08  /  The trajectoryWhat this becomes by 2030

Two numbers, taken together, define the risk window. The market is racing to deploy autonomous agents, and it is nowhere near ready to govern them.

The governance gap Intent to deploy far outruns the ability to govern Plan to deploy agentic AI within 2 years 74% Have a mature agent governance model 21% a 53-point readiness gap
Autonomous agents inherit credentials and act at machine speed, feeding the loop faster than any human could. Deploying them without owning the loop is how capture accelerates. Deloitte State of AI in the Enterprise 2026.

Follow the money, and the direction is unambiguous. The agentic and sovereign-AI markets are both being built to resolve this very tension.

Where the spend is going, 2026 to 2030 $8.5B2026 $45B2030 agentic AI market By 2030, sovereignty could shape 30–40% of all AI spend a $500–600B market, within $1.3–1.5T total.
Gartner projects 35 percent of countries will rely on region-specific AI platforms by 2027, up from 5 percent. The capital is relocating toward owned and sovereign environments. Deloitte / WEF (agentic); McKinsey (sovereign); Gartner (regional platforms), 2026.

Read together, these are not three trends. They are one: the market discovering, at scale, that it climbed onto the consumption rung of the AI Maturity Curve, and beginning to relocate capital toward the compounding rung, where the loop is owned. That relocation is the whole investment thesis of the next five years.

09  /  Five years outTwo enterprises in 2031

Extrapolate the two forces, capability converging and specificity compounding, and by 2031 the enterprise landscape has split in two. The dividing line is not size, sector, or which model a firm chose. It is the single decision made years earlier about where the loop would close. The same technology produces two opposite outcomes.

2031

The Captured Enterprise

  • Six years of prompts, evals, agent memory, and fine-tunes are welded to one provider. Migration now costs more than the original build.
  • The vendor holds full pricing power. In a downturn it raises rates and the firm cannot say no, because there is no working alternative.
  • A regulator asks for lineage it cannot produce, and its "AI advantage" turns out to be its supplier's advantage, rented back at a margin.
Its moat quietly became the vendor's moat.
2031

The Sovereign Enterprise

  • Models are interchangeable commodities routed underneath. When a cheaper or better one ships, it is a configuration change, not a project.
  • Evaluations, memory, and corrections are owned IP that compounds. Six years of judgment sit inside its own boundary.
  • Cost per unit of value falls as capability rises, lineage is provable on demand, and the firm, not the supplier, captures the compounding.
It used every model and kept what made it unique.

Both enterprises bought the same intelligence from the same vendors. The difference is entirely architectural, and it was decided long before it became visible on anyone's financials.

The serious risk

A silent transfer that is discovered only when it is too expensive to reverse

The danger is not a breach. It is irreversibility. Because asset specificity compounds, every enterprise has a closing window. Past a certain depth of single-provider tuning, the switching cost permanently exceeds the rebuild cost, and dependency becomes structural rather than commercial. The window closes quietly, with no alarm and no incident report.

At market scale the same mechanism concentrates the loops of much of the economy inside a handful of providers, Williamson's hold-up operating systemically. The serious risk is not that any single firm overpays. It is that an entire economy wakes up in 2031 to find the intelligence it built is owned, and priced, by someone else.

The solution

Own the loop before the window closes

The solution is not a better vendor, a stronger model, or a tighter contract. It is a deliberate architectural choice, made while switching cost is still low, to own the learning loop: treat models as interchangeable inputs, and treat your evaluations, memory, corrections, and orchestration as proprietary IP that lives inside a trust boundary you control.

The window is open today. It will not stay open, and the cost of the decision only rises. The two sections that follow turn that choice into a diagnostic and a discipline.

10  /  The diagnosticThe Second Payment Exposure Test

Concepts do not change behavior; diagnostics do. These are the six questions I put to technology leaders to locate an organization on the curve. None asks which model you use.

A CXO Intelligence diagnostic

Are you paying the second payment?

Score 1 point for every No. The paperwork being in order is not a Yes.

  1. Do you own a private evaluation set defining "good" for your top three AI workflows, independent of any provider?
  2. If your primary model were withdrawn tomorrow, could you run the same workflows on another within a week, against those same evals?
  3. Does your agent memory and correction history live inside a boundary you control, not a provider's tenant?
  4. Can you produce provable data lineage sufficient for DPDP, the EU AI Act, or your regulator?
  5. Is your orchestration layer decoupled from any single model, so routing is configuration, not a rebuild?
  6. Have you quantified your switching cost across model, data, and workflow, with a named owner tracking it?
5–6 · Owner
The loop closes on your side. Compounding works for you.
3–4 · Exposed
Partial control. The exponent is drifting. Act before year two.
0–2 · Captured
You are paying the Second Payment in full. Every month deepens it.

11  /  The responseThe trust boundary, in five disciplines

Arrow's paradox found its institutional answer in the patent, which let inventors disclose without surrendering. The Reverse Information Paradox needs an architectural equivalent, the trust boundary: a hard perimeter where an organization's evaluations, memory, traces, adapted weights, and institutional context accumulate and improve together, and where nothing, exhaust included, crosses without consent.

The reason the response is architectural rather than contractual is worth stating plainly. The loop runs on five assets: memory, evaluations, orchestration, retrieval, and the feedback path that turns corrections into improvements. Whoever owns those five owns the enterprise learning loop, regardless of which model executes underneath at any given moment. Models are the interchangeable part; the loop is the accumulating part. A contract can promise good behavior from the model layer. Only architecture decides who holds the accumulating layer, and that is the design brief the disciplines below execute.

Control

Own your memory, traces, feedback, and decisions. Build private evaluations; your evals define what good means inside your walls.

Capability

Build learning environments inside the tenant boundary, where models improve against real workflows without exposing what makes them valuable.

Choice

Decouple orchestration from any single model, and keep tuning model-agnostic so the asset stays portable in value, not just in bytes.

Cost

A decoupled layer lets you route context, model, and task in the most efficient combination, turning cost discipline into a capability.

Compound

Bring the four together and AI investment compounds the value of the firm, rather than the value of the firm's supplier.

None of this is all-or-nothing, and it should not be. Owning the loop is expensive, so spend the effort where it pays. Apply the full discipline to the handful of crown-jewel workflows that encode durable advantage, and rent freely for commodity tasks where switching cost is trivial. The test is simple: if a workflow accumulates judgment a competitor could never buy, the loop belongs inside your boundary. If it does not, let the market compete for your spend.

PA
Author's view
Prashant Akhawat

A principle needs an operating discipline

The trust boundary is the right principle, but a principle is not a control. It needs a repeatable discipline that turns "protect the loop" into decisions an architect and an auditor can both act on, giving every concern a named place and a named owner from strategic commitment through to operational evolution. This is the work of the AI-SAFE framework, which treats AI as enterprise substrate rather than a tool and maps directly onto the five disciplines above.

The layering is deliberate. The forthcoming book sets out the WHY, the reorganization of the firm around learning. The Cognition Stack describes the WHAT, the asset. AI-SAFE supplies the HOW. Nadella has given the market a vivid WHY. Enterprises still have to build the HOW.

Trust Ring · Value Ring
The operating framework

AI-SAFE V1.0

The AI Substrate Architecture Framework for Enterprises: six aspect areas crossed with six abstraction levels (Commit · Design · Compose · Deploy · Operate · Adapt), a 36-cell matrix wrapped in a Trust Ring of governance and a Value Ring of FinOps. It is the HOW layer that operationalizes the trust boundary and the five disciplines above.

Explore the AI-SAFE framework akhawat.com/ai-safe

The question every board should be asking

The Reverse Information Paradox is not an argument against buying intelligence. It is an argument for buying it on terms that let you keep what you create while using it. Once you separate Training Leakage from Loop Capture, the work becomes clear: the contract handles the first, but only architecture handles the second. The data shows the market already dividing into firms that own their loop and firms that merely rent more models. No firm should have to surrender the knowledge that makes it distinctive as the price of using intelligence; building that guarantee, deliberately and early, is the work of the moment. Nadella named the symptom. The mechanism is Loop Capture, and the remedy is ownership, decided while the window is still open.

The next decade will not be won by the company with the best model. It will be won by the company whose organizational learning compounds the fastest.

PA
About the author

Prashant Akhawat

Chief Technology and AI Officer at Ninestars, and a technology practitioner with over 25 years scaling enterprise platforms, the last decade spent turning AI into governed, production-scale capability for regulated industries across life sciences, pharmaceuticals, financial services, media, and government. The enterprise AI platform he leads serves 50+ organizations and is the subject of a published AWS case study: a 10x increase in scale, 60 percent lower total cost of ownership, and 99.7 percent SLA reliability. He is the creator of AI-SAFE V1.0, the AI Substrate Architecture Framework for Enterprises, and of the Cognition Stack; a keynote speaker at AWS Summit Bengaluru 2026 and AWS Summit Mumbai 2025; and has been featured in The Economic Times CIO and Mint. An alumnus of BITS Pilani and IMI Delhi, he is the author of a forthcoming book on AI as enterprise substrate and writes the CXO Intelligence Series at akhawat.com.

Keep reading

Read the full series

Every edition of the CXO Intelligence Series, all in one place.

All articles by Prashant Akhawat akhawat.com/writing
Stay current

Never miss an edition

Subscribe to the CXO Intelligence Series newsletter on LinkedIn.

Subscribe on LinkedIn linkedin.com/newsletters/cxo-intelligence-series