The Anatomy of Lock-In

Lock-in is rarely a clause you signed. It is a condition you arrive at: the point where staying with software you have outgrown is cheaper than leaving it. Both you and the vendor know it. That gap, between what you would pay to go and what you will tolerate to stay, is not an accident. It is the product.

Charlie Munger put the principle plainly:

“Show me the incentive and I’ll show you the outcome.”

The vendor’s incentive is your switching cost. So it is built to grow.

The five mechanisms

Lock-in is assembled from parts and they are the same parts everywhere.

Data gravity. Years of your records live inside the system. The more there is, the harder it is to move. The export, when you ask for it, comes in a shape designed to be technically compliant and practically useless.

Proprietary formats. Your workflows, automations and configurations are expressed in the vendor’s private language. None of it ports. Leaving means rebuilding logic you already paid to define once.

Integration sprawl. Over time the platform becomes the hub a dozen other tools plug into. Each integration is a thread; together they are a net. You are no longer switching one tool, you are unpicking a system.

Retraining. Your team’s competence is muscle memory in this interface. A switch resets that to zero. The fear of the productivity dip is itself a cost the vendor never has to mention.

Contract structure. Multi-year terms, auto-renewals and price escalators that activate precisely when the other four mechanisms have made you unable to walk. The increase you would have fought in year one, you will absorb in year four.

The asymmetry

Notice what each mechanism has in common: it costs the vendor almost nothing to build and costs you dearly to escape. That asymmetry is the entire game. A useful question to ask of any platform is not “how good is it?” but “what happens the day I want to leave?” The honest answer is usually engineered before you ask it.

This is not villainy; it is incentive. A subscription business is rewarded for retention and the cheapest retention is the kind you cannot refuse. Munger’s rule again: the outcome follows the incentive, whatever anyone intends.

Ownership is the exit

The antidote isn’t a better vendor. It is a different structure. When software is fit-built and handed over (code, data, infrastructure and documentation in your hands), none of the five mechanisms can form. The data is already yours, in your store. The logic is in source you hold. There is no licence to escalate and no renewal to be trapped by. Leaving, staying or changing direction becomes a decision you make on the merits, not a ransom you calculate.

That is the quiet argument under everything we build: ownership isn’t about controlling the technology for its own sake. It is about keeping the option to change your mind.

Before you sign

You can read the anatomy of a future lock-in in the contract in front of you. Ask three questions before signing any platform your business will come to depend on: In what format can I export all my data and how usable is it? Who owns the customisations and configurations I pay to build? What does the exit clause actually cost me? If the answers are vague, that vagueness is the point. It is a five-year cost you are agreeing to now.

A two-week Fit Assessment reads your stack for the lock-in already forming and prices the cost of staying against the cost of owning.