Enterprise software pricing concessions, switching costs, and exit leverage

Research Question

How do enterprise software vendors use upfront pricing concessions to increase switching costs over contract lifecycles, and what abstraction or architectural investment strategies demonstrably reduce total cost of ownership (TCO) by preserving exit leverage?

Findings

Executive Summary

Enterprise software vendors systematically use upfront pricing concessions to build installed bases, then exploit accumulated switching costs at renewal through maintenance-fee escalation, egress charges, and proprietary integration dependencies. The Competition and Markets Authority (CMA) 2025 final decision confirmed fewer than 1% annual switching rates in UK cloud infrastructure and identified egress fees and technical lock-in as the primary commercial barriers. Software licensing represents only 20-30% of enterprise software TCO over a five-to-ten year lifecycle; migration, integration, and support costs account for the remaining 70-80%, explaining why sourcing decisions based on headline pricing structurally underestimate lock-in exposure. Regulatory interventions (EU Data Act, CMA Strategic Market Status process) confirm that market forces alone are insufficient to correct the pricing distortions created by high switching costs, and mandate vendor-side changes including egress fee elimination by 2027. Architectural investments in open standards, container portability, and portable data models reduce the technical floor of switching costs, making exit threats credible and improving bargaining position at renewal even before regulatory obligations take effect.

Key Findings

1. The theoretical model of two-period pricing in switching-cost markets predicts that vendors set below-cost initial prices to build installed bases and recoup profit through higher installed-base prices at renewal, a prediction corroborated by the sub-1% annual switching rates documented by the CMA and by documented maintenance-fee structures.

2. The CMA 2025 final decision found that fewer than 1% of enterprise cloud customers switch cloud infrastructure providers annually in the United Kingdom, attributing this low rate to egress fees, lack of interoperability, and technical lock-in as the primary commercial barriers that depress competitive pressure on incumbents.

3. Microsoft and Amazon Web Services (AWS) each hold approximately 30-40% of UK cloud infrastructure spend, and the CMA estimated that even a 5% overcharge due to reduced competition would cost UK organisations approximately £500 million in additional annual expenditure on a total cloud spend base of £10.5 billion.

4. Software licensing typically represents only 20-30% of the lifecycle TCO of enterprise software such as an Enterprise Resource Planning (ERP) platform; implementation, migration, integration maintenance, and support costs account for 70-80%, and organisations relying on vendor-quoted licensing prices underestimate true TCO by 40-60%.

5. Direct enterprise switching costs including data extraction, process redesign, integration re-platforming, and productivity loss during transition are estimated at 25-50% of the original platform investment, making exit threats non-credible at renewal unless the cost differential with the incumbent is large enough to justify that expenditure.

6. The EU Data Act (Regulation (EU) 2023/2854), applicable from September 2025, mandates that cloud and data-processing service providers reduce switching fees to cost-based levels by end 2026 and eliminate them entirely by January 2027, providing a legislated floor for commercial exit rights for EU-based enterprise customers.

7. EU Data Act Article 25 requires provider contracts to include 30-calendar-day portability windows, maximum two-month notice periods, 30-day data-retrieval minimums, and exit-strategy support obligations, establishing contractual switching rights that apply to all new and existing contracts from September 2025.

8. The Cloud Native Computing Foundation (CNCF) cloud-native approach using container orchestration and declarative Application Programming Interfaces (APIs) reduces the technical component of switching costs by decoupling workloads from provider-specific infrastructure, but does not address commercial lock-in created by data model dependencies or proprietary managed-service integrations.

9. Enterprises that invest in documented migration playbooks, portable data exports, open-standards-based integrations, and staff capability on alternative platforms can make credible exit threats that discipline incumbent pricing at renewal, because the vendor cannot reliably assume that switching is operationally infeasible within the contract notice period.

10. Williamson's asset-specificity concept from transaction cost economics explains why switching costs compound over the contract lifecycle: each additional customisation or integration built on vendor-proprietary infrastructure raises relationship-specific investment and increases the vendor's hold-up leverage at every subsequent renewal.

Assumptions

• Two-period pricing model maps to multi-year enterprise contracts: the Klemperer/Farrell model uses a two-period structure, but enterprise contracts run over multiple renewal cycles. The assumption is that the first-period discount logic extends to multi-period settings because each renewal cycle re-applies the installed-base pricing logic. Justification: this is consistent with the empirical observation of escalating maintenance fees over time.

• The 20-30% / 70-80% TCO split is an order-of-magnitude estimate. Exact figures depend on platform complexity, depth of customisation, and organisational size. Justification: multiple independent industry practitioner sources converge on this order of magnitude.

• Architectural portability investment reduces total exit costs: reducing technical switching costs (via open standards, containers) creates a credible exit option even when commercial costs remain. Justification: switching-cost theory predicts that credibility depends on total switching cost being below a threshold; reducing the technical component brings total cost closer to that threshold.

Analysis

The upfront-discount-to-lock-in dynamic is a rational equilibrium in any market where switching costs are high, predictable, and accumulate post-onboarding. Farrell and Klemperer's model predicts that, from a social welfare perspective, such markets can be competitive in total (vendors compete for new customers), but the welfare is distributed unfavourably: the discounts go to new customers who have not yet been locked in, while the incumbents recoup the investment from existing customers who cannot credibly exit.

CMA evidence from the 2025 final decision confirms the theoretical prediction quantitatively in a specific, well-documented market (UK cloud infrastructure). A sub-1% annual switching rate is consistent with the theoretical prediction of near-zero switching in high-switching-cost markets, and the CMA's estimate of £500M additional cost at 5% overcharge provides a concrete scale of the welfare distortion.

TCO distribution evidence (20-30% licensing, 70-80% lifecycle) is supported by consistent industry practitioner estimates rather than peer-reviewed academic literature. Post-onboarding costs accumulate as lock-in deepens, so the specific numbers should be treated as indicative rather than precise.

Architectural interventions (CNCF cloud-native, open APIs, portable data models) address the technical layer of switching costs but not the commercial layer. Enterprises operating under EU Data Act obligations have a regulatory backstop that reduces commercial exit costs over time, but for enterprises outside EU/UK regulatory scope or using non-cloud enterprise software categories, the architectural investment path is the primary available mechanism.

Preserving exit leverage requires investment before lock-in accumulates across three areas: architectural (open standards, containers, portable data models), contractual (explicit portability clauses, exit-strategy obligations, and data-retrieval rights negotiated at signing), and regulatory (EU Data Act and CMA oversight where jurisdiction applies). Architectural investment reduces the technical cost floor; contractual terms codify the operational preconditions for switching; regulatory rules set a minimum enforceable standard. The most durable posture combines all three because commercial and technical switching costs are partially independent.

Network effects (the tendency of platform value to increase with user count) are a complementary mechanism in cloud markets: the Farrell and Klemperer paper explicitly models both switching costs and network effects as sources of installed-base pricing power. In cloud infrastructure, network effects manifest through ecosystem depth (availability of compatible third-party tools and integrations) rather than direct user-to-user value. This item focuses on switching costs because they are the primary mechanism targeted by the EU Data Act and CMA investigation, and because architectural portability strategies directly address switching costs but do not reduce network-effect-driven advantages. Network effects are therefore out of scope for the architectural intervention recommendations but are relevant context for understanding why cloud market concentration may persist even after switching costs are reduced.

Risks, Gaps, and Uncertainties

• ERP TCO figures lack a peer-reviewed empirical study. The 20-30% / 70-80% split and the 25-50% switching cost estimate are drawn from industry practitioner sources; a systematic academic survey would provide stronger evidence.
• CMA cloud findings may not generalise to other enterprise software categories. The CMA investigation was specifically scoped to cloud infrastructure (IaaS and PaaS). Switching cost dynamics for SaaS platforms, horizontal ERP, or enterprise collaboration tools may differ in composition and magnitude.
• EU Data Act effects are not yet observable. The regulation entered application in September 2025; empirical evidence on vendor compliance, actual switching behaviour changes, and any offsetting fee strategies by providers is not yet available.
• Portability investment return on investment (ROI) is not empirically quantified. No study was identified that directly measures the improvement in renewal pricing outcomes achieved by enterprises that invested in architectural portability; this remains a theoretically grounded but empirically unquantified claim.
• The NBER URL in the seeded Sources was incorrect. The seeded URL (www.nber.org resolves to a different paper by Banerjee, Iyer, and Somanathan. The Farrell and Klemperer paper is accessible at the CEPR (Farrell and Klemperer (2007) Coordination and Lock-In: Competition with Switching Costs and Network Effects and at Berkeley (eml.berkeley.edu This error was corrected in the Sources section.

Open Questions

• Does the upfront-discount-to-lock-in pattern differ between on-premises ERP, cloud SaaS platforms, and cloud infrastructure? Are switching cost compositions consistent across these categories?
• What is the empirically measurable effect of maintaining architectural portability (open APIs, containerisation, portable data models) on negotiated pricing improvements at renewal?
• How will cloud providers respond to EU Data Act switching-fee elimination? Will they offset eliminated egress fees through other pricing mechanisms such as premium API access or proprietary service bundles?
• Should enterprises in non-EU jurisdictions invest in meeting EU Data Act contract standards voluntarily (before any regulatory obligation) as a mechanism for accelerating the reduction of commercial exit costs?

Output

• Type: knowledge
• Description: This item establishes that the upfront-discount-to-lock-in sequence in enterprise software markets is theoretically predicted by switching-cost economics and empirically confirmed by regulator investigations, and that preserving exit leverage requires a combination of architectural investment (portable data, open standards, container portability), contractual negotiation (explicit portability clauses before lock-in accumulates), and regulatory reliance where available (EU Data Act, UK CMA oversight).
• Key sources: Farrell and Klemperer (2007) Coordination and Lock-In: Competition with Switching Costs and Network Effects UK Competition and Markets Authority (CMA) Cloud Services Market Investigation Final Decision (2025) European Union Data Act (Regulation (EU) 2023/2854)

sources

• Farrell and Klemperer (2007) Coordination and Lock-In: Competition with Switching Costs and Network Effects. Economics foundation for switching-cost lock-in mechanisms. Source correction: the seeded URL www.nber.org resolves to a different paper (Banerjee, Iyer, and Somanathan on public goods); replaced with the CEPR discussion paper for the same Farrell/Klemperer work.
• Klemperer (1987) Markets with Consumer Switching Costs. Classic model of switching-cost competition dynamics.
• UK Competition and Markets Authority (CMA) Cloud Services Market Investigation Final Decision (2025). Contemporary regulator evidence on enterprise switching barriers in cloud infrastructure.
• European Union Data Act (Regulation (EU) 2023/2854). Policy intervention focused on cloud and data-processing service switching and portability.
• EU Data Act Article 25 (contractual terms for switching). Primary legal text on switching rights and fee restrictions.
• Cloud Native Computing Foundation (CNCF) Cloud Native Definition v1.1. Architecture principles frequently cited as reducing platform lock-in risk.
• ERP Research: Total Cost of Ownership Calculator and Guide. Practitioner-facing TCO framework for Enterprise Resource Planning lifecycle cost estimation.
• Arion ERP: Beyond the Sticker Price, unpacking the true TCO for ERP systems. Industry analysis of ERP cost distribution across licence, implementation, migration, and support.