Software Growth

Switching costs

Switching costs are the money, time, effort and risk a customer faces when they leave one product for another, and they protect SaaS revenue.

Switching costs are everything a customer gives up by changing from your product to a competitor's. That includes direct fees, but for software it is mostly time: moving data, rebuilding workflows, retraining staff and risking mistakes during the move. High switching costs keep customers from leaving even when a rival is slightly better, which makes them one of the most reliable parts of a moat.

Types of switching costs in software

Matt Rickard lists six kinds that explain why enterprise software retains customers despite complaints about it (Matt Rickard):

  • Data gravity: moving your data costs money and manual work.
  • Integration surface area: the more and deeper the integrations, the harder to replace the product.
  • Proprietary APIs: interfaces competitors cannot match, as with Stripe and Twilio.
  • Identity systems: user credentials and permissions tied to many other apps.
  • UI and workflow familiarity: trained users and muscle memory.
  • Bundling: more products used from one vendor, shortening sales cycles and adding stickiness.

Hamilton Helmer treats switching costs as one of his seven sources of durable power in 7 Powers, and Rickard recommends the book for its dedicated chapter on the topic.

A way to think about a customer's decision

A customer rationally switches when the gain from the new tool outweighs the cost of moving, and you can estimate how long it takes to pay off:

Say a customer pays you $50 a month and a rival charges $30. Migration would take 20 hours of staff time valued at $50 an hour, or $1,000.

That is more than four years. Few will bother, unless the rival is far better. This is why a small price gap alone rarely moves customers, and why founders who undercut an incumbent by 20 percent are often disappointed.

Why it matters for your numbers

Switching costs show up in churn rate and net revenue retention. Products that store important data, run daily workflows and connect to other tools tend to keep customers longer than standalone tools. When you decide what to build, ask which features make the product more embedded: integrations, history and reports that grow with time, team settings, and templates the customer has customized.

Good lock-in versus bad lock-in

Raising switching costs by making the product more useful is sound. Raising them by blocking data export is hostile, and it creates resentment: customers who feel trapped leave the moment an alternative appears, and leave reviews on the way out. This is the difference between healthy stickiness and vendor lock-in. Offering a clean export is itself a trust signal, and it costs you little if the product is good.

A flip side for new entrants

If you are the challenger, you need to lower the incumbent's switching cost: offer free migration, import tools, API-compatible formats and a parallel-run period. Many tools win their first customers by making the move take an hour instead of a week.

Sources

Back to the SaaS glossary