Switching Costs

1. Definition

Switching Costs exist when a customer who would otherwise prefer a competing product stays with the incumbent because the cost of leaving exceeds the value of the alternative. The benefit is durable revenue at price levels above what a perfectly contestable market would clear. The barrier is that the challenger must compensate the customer for the switching cost — in cash, services, or time — before the customer will even evaluate the alternative on its merits.

Klemperer's 1987 economics paper formalized three distinct flavors that behave differently and respond to different attacks: procedural (the customer's staff must be retrained, processes redesigned), financial (cash outlay for migration, sunk integration costs, contractual penalties), and relational (vendor trust, escalation paths, the rolodex of who-to-call-when-something-breaks). Most products have all three; the dominant flavor determines the defense.

2. Historical deployers

• SAP and Oracle ERP — financial + procedural at industrial strength. Mid-market migrations off either platform run $5–50M per Gartner benchmarks; large-enterprise migrations cross $100M. Customers stay until the system literally cannot do what the business needs.
• Bloomberg Terminals — procedural + relational. Traders learn the keystrokes once and the pattern is permanent; the data and the function-key memory together are why $24,000-per-seat per year survives every attempted disruption.
• Intuit QuickBooks — relational + procedural at SMB scale. The accountant referral channel is itself a switching cost — the customer can leave QuickBooks, but their accountant works in it.

3. The load-bearing assumption

Switching Costs require the cost of leaving to exceed the discounted value of the alternative, calculated honestly by the customer. That arithmetic depends on three sub-assumptions: the cost of leaving is real (not just inertia), the alternative is genuinely better (or the moat is feature parity, not switching), and migration tooling does not collapse the cost. When any of those breaks, the moat thins fast.

The deeper assumption is that the switching cost is paid by the same party that captures the value of staying. When the buyer (CIO) pays the migration cost but the user (employee) gets the value of switching, the moat is structurally unstable — the parties' incentives are misaligned, and the buyer eventually pushes back.

4. How it's deployed and won

1. Identify which flavor you are running. Procedural switching costs respond to retraining tooling; financial to migration discounts; relational to channel competition. A defender who confuses procedural for relational fights the wrong attacker.
2. Embed during onboarding. The deepest switching costs are the ones the customer pays for unconsciously — configuration, integrations, customizations — in the first year of use. The vendor builds the cost into the product surface.
3. Multiply the integration surface. Each additional connector, custom field, or workflow tied to your system raises the migration cost faster than linear. SAP's real moat is the third-party ecosystem of consultants who built the customizations.
4. Bind the relational layer. Make the vendor staff who own the customer relationship economically locked to your platform — through certification, partnership tiers, and exclusive features.
5. Resist data portability standards — or, if forced, ensure they expose only the data, not the workflow logic that uses the data.

5. Classical failure modes

• Migration tooling. A challenger ships purpose-built migration assistants that collapse procedural switching cost to days. Salesforce did this to Siebel; later, Workday did it to PeopleSoft.
• Bridge integrations. The challenger maintains compatibility with the incumbent's integrations, letting customers run side-by-side until the parallel migration completes.
• Generational replacement. The customer doesn't migrate; the customer's replacement (new CIO, new business unit, acquisition) brings the new platform with them. Switching cost is reset by org change.
• Forced data portability. Regulation (GDPR data portability; PSD2 banking) makes the data leg of switching free, leaving only the procedural and relational legs.
• Re-bundling. A platform that owns the layer above (Microsoft 365, Salesforce, ServiceNow) absorbs the workflow into its bundle, reducing the standalone product to a component the customer was already paying for.

Visual: the three flavors of switching cost

Cross-references

Switching Costs are the moat most often paired with Process Power (chapter 07) — the customer's organizational know-how about how to use your product is itself a switching cost — and with Cornered Resource (ch. 06) when the resource is exclusive integration rights. The hardest defender confusion is with Network Economies (ch. 02): a single user's difficulty leaving (switching) versus the value lost when many users leave together (network).