switching cost

Switching cost is everything a customer loses by moving to a competitor, and it is rarely money. It is time spent migrating data, risk of something breaking during the move, and the retraining of habits a team has built over months. A product can be objectively worse and still keep 90 percent of its customers if switching cost is high enough.

Enterprise software lives on this. Salesforce customers do not stay because Salesforce has the best interface in 2024. They stay because five years of custom fields, integrations, and trained staff make leaving a multi month project with real failure risk. That project cost, not the product quality, is the retention engine.

Consumer products have switching cost too, just smaller. Changing your primary email address means updating logins on dozens of sites. Gmail does not need to be the best inbox forever. It needs the cost of leaving to stay higher than the annoyance of staying.

Founders often try to build switching cost through lock in, like proprietary file formats or punitive contract terms. This works short term and creates long term resentment, and it shows up publicly, in reviews and in churn spikes the moment a viable alternative appears with a migration tool. Slack lost enterprise deals to Microsoft Teams partly because Teams bundled with Office, lowering the switching cost in the other direction.

The more durable version of switching cost comes from genuine accumulated value, like a decade of financial history in Mint or years of design files in Figma, not from making the exit door hard to find. Customers forgive the first kind. They punish the second kind on the way out and tell everyone why.