From ByDesign to GROW
Edition 5 - Nineteen years of selling public-cloud ERP: ByDesign's quiet delisting (20 Apr 2026), five refused modification trade-offs, and why 2027 finall
Unfiltered: SAP Public Cloud — Edition 5
Executive thesis SAP has been selling public-cloud ERP since 2007. Business ByDesign arrived two years late, never found its market, and is being delisted for new customers in 2026. S/4HANA arrived in 2015, but for most of a decade the cloud editions were the smaller half of the story. Only with GROW in 2023 did public cloud get a motion of its own — and only now, with the 2027 deadline closing, is it the default question rather than an optional one. The pattern across all nineteen years is the same: SAP kept betting on standardisation, and the market kept paying for flexibility. That tension has not been resolved. It has been moved.
On 20 April 2026, SAP removes Business ByDesign from the price list for new customers.
Existing customers keep their support. There was no farewell keynote. For a product launched in 2007 as SAP’s answer to the cloud, it is a very quiet ending.
It is also a good moment to ask a question that gets skipped in every migration workshop: how did we actually get here? Not the roadmap version. The version with the false starts in it.
Because if you are deciding between Public and Private Cloud this quarter, you are not choosing between two products. You are choosing a position in a nineteen-year argument that SAP has been having with its own installed base.
2003–2006 · The architecture promise
What SAP said: mySAP ERP, then Enterprise Services Architecture. Break the monolith into services. NetWeaver becomes the platform. Composition replaces modification.
What happened: The vocabulary landed. The architecture largely did not. Customers kept customising in ABAP because that is what worked, what their people knew, and what the business asked for on Friday afternoon.
The verdict: instructive. This is the first appearance of a pattern that repeats for two decades — SAP proposes standardisation as an architectural principle; customers accept it as a slide and decline it as a practice.
2007 · Business ByDesign — the first cloud ERP
What SAP said: Complete, integrated ERP on demand for mid-sized companies. No infrastructure. A genuine bet, and an early one — this was two years before most enterprise vendors took SaaS seriously at all.
What happened: It shipped roughly two years behind plan, and adoption came in far below expectation. The architecture was of its time and did not age into modern cloud standards. It was inconsistently marketed for most of its life.
The verdict: ugly, but honourable. ByDesign was not a bad idea. It was an early idea, executed against an architecture and a market that were not ready. The mistake worth learning from is not that SAP built it — it is that SAP never fully decided whether to back it or bury it, and spent a decade doing neither.
2010–2014 · HANA, the shopping spree, and “Run Simple”
What SAP said: In-memory changes everything. Then: cloud is where the growth is — SuccessFactors, Ariba, Fieldglass, Concur, bought in rapid succession. Then, in 2014, the brand promise: Run Simple.
What happened: HANA was real and consequential. The acquisitions bought genuine cloud revenue and genuine cloud capability, mostly in line-of-business rather than core ERP. “Run Simple” became one of the most quoted taglines in enterprise software, frequently by people pointing at an SAP landscape that was anything but.
The verdict: good — with a credibility cost. The technology bets were sound. But promising simplicity to an installed base living with twenty years of accumulated complexity created a gap between message and experience that SAP is still paying for. Every Clean Core conversation today happens in the shadow of it.
2015 · S/4HANA — the re-platforming
What SAP said: A new suite, rebuilt on HANA. Simplified data model. Fiori. The successor to ECC.
What happened: The on-premise and private editions carried the adoption. Public-cloud editions existed from early on but remained the smaller path for most of the decade — narrower functional scope, tighter extensibility, and a customer base whose entire operating model assumed the ability to modify.
The verdict: the right product, an unresolved question. S/4HANA settled the technology question and left the operating model question open. That question is the one you are still answering today.
2016–2019 · Leonardo and the Intelligent Enterprise
What SAP said: Leonardo — IoT, machine learning, blockchain, analytics, bundled as an innovation brand. Then the Intelligent Enterprise. Then Qualtrics, and experience data as the missing half of operational data.
What happened: Leonardo was quietly de-emphasised and folded away. The Intelligent Enterprise survived as a framing. Qualtrics was bought for around $8bn, IPO’d, and sold again in 2023.
The verdict: the bad. Not because the technologies were wrong — most of them are now embedded and useful — but because this era taught a generation of SAP customers to treat strategic branding as weather. That scepticism is now aimed at Business AI, whether or not it deserves it.
2021 · RISE — transformation as a subscription
What SAP said: One contract. Infrastructure, licence and services bundled. Choose your hyperscaler; SAP runs it. Business transformation as a service.
What happened: RISE became the dominant motion for existing large customers — largely private cloud, and largely a commercial and operating-model change rather than an architectural one. Many customers moved with their complexity intact.
The verdict: good commercially, ambiguous architecturally. RISE solved the question of who runs it. It did not, by itself, answer what should be standardised. A lift-and-shift into RISE is entirely possible, and common.
2023 · GROW — public cloud finally gets its own motion
What SAP said: GROW with SAP. Public-cloud ERP as true SaaS, with a fit-to-standard implementation approach, aimed first at midmarket and new customers.
What happened: For the first time, public cloud had a named motion, a partner model and an implementation method built around standardisation instead of around modification. Clean Core stopped being architectural advice and became a commercial precondition.
The verdict: the good. Sixteen years after ByDesign, SAP shipped a public-cloud ERP proposition the market could actually buy. That is the genuinely important development of the last five years, and it gets less attention than any AI announcement.
2025–2026 · Business AI, Business Data Cloud, Autonomous Enterprise
What SAP said: AI embedded across the suite. Business Data Cloud as the governed knowledge core. At Sapphire 2026, BTP, BDC and Business AI brought together as the SAP Business AI Platform, with the Knowledge Graph at its centre. The Autonomous Enterprise as the destination.
What happened: Commercially it is working — Q2 2026 showed €22.9bn current cloud backlog, up 27%, with management stating AI and Business Data Cloud were key pillars in more than 90% of the fifty largest deals. Externally, scepticism about delivery pace persists; UBS downgraded the stock in August 2026 on exactly that question.
The verdict: too early, and that is the honest answer. The strategy is coherent. The delivery record for strategic brands from this company is mixed. Both things are true.
The pattern, in three lines
Read across nineteen years and three things repeat.
One — SAP has always been right about direction and early about timing. Services architecture in 2004, cloud ERP in 2007, in-memory in 2010, AI-in-the-suite in 2024. The direction has generally been correct. The market arrived years after the announcement, every time.
Two — every strategy has asked customers to give up modification, and customers have mostly declined. ESA, ByDesign, S/4HANA public cloud, Clean Core, fit-to-standard. Same request, five times, different vocabulary. The only thing that has materially changed customer behaviour is not persuasion. It is the 2027 deadline.
Three — the branding cycle has cost SAP more credibility than any technical failure. Run Simple, Leonardo, Intelligent Enterprise. Customers now discount strategic announcements by default, which makes it harder for SAP when a genuinely important shift — like GROW — actually arrives.
What this means for the decision on your desk
Do not treat Public Cloud as a new question. It is a nineteen-year-old question that has finally become answerable, because the product is finally credible and the deadline finally forces it. That is a better position than SAP has ever been in — and a worse position for you, because your optionality is shrinking while the choice gets harder.
Judge the delivery record, not the announcement. The reasonable posture on Business AI and Business Data Cloud is neither belief nor dismissal. It is: what is generally available today, on what evidence, and what is my plan if it lands two years later than promised? That question has a good historical basis.
And understand that fit-to-standard is the same request SAP has been making since 2004 — only now it is enforced by the commercial model rather than recommended in an architecture guideline. That is why it is finally working. It is also why it deserves a harder look than “the vendor says so.”
Which leads to the question I put in the last edition of Executive Clarity, and will keep asking: if standardisation is what finally made SAP’s cloud work, what does standardisation do to the reason SAP was hard to replace in the first place?
Nineteen years to sell a cloud. The interesting part starts now.
Where this argument continues
The decision this history leads to is documented, sequenced and kept current on sapperment — not as content, but as a decision architecture.
Read the decisions. Public vs Private Cloud — what operating model you are choosing. RISE vs GROW — how you acquire and consume it. ECC timeline — when you actually have to move. All eight sit in the Executive Clarity Decision Library, sequenced the way a board meets them.
Contest them. Leading Top Voices and Experts bring independent, domain-specific perspectives. Expertise is organised by domain rather than prominence. Publishing is by invitation — if you have a practitioner perspective that deserves to outlive the feed, propose yourself as an LTV author.
Build the capability. The sapperment Talent Network is live in beta. Skills are published under a reference number — no names, no photos, no CV uploads — so specialists currently in a job can be found without exposing a search to their employer. Browse by domain or join.
Nineteen years of SAP strategy, and the one thing that never changed is that the vendor’s roadmap and your decision are not the same document. That gap is what this platform exists to close.
Evidence and sources
Evidence note: Dates, product announcements and financial figures below are documented public claims. The reading of a repeating pattern across eras is an inference. The verdicts on each era are the author’s point of view, formed over twenty-five years in this ecosystem — they are opinion, and labelled as such. No non-public SAP material was used in this article.
SAP, Q2 and Half-Year 2026 Results — current cloud backlog, cloud revenue, AI and BDC in the 50 largest deals.
SAP, “SAP Unveils the Autonomous Enterprise,” 12 May 2026 — Business AI Platform and Knowledge Graph.
SAP News, “New SAP S/4HANA Release and Maintenance Strategy,” 2022 — release cadence and maintenance framework.
SAP Learning, “Exploring the Strategy Updates for RISE with SAP and SAP GROW” — current positioning of the two motions.
The Register, “SAP extends support deadline for getting off legacy software,” 28 January 2025 and Rimini Street, “No Extension to ECC Support 2027 Deadline” — the 2027 mainstream and 2030 extended maintenance dates, and the conditional RISE-linked options.
ERP Research, “SAP Business ByDesign: Delisting & Migration” and Walldorf Consulting, “The End of SAP Business ByDesign” — 2007 launch, delayed delivery, below-plan adoption, and the April 2026 delisting for new customers. Delisting date reported by these secondary sources.
MarketWatch, “SAP stock slumps as UBS downgrades stock on ‘slow’ move into AI,” 26 August 2026 — external scepticism on delivery pace.
First published on LinkedIn. Subscribe to Unfiltered: SAP Public Cloud to get new editions as they appear — or browse the sapperment library.