Thirteen essays into this series, the line has never moved: the layer you don't own is the layer that owns you. I've named distribution (#45), the model (#46), identity (#47), access (#48), the harness (#49), the meter (#50), the runtime (#51), the data (#52), accountability (#53), the rail (#54), the router (#55), the consolidator (#56), and the licence (#57).
Every one of those essays was really about the same question in disguise: how hard would it be to leave? Today I want to name that question as its own layer, because the cost of exit is not a side effect of the other layers. It is manufactured, priced, and defended — and it is the quietest thing you don't own.
The headline that made me write this
New York City's "Click to Cancel" rule went into effect (337 points on HN). Read what that means literally: a government had to legislate that a service you signed up for in one click must also be cancellable in roughly one click. Nobody passed a law for a feature. They passed a law because the exit had been quietly engineered to cost more than the entrance — and everyone in the industry knew it.
Look at the same day's board and the pattern hardens. Nitter, the free Twitter front-end that thousands of people had come to rely on, posted an update seeking funding and legal help (416 pts) — a tool that had become infrastructure, begging to survive against a platform that could strangle it at the API. And the third Yandex Cloud data center was hit (549 pts), a reminder that "the cloud" is a handful of buildings and your redundancy is only as real as your second location.
Three unrelated stories, one layer. Leaving is a layer.
Why exit is its own layer
Exit cost looks like an inconvenience. It is actually the most honest measure of who holds power in a relationship, because it is the one number both sides price carefully and only one side talks about.
- Data gravity. Your data is heavy. It lives in their schema, their ids, their history. Export is always possible and almost never sufficient — what comes out is never what you put in, and the difference is the toll.
- Integration gravity. You didn't adopt a product, you wired it into eleven others. The integration is the lock. Each webhook and sync you add raises the price of the door by a little.
- Social gravity. You can leave alone; your team, your vendors, and your customers leave with you or not at all. Coordination is the real switching cost, and it scales with headcount.
- Institutional gravity. Procurement, security review, training, and the sunk-cost story you've told your board all push toward staying. The most expensive part of leaving is often the apology.
The tell: friction is asymmetric by default
Entry is free and instant by design; exit is slow and manual by default. That asymmetry is not an accident of the tools — it is the business model. Retention is cheaper to build than acquisition, so the pull of every product is toward making the door harder to find, not the room nicer to be in. When regulators show up, they don't demand a better product. They demand a working door.
And here is the uncomfortable part you already know: you cannot read exit cost off a pricing page. It lives in the export format, the contract's notice period, the support thread you haven't needed yet, and the number of systems that would blink red if you pulled the plug. Those are the things that decide what leaving really costs.
What to actually do
- Measure your exit cost while you're happy. A spreadsheet: what data, in what format, how long to migrate, who else has to move, what breaks for how many days. An exit cost you've never measured isn't a low one.
- Prefer vendors whose door is priced in. A clean, documented export API is a mechanism. "Contact your account manager to discuss data portability" is a mood. Buy the mechanism.
- Keep the escape hatch warm. Sole-source nothing that matters. Have a second rail, a second region, a fork path, a running export. Redundancy you've never tested is a story you tell your board.
- Diversify your dependencies before you need to. If one platform's API change can delete a tool you rely on — the Nitter lesson — spread the load now, at your convenience, not during the incident.
- Price the exit into anything long-lived. For infra you'll run for five years, "easy to leave" is a hypothesis. Budget the migration as a scheduled cost, not an emergency.
The one-line version
Exit cost is a layer because it sits above every other layer and decides what all of them are worth to you. You can own your data, run your own runtime, hold your own licence — and still be stuck, because the door was never really open. The layer you don't own is the layer that owns you, and the exit is the layer that decides whether "own" was ever a choice you could exercise.
Top comments (0)