GROW with SAP:
What It Costs, What's Included, and What to Negotiate

GROW with SAP is a commercial package built around SAP S/4HANA Cloud Public Edition — the multi-tenant SaaS version of SAP's flagship ERP. Unlike RISE with SAP (which centres on S/4HANA Private Edition or Managed Cloud), GROW uses a shared cloud infrastructure with standardised processes and a predefined adoption methodology called SAP Activate.

The GROW package includes: the S/4HANA Cloud Public Edition subscription, a defined set of BTP services for integration and extensibility, access to SAP Build (low-code development), and a collection of SAP Business Accelerator Hub content (pre-built APIs, integrations, and industry best-practice process flows). SAP positions these inclusions as reducing the cost and time of implementation — the theory being that a pre-configured cloud system on standardised infrastructure needs less professional services investment than an on-premise or private cloud deployment.

In practice, GROW with SAP is a viable path for mid-market companies that can align their processes to SAP's standardised cloud configuration and do not require deep customisation. Companies with complex, differentiated processes — multi-entity structures, specialised manufacturing operations, heavily regulated industries — typically find GROW's constraints limiting within 18 months of deployment. Our RISE and GROW advisory service helps organisations determine which offering genuinely fits their requirements before committing to either.

SAP sales teams present GROW and RISE as choices on a spectrum — same destination, different routes. That framing obscures commercially and technically important differences that affect total cost of ownership over a 5- to 10-year horizon.

Dimension	GROW with SAP	RISE with SAP
SAP Product	S/4HANA Cloud Public Edition (multi-tenant SaaS)	S/4HANA Cloud Private Edition or Managed Cloud (dedicated)
Infrastructure	SAP-managed shared cloud	SAP-managed dedicated cloud (can run on hyperscaler)
Customisation	Restricted — extensibility via BTP only, no core modifications	High — customer-specific configuration and custom code permitted
Release cadence	Mandatory quarterly releases — SAP controls timing	Customer-controlled release schedule within SAP maintenance windows
Target market	Mid-market / growth companies	Large enterprise
Implementation time	Typically 6–12 months (SAP Activate methodology)	Typically 18–36 months
Entry price	Lower	Higher — includes infrastructure cost
BTP inclusion	Defined BTP entitlement for integration/extension	BTP credits included — typically larger pool

The GROW with SAP package is sold as a bundle. Understanding exactly what the bundle contains — and what is excluded — is essential before evaluating the headline price.

Core Inclusions

• SAP S/4HANA Cloud Public Edition subscription — the core ERP licensed by Named User. The specific functional scope depends on which line-of-business modules are contracted.
• SAP Business Technology Platform entitlement — includes SAP Integration Suite at a base tier, SAP Build Work Zone Standard, and a defined pool of cloud credits for additional BTP services. The BTP inclusion is scoped — it covers standard integration use cases, not unlimited BTP consumption.
• SAP Business Accelerator Hub access — pre-built integration content, API business hub, and industry best-practice process content.
• SAP Build — low-code/no-code application development and process automation tools. Included at a defined capacity level.
• SAP Activate methodology and toolset — structured implementation roadmaps and fit-to-standard analysis tooling.
• Standard support — SAP Enterprise Support included. Note: this contributes to SAP's 22% annual maintenance fee structure within the subscription economics.

Common Exclusions (Often Assumed to Be Included)

• Advanced analytics — SAP Analytics Cloud beyond basic reporting requires a separate licence.
• Ariba, SuccessFactors, Concur, Fieldglass — these are separate products not bundled into GROW.
• Extended BTP consumption above the included tier.
• SAP Signavio for process mining and design — priced separately.
• Implementation professional services — GROW includes methodology, not implementation delivery.
• Data migration tooling beyond SAP's standard included migration cockpit.

GROW with SAP pricing is built primarily on Named User licences, with additional charges for BTP consumption above included entitlements. SAP does not publish list prices for GROW — pricing is negotiated commercially and varies by region, deal size, competitive situation, and SAP's quarterly revenue targets.

Named User Types in GROW with SAP

S/4HANA Cloud Public Edition uses a simplified Named User structure compared to the on-premise catalogue. The primary user types in GROW contexts are:

• SAP S/4HANA Cloud PE (Full Use) — full-access users who can perform any function within the system. This is the most expensive user type, typically required for finance, procurement, and operations professionals.
• SAP S/4HANA Cloud PE (Self-Service) — limited-access users for employee self-service scenarios such as expense management, timesheet entry, and basic HR interactions. Significantly cheaper than Full Use.

The ratio of Full Use to Self-Service users is a critical cost driver. SAP's initial proposals routinely over-allocate Full Use licences. In our experience, a forensic review of actual role requirements typically reduces Full Use counts by 15–30%, with corresponding cost savings. This is the first analysis any enterprise should commission before accepting a GROW pricing proposal.

Contract Terms

GROW contracts are typically offered in three- and five-year subscription terms. Five-year terms attract better per-user pricing but commit the organisation to SAP's platform for a longer period. Given how rapidly SAP's cloud product portfolio evolves — and how frequently pricing models change — we advise clients to understand the full commercial implications of longer-term commitments before accepting the discount incentive.

SAP's GROW headline price is designed to be accessible. The real cost picture typically looks different by the end of year two. These are the most common cost escalation vectors we see in GROW deployments.

1. User Count Creep

GROW contracts lock in an initial user count. As organisations go live and expand usage, additional users are added — typically at list price unless a contractual expansion mechanism was included at the time of signing. Enterprises that do not negotiate user expansion pricing upfront routinely pay 40–60% more per user for subsequent additions than they paid at initial contract signature.

2. BTP Overrun Charges

The BTP integration entitlement in GROW is sized for standard use cases. Any integration beyond the included tier — connecting third-party systems, building custom Fiori extensions, automating inter-company processes — generates consumption charges against your BTP credit pool. When that pool is exhausted, charges accrue at list price. We have seen GROW customers with BTP overrun charges equal to 40% of their core ERP subscription cost within 18 months of go-live.

3. Add-On Licences

Every conversation with SAP about a new functional requirement that falls outside the core GROW scope creates an opportunity for SAP's account team to propose an additional product. Signavio for process intelligence, additional Analytics Cloud planning seats, advanced procurement tools — these add-ons accumulate rapidly and are rarely included in the initial GROW proposal.

4. Implementation Cost Overruns

While implementation costs are not SAP licence costs, they are directly influenced by the GROW contract structure. SAP Activate methodology assumes a fit-to-standard approach — if your processes require significant customisation via BTP extensions, your implementation partner's professional services costs will escalate. Some mid-market organisations find that the BTP extension work required to make GROW function for their business rivals the implementation cost of an on-premise deployment.

5. Forced Quarterly Upgrades

S/4HANA Cloud Public Edition releases quarterly updates that are mandatory — customers cannot defer them. Each upgrade requires re-testing custom extensions and integrations. For organisations with significant BTP extensions, quarterly upgrade testing costs can become material. This ongoing cost is rarely surfaced during the initial GROW sales process.

GROW contracts have more negotiating room than SAP's commercial teams suggest. Here are the specific terms worth pushing on — supported by the leverage available to any informed buyer.

User Expansion Pricing

Negotiate the price of additional users before signing. Establish a contractual expansion rate that matches or improves on your initial per-user price. Without this, SAP will quote list price for every user added after go-live — which is 30–50% higher than the volume-discounted price you receive at initial contract signature.

BTP Credit Sizing and Top-Up Pricing

Model your expected BTP consumption before signing and negotiate a credit pool that is 25–30% larger than SAP's standard GROW inclusion. Also negotiate a preferential top-up rate — the price you pay per additional credit block if your included entitlement is exceeded. Without a contractual top-up rate, SAP will apply list price to overruns.

Price Escalation Caps

SAP's standard GROW contracts include annual price escalation clauses tied to CPI or SAP's own metrics. In 2024 and 2025, these clauses triggered increases of 4–8% per year. Negotiate a hard cap on annual price escalation — ideally at CPI or a fixed low percentage — before signing.

Upgrade Testing Support

If you have BTP extensions, negotiate for SAP's support in quarterly upgrade testing — either through included professional services days or a preferential rate for SAP-delivered regression testing services. This is especially important if your organisation lacks a dedicated SAP development team.

Exit and Migration Rights

Negotiate the right to export your data in standard formats and the terms under which you can migrate to RISE with SAP (or away from SAP entirely) at the end of the initial contract term. SAP's standard terms make it difficult and expensive to exit — ensuring clear data portability and migration support provisions protects you if business requirements evolve. For a full treatment of SAP contract clause risks, see our article on SAP Enterprise Agreement traps.

If you are currently in active GROW negotiations, our SAP contract negotiation service can join your commercial discussions as an independent buyer-side advisor. We know SAP's playbook because we built it — and we know exactly where the negotiating room is. Read our comprehensive RISE with SAP guide for broader context on SAP's cloud commercial strategy.

Is GROW with SAP only for small companies?

SAP markets GROW to mid-market companies, typically in the range of €100M to €1B revenue, though there is no hard revenue cap. Larger enterprises occasionally select GROW for subsidiary deployments or newer business units where process standardisation is achievable. The key constraint is S/4HANA Cloud Public Edition's standardisation — if your business requires custom code or highly differentiated processes, RISE with SAP is the more appropriate option regardless of company size.

Can you customise S/4HANA Cloud Public Edition in GROW?

Customisation in S/4HANA Cloud Public Edition is restricted. Core application code cannot be modified. Extensions must be built in the side-by-side extensibility model using BTP's SAP Build and Cloud Application Programming (CAP) framework. This keeps the core clean for mandatory upgrades but shifts complexity and cost into BTP. Heavy use of side-by-side extensibility can significantly increase BTP consumption charges and implementation effort.

What happens at the end of a GROW contract term?

At the end of a GROW contract term, you enter renewal negotiations with SAP. SAP's commercial team will typically propose a price increase based on user count growth and any add-ons accumulated during the term. The leverage available to buyers at renewal includes competitive alternatives (Microsoft Dynamics, Oracle NetSuite, Infor) and the credible threat of a long, expensive migration. Engaging an independent SAP licensing advisor before renewal negotiations begin is highly recommended.

How does GROW licensing differ from classic SAP on-premise licensing?

On-premise SAP licences are purchased outright (perpetual) with an annual maintenance fee of 22% of net licence value. GROW is a subscription — you pay annually or as a multi-year commitment, with no perpetual ownership. The long-term cost profile varies significantly: perpetual licences may be cheaper over 10+ years if you maintain stable user counts, while subscriptions offer more flexibility and include infrastructure. Subscription contracts also expose you to SAP's ability to reprice at renewal, which perpetual licences do not.

Does GROW with SAP include SAP SuccessFactors or Ariba?

No. SAP SuccessFactors (HR), SAP Ariba (procurement), SAP Concur (expenses), and SAP Fieldglass (contingent workforce) are separate products with separate licences and subscription fees. They are not included in GROW with SAP. SAP's pre-sales teams may discuss these products in the context of GROW, but any inclusion requires specific commercial negotiation and will add to total contract value.