★ WIDE MOAT STOCKS & COMPETITIVE ADVANTAGES ★

Checking

SAP SE

SAP · XETRA

Market cap (USD)$187.2B
SectorTechnology
IndustrySoftware - Application
CountryDE
Data as of
Moat score
66/ 100

Weighted average of segment moat scores, combining moat strength, durability, confidence, market structure, pricing power, and market share.

Request update

Spot something outdated? Send a quick note and source so we can refresh this profile.

Overview

SAP SE is a German enterprise software vendor now reported through Applications, Technology & Support (about 89% of FY2025 revenue and 97% of segment profit) and Core Services (about 11% of revenue and 3% of segment profit). The strongest moat sits in ATS: ERP-centered systems of record create workflow/data lock-in, suite bundling supports cross-sell, partners add implementation and extension capacity, and cloud backlog/support renewals improve revenue visibility. Core Services is lower moat because consulting and implementation markets remain competitive. Key risks are cloud migration execution, best-of-breed displacement, Oracle/Microsoft/Workday/ServiceNow competition, data-portability pressure, cyber/compliance incidents, and AI/platform shifts.

Primary segment

Applications, Technology & Support

Market structure

Oligopoly

Market share

HHI:

Coverage

2 segments · 5 tags

Updated 2026-07-01

Segments

Applications, Technology & Support

Enterprise application software suites, ERP-centric cloud subscriptions, software support, and platform services

Revenue

89.3%

Structure

Oligopoly

Pricing

moderate

Share

Peers

ORCLMSFTCRMNOW+1

Core Services

Enterprise software consulting, implementation, and premium support (SAP landscapes)

Revenue

10.7%

Structure

Competitive

Pricing

weak

Share

Peers

ACNIBMCTSHDXC

Moat Claims

Applications, Technology & Support

Enterprise application software suites, ERP-centric cloud subscriptions, software support, and platform services

SAP changed to Applications, Technology & Support (ATS) and Core Services reporting in 2025. FY2025 segment revenue was EUR32.847bn out of EUR36.800bn, with EUR13.345bn of EUR13.777bn segment profit; Q1 2026 ATS revenue share was about 90%.

Oligopoly

Data Workflow Lockin

Demand

Strength

Strength 4 of 5

Durability

Durability 3 of 3

Confidence

Confidence 4 of 5

Evidence

Evidence 2 of 5

Core ERP and adjacent suites sit in the system-of-record layer; migrations and process redesign create high change costs.

Data Workflow Lockin moat: definition, examples, and stocks

Erosion risks

  • Rise of modular, API-first best-of-breed stacks reduces suite dependence
  • Customer migrations to competitor clouds during major ERP refresh cycles
  • Data portability and interoperability mandates

Leading indicators

  • Net retention / renewal rates for cloud subscriptions
  • Share of customers adopting S/4HANA Cloud vs legacy ECC
  • Customer reported churn or competitive displacement in large deals

Counterarguments

  • Large enterprises can multi-vendor and standardize on hyperscalers with alternative app ecosystems
  • Cloud-native ERPs can win greenfield deployments faster than SAP migrations

Suite Bundling

Demand

Strength

Strength 4 of 5

Durability

Durability 3 of 3

Confidence

Confidence 3 of 5

Evidence

Evidence 2 of 5

ERP-centered suite plus adjacent LoB apps and analytics/AI creates cross-sell and reduces point-solution penetration in core processes.

Suite Bundling moat: definition, examples, and stocks

Erosion risks

  • Customer pushback against bundled pricing
  • Regulatory scrutiny of tying/bundling in enterprise software
  • Best-of-breed vendors winning specific LoB categories

Leading indicators

  • Attach rates of BTP / analytics / LoB apps to core ERP deals
  • Average contract value (ACV) expansion for existing customers
  • Competitive win/loss on core ERP with/without suite

Counterarguments

  • Enterprises increasingly procure modularly and integrate through iPaaS
  • Suites can lag specialist functionality, driving selective replacement

Ecosystem Complements

Network

Strength

Strength 4 of 5

Durability

Durability 3 of 3

Confidence

Confidence 4 of 5

Evidence

Evidence 2 of 5

Large partner ecosystem builds extensions and delivers implementation capacity, reinforcing SAP adoption and creating complements around BTP and ERP.

Ecosystem Complements moat: definition, examples, and stocks

Erosion risks

  • Partner talent shifts toward competing platforms
  • Quality/control issues in partner-delivered implementations
  • Platform commoditization reduces extension differentiation

Leading indicators

  • Number of active partners and certified consultants
  • Partner-sourced pipeline / % revenue influenced by partners
  • Marketplace extension growth and usage

Counterarguments

  • Systems integrators can be platform-agnostic and steer customers to alternatives
  • Partners capture much of services profit, limiting SAP ability to enforce quality/pricing

Long Term Contracts

Demand

Strength

Strength 3 of 5

Durability

Durability 2 of 3

Confidence

Confidence 4 of 5

Evidence

Evidence 3 of 5

Recurring support and cloud subscriptions (plus multi-year cloud backlog) increase revenue visibility and reduce short-term competitive pressure at renewal.

Long Term Contracts moat: definition, examples, and stocks

Erosion risks

  • Renewal repricing pressure during IT budget downturns
  • Customer migrations off maintenance to competitor SaaS during modernization cycles
  • Shorter contract durations in SMB/upper mid-market

Leading indicators

  • Cloud backlog / remaining performance obligations trend
  • Recurring revenue mix and renewal rate
  • Support revenue stability vs cloud migration pace

Counterarguments

  • Contracts renew, but customers can use renewal cycles to demand concessions
  • Cloud contracts can be repriced downward if value perception declines

Compliance Advantage

Legal

Strength

Strength 3 of 5

Durability

Durability 2 of 3

Confidence

Confidence 3 of 5

Evidence

Evidence 1 of 5

Capabilities oriented toward public sector and regulated customers (e.g., security, sovereign cloud initiatives) can be a differentiator in high-compliance deployments.

Compliance Advantage moat: definition, examples, and stocks

Erosion risks

  • Regulation changes faster than product/security roadmap
  • Government procurement shifts toward open standards and interoperability
  • Competition from hyperscaler sovereign cloud offerings

Leading indicators

  • Public sector cloud wins and renewals
  • Security/compliance certifications achieved and maintained
  • Incidents that trigger increased scrutiny (breaches, outages)

Counterarguments

  • Large competitors also invest heavily in compliance certifications and sovereign cloud
  • Public-sector buying can be price-sensitive and policy-driven

Core Services

Enterprise software consulting, implementation, and premium support (SAP landscapes)

FY2025 Core Services revenue was EUR3.953bn out of EUR36.800bn, with EUR432m of EUR13.777bn segment profit. Q1 2026 Core Services revenue was EUR945m and profit was EUR84m.

Competitive

Brand Trust

Demand

Strength

Strength 2 of 5

Durability

Durability 2 of 3

Confidence

Confidence 3 of 5

Evidence

Evidence 1 of 5

SAP-branded support tiers can be trusted for mission-critical operations, but systems integrators often capture implementation spend.

Brand Trust moat: definition, examples, and stocks

Erosion risks

  • Customers prefer independent SIs for transformation programs
  • Delivery quality issues can damage trust quickly
  • Talent scarcity and wage inflation reduce differentiation

Leading indicators

  • Services attach rate to cloud deals
  • Customer satisfaction/NPS for premium support programs
  • Share of services delivered by SAP vs partners

Counterarguments

  • Global SIs (and boutique firms) often have deeper implementation benches and industry-specific accelerators
  • Services are easier to substitute than core software

Evidence

other

...embedding agentic AI into end-to-end business processes...

Positions SAP around cross-functional enterprise processes, consistent with workflow lock-in.

other

...preserves mission-critical business context across all data.

SAP Business Data Cloud emphasizes mission-critical data context, increasing migration and redesign friction.

other

Cloud ERP Suite contributed 86% to overall cloud revenue...

Shows cloud growth is concentrated in the ERP-centered suite, supporting cross-sell and bundling relevance.

other

The ATS segment represents SAP's cohesive product portfolio...

SAP describes ATS as one cohesive commercialized product portfolio, consistent with suite bundling.

other

Partners play a key role in driving market adoption...

SAP says partners co-innovate, embed, resell, and implement its software, supporting ecosystem complements.

Showing 5 of 11 sources.

Risks & Indicators

Erosion risks

  • Rise of modular, API-first best-of-breed stacks reduces suite dependence
  • Customer migrations to competitor clouds during major ERP refresh cycles
  • Data portability and interoperability mandates
  • Customer pushback against bundled pricing
  • Regulatory scrutiny of tying/bundling in enterprise software
  • Best-of-breed vendors winning specific LoB categories

Leading indicators

  • Net retention / renewal rates for cloud subscriptions
  • Share of customers adopting S/4HANA Cloud vs legacy ECC
  • Customer reported churn or competitive displacement in large deals
  • Attach rates of BTP / analytics / LoB apps to core ERP deals
  • Average contract value (ACV) expansion for existing customers
  • Competitive win/loss on core ERP with/without suite

Keep the research going

Created 2025-12-30
Updated 2026-07-01

More Rankings & Systems

Curation & Accuracy

This directory blends AI‑assisted discovery with human curation. Entries are reviewed, edited, and organized with the goal of expanding coverage and sharpening quality over time. Your feedback helps steer improvements (because no single human can capture everything all at once).

Details change. Pricing, features, and availability may be incomplete or out of date. Treat listings as a starting point and verify on the provider’s site before making decisions. If you spot an error or a gap, send a quick note and I’ll adjust.