Independent comparison of SAP's two cloud ERP paths: RISE with SAP for established enterprises seeking comprehensive digital transformation, and GROW with SAP for mid-sized companies seeking rapid, simplified cloud ERP adoption. Covers cost models, FUE licensing, contract structures, indirect access risks, and negotiation strategies.
Part of the SAP Licensing Knowledge Hub. See also: What Is SAP RISE? | FUE Licensing Explained | SAP RISE Advisory Services.
RISE with SAP is SAP's flagship cloud offering, introduced in 2021, bundling S/4HANA Cloud (Private or Public Edition) with BTP credits, SAP Signavio for process intelligence, and SAP Business Network under a single subscription. SAP and hyperscaler partners (AWS, Azure, GCP) manage hosting, monitoring, and updates. Sold on subscription basis with 3-5 year terms, priced on Full User Equivalents (FUEs). SAP claims up to 20% TCO reduction versus on-premises, though independent analysis frequently finds this optimistic without rigorous licence optimisation. Best suited for mid-sized to large enterprises, existing SAP customers migrating from on-premises, organisations with complex processes, industry-specific requirements, or regulatory needs requiring private cloud.
GROW with SAP, launched in 2023, provides fast-track cloud ERP for small and mid-sized businesses. Centres on S/4HANA Cloud Public Edition as a SaaS, multi-tenant ERP in preconfigured best-practice packages deployable in weeks. Available in Base (core finance, procurement, sales, operations, starter BTP credits, basic Ariba) and Premium (adds advanced financial modules, SAP Analytics Cloud planning, Sales Cloud CRM, Concur Expense). Uses FUE licensing with lower upfront investment and predictable subscription fees. Best for organisations below $1B revenue, SAP newcomers, greenfield implementations, and those willing to adopt standardised best practices with minimal customisation.
| Cost Dimension | RISE with SAP | GROW with SAP |
|---|---|---|
| Pricing model | Custom-bundled subscription tailored to each customer | Pre-packaged subscription with transparent tier pricing |
| Upfront investment | Higher: broader scope, migration services, complex bundle | Lower: no large licence fee or infrastructure investment |
| Infrastructure costs | Included (hyperscaler choice: AWS, Azure, GCP) | Included (SAP-managed multi-tenant public cloud) |
| Customisation costs | Significant: Private Cloud supports extensive customisation | Minimal: clean core approach, standard processes |
| BTP credits included | More generous allocation for enterprise integration | Starter allocation for basic extension and integration |
| Typical contract term | 3-5 years | 3 years (sometimes shorter for SMEs) |
| Overall cost level | Higher: comprehensive bundle covering more ground | Lower: narrower scope, optimised for mid-market budgets |
| Cost Risk | Detail |
|---|---|
| Indirect access and Digital Access fees | If third-party systems create or access SAP data, additional licensing may be required even in cloud subscriptions. RISE contracts may include some Digital Access document allocation, but if e-commerce, CRM, or external systems generate documents beyond coverage, unbudgeted costs result. Clarify treatment in writing during negotiation. GROW customers with simpler landscapes should still inventory external integrations |
| BTP credit overages | Both offerings include prepaid BTP credits for platform services. RISE includes more generous credits. If consumption exceeds included credits, additional charges apply. Model expected BTP consumption against included credits and negotiate additional capacity at favourable rates during initial contract rather than paying list price for overages |
| Scalability and overage charges | Contracts specify FUEs, system size, and storage. Growing beyond contracted amounts requires amendments at pre-negotiated rates (if agreed) or higher list prices. For GROW, exceeding scale may signal need to transition to RISE, introducing migration complexity and cost. Negotiate foreseeable expansion rates upfront |
| Renewal and annual escalation | SAP frequently builds 3-5% annual escalators. Without renewal price protections, organisations face significant cost uncertainty at renewal when deeply invested with limited alternatives. Negotiate price caps and maximum renewal increases from the outset |
SAP's sales team has limited incentive to highlight indirect access exposure, BTP overages, or renewal escalation during the sales process. Understanding and addressing these risks during contract negotiation is essential for maintaining cost predictability throughout the subscription term.
| Licensing Dimension | Detail |
|---|---|
| Perpetual to subscription shift | Traditional: one-time perpetual fee + 22% annual maintenance, customer owns rights indefinitely. RISE/GROW: subscription covers software, hosting, maintenance, updates for defined period. If subscription ends, access is lost. Shifts CapEx to OpEx with higher ongoing costs but no upfront investment |
| FUE licensing simplification | Both use Full User Equivalents as primary metric. Professional user = 1.0 FUE, lighter user = 0.2 FUE. Simplifies compliance by reducing multiple licence categories to single aggregate metric. Five light users might equal one FUE, allowing mix adjustment without contract amendments |
| Consumption-based components persist | BTP credits serve as currency for platform services, Ariba Network includes document allocation, Digital Access may apply for indirect document creation. These ancillary consumption metrics can generate unexpected costs if not managed proactively |
| Scalability mechanics | Additional FUEs or modules added by amending subscription. Scaling down typically not permitted until renewal. Negotiate ramp-up provisions and pre-agreed rates for additional FUEs |
| Contract Aspect | RISE with SAP | GROW with SAP |
|---|---|---|
| Contract type | Custom enterprise agreement under SAP Cloud GTC (approximately 4 pages vs traditional 40-50 page on-premises contracts). Highly customised, each element priced separately | Standardised package agreement. More boilerplate with limited room to alter structure. Reflects pre-packaged nature of offering |
| Term | 3-5 years multi-year | Typically 3 years (shorter for smaller deployments) |
| Negotiation leverage | More opportunity for bespoke terms due to enterprise scale and complexity | Less leverage on individual terms due to standardisation. SMEs have more limited negotiating power |
| Key risk | Terms from previous agreements (special discounts, perpetual licence protections, negotiated audit provisions) do not automatically carry over to new Cloud GTC | Outgrowing the offering during contract term and needing to transition to RISE mid-agreement |
Both RISE and GROW contracts require careful attention to renewal provisions (capping annual increases, securing renewal price protections), flexibility terms (adding users, adjusting product mix, handling acquisitions or divestitures), and exit provisions (data return, transition assistance, termination penalties). These terms are frequently the most impactful on long-term cost and should be negotiated rigorously before signing rather than addressed reactively at renewal when leverage is significantly reduced.
| Strategy | Detail |
|---|---|
| Right-size the subscription before signing | Challenge every component in SAP's proposal. Remove unnecessary products, features, or FUE counts. Ensure genuinely needed capabilities are included to avoid change-order fees. For RISE: validate BTP credit allocation, Signavio inclusion, infrastructure sizing. For GROW: confirm Base vs Premium matches requirements and FUE count aligns with actual user population |
| Negotiate future growth rates in advance | If anticipating additional FUEs, modules, or capacity during term, negotiate those rates now. Include clauses for adding users at same per-FUE rate or fixed discount off list. Without pre-negotiated rates, mid-term expansion becomes a new sales event at higher prices. For GROW: discuss transition terms to RISE that protect existing investment |
| Secure price protections and renewal caps | Cap annual increases within term (target 0% first two years, maximum 3% thereafter or CPI with cap). Negotiate renewal price cap limiting SAP's ability to impose steep increases at term expiry. Without renewal protections, organisations face significant cost risk when deeply invested with limited alternatives |
| Choose | When |
|---|---|
| RISE with SAP | Mid-sized to large enterprise with existing SAP ECC or S/4HANA on-premises. Complex processes requiring extensive customisation. Industry-specific requirements. Multiple system integrations. Regulatory requirements necessitating private cloud. Global footprint requiring multi-region infrastructure. Higher cost justified by breadth of services and migration complexity |
| GROW with SAP | Small to mid-sized enterprise (typically below $1B revenue). New to SAP or switching from legacy non-SAP ERP. Willing to adopt standardised best practices with minimal customisation. Seeking rapid deployment (4-8 weeks). Budget-conscious with preference for predictable lower-cost subscription. Greenfield deployment without legacy SAP to migrate |
Organisations starting with GROW that outgrow the offering can transition to RISE. The migration involves moving from multi-tenant public cloud to private cloud, re-implementing customisations, and negotiating a new contract. Plan for this in the original GROW contract if there is any possibility requirements will exceed GROW's capabilities during the term. Independent advisory from a firm with no SAP commercial relationship ensures analysis, right-sizing, and negotiation serve the customer's interests exclusively.
SAP's announcement that mainstream ECC maintenance ends in 2027 (extended maintenance available through 2030 at premium) creates urgency for customers to plan S/4HANA migration. This deadline gives SAP's sales team a compelling narrative for encouraging RISE or GROW adoption. Organisations should be cautious about hasty decisions driven by deadline pressure. Extended maintenance through 2030 provides additional runway. SAP has also signalled that RISE and GROW may converge into a simplified "SAP Cloud ERP" offering in future. Understanding the direction of SAP's cloud packaging strategy is important for avoiding a contract optimised for today's structure but disadvantaged by future changes.
RISE is a comprehensive, customisable cloud transformation offering for mid-sized to large enterprises, particularly existing SAP customers migrating from on-premises. Supports Private and Public Cloud with extensive customisation. GROW is a streamlined, pre-packaged cloud ERP for small to mid-sized organisations and SAP newcomers, centred on S/4HANA Cloud Public Edition with standardised best practices and rapid deployment (4-8 weeks). RISE offers more scope and flexibility at higher cost; GROW prioritises simplicity and speed at lower cost.
Full User Equivalents normalise different user types into a single metric. A Professional user accessing full SAP functionality is typically 1.0 FUE, while lighter users (self-service, read-only) are assigned fractional values (0.2 or 0.3 FUE). The organisation purchases a total FUE count, and the mix can change within that total without contract amendments. Both RISE and GROW use the FUE model. See our FUE licensing guide for detailed calculation.
GROW scales with the business through additional FUEs and modules. However, its Public Cloud Edition has inherent limitations on customisation and architecture. Organisations expecting to exceed GROW's scale or require Private Cloud deployment, extensive customisation, or complex integrations should plan for potential transition from GROW to RISE. Address this in the original contract through pre-negotiated transition terms.
Four most significant: indirect access fees from third-party systems creating documents without explicit coverage; BTP credit overages from exceeding included platform service allocation; overage charges from growing beyond contracted FUEs without pre-negotiated rates; and renewal price escalation where SAP seeks significantly higher pricing at term end. All four should be addressed proactively during initial negotiation through explicit provisions, pre-agreed rates, and price caps.
SAP sometimes offers conversion credits for existing perpetual investments when transitioning to RISE. Availability and value varies and is negotiable. Credits are typically structured as subscription discounts rather than direct financial credits, and may not apply for the full term. Negotiate explicitly and document in contract. GROW, targeting newcomers, less commonly involves conversion but organisations with existing assets should explore whether credit is available.
The 2027 mainstream maintenance end creates urgency for S/4HANA migration. Extended maintenance is available through 2030 at premium, providing additional planning runway. Be cautious about hasty decisions driven by deadline pressure. SAP's evolving cloud packaging means today's RISE/GROW structure may change. A measured approach evaluating requirements, negotiating thoroughly, and considering the full timeline is preferable to rush-driven decisions.
For RISE contracts and larger GROW deployments, independent advisory consistently delivers returns exceeding advisory cost. SAP's sales team is incentivised to maximise contract value and has no inherent incentive to help right-size, negotiate lower pricing, or secure renewal protections. An independent advisor with no SAP commercial relationship ensures right-sizing, benchmarking, and negotiation serve the customer exclusively. Particularly valuable for organisations unfamiliar with FUE mechanics, indirect access, BTP overages, and renewal escalation risks.
Redress Compliance provides independent advisory for organisations evaluating, negotiating, and optimising SAP RISE and GROW agreements. No SAP partnerships, reseller relationships, or referral arrangements. 100% vendor-independent. Fixed-fee engagement.
SAP RISE Advisory ServicesIndependent SAP advisory. RISE vs GROW evaluation. FUE optimisation. Contract negotiation. 100% vendor-independent, fixed-fee engagement.