Switching Cost

Origin & evolution

The idea entered strategy through Michael Porter, who treated switching costs as one of the forces shaping industry competition and a barrier that protects incumbents. The rigorous economics came from Paul Klemperer, whose Markets with Consumer Switching Costs (Quarterly Journal of Economics, 1987) showed that even small switching costs can soften competition, because once customers are locked in, a market with switching costs can produce outcomes🏆OutcomeStrategyA desired business or user outcomeView reference → that resemble collusion in a market without them. Firms compete hard up front to capture customers they can later exploit.

Klemperer extended the analysis over the following decade, and he and Joseph Farrell synthesised the field in Coordination and Lock-In: Competition with Switching Costs and Network Effects, the chapter in the Handbook of Industrial Organization🏙️OrganizationPortfolioThe top-level organisational entityView reference →. The central result reframed how strategists read cheap introductory offers and price wars. A firm that prices below cost to acquire a customer is buying future market power over that same buyer, the power to charge above the competitive level once the customer is locked in. Penetration pricing and switching costs are two halves of one move.

Practitioners later sorted switching costs into types. Procedural costs are the time and effort of migrating: exporting data, reconfiguring, retraining a team. Financial costs are the money lost, such as a forfeited prepayment, a new contract, or sunk investment in the old product. Relational costs are the human ties broken, the trusted contact, the community, the accumulated reputation inside a platform. Each type can be designed up to deepen lock-in, and each is where the ethical question gets pointed.

How it works in practice

A team has used a project tool for three years. The subscription🔂SubscriptionSales & RevenueA recurring subscriptionView reference → is £15,000 a year, and a rival offers the same features⭐FeatureProduct SpecificationA product capability or featureView reference → for £9,000. The headline saving is £6,000 a year, so the move looks obvious until the switching costs are counted. Procedural: two months of migrating 40,000 tasks☑️TaskProduct SpecificationA unit of work within a story or epicView reference →, rebuilding 200 automations, and retraining 60 people, work that pulls senior time away from delivery. Financial: a year already prepaid, and three months of running both tools in parallel. Relational: a body of institutional knowledge encoded in the old tool's structure that does not export cleanly.

Add it up and the first-year cost of switching swamps the saving, so the team stays. The incumbent keeps a customer it might lose on a clean comparison. The honest version of this advantage comes from a product so embedded in real work that leaving genuinely costs something. The hostile version manufactures the friction: broken data export, contracts that auto-renew on a hidden date, formats that lock data in. The first is a moat the customer would defend. The second is a trap the customer resents, and resentment finds an exit eventually, often through a regulator who mandates data portability.

Switching Cost vs. its neighbours

• Competitor🥊CompetitorMarket IntelligenceA competing product or companyView reference → is the destination a switching cost makes expensive to reach. The cost is the height of the wall between a customer and the alternative. A competitor with a better product still loses if the wall is high enough, which is why incumbents invest in raising it.
• Value Proposition✨Value PropositionBusiness ModelA unique value offered to customersView reference → is the reason a customer chooses you in the first place; switching costs are why they stay after a rival matches that reason. A business that relies on switching costs to retain customers a competitor has out-built is living on borrowed time, because the friction decays as migration tools improve.
• Persona🎭PersonaUserAn archetype representing a user segmentView reference → is who actually bears the cost. The same switch is cheap for a solo user with little to migrate and punishing for an enterprise admin with thousands of records and dozens of integrations. Switching cost is never a single number; it is specific to the person standing at the exit.

In the graph

In the Unified Product Graph, Switching Cost sits in the users region and connects through persona_incurs_switching_costPersonaincursSwitching Costhierarchy, which fixes the cost to the specific person who pays it. That placement carries the argument Klemperer's economics implies: a switching cost is experienced by someone, and it differs by who is leaving and what they have built up. Modelling it on the persona keeps the analysis honest. It lets a team ask whether a given persona's lock-in comes from genuine embedding in their work or from friction the product manufactured, the question that decides whether a moat is an asset or a liability waiting for a regulator.