SaaS / Enterprise SoftwareEurope
← Sticker Wall
JOURNEY · DETAIL
SAP: Five Former IBM Employees Started in a Garage and Built the Global ERP Software King
Founded: Dietmar Hopp, Hans-Werner Hector, Hasso Plattner, Klaus Tschira, Claus Wellenreuther · SAP SE
JOURNEY
Key Fields
FIELD STAMPSIndustrySaaS / Enterprise Software
RegionEurope
ScaleGiant
ChannelOther
Origin
In 1972, five system engineers from IBM's Mannheim office in Germany realized during a customer project that enterprise financial and inventory management software involved a high degree of repetitive customization, requiring development from scratch every time. They proposed creating a standardized, cross-enterprise reusable real-time financial software package, but IBM management rejected the idea as a distraction from their core hardware sales focus. The five resigned and founded SAP in a small Mannheim office with the goal of enabling companies to handle financials, inventory, and orders with a single software suite rather than writing one-off code for every business.
Milestones
1972
Inception Turning Point
After resigning from IBM, the five founders established SAP, initially relying on custom development projects to sustain cash flow. That same year, they secured their first customer—a subsidiary of ICI in Östringen, Germany—developing a real-time financial RF system. Although this project generated no productized revenue, it allowed the team to validate the technical approach of real-time data entry and instant posting, laying the foundation for future standard software. In its first year, the company had fewer than 10 employees, with revenue coming primarily from project fees, which fell far short of supporting product R&D.
1973
Productization PMF
SAP launched the real-time financial software RF, subsequently expanding it into the Materials Management (RM) module to form an early integrated financial and inventory software solution. In 1976, SAP registered as a limited liability company and established SAP GmbH as a sales and support entity, gradually shedding its pure outsourcing identity. By 1978, the company began selling standard software licenses to mid-sized manufacturing enterprises instead of developing custom solutions for each client, pivoting its business model from project-based to software licensing.
1979
Product Upgrade Growth
SAP released its second-generation product, SAP R/2, integrating financial, material, production, and sales modules on mainframe systems, making it one of the few standard software solutions capable of covering entire corporate workflows. R/2 primarily served large manufacturing enterprises in German-speaking regions, such as chemical and automotive clients. As its customer base expanded, SAP began forming industry solution teams and established a sales network centered in Germany and expanding across Europe.
1992
Architecture Transition Turning Point
SAP released SAP R/3 based on a client/server architecture, completely eliminating reliance on expensive mainframes and enabling mid-sized enterprises to deploy ERP systems. This decision propelled SAP from a European software vendor into the US market, establishing numerous branch offices throughout the United States during the 1990s. R/3 became synonymous with ERP, driving SAP's revenue from approximately 750 million German marks in 1991 to over 3 billion marks by 1996.
1999
Ecosystem Expansion Growth
SAP launched the mySAP.com strategy, expanding ERP capabilities into customer relationship management, supply chain management, and business intelligence, while introducing support for internet technologies. Through acquisitions and a partner ecosystem, the company established an integrated delivery framework encompassing consulting, implementation, and operations. By 1999, SAP employed over 25,000 people globally, with annual revenue surpassing 5 billion euros, making it Europe's most valuable software company.
2004
Platformization PMF
SAP released the NetWeaver integration platform, attempting to transform ERP from a single application into a developable, integrable enterprise technology foundation. During this phase, SAP acquired companies like Business Objects to strengthen its analytics capabilities. Although NetWeaver did not become an independent revenue engine, it laid the groundwork for the subsequent S/4HANA tech stack and partner development model, facilitating SAP's transition from a pure application vendor to a platform company.
2011
Cloud & In-Memory Computing Transition Failure
SAP launched the in-memory computing-based SAP HANA database and began promoting cloud ERP products like Business ByDesign. However, Business ByDesign progressed slowly in the mid-market, undergoing multiple positioning and team adjustments before ultimately failing to become a mainstay of SAP's cloud business. Concurrently, SAP acquired SuccessFactors for approximately $3.4 billion to enter the human resources cloud services sector, though the migration speed of traditional ERP customers to the cloud fell far short of management expectations.
2015
Core Product Reconstruction Turning Point
SAP released S/4HANA, rearchitecting the financial, manufacturing, and supply chain logic of legacy R/3 and ECC onto the HANA in-memory database. The company announced the cessation of standard maintenance for older ERP versions by 2027, forcing tens of thousands of customers to make migration or replacement decisions. This decision sparked massive implementation consulting demand, while also prompting some clients to consider alternatives like Workday or Oracle. SAP aimed to lock in subscription revenue for the next decade via S/4HANA, but faced continuous pressure regarding execution pace and migration costs.
2021
Cloud-First Growth
SAP launched RISE with SAP, bundling S/4HANA Cloud, infrastructure, and subscriptions to lower the barrier for customers moving to the cloud. In fiscal 2021, SAP's cloud revenue reached approximately 9.4 billion euros, accounting for over 30% of total revenue. Total revenue stood at roughly 10.5 billion euros, with a workforce exceeding 100,000 employees. Despite cloud growth, the transition period away from substantial legacy maintenance revenue continued to impact profit margins and short-term financial performance.
Turning Points
- Resigning from IBM and rejecting the hardware-bundling model to establish the standard software product direction
- The 1992 R/3 transition to client/server architecture, unlocking the US and global mid-market enterprise sectors
- The 2015 S/4HANA forced migration strategy shifting maintenance revenue to cloud subscriptions, re-securing customer lock-in
- Bolstering non-ERP cloud capabilities through multiple strategic acquisitions including SuccessFactors, Ariba, and Qualtrics
Failures & Pitfalls
- Business ByDesign failed to crack the mid-market cloud ERP sector despite multiple positioning adjustments
- Slower cloud transition in the 2010s compared to Salesforce and Workday, forcing high-cost catch-up acquisitions
- Despite technological breakthroughs, SAP HANA failed to become an independent product revenue stream spanning the broader database market
- S/4HANA migration complexity and costs drove some customers toward Oracle or Workday alternatives
- Early over-reliance on direct sales and large consulting partners led to high implementation costs and lengthy delivery cycles
关键成功要素
- Replacing project customization with a standard software licensing model was core to SAP's evolution from an outsourcer to a product company
- The R/3 transition to client/server architecture lowered deployment barriers, enabling ERP adoption among mid-sized enterprises
- Once large enterprises run financials and supply chains on SAP, high switching costs create powerful customer lock-in
- Although slow, the cloud transition successfully converts one-time licenses into long-term subscriptions via S/4HANA and RISE
- Continuous acquisitions of SuccessFactors, Ariba, Qualtrics, and others effectively filled gaps in non-ERP cloud capabilities
Lessons
- Standard products must break free from reliance on single-customer projects early on, or pricing power will suffer
- Missing the window for architectural transition leaves slow-moving software companies vulnerable to disruption by cloud waves
- Locking in enterprise clients requires deep data and workflow integration into daily operations, not just contracts
- Subscription transitions cause short-term profit dips, but renewal stability is healthier than one-off license income
- Technological leadership does not equal market leadership; HANA's database ambitions were ultimately constrained by the upper-layer application ecosystem
Core Data
- 创始年份：1972
- 创始人数量：5
- 2021年云收入：9.4 billion EUR
- 2021年总营收：10.5 billion EUR
- 全球员工数：Over 100,000
- 市值：Over 180 billion EUR
Competitors / Peers
SAP's main competitors in the ERP and enterprise management software market are Oracle, Microsoft, and Workday. Oracle directly contests large enterprise clients through its database-plus-cloud-applications portfolio, with its Fusion ERP going head-to-head with S/4HANA over the long term. Microsoft bundles Dynamics 365 with the Azure and Office ecosystems to offer a lower-cost alternative in the mid-market. Workday targets human resources and financial cloud domains, capturing clients slow to upgrade SAP by leveraging a lighter, pure-cloud architecture. Salesforce, while not offering core ERP, sits further up the cloud stack and diverts enterprise software budgets in sales and customer management scenarios. SAP's core strengths lie in its industry depth across financials, manufacturing, and supply chains as well as its global delivery network, but its cloud subscription growth rate and product usability have historically lagged behind these rivals.