top of page
Won by becoming the single system of record every large enterprise's core financial and operational processes ran on, then defending that position for decades by making 'ripping out SAP' organizationally unthinkable.
1
MODEL
BUSINESS MODEL
SaaS, Platform Ecosystem, Holding Company
model bm
HOW THEY BUILT IT
- Built its dominance from the 1970s-90s on-premise ERP era, becoming the default backbone for finance, supply chain, HR, and manufacturing processes at the world's largest enterprises.
- Transitioned its core install base toward cloud (S/4HANA Cloud) over the past decade, converting decades of on-premise license and maintenance revenue into a recurring cloud subscription model without losing the underlying customer relationships.
- Grew via major acquisitions (Ariba for procurement, SuccessFactors for HR, Qualtrics for experience management, Signavio for process mining/IBP-adjacent capability) to broaden the platform without building every module from scratch.
- Positions its ecosystem of partners (implementation consultancies, ISVs building on SAP's platform) as a force multiplier, letting SAP capture platform economics from an entire industry of consultants who make their living implementing and customizing SAP.
HOW TO ARCHITECT IT
1) Become the system of record for a process too mission-critical to switch (core financials, supply chain), because that's where genuine multi-decade lock-in lives. 2) Convert your installed base to a recurring cloud model gradually rather than abruptly, preserving the deep customer relationships built over decades. 3) Acquire category leaders in adjacent enterprise functions rather than building each one slowly, using your existing customer base as instant distribution for the acquired product. 4) Cultivate a large implementation-partner ecosystem, because their livelihoods becoming tied to your platform turns your customer base's switching costs into an entire industry's incentive to keep you entrenched.
DISTRIBUTION MODEL
Enterprise Sales, Channel Sales, Partnership Distribution
dm
HOW THEY OPERATIONALIZED
- Enterprise, multi-year sales cycles led by direct account teams for the largest global customers, supplemented by a vast network of implementation and consulting partners (Accenture, Deloitte, IBM) for delivery at scale.
- Channel partnerships with regional resellers and systems integrators extend SAP's reach into mid-market and geographies its direct sales force can't cover cost-effectively.
- Builds and certifies an ISV ecosystem on top of its platform (SAP Store, Business Technology Platform) that extends functionality without SAP having to build every vertical-specific feature itself.
HOW TO REPLICATE WHAT WORKED
What worked: pairing the cloud migration of its core ERP (S/4HANA Cloud) with a genuine deadline (end-of-support dates for older on-premise versions) created forcing-function urgency for its installed base to upgrade, converting inertia into a scheduled, revenue-generating migration wave rather than an optional upsell.
The trap: decades of accumulated custom configurations and integrations at large customers make any SAP upgrade a genuinely difficult, expensive, multi-year project — a complexity SAP itself must manage carefully, because if migrations become painful enough, it opens a window for competitors (Workday, Oracle Cloud) to win greenfield or replacement deals during the transition.
| PATTERNS OF THIS MODEL
PATTERNS IN SYSTEM-OF-RECORD INCUMBENTS MIGRATING AN INSTALLED BASE:
1. OWN A PROCESS TOO CRITICAL TO SWITCH. Migration risk exceeding any efficiency gain is the only truly durable moat in enterprise software; everything else derives from it.
2. MIGRATE THE BASE GRADUALLY. A forced cutover invites the competitive re-evaluation a decade of lock-in was designed to prevent.
3. ACQUIRE CATEGORY LEADERS IN ADJACENT FUNCTIONS AND USE THE INSTALLED BASE AS DISTRIBUTION. The acquisition's value is your customer list, not their product.
4. A PARTNER ECOSYSTEM CONVERTS SWITCHING COSTS INTO AN INDUSTRY'S INCENTIVE. Entrenchment defended by people you do not employ is the cheapest defence there is.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — OWN A PROCESS TOO CRITICAL TO SWITCH.
Standard: rank ideas by who gets fired if the migration fails. Core financials generate multi-decade lock-in because the risk is existential, not expensive.
GOLDMINE 2 — MIGRATE THE BASE GRADUALLY.
Standard: a decade-long cloud conversion preserved relationships a forced cutover would have broken.
GOLDMINE 3 — MAKE PARTNERS' LIVELIHOODS DEPEND ON YOU.
Standard: an implementation industry converts customer switching costs into a sector's incentive to keep you entrenched. Strongest moat in the dataset; takes decades.
THE PIT — THE ECOSYSTEM THAT PROTECTS YOU DEFINES YOUR REPUTATION.
Buyers experience SAP through implementations they didn't choose the vendor for. You cannot control the experience your moat delivers.
THE SECOND PIT — ACQUIRED BREADTH SHOWS ITS SEAMS.
Ariba, SuccessFactors, Qualtrics arrived separately; customers feel it.
MOVE WITH CAUTION — INESCAPABLE LOCK-IN EVENTUALLY BECOMES POLITICAL.
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
MARKET TYPE
Mature Market
WHY THEY WON
Enterprise ERP is a mature, largely consolidated market where SAP, Oracle, and a handful of others have divided the largest global enterprises for decades. SAP's ongoing win in this mature market comes from deepening its entrenchment (cloud migration, acquisitions, ecosystem) at existing accounts rather than winning meaningfully new logos. Lesson: in a mature market you already dominate, growth increasingly comes from expanding wallet share and switching-cost depth at existing customers rather than net-new customer acquisition.
ENTRY STRATEGY
Greenfield Entry
EXECUTION
SAP's current growth strategy leans heavily on acquiring category leaders (Qualtrics, Signavio, Ariba, SuccessFactors) to enter adjacent enterprise software categories rather than building each new capability from scratch, evidenced by its continued M&A activity expanding into experience management and process intelligence.
FOOTHOLD STRATEGY
fs
Lighthouse Customer Strategy
SAP's original foothold was large German and European manufacturing conglomerates needing integrated financial and materials management software in the 1970s-80s, whose scale and credibility became the reference standard that pulled other large enterprises globally toward SAP as the 'safe choice' for mission-critical ERP.
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
Executive-level enterprise sales and account management reinforced by industry-specific solution marketing (SAP for retail, manufacturing, utilities), flagship annual events (SAP Sapphire) that showcase platform roadmap to existing customers and prospects, and cloud-migration campaigns tied to on-premise end-of-support timelines.
KEY LEARNING
If you dominate a mature enterprise category, use acquisition to expand into adjacent categories rather than slow organic build, since your existing customer relationships are instant distribution for acquired products. If your installed base resists migration to a new model, create genuine deadlines (end-of-support dates) rather than relying on the new model's merits alone to drive urgency.
gc
Market Context
| MARKET INTELLIGENCE
THE STANDARD: In a mature market you dominate, growth comes from deepening switching costs at existing accounts, not from new logos.
RULE 1 — THE INSTALLED BASE IS THE PRODUCT STRATEGY. Your roadmap's job is to make staying easier than leaving.
RULE 2 — ONLY A DEADLINE MOVES A MATURE INSTALLED BASE. End-of-maintenance dates drive more migration than any feature.
RULE 3 — THE INTEGRATOR ECOSYSTEM IS DISTRIBUTION AND INERTIA. They shape module selection before an RFP exists, and earn more from complexity than you do from licences.
RULE 4 — ADJACENCY IS THE GROWTH ENGINE. Procurement, HR, travel and analytics attach to the same customer; buying them is the pattern.
MARKET TYPE: Mature Market (enterprise ERP).
| MARKET ENTRY PLAYBOOK
THE STANDARD: FOR AN INCUMBENT SUITE, ACQUISITION IS NOT A TACTIC — IT IS THE ENTRY MECHANISM INTO EVERY ADJACENT CATEGORY, because building takes longer than the category's window.
RULE 1 — BUY THE CATEGORY LEADER, NOT THE CHEAP ASSET.
The established name brings customer base, category definition and talent at once. Discount acquisitions buy integration work.
RULE 2 — THE INSTALLED BASE IS THE SYNERGY AND THE LIMIT.
Cross-sell works for products the same buyer wants; it fails where the buying function differs.
RULE 3 — A SUITE CAN DIVEST AS FAST AS IT ACQUIRES.
Portfolio fit, not product performance, governs the outcome — a founder selling in should price that risk.
EVIDENCE: entered experience management, procurement, HCM, travel expense and process intelligence by acquisition (Ariba, SuccessFactors, Concur, Qualtrics, Signavio). Qualtrics bought for ~$8B in 2019, IPO'd 2021, sold to Silver Lake and CPP Investments in 2023 at ~$12.5B.
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: THE MOST DURABLE LIGHTHOUSE STRATEGY IS ONE WHERE YOUR REFERENCE CUSTOMERS ARE THE COMPANIES EVERY OTHER BUYER ALREADY BENCHMARKS AGAINST. Own the top of one industry in one country and the rest follows by imitation.
RULE 1 — START WITH THE MOST OPERATIONALLY COMPLEX BUYER IN A CONCENTRATED INDUSTRY. Large manufacturers had the hardest integration problem and the deepest pockets; solving for them produced a product that could be simplified downward but never the reverse.
RULE 2 — INTEGRATION ACROSS FUNCTIONS IS THE MOAT, NOT ANY SINGLE MODULE. Once finance, materials and production share one record, replacement means replacing the company's operating system.
RULE 3 — THE IMPLEMENTATION PARTNER ECOSYSTEM IS THE REAL DISTRIBUTION NETWORK. Consultancies whose practices depend on you will recommend you before any RFP exists — and that ecosystem, once built, is nearly impossible for a challenger to replicate.
RULE 4 — INCUMBENCY IN MISSION-CRITICAL SYSTEMS CONVERTS EVERY TECHNOLOGY SHIFT INTO A MIGRATION EVENT YOU CONTROL. The end-of-support date is the sales trigger.
EVIDENCE: SAP's original foothold was large German and European manufacturing conglomerates needing integrated financial and materials management in the 1970s–80s, whose scale made SAP the safe choice globally. It is publicly listed; consult current filings rather than any summary for figures, as the cloud transition materially changes reported growth.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
REVENUE MODEL
Subscription, Licensing Fees, Contract Revenue
PRICING MODEL
Tiered Pricing, Value-Based Pricing
WHY THEY WON
Revenue spans legacy on-premise license and annual maintenance fees (declining), growing cloud subscription revenue from S/4HANA Cloud and acquired SaaS products (SuccessFactors, Ariba, Qualtrics), and large, multi-year enterprise implementation/consulting contract revenue often delivered through partners.
Enterprise contracts are custom-quoted and tiered by user count, module scope, and deployment complexity rather than published list pricing, with cloud subscription pricing increasingly replacing the legacy perpetual-license-plus-maintenance model as customers migrate to S/4HANA Cloud.
TARGET AUDIENCE
CUSTOMER BUYING BEHAVIOUR
tg cb
Finance, supply chain, HR, and operations leaders at large global enterprises and increasingly mid-market companies needing integrated ERP
Highly considered, multi-year, committee-led procurement processes involving IT, finance, and executive leadership, often mediated through systems-integrator partners for implementation
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
THE STANDARD: When you are the system of record, your price is set by the cost of leaving, not the cost of alternatives. Every adjacent module is priced against a migration nobody will authorise.
RULE 1 — THE ERP IS PRICED ON REPLACEMENT RISK, WHICH IS EFFECTIVELY UNBOUNDED.
Ripping out finance, supply chain and HR simultaneously is a multi-year programme with career consequences. That is the real comparison, and it favours the incumbent absolutely.
RULE 2 — MAINTENANCE AND SUPPORT PERCENTAGES ARE THE ANNUITY, NOT THE LICENCE.
A recurring percentage of licence value produces decades of revenue from a single decision. Any perpetual-licence business without this line has under-monetised its installed base.
RULE 3 — MIGRATION DEADLINES ARE THE INDUSTRY'S MOST POWERFUL REPRICING INSTRUMENT.
End-of-support dates for legacy versions force customers into a new commercial model on the vendor's timetable. It is effective and it generates real customer resentment — budget for both.
RULE 4 — INDIRECT ACCESS AND LICENCE AUDITS ARE A REVENUE CHANNEL WITH A REPUTATIONAL COST.
Charging for system-to-system access surprises customers and generates litigation. Treat compliance revenue as borrowed against future goodwill.
RULE 5 — PARTNERS AND INTEGRATORS AMPLIFY YOUR PRICE AND DILUTE YOUR CONTROL.
Implementation frequently costs multiples of the licence. That total is what the buyer remembers.
THE WILLINGNESS-TO-PAY INSIGHT: An enterprise is not buying software — it is buying the avoidance of a transformation programme. Willingness to pay for incumbency is a function of disruption avoided, which is why the system of record can raise prices in ways no challenger can match.
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
A forced end-of-support deadline is the largest revenue event a legacy vendor can engineer and the widest door a competitor will ever get. Every customer must decide, and each decision is winnable by someone else.
Perpetual licence plus maintenance is front-loaded; the subscription transition is dilutive during the crossover regardless of outcome.
When system integrators own the migration conversation, the vendor is absent from its own most important sale.
Acquired SaaS assets age inside a suite while specialists compete unencumbered.
SAP's ECC deadline (2027, extended support to 2030) is the reference case. Verify current cloud backlog from filings.
Where the model can break
4
MOTION
GROWTH EXPANSION MODEL
COMPETITIVE STRATEGY
motion ge cs
Horizontal Expansion
HOW THEY EXPAND
SAP's core competitive posture is defensive — protecting its enormous installed base against cloud-native ERP and HR challengers (Workday, NetSuite) by deepening its own cloud offering and ecosystem lock-in rather than aggressively pursuing net-new greenfield accounts as its primary growth driver.
Defensive Strategy
HOW THEY COMPETE
SAP's core competitive posture is defensive — protecting its enormous installed base against cloud-native ERP and HR challengers (Workday, NetSuite) by deepening its own cloud offering and ecosystem lock-in rather than aggressively pursuing net-new greenfield accounts as its primary growth driver.
GROWTH ENGINE
GTM
ge n gtm
Partnership Growth, Platform Integrations
Every implementation partner (Accenture, Deloitte) whose consultants are trained and certified on SAP has a direct financial incentive to keep recommending SAP for new engagements, and every ISV building on SAP's Business Technology Platform extends SAP's functional footprint without SAP building it — the loop compounds as more of the enterprise-software services industry's revenue becomes tied to SAP's continued dominance, though it can weaken if a rival platform builds a comparably large partner ecosystem.
Enterprise account-based sales and executive relationship management reinforced by a vast global implementation-partner ecosystem, flagship industry events, and cloud-migration campaigns tied to on-premise support deadlines that create structured upgrade urgency.
SUSTAINING MOATS
Switching Costs, High Customer Lock-In, Brand Power, Technology Advantage (complex enterprise scenarios)
moat
Every additional year of custom configuration, integration, and institutional process knowledge built around SAP at a large enterprise raises the cost and risk of switching, and the sheer size of SAP's certified implementation-partner ecosystem creates a self-reinforcing industry-wide incentive to keep recommending and maintaining SAP rather than displacing it.
| MOAT INTELLIGENCE
THE STANDARD: The deepest enterprise moat is a migration deadline the vendor sets. When support for the legacy system expires, every customer must move — and the incumbent decides where.
RULE 1 — END-OF-SUPPORT DATES ARE THE MOST POWERFUL COMMERCIAL INSTRUMENT IN ENTERPRISE SOFTWARE. They convert a discretionary upgrade into a board-level programme with a fixed date, forcing a re-decision at a moment the incumbent has prepared for and competitors have not.
RULE 2 — THE PARTNER ECOSYSTEM IS DISTRIBUTION YOU DO NOT PAY FOR. Global integrators with tens of thousands of certified consultants recommend the platform their staffing model depends on. Competitors cannot buy that quickly at any price.
RULE 3 — MIGRATION IS ALSO THE MOMENT OF MAXIMUM VULNERABILITY. A customer already rebuilding is the only one genuinely willing to evaluate alternatives. Forced migrations create revenue and the largest competitive opening the incumbent will ever offer.
RULE 4 — BUYING ADJACENT CAPABILITY REMOVES INDEPENDENT COMPETITORS FROM THE BOARD. SAP's acquisition of WalkMe took the largest standalone digital adoption vendor off the market, changing the competitive set for everyone remaining.
EVIDENCE:
- Largest enterprise application vendor by installed base — ERP, SuccessFactors, Ariba, Concur, analytics and supply chain — driving customers from legacy ECC to S/4HANA.
- I DID NOT VERIFY SAP'S CURRENT CLOUD BACKLOG, REVENUE, MIGRATION COMPLETION RATES OR SUPPORT DEADLINE EXTENSIONS. These move quarterly and are reported inconsistently in secondary sources; take them from SAP's own quarterly statement.
- SAP completed its acquisition of WalkMe in 2024, absorbing the digital adoption category leader.
THE SIGNAL: if your business depends on customers migrating, you control the timing and you concentrate all churn risk into that window. Incumbents win most forced migrations — and lose more accounts during them than in all other periods combined.
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M — OWN THE PROCESS, NOT THE FEATURE
Not a startup case. The founding lesson still holds: standardise a business process across an industry and the software becomes the definition of how work is done.
Consultants and trained staff are the moat, not the code.
$1–5M — LET IMPLEMENTERS BUILD CAREERS ON YOU
A partner ecosystem whose livelihood depends on your product is the most durable distribution in enterprise software.
$5–10M — SELL TO THE BOARD, DELIVER TO THE PROCESS OWNER
Enterprise process software is a transformation purchase; the sponsor is always above the user.
$10–50M — MODULARISE SO EVERY DEPARTMENT IS AN EXPANSION
Finance, HR, procurement, supply chain on one data model. Cross-sell inside the account beats new logos permanently.
$50–100M — BUY THE CATEGORY YOU CANNOT BUILD
SAP's cloud portfolio is substantially acquired — SuccessFactors, Concur, Qualtrics, Taulia, WalkMe. Integration burden is the true price.
Rule: at scale, M&A is product strategy, not an admission of failure.
$100M+ — MANAGE THE MIGRATION, NOT THE ROADMAP
The hard problem is moving an installed base off perpetual licences onto cloud subscriptions without losing them; deadlines and incentives, not features, drive it.
Verify current revenue and cloud-backlog figures in SAP's filings; any number quoted here dates within a quarter.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: An end-of-support date is the strongest forcing function in enterprise software — it converts inertia into a scheduled migration. It only works with genuine lock-in.
SEQUENCE:
1. Publish a hard sunset for the legacy product so the conversation becomes their risk, not your roadmap.
2. Ship new capability only on the new platform.
3. Use the migration to strip years of accumulated customisation.
WORKED: A vast installed base converted into a predictable, multi-year revenue wave.
CAUTION:
1. EVERY FORCED MIGRATION IS A COMPETITOR'S OPENING. A painful upgrade is the one moment a locked-in customer will evaluate alternatives.
2. THE CUSTOMISATION THAT WON THE ACCOUNT IS THE LIABILITY THAT MAKES THE UPGRADE EXPENSIVE.
3. WITHOUT REAL ENTRENCHMENT, A DEADLINE JUST LOSES CUSTOMERS.
bottom of page