SAP Didn't Expand Into the Cloud. It Bought Its Way In, at a 52% Premium.

On a Saturday in December 2011, SAP agreed to pay $40.00 a share for a company whose stock had closed the previous day around $26 — a 52% premium for a cloud HR firm called SuccessFactors, worth roughly $3.4 billion in enterprise value.³ Five months later it paid a 20% premium for Ariba, an e-procurement network.⁴ Two years after that, another 20% premium for Concur, the travel-and-expense company, at about $8.3 billion.⁵ Three deals, over $16 billion, every one done above the asking price the market had set. SAP wasn't bargain-hunting. It was paying whatever it took.

The official story is that this was a cloud strategy — a deliberate march into adjacent enterprise software. It was really a confession. SAP had built the most entrenched on-premise business software on earth and discovered, around 2010, that the same dominance gave it almost no head start in the cloud. So it stopped building and started buying. The premiums weren't a strategic flourish. They were the toll an incumbent pays when its moat doesn't extend into the next territory.

For forty years, SAP expanded by building

Five IBM engineers founded SAP in 1972 to write standard enterprise software for real-time data processing.¹ What followed was textbook organic adjacency. The first product handled financial accounting. Then R/2, in 1979, pushed into materials management and production planning. Then R/3, in 1992, established the client-server ERP standard that the world's large companies ran their operations on.⁸ Each step was a logical extension built in-house, and each one reinforced the same moat: once a company runs its accounting, inventory, and production on SAP, ripping it out is unthinkable. By 2003 the company was so global it employed more people outside Germany than inside it — 17,000 to 13,000.⁸ For four decades, the pattern was invent, install, lock in, repeat.

Then the ground moved. Software stopped being something you bought and installed and became something you rented over the internet. The new entrants — SuccessFactors in HR, Ariba in procurement, Concur in expenses — were born in the cloud, sold by subscription, and updated continuously. SAP's great strength, the deep on-premise installation, was suddenly the thing customers wanted to escape. The moat held the existing castle perfectly. It just didn't reach the new land.

Why the incumbent had to buy instead of build

Here is the mechanism most coverage skips. SAP's incumbency was a moat with a ceiling. The same architecture, sales motion, and on-premise mindset that made it dominant also made it slow to ship cloud-native products customers would actually switch to — and in a subscription market, the company that signs the contract first holds the customer for years. SAP couldn't out-build firms that had a half-decade head start and no legacy code to drag along. It could only out-spend them. A 52% premium for SuccessFactors isn't a price for a company; it's a price for time SAP could not manufacture itself. Buying the market leader was the only way to arrive in the adjacency already at scale rather than years behind.

Notice the language of the deals. SuccessFactors was bought to 'accelerate' the cloud strategy.³ Concur was framed as expanding the 'world's largest business network.'⁵ Acceleration is the word you use when you're behind. The pattern across all three is the same: not a company entering an adjacency from a position of strength, but one closing a gap with its checkbook because the clock was running and the moat wouldn't carry it across.

But it worked — so wasn't the premium worth it?

The fair objection is that this critique is sour about a strategy that plainly succeeded. Look at the numbers: in FY2024 SAP reported €34.18 billion in total revenue, with cloud revenue of €17.14 billion, up 25%, and a total cloud backlog of €63.3 billion.⁶ The cloud, which barely existed for SAP in 2010, is now its growth engine — and the year before, FY2023 cloud revenue had already grown 20% on a €13.7 billion current backlog.⁷ If overpaying by a few billion in 2011–2014 bought a business now generating €17 billion a year, that is one of the better trades in enterprise software. Premiums look expensive only until the asset compounds.

True — and it concedes the real point rather than refuting it. The cloud business is real and large, but SAP did not grow it from its ERP roots the way it grew R/2 and R/3 from financial accounting. It purchased it, fully formed, from companies that did the building. The premium proves the thesis instead of disproving it: an incumbent that could have extended its own moat into the cloud would not have needed to pay 52% over market to rent someone else's. Success at the cash register doesn't change where the engine was made. SAP's ERP dominance was a fortress, not a launch pad — and the bill for that distinction came to over $16 billion.

SAP spent its first forty years proving that a great enterprise platform expands by building outward from its core. It spent three years from 2011 to 2014 proving the limit of that idea. When the market shifted to the cloud, the most entrenched business software company on earth discovered that entrenchment doesn't travel. So it wrote checks — 52%, 20%, 20% over market — and bought the future it couldn't ship. The cloud revenue is real today. But the lesson is sharper than the success: incumbency is a wall, and a wall is wonderful for defending what you have and nearly useless for reaching what's next. SAP learned the difference at over $16 billion, premiums included.