Switching Costs Are the Quietest Moat and Often the Strongest
A competitor can build a better product and still lose, because the customer has to pay to leave. That cost is rarely the price, and it is usually not written down anywhere.
Why Better Products Lose
The standard assumption is that a superior product wins. It frequently does not, and the reason is that the comparison a customer actually faces is not product against product.
It is the new product, minus the cost of moving, against the incumbent. If moving costs enough, the challenger has to be better by more than that margin before switching is rational.
An incumbent does not need to be as good as the challenger. It needs to be within the switching cost of as good, and that gap can be very wide.
What the Cost Is Made Of
| Type | What it looks like |
|---|---|
| Learning | Staff know the current system, retraining takes months |
| Data | History lives in the incumbent, migration is risky and lossy |
| Process | Workflows built around how the tool behaves |
| Integration | Other systems connect to it, each one has to be rebuilt |
| Contractual | Termination terms, remaining licence periods |
| Risk | Migration might fail, and someone owns that decision |
Only the contractual line has a number attached. The rest are real and unbudgeted, which is why they are underestimated by challengers and felt acutely by buyers.
The Risk Component Is Underrated
The last row often dominates. Switching a core system is a project that can fail visibly, and the person who authorised it owns that failure personally.
Staying with an adequate incumbent carries no such exposure. This produces a strong asymmetry: the upside of a successful migration is diffuse and shared, the downside is concentrated on one career.
That is why enterprise buyers accept products they complain about continuously. The complaints are genuine and switching is still not worth the personal risk.
How Companies Deepen It
Switching costs can be engineered, and most enterprise software strategy is exactly that.
Adding adjacent modules means leaving requires replacing several things at once. Encouraging integrations multiplies the number of connections that break. Storing more customer history makes migration lossier. Certifying administrators creates a trained population with a stake in the current system.
None of this makes the core product better. All of it raises the bar a competitor must clear.
Where It Is Weak
Switching costs are low where the product is standalone, holds little history, and touches nothing else. Consumer applications with no stored data and no integrations have almost none, which is why consumer software markets turn over so much faster than enterprise ones.
They also erode when a technology shift resets the comparison. If the whole category has to be replaced anyway, the incumbent advantage evaporates, because the customer is paying the migration cost regardless. Platform transitions are when long dominant positions actually change hands.
Reading It in Financials
High switching costs leave traces. Gross retention stays high even when the product is not obviously best in class. Pricing power persists, with annual uplifts customers accept while complaining. Sales cycles are long, because the buyer knows the decision is hard to reverse.
The clearest signal is a company that raises prices repeatedly and loses very few customers. That combination is difficult to explain any other way, and it is worth more than most claimed moats.
The Bottom Line
Switching costs let an incumbent keep customers it could not win today, because the customer compares the alternative net of disruption, retraining, integration work and personal career risk. Most of that cost never appears on an invoice, which is why challengers consistently underestimate it. Watch for high retention combined with sustained price increases, and watch for platform shifts, which are when the moat briefly drains.