SAP has created two distinct cloud pathways for S/4HANA adoption: RISE with SAP (for enterprises) and GROW with SAP (for mid-market and greenfield). Both are subscription bundles that combine software, infrastructure, and services — but their target markets, pricing models, included entitlements, and commercial flexibility differ significantly. This guide cuts through the marketing to compare the real cost and commercial implications of each path.
RISE with SAP is SAP's enterprise cloud transformation bundle, launched in 2021. It is designed for large enterprises migrating from on-premise SAP ERP (typically ECC 6.0) to S/4HANA Cloud Private Edition. RISE bundles:
The key characteristic of RISE: it is a single subscription from SAP that covers infrastructure, software, and managed operations. SAP becomes the managed service provider. The customer no longer procures infrastructure separately — this is both a commercial lock-in mechanism and a potential cost advantage if SAP's infrastructure costs genuinely undercut direct hyperscaler pricing.
GROW with SAP is SAP's cloud ERP offering for mid-market companies (typically under 1,000 employees) or large enterprises doing greenfield (brand new, not migrating legacy systems) S/4HANA deployments. GROW is built on S/4HANA Cloud, Public Edition — a multi-tenant SaaS model shared across many customers.
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
GROW includes:
Key differences from RISE: GROW runs on Public Edition (not Private) — which means less customisation is possible, the infrastructure is shared multi-tenant (no dedicated environment), implementation is typically faster (3–6 months vs. 12–18+ for RISE), and per-user pricing is lower at equivalent scale. GROW is simpler, faster, but less flexible.
| Dimension | RISE with SAP | GROW with SAP |
|---|---|---|
| Target customer | Large enterprise / ECC migration | Mid-market / Greenfield |
| S/4HANA edition | Private Edition (dedicated) | Public Edition (multi-tenant) |
| Infrastructure | Dedicated, SAP-managed | Shared SaaS (multi-tenant) |
| Customisation capability | Extensive (ABAP custom code supported) | Limited (BTP extensions only) |
| Implementation time | 12–24 months | 3–6 months |
| Typical contract term | 5 years | 3 years |
| Pricing basis | Per SAPS (compute unit) + named users | Per named user |
| BTP included | Yes (starter pack included) | Limited or separate |
| Infrastructure cost visibility | Bundled (opaque to customer) | Not applicable (SaaS) |
| Exit flexibility | Moderate (data export rights, but sticky) | Higher (standard SaaS exit) |
RISE pricing is notoriously complex and non-transparent — and this complexity is, from SAP's perspective, intentional. It allows SAP to tailor pricing to each customer's negotiating power and willingness to pay.
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
SAPS-based infrastructure pricing: SAP Application Performance Standard (SAPS) is SAP's compute measurement unit. Your infrastructure cost is tied to SAPS allocation, which depends on your system size, user count, and data volumes. SAP determines the SAPS requirement — customers often find they cannot accurately predict final SAPS costs pre-implementation. The process is: SAP Consulting estimates SAPS, the customer's SI validates it, and by the time you're in contract negotiation, changing the SAPS estimate is difficult. This is a classic principal-agent problem: SAP has incentive to overstate SAPS, and the customer is locked in.
Named user licensing: On top of SAPS infrastructure, you pay named user licence fees for S/4HANA (Professional, Limited Professional, Employee, Developer user types — the same user classification model as traditional on-premise SAP licences). A Professional user on RISE costs roughly $18K–$28K annually, depending on contract term and negotiation. For a 500-user RISE environment, this easily reaches $7M–$14M per year before infrastructure.
BTP consumption: RISE includes a starter BTP entitlement (typically valued at $100K–$500K annually). Anything above the starter allocation is charged additionally — either on a consumption basis or subscription. Many customers find their BTP costs exceed the starter allocation once they begin integrating third-party systems and building cloud-native extensions. This is another hidden cost layer.
Annual escalation: RISE contracts typically include 3–5% annual escalation, compounding. Over a 5-year contract, this compounds to roughly 16–28% total increase, which is material.
Services not included: Implementation, data migration, custom code remediation, integration development — all charged separately (either by SAP Consulting at premium rates or by a partner SI). SAP implementation consulting often adds $2M–$5M to the total 5-year cost for enterprise deployments.
The total cost of RISE at 10 years typically exceeds the total cost of a well-negotiated on-premise S/4HANA deployment by 30–50% at large enterprise scale. The gap narrows significantly for organisations that genuinely offload infrastructure and BASIS operations costs and have simplified process footprints that reduce implementation complexity. For complex, highly customised ERP environments, RISE often costs more than on-premise.
GROW with SAP uses a simpler per-user subscription model that closely resembles SaaS pricing for Workday, Oracle Fusion Cloud, and Microsoft Dynamics 365.
Per-user per-month pricing: GROW typically costs $150–$250 PUPM (per user per month) for full S/4HANA Public Edition access, depending on region, volume, term length, and negotiation. For a 500-user organisation over 3 years, this translates to $2.7M–$4.5M in subscription costs. For a 1,000-user organisation, $5.4M–$9M. The pricing is transparent and comparable — you can benchmark against Workday, Oracle Fusion, or Dynamics pricing.
Module add-ons: Treasury, advanced HR, Manufacturing, and other advanced modules are priced separately (typically +$20–$50 PUPM per module). For many mid-market organisations, this adds $200K–$800K annually depending on module adoption.
No separate infrastructure cost: Infrastructure is bundled into the SaaS fee — no SAPS complexity, no hidden infrastructure allocation uncertainty. This is a major advantage of GROW: you know exactly what you're paying.
Implementation is separate: GROW implementation costs are typically lower than RISE (3–6 month projects) but still significant. Budget $200K–$1M+ for mid-market implementations, depending on process complexity and customisation. For a greenfield deployment (no legacy system to migrate from), implementation costs are at the lower end. For an ERP replacement, costs are higher.
Annual escalation: Like RISE, GROW contracts typically include 2–3% annual escalation (slightly lower than RISE because the SaaS model has lower cost inflation). Over 3–5 years, this is material but more manageable than RISE's typical 3–5%.
Let's compare five-year TCO for two illustrative scenarios:
| Cost Component | RISE (500 users, 5yr) | GROW (500 users, 5yr) |
|---|---|---|
| Subscription / Licence | $3.5M–$5.5M | $2.0M–$3.5M |
| Infrastructure (SAPS) | Bundled in subscription | Included in SaaS |
| Implementation | $2M–$5M (12–18 month project) | $0.5M–$1.5M (3–6 month project) |
| BASIS / Managed Ops | Bundled in RISE (SAP-managed) | SAP-managed (included in SaaS) |
| Custom development | $0.5M–$2M (Private Edition supports ABAP) | $0–$0.2M (Public Edition very limited) |
| BTP / Integration overruns | $0.2M–$1M (above starter allocation) | $0–$0.3M (minimal BTP use) |
| 5-Year Total | $6.2M–$13.5M | $2.5M–$5.0M |
| Cost Component | RISE (2,000 users, 5yr) | GROW Not Suitable (ECC Migration) |
|---|---|---|
| Subscription / Licence | $10M–$18M | N/A — GROW not fit for ECC migration |
| Implementation | $5M–$12M (18–24 month project) | N/A |
| Custom code remediation | $1M–$4M (complex ECC customisation) | N/A |
| BTP / Integration | $0.5M–$2M | N/A |
| 5-Year Total | $16.5M–$36M | Not applicable |
This illustrative comparison highlights why GROW is typically better value for organisations that can operate within S/4HANA Public Edition's process footprint. For mid-market and greenfield deployments, GROW delivers 50–60% lower TCO than RISE. RISE becomes the right choice when the organisation requires significant customisation, has complex integrations, or is migrating a highly customised ECC environment where a lift-and-shift approach is required. For large ECC migrations, RISE is often the only viable path, making cost comparison moot — the question is how to minimise RISE's costs, not whether to choose it over GROW.
The most common source of RISE budget shock is discovering what is NOT included. SAP's messaging emphasises "all-in" bundling, but the reality is more nuanced.
Key negotiation points for RISE:
Key negotiation points for GROW:
Uncertain about GROW vs RISE costs for your organisation?
Our panel of SAP cloud negotiation specialists provides independent TCO analysis and commercial benchmarking.
Our panel of SAP specialists provides independent GROW and RISE TCO analysis, pricing benchmarking, and commercial negotiation support to help you choose the right cloud path and maximise value.