Frameworks / The Exit Multiple
Staying is priced. Leaving is guessed. The Exit Multiple puts them on the same footing.
Every AI deployment arrives with a price for staying: inference run-rate, licences, support. It has a budget line and a quarterly review. The price of leaving has no line. It gets assembled when the question becomes real, in a hurry, by whoever is asked, from functions that have never added their numbers together.
The Exit Multiple is one ratio, per workload: total cost to leave divided by annual AI run-rate. Read it as the years of running cost you would spend to get out. The ratio matters more than either number, because it compares workloads and vendors on one scale, and because it moves. A multiple that climbs quarter after quarter is a dependency accruing in plain sight.
Five ledgers, five owners
The top of the ratio is not one number. It is five, and each sits with a different part of the organisation.
- Architecture: what must be rebuilt. Pipelines, integrations, orchestration. Engineering owns it.
- Context: what must be regenerated or re-earned. Embeddings, fine-tunes, retrieval logic, evaluation history, agent scaffolding. This is the Context Layer, and almost nobody governs it.
- Organisation: what people must relearn. Skills, processes and approvals that formed around one platform. The operating model owns it.
- Contract: what leaving triggers. Commitments, notice periods, penalties, data return. Procurement and legal own it.
- Sovereignty: what jurisdiction requires. Where the workload may run, under whose law, with whose regulator’s approval. Risk owns it.
A multiple is measured. A tolerance is chosen.
Once leaving has a number, the number starts to sound like an answer. It is not one. Two organisations can hold the same multiple and be right to disagree about it: one is buying speed with open eyes, the other answers to a regulator or a board that will not accept it. The arithmetic is identical. The tolerance is not.
Tooling will increasingly keep the multiple current, draw the bands and flag the drift. Where the line belongs turns on what the organisation is for, what speed is worth to it, and what it could survive losing. That stays with whoever signs the renewal.
How to see it in the field
The tell is a board question about leaving that turns into a project. If nobody can produce even a rough exit cost for the workload that matters most, the multiple exists but has never been read. A second tell is a single precise figure: a leader who quotes the exit cost to one decimal place is claiming a precision nobody in the building has. A third is a regulatory change being read as the cost of leaving falling, when it has removed one line from one ledger and left the other four untouched.
Keeping it honest
Estimate in ranges, not points. The width of the range is information too: it tells you which ledger to examine first. Then treat the tolerance as a conviction with a review date. Set it, record who set it, and revisit it when the multiple, the vendor or the regulation moves. The multiple applies to every option, including a private stack on your own floor, where hardware, skills and context bind just as surely. It is not an argument for leaving anywhere. It is how you tell whether the dependency you hold is a position or a liability.
Part of the Frameworks series. First argued in Staying is priced. Leaving is guessed. Builds on the Context Layer; related to the Workload Sovereignty Matrix.