Switching Costs Power
Lock in customers so that the cost of leaving exceeds the benefit of any alternative
Switching Costs arise when a consumer values compatibility across multiple purchases from a specific firm over time. The Benefit is the ability to charge higher prices for follow-on products because competitors must compensate customers for the full cost of switching. The Barrier is the unattractive cost/benefit of share gains for challengers -- they must effectively subsidize the entire switching cost to lure customers away.
Helmer uses SAP's enterprise resource planning software as his primary case. Despite abysmal customer satisfaction -- 43% unhappy with response times, 50% unable to predict performance -- 89% of SAP customers planned to continue paying annual maintenance fees. The explanation lies in the enormous switching costs: financial (buying new software and complementary applications), procedural (retraining employees across HR, sales, procurement, and accounting), and relational (breaking established bonds with service teams). When HP migrated to SAP, even with careful preparation, 20% of orders stalled, causing a $160M hit.
Switching Costs are non-exclusive: all players can enjoy their benefits. SAP, Oracle, and IBM all benefit from high customer retention. The key competitive position element is binary -- you either have the customer or you do not. This makes the takeoff stage critical, as that is when customers are first acquired before the price competition that eventually arbitrages out the value of new customer acquisition.
- Switching Costs arise from the value customers place on compatibility across multiple purchases over time
- Three categories: Financial (transparent monetary costs), Procedural (loss of familiarity, retraining, risk), and Relational (broken emotional bonds with service teams and user communities)
- The Benefit only applies to follow-on sales to existing customers -- there is no advantage with potential new customers
- Switching Costs are non-exclusive: all competitors can build them, so the race is to acquire customers first
- Product portfolio expansion amplifies all three types of Switching Costs simultaneously
- Tectonic technology shifts can sweep away Switching Costs advantages -- SAP and Oracle race to prevent cloud leapfrogging
- Design deep integration into customer workflows from the startBuild your product to become embedded in multiple functions within the customer's organization. SAP touches HR, sales, procurement, accounting, and manufacturing. The deeper the integration, the more procedural switching costs accumulate as employees learn the system and build their workflows around it.
- Acquire customers during the takeoff phase before price arbitrage sets inSwitching Costs only benefit you if you have the customer. During takeoff, customers are eager to find any supplier and haven't yet internalized the lifetime value of their choice. Once the market matures, all players understand customer value and compete aggressively for new acquisitions, arbitraging out the benefit. Win customers early.
- Build a portfolio of complementary products and add-on servicesExpand your product line through both internal development and acquisitions. SAP built an enormous portfolio of offerings and made numerous acquisitions to extend coverage. More products means more financial switching costs, more procedural retraining, and deeper relational bonds -- amplifying all three switching cost categories simultaneously.
- Create data gravity and proprietary formats where appropriateApple's iTunes used proprietary formats so that switching meant forfeiting prior purchases. When customers accumulate years of data, customizations, and integrations on your platform, the migration cost compounds. Ensure your product accumulates customer-specific value that cannot be easily exported.
SAP dominates enterprise resource planning despite chronic customer dissatisfaction. A Compuware study found 43% of 588 SAP customers were unhappy with response times and 50% felt unable to predict performance. Yet 89% planned to continue paying maintenance fees. When HP attempted a SAP migration, even with a senior VP who had overseen five prior migrations and three weeks of extra preparation, 20% of customer orders stalled during the transition, costing HP $160M. The combination of financial, procedural, and relational switching costs creates an inescapable lock-in.
Helmer uses two cases: SAP's enterprise software and Apple's iTunes ecosystem. SAP's paradox of high retention with low satisfaction perfectly illustrates Switching Costs Power. The HP migration disaster -- in which a carefully planned SAP implementation caused 20% of customer orders to stall, resulting in a $160M financial hit -- demonstrates why customers stay locked in despite dissatisfaction. The cost and risk of switching is simply too high to justify.