What vendor lock-in really means once AI runs the stack

I sat in on a renewal call last quarter where a CFO asked her head of AI a simple question. If this vendor doubled its price tomorrow, how fast could we leave? The room went quiet. Not because the answer was bad. Because nobody actually knew.

That silence is the real story of AI vendor lock-in in 2026, and it has almost nothing to do with the contract that took three weeks to negotiate.

The myth goes like this: lock-in is a legal problem. Beat it with a good exit clause, a data-portability paragraph, and a model that swaps out. Pick the open one, keep the data in a store the company controls, and the risk is handled.

Vendor lock-in stopped being the contract you signed

Give the myth credit, because for twenty years it was exactly right. The classic Oracle or SAP trap was the migration project and the license terms. Escape was a legal and data-export problem, so a sharp procurement lead could contain it with the right paragraph.

And right now the whole market is selling that same cure. Anthropic donated the Model Context Protocol to the Linux Foundation, so the plumbing between agents and tools is turning into a neutral standard. AI gateways promise routing between OpenAI, Anthropic, and Google without rewriting a line. Gartner expects 70% of companies building multi-model apps to run a gateway by 2028, up from under 5% in 2024. So it feels handled. If the protocol is standard and the model is swappable, where is the trap?

The trap is that the model was never the expensive part to leave.

What 1,000 executives admitted about their own stack

IBM’s Institute for Business Value ran this down with Oxford Economics, and the sample is serious: 1,000 senior executives across 16 countries and 17 industries, at companies from $260M to $92B in revenue. It published in June. The headline finding is not that switching costs money. It is that most companies cannot see what they would be switching away from.

Read that again. Nine in ten leadership teams cannot fully map what their AI actually depends on. And it follows that 71% said switching their primary vendor or model would be difficult today, while 81% said a seven-day outage at a primary vendor would be severe or critical, effectively halting operations. The average company had already absorbed six AI-related disruptions in two years, most of them traced back to a vendor.

Here is the part that should change how a budget review sounds. The companies with the most control across their AI stack protected 55% more operating profit from those disruptions than the companies with the least. That is not a governance nicety. That is EBIT.

The other tells line up. IBM found 73% of companies call their AI setup intentionally multi-vendor, but the top reasons were independent business-unit decisions and geographic necessity, both at 69%, not a deliberate portability strategy. That is multi-vendor by accident wearing a strategy costume. TechInformed, covering the same study, flagged a quieter penalty: companies pay 2.8 times more in token processing when data placement is misaligned with where the model runs, roughly $50M a year for a $20B enterprise. And a VaaSBlock analysis in late June made the accumulation visible, describing enterprises stacking switching costs across four vendors at once, Microsoft, Salesforce, ServiceNow, and AWS, with no method to measure the total.

None of this is a fringe reading. A separate Zapier survey of 542 executives found only 6% could drop their main AI vendor without disruption, and of the two-thirds who had actually attempted a migration, 58% said it failed outright or cost far more than expected. Two independent studies, same direction.

Where the lock-in actually lives now

The switchable layer is getting cheaper by the month. Model weights, the protocol, the API call, all commoditizing on schedule. The sticky layer is everything built around them, and it migrated to three places.

The first is where the data sits. Misplace it against the model and the bill climbs 2.8x before anyone changes a single feature. The second is the behavior tuned into one model: the prompts, the fine-tunes, the eval suite, the quirks a team learned to work with. The third is the workflow scaffolding wrapped around the agent, the connectors and approval steps and downstream systems that assume this vendor’s shape. Swap the model and none of that moves.

The model is the one part of an AI stack a team can actually replace. The lock-in is everything wrapped around it.

So the exit clause protects the wrong thing. It governs the layer that was already going to be portable, and stays silent on the data, behavior, and scaffolding that carry the real cost. That is why control and visibility, not contract language, are what showed up in the profit numbers.

How to price a switch before the CFO has to ask

Here is the calming part, because this is figure-out-able and it does not need a portability project this quarter. It needs one honest afternoon.

Pick the single most AI-dependent workflow and answer the CFO’s question for that one alone. If this vendor doubled its price, what exactly gets rebuilt, and how long does it take? Most teams find the model swap is the easy 10% and the data placement and workflow rewiring is the other 90%. Write that number down. That is the real switching cost, and it is the one figure the 91% cannot produce on request.

Then decide, on purpose, where lock-in is worth accepting and where an exit stays open. Multi-vendor by design beats multi-vendor by accident every time. The goal was never zero dependency, which is a fantasy anyway. It was dependency chosen with eyes open, priced honestly, and survivable for a week if a vendor goes dark.

The companies protecting that extra 55% of profit are not the ones with the cleverest contracts. They are the ones who could answer the CFO in the room without the silence.