GROW with SAP and RISE with SAP both deliver S/4HANA as a cloud subscription, both price in FUE units, and both bundle infrastructure, software, and services into a single contract. The marketing positioning often runs them together, with the implication that GROW is RISE for smaller deals. The implication is misleading. The two packages have substantively different product scopes, extensibility models, contractual structures, and economic profiles. Choosing between them is a strategic decision and the wrong choice locks the buyer into an architecture that does not fit. Across our S/4HANA migration compliance engagements we apply five decision criteria to the question.
Criterion one — process scope
RISE supports the full S/4HANA process scope. GROW supports a defined subset of S/4HANA processes, specifically the public-cloud edition’s standard scope. The subset is meaningful: GROW omits certain industry-specific scenarios, certain country localisations, and certain advanced configurations that the private-cloud edition supports. For buyers whose process scope falls inside the GROW subset the limitation is not a constraint; for buyers whose process scope falls outside, GROW is not a feasible option.
The buyer-side preparation is the process scope inventory. Document the processes that the current estate supports, the processes that the future estate needs to support, and the alignment of both against the GROW standard scope. The GROW package contents piece sets out the scope inventory.
Criterion two — extensibility
RISE permits in-core customisation under defined conditions, including ABAP development in the customer namespace, modification of standard objects with SAP approval, and the broader extension patterns established under the on-premise model. GROW does not. GROW permits side-by-side extension through BTP only; the S/4HANA core is delivered as a managed software environment with no in-core modification permitted.
The decision criterion is the buyer’s extensibility requirement. Buyers whose business processes can be implemented within S/4HANA standard plus BTP-based side-by-side extensions can use GROW. Buyers who require in-core customisation cannot. The decision should be made on a documented analysis of the actual extension requirements rather than on a general aversion to constraint. The GROW topic page covers the extensibility framework.
Criterion three — release cadence
RISE permits the buyer to defer S/4HANA upgrades within defined limits. The buyer typically has a window of several quarters in which to schedule and execute the upgrade, with SAP support for the older version continuing across the deferral window. GROW does not. GROW upgrades are scheduled centrally by SAP, typically twice per year, and the buyer’s consumption of the upgrade is not optional in the same way.
What the cadence means in practice
For buyers with stable processes and limited downstream dependencies, the GROW cadence is a benefit: SAP keeps the system current without buyer-side effort. For buyers with complex downstream integrations or substantial side-by-side extensions, the GROW cadence is a risk: each upgrade can affect the side-by-side environment in ways that require buyer-side testing and remediation under SAP’s timeline rather than the buyer’s. The GROW public-cloud restrictions piece covers the cadence-related constraints.
Criterion four — FUE pricing
Both packages price in FUE. The per-FUE rates differ materially. GROW typically prices at a lower per-FUE rate than RISE, reflecting the more constrained product scope, the absence of customisation, and the smaller buyer profile. The lower per-FUE rate is the headline economic argument for GROW.
The total economic position is more complex than the per-FUE rate. The relevant comparison is the contracted FUE quantity times the per-FUE rate times the term length, adjusted for the BTP credit allocation, the migration cost, and the future-state extensibility cost. A GROW deployment with substantial BTP side-by-side extensions can carry total cost in line with a RISE deployment with in-core customisation. The decision should be made on the total economic position rather than on the per-FUE rate alone. The GROW vs RISE compliance comparison white paper covers the full economic model.
GROW is not RISE for smaller buyers. It is a different product with different process scope, extensibility, and cadence. The right buyer for GROW is one whose process and extension requirements fit inside the GROW envelope. The right buyer for RISE is one whose requirements need the broader envelope. The choice between them is a strategic architectural decision, not a pricing decision.
Criterion five — contractual structure
RISE contracts are negotiated at significant length and detail, with material commercial flexibility on T-shirt sizing, credit allocation, exit terms, and the broader provisions. GROW contracts are closer to standard SaaS subscriptions, with less negotiation flexibility and faster contract execution. The trade-off is real: GROW is faster to procure and simpler to manage; RISE is slower to procure and more complex but with more commercial levers.
The relevance to the buyer depends on the deal size and the buyer’s procurement sophistication. For smaller deals where the procurement effort is itself a cost, the GROW simplicity is a benefit. For larger deals where the negotiation effort is justified by the contract value, the RISE flexibility is a benefit. The RISE pricing model piece covers the RISE flexibility points in detail.
Where hybrid deployments fit
For organisations with mixed requirements, the hybrid deployment is sometimes the right answer: GROW for a subsidiary or business unit whose requirements fit the GROW envelope, RISE for the parent estate whose requirements need the broader envelope. The hybrid carries its own complications: two contracts, two service profiles, two release cadences, two integration architectures.
The hybrid economic position can be favourable when the two estates are large enough to justify the separate management overhead. It is rarely favourable for small estates where the management overhead exceeds the entitlement savings. The decision should be made on a documented analysis of the management cost against the entitlement saving.
What to document before the decision
The decision between GROW and RISE should rest on documented analysis of: the process scope inventory; the extensibility requirements; the release-cadence tolerance; the total economic position over the contract life; and the contractual flexibility requirement. The five together produce a defensible architectural decision. Skipping any one of the five produces a decision that is liable to be revisited at the first significant change in the business context. The pharma migration case file documents an estate that worked through the five criteria during a brownfield-to-cloud transition.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.
The follow-through
Once the decision is made, the implementation work follows from the decision. A GROW deployment focuses on side-by-side extension design from day one. A RISE deployment focuses on FUE conversion, T-shirt sizing, and credit allocation. Both deployments focus on the exit terms negotiated at sign. The architectural decision shapes the implementation; the implementation shapes the long-term economics; and the exit terms shape the renewal leverage that compounds across the contract life. The FUE in GROW piece covers the FUE conversion mechanics in detail.