Switching costs

Why It Matters

Switching costs create a moat by making it painful for customers to leave. The higher the switching costs, the more defensible your revenue.

Investors look for products that become more embedded over time, with more data stored, more integrations built, and more team workflows dependent on the tool.

Types of Switching Costs

Data lock-in comes from historical data, configurations, and customizations that are hard to migrate. Workflow dependencies come from team processes and automations built around the product. Integration costs come from connections to other tools that would need to be rebuilt. Learning costs come from the time it takes to retrain a team on a new tool. Contractual costs come from annual contracts, volume commitments, and negotiated pricing.

Worked Example

Switching a CRM involves data migration that takes 8 to 12 hours of engineering time, a rebuild of more than 40 automations, two weeks of reduced productivity while the team retrains, and reconnecting five integrated tools. The total implicit cost often runs $20,000 to $50,000 or more for a mid-market company, which is exactly the friction that keeps a customer in place.

Common Mistakes

Relying on artificial lock-in, such as making data export deliberately hard, which breeds resentment and bad reviews. Confusing low churn with high switching costs, since some products have low churn simply because they are cheap or forgotten rather than because switching is genuinely hard. Not building switching costs intentionally, when they work best as a natural byproduct of delivering value rather than an afterthought bolted on later.

How to Show It in Your Pitch Deck

On your moat slide, list the specific switching costs your product creates, with data on how they grow over time such as integrations per customer or data volume. Example line: an average of 12 integrations per customer, 18 months of historical data, and more than 40 team workflows built on the product.

Related Terms