Leadership in the Age of AI

Your whole AI stack now runs on one vendor. What happens when you want to leave?

Thomas Green 28 August 2026 5 min read
Key points
  • Standardising your whole AI stack on a single vendor is fast to start and expensive to leave. Lock-in now builds up across several layers at once: the model, the orchestration that connects your workflows, your data, your governance records and your team's know-how. The cost of switching does not add up. It multiplies.
  • Portability is bargaining power. The ability to move keeps your pricing power, your negotiating position and your freedom to adopt something better later.
  • The fastest-growing lock-in is not the model. It is the orchestration layer that wires AI into how your business runs, which is far harder to unpick than swapping one model for another.
  • The most capable buyers are already hedging. Large firms are signing deals with more than one AI provider on purpose, to keep their options open.
  • Built for portability, your AI stack keeps you in control of your costs, your data and your direction.

You standardised on one AI provider, and it was the right call at the time. One vendor, one contract, one way of doing things, and you moved fast while everyone else was still deciding. Then, a year on, you notice something. The provider's prices firmed up and you took it. A better model launched elsewhere and you could not really move. Quietly, without a decision being made, your options narrowed. The speed you bought early has turned into a dependence you did not choose.

This is worth understanding before it hardens further, because it is still fixable. Lock-in is rarely a single decision you can point to. It accumulates, layer by layer, until leaving feels impossible and the vendor knows it. The good news is that portability is a choice you can design in, and the bargaining power it buys you is real and lasting. It is really a question of how you adopt AI, which is exactly where most organisations go wrong.

Why is AI lock-in worse than the software lock-in you know?

Because it stacks in more places at once. With traditional software, the switching cost was mostly the data and the retraining. With AI it builds across several layers at once. There is the model itself, the orchestration that connects AI into your workflows, the data you have fed it, the records that prove your governance, and the working knowledge your team has built around one vendor. Each layer alone is a cost. Together they multiply, because unpicking one means touching all the others.

The layer that catches leaders out is orchestration. As you move from a few isolated AI uses to connected workflows where AI hands work between steps, that connective layer becomes the core of how your business runs. It is far harder to leave than a simple model subscription, because it is wired into your operations. This is the same lesson behind treating your own knowledge and architecture, not a single vendor's tool, as the real advantage.

AI lock-in is rarely one decision. It accumulates layer by layer until leaving feels impossible and the vendor knows it. Portability is the bargaining power you design in early.
Where AI lock-in accumulatesDetail
The layers that bind you to a vendormodel, orchestration, data, governance records, team know-how
How the switching cost behavesmultiplicative, not additive across those layers
Fastest-growing lock-in in 2026the orchestration layer wired into your workflows
What mature buyers are doingsigning with more than one provider on purpose (e.g. ServiceNow with both OpenAI and Anthropic, Jan 2026)

What does keeping your options open actually look like?

It looks like the moves the most capable buyers are already making. Large enterprises are deliberately working with more than one AI provider rather than betting everything on one. ServiceNow signed deals with both OpenAI and Anthropic in early 2026, and other major firms have taken the same multi-provider path, treating optionality itself as a feature worth paying for. They are not being indecisive. They are keeping their pricing power and their freedom to adopt the next better thing.

The lower-altitude question is which AI vendor is best, as though you must pick one and commit. The better question is how to build so that no single vendor owns your future. That means keeping a clean separation between the layer that runs your workflows and the specific model underneath, so you can change the model without rebuilding the business around it. It is the same discipline as playing your own game with AI rather than the game a vendor sets for you.

So how do you build for portability?

You design the freedom to move in from the start, rather than trying to buy it back later at a premium. The aim is to capture the speed of a single vendor without surrendering your bargaining power. Work it in this order:

  1. Separate your workflows from the model. Keep the layer that runs your business loosely coupled to any one provider's model, so you can swap the model without rebuilding everything around it.
  2. Keep your data yours. Hold your data and its structure in a form you own and can export, not locked inside a vendor's format.
  3. Use more than one provider where it counts. For your most important workflows, keep a credible second option live, so the ability to move is real rather than theoretical.
  4. Price the exit before you sign. Ask what leaving would actually take at every renewal. If nobody can answer, the lock-in is already deeper than you think.
  5. Own the know-how. Make sure your team understands the workflow, not just one vendor's buttons, so the capability stays with you.

Building an AI stack that keeps you in control?

The Strategy Session works on the architecture of your AI programme: capturing the speed of adoption while keeping your pricing power, your data and your freedom to move. We design portability in, so your bargaining power stays with you.

Book your Strategy Session

What does this make possible?

An AI programme that serves you rather than the other way round. When portability is built in, you keep the upside of moving fast without the trap that usually follows. Your costs stay under pressure because the vendor knows you can leave. A better model arriving becomes an opportunity, not a source of regret. Your data and your direction stay in your hands. That is a far stronger footing than a dependence you did not choose and cannot easily undo.

Picture the next renewal. Instead of accepting whatever terms arrive because leaving is unthinkable, you negotiate from a real alternative, and the conversation changes entirely. When a stronger model launches, you adopt it in weeks rather than wishing you could. You bought the speed of AI early and kept your freedom too, because you designed for it. That combination, momentum without dependence, is what separates the businesses that command their AI future from the ones quietly handing it away.

Frequently asked questions

What is AI vendor lock-in?
It is the growing difficulty and cost of leaving a single AI provider once your business depends on it. Unlike older software lock-in, it accumulates across several layers at once: the model, the orchestration wired into your workflows, your data, your governance records, and your team's know-how. Because those layers interlock, the cost of switching multiplies rather than simply adding up.
Why is orchestration lock-in the biggest risk?
Because the orchestration layer connects AI into how your business actually runs, handing work between steps and systems. As you move from isolated AI uses to connected workflows, that layer becomes the operational core, which is far harder to unpick than swapping one model for another. It is the fastest-growing form of AI dependency, and the one leaders most often miss.
How do you avoid AI vendor lock-in?
Keep the layer that runs your workflows loosely coupled to any single model. Hold your data in a form you own and can export. Keep a credible second provider live for your most important workflows. Ask what leaving would take before every renewal, and make sure your team owns the workflow rather than one vendor's interface. The goal is to keep the speed while keeping the freedom to move.
Thomas Green

About the author

Thomas Green

British technology futurist, AI keynote speaker and advisor. Thirty years across enterprise technology and AI strategy, helping leaders navigate the future of work. The futurist who died.

Get Thomas’ thinking into your inbox

Thoughts, stories and ideas on AI, leadership, and the future of work.