RISE with SAP is marketed as a single contract, single vendor, single price. In practice, it bundles S/4HANA Private Edition or Cloud, SAP BTP credits, Business Process Intelligence, and infrastructure into a deal structure that obscures true cost, locks you into SAP's pricing escalators, and embeds commercial terms most enterprises don't read until they're already signed. This guide tells you what is actually inside a RISE proposal — and how to negotiate it.
RISE with SAP, launched in 2021, is SAP's answer to a problem SAP helped create: the complexity of migrating a large on-premise SAP ECC landscape to S/4HANA. Rather than sell you licences, infrastructure, implementation services, and support separately, RISE bundles many of these components into a single subscription contract.
From SAP's perspective, RISE accelerates cloud adoption, increases recurring revenue, and reduces customer attrition by locking enterprises into long-term subscriptions. From your perspective, RISE can genuinely simplify vendor management — but only if you understand exactly what you are signing, what you are not getting, and what will cost you extra once you are locked in.
RISE is built around two delivery paths. S/4HANA Private Edition (formerly HEC) runs your S/4HANA instance on a hyperscaler infrastructure chosen from SAP's approved list: AWS, Azure, Google Cloud, or Alibaba Cloud. S/4HANA Cloud, public edition is SAP's full multi-tenant SaaS offering — standardised, highly restricted, and appropriate only for organisations willing to adopt SAP's best-practice processes with minimal customisation. Most large enterprises take Private Edition.
SAP's RISE marketing materials list an impressive array of inclusions. The reality is more nuanced. Many components are included in name but restricted in scope, and the definition of what is "included" versus what requires additional purchase can change at contract renewal.
| Component | Status | What to Know |
|---|---|---|
| S/4HANA Private Edition licences | Included | Named user licences within agreed scope. Additional users require contract amendment and typically trigger price escalation. |
| SAP BTP credits | Included | A defined credits allocation per year. 70% of customers never fully consume these. Credits do not roll over and expire annually — check your BoM carefully. |
| SAP Business Network Starter | Included | Starter tier only. Full supplier network access and advanced features require separate Ariba procurement. |
| SAP Business Process Intelligence | Included | Process mining and benchmarking tools. Useful for identifying S/4HANA migration readiness, but the data it generates is shared with SAP's commercial team. |
| Infrastructure (hyperscaler) | Included | Managed by SAP on your chosen hyperscaler. Sizing is agreed at contract start — if you undersize, costs increase. Negotiate sizing assumptions in writing. |
| Enterprise Support | Included | At 22% of licence value annually. You cannot opt down to Standard Support within RISE. This is one of the largest hidden cost components. |
| SuccessFactors, Ariba, Concur | Extra Cost | LoB SaaS applications are NOT included in RISE. Each requires a separate subscription. SAP's bundling narrative often implies more than is contractually true. |
| Implementation services | Not Included | RISE does not include the cost of migrating your ECC landscape to S/4HANA. This is the single largest cost in most RISE programmes — often 3–5× the annual subscription. |
| Custom development / extensions | Not Included | Any custom code must be re-engineered as BTP extensions. Depending on your current landscape, this is a significant additional investment. BTP consumption costs are additive. |
Our RISE with SAP advisory team has reviewed over 50 RISE proposals. We build a true Total Cost of Ownership model that includes implementation, BTP consumption, hidden escalators, and the LoB applications SAP's proposal left out. Book a proposal review before you sign.
Get a Free RISE Proposal Review →RISE pricing is subscription-based, structured around Named Users and additional metric-based consumption for BTP and other components. Understanding the pricing levers is essential before you enter any negotiation with SAP's commercial team.
S/4HANA in RISE is still licence-counted by Named User types: Professional, Limited Professional, Employee, and Developer. The RISE subscription wraps these into an annual fee, but the underlying user metric remains the same. Overstating your user count in the initial sizing (which SAP's sales team will encourage to maximise deal size) locks you into a higher baseline for all future renewals.
HANA database sizing, memory, and compute capacity are agreed at contract inception. SAP uses a "T-shirt sizing" model that often rounds up significantly. If your landscape grows faster than projected, you pay consumption overages. If it grows slower, the credits and headroom you've bought expire unused. Independent sizing analysis before contract signature is essential.
RISE contracts include annual price escalation clauses — typically 3–5% per year, often linked to an index. Over a 5-year term, a 4% annual escalation adds over 22% to your total cost. These clauses are negotiable before signature and nearly impossible to re-open post-signature.
SAP Business Technology Platform is consumed via credits included in RISE. When you exhaust these credits — for integration, extension, analytics, or automation workloads — you pay consumption-based overages at list price. BTP list pricing is substantially above what you can negotiate at contract inception.
The most significant architectural decision within RISE is whether to take S/4HANA Private Edition (the successor to HEC) or S/4HANA Cloud, public edition. These are fundamentally different products with fundamentally different commercial and operational implications.
Your S/4HANA instance runs on SAP-managed infrastructure (AWS, Azure, GCP, or Alibaba) in a dedicated environment. You retain the ability to customise processes, maintain existing integrations with modifications, and control your upgrade schedule to a degree. Enterprise Support at 22% applies. This is the right choice for most large, complex enterprises with significant customisations.
Best for: Complex landscapes, manufacturing, regulated industries, high customisation
A true multi-tenant SaaS delivery. Updates are applied automatically on SAP's schedule (twice yearly). Customisation is restricted to BTP-based extensions. Standard business processes must be adopted largely as-delivered. Costs are typically lower than Private Edition, but the operational constraints are significantly greater.
Best for: Greenfield deployments, subsidiaries, organisations adopting SAP's standard processes without legacy complexity
The licensing implications of this choice are substantial. Private Edition retains a Named User model. Public Edition introduces role-based user types that may differ from your current on-premise entitlements. Understanding the user count impact of moving from ECC to either S/4HANA variant is a core component of any RISE financial analysis.
RISE contracts are SAP's most complex and commercially significant deals. SAP commits significant pre-sales resource to RISE proposals precisely because the 5-year subscription revenue is material to SAP's cloud revenue targets. That creates negotiating leverage — but only if you use it before signature, not after.
SAP's pre-sales team will size your infrastructure requirements generously. Every MB of excess HANA memory you commit to is an annual cost that compounds over the contract term. Engage independent sizing expertise to produce a bottom-up infrastructure model before entering commercial discussions.
Negotiate a maximum annual price escalation — ideally below 2% and capped at CPI. SAP's standard RISE T&Cs include uncapped or index-linked escalation. Over five years, the difference between 2% and 4% compounding is material. This clause is negotiable before signature.
Negotiate a BTP credit allocation that matches your modelled consumption — not SAP's default inclusion. Then negotiate a contractual right to roll over unused credits between years. SAP's default position (credits expire annually) means you pay for value you never receive.
If you plan to contract for SuccessFactors, Ariba, or Concur within the RISE programme period, negotiate pricing for these products at deal signature — even if you don't plan to deploy them immediately. RISE is SAP's biggest negotiating moment; use it to lock in pricing across your full cloud estate.
SAP's RISE contracts are notoriously difficult to exit mid-term. Negotiate data portability rights, migration assistance obligations, and contractual remedies if SAP fails to meet SLA commitments before you sign. Once signed, these provisions are nearly impossible to add.
SAP's quarter-end and year-end periods (March, June, September, December) see the deepest discounting as SAP's sales team pushes to hit revenue targets. A deal signed on December 31st will often achieve discounts of 15–25% higher than the same deal signed in October. Use this timing deliberately.
Our SAP contract negotiation team has negotiated RISE deals with enterprises across all industries. We know SAP's playbook, their discount waterfall, and where they have room to move — and where they don't.
Our RISE advisory team reviews your proposal line by line, models the true 5-year TCO, and prepares a negotiation brief that identifies every commercial lever available to you. Enterprises that engage us before signing save an average of 25–35% on their RISE total contract value.
Book a RISE Contract Review →The period between signing a RISE contract and going live on S/4HANA — which typically runs from 18 months to 3 years for complex landscapes — creates a dual-running cost problem. You are paying RISE subscription fees while still operating your ECC landscape on-premise.
This parallel running period is one of the most significant budget risks in any RISE programme, and it is rarely modelled accurately in the initial business case. Key licensing considerations include:
On-premise ECC maintenance fees during migration. If you have existing ECC licences under a perpetual model, your 22% maintenance fee continues through the migration period. SAP will not waive this in parallel with RISE subscription fees without specific contractual negotiation — but it is possible to negotiate a maintenance reduction or conversion credit if you engage early.
ECC extended maintenance (2027 and beyond). SAP mainstream maintenance for ECC ends in 2027. If your S/4HANA go-live slips beyond this date — which is common in complex migrations — you face either extended maintenance fees (at a premium) or an accelerated migration with associated quality risks. Plan for this explicitly in your RISE negotiation. See our S/4HANA migration licensing guide for a detailed analysis of the 2027 deadline implications.
User licence reconciliation at go-live. The user count that appears in your RISE contract at signature should be validated against your actual go-live user population before your first renewal. Users who were counted in the initial RISE baseline but who will not use S/4HANA should be reclassified or removed. This is a negotiation that must happen at the first renewal — not assumed to happen automatically.
SAP's ECC mainstream maintenance deadline creates genuine urgency for organisations that have not yet committed to S/4HANA. SAP's sales team is using this deadline aggressively to accelerate RISE signings. The deadline is real, but the urgency is being used to reduce your negotiating window. Independent analysis of your migration timeline and options gives you the facts you need to negotiate from a position of strength rather than panic.
Renegotiating a RISE contract post-signature is possible but significantly harder than negotiating before signature. The primary opportunities to reopen commercial terms arise at renewal (typically at 3 or 5 years), when you add significant new users or modules, or when SAP changes the product scope in a way that affects your consumption. The most effective time to negotiate is always before signature, when SAP needs the deal most.
Over a 5-year horizon, RISE typically costs more than perpetual licences plus infrastructure, if you model accurately. The value proposition of RISE is not primarily cost — it is vendor consolidation, managed infrastructure, and a defined migration path. If cost is your primary driver, a hybrid approach (perpetual licences on third-party cloud infrastructure) often produces better TCO outcomes. The right answer depends on your specific landscape, risk appetite, and internal infrastructure capability.
SAP will typically credit a proportion of your existing on-premise licence investment against the RISE subscription — this is called a "trade-in" or "licence credit" mechanism. The credit terms are negotiable and vary significantly based on your licence type, the product mix, and your commercial relationship with SAP. Perpetual licences do not automatically convert to RISE subscriptions; the credit must be explicitly structured in the RISE contract.
SAP Business Technology Platform is SAP's cloud development and integration platform. In RISE, it replaces the traditional on-premise extension model — if you want to build custom functionality on top of S/4HANA in the cloud, you do it on BTP. The BTP credits included in RISE sound generous, but 70% of customers fail to fully consume them, and when you do exceed your credit allocation, you pay BTP consumption pricing at rates that are substantially above what you could have negotiated at contract inception.
No. RISE does not include the cost of migrating your ECC landscape to S/4HANA. Implementation is a separate engagement with SAP or your SI of choice. For complex ECC landscapes, implementation costs typically range from 2× to 5× the annual RISE subscription. This is the most frequently misunderstood aspect of RISE — the "simplification" of RISE covers the ongoing subscription, not the cost of getting there.
RISE Private Edition supports AWS, Azure, Google Cloud, and Alibaba Cloud. You select a preferred hyperscaler, but the infrastructure is managed by SAP — you do not have direct access to manage or right-size the environment yourself. This is a significant change from self-managed cloud deployments and affects your ability to control infrastructure costs, performance tuning, and data sovereignty. Negotiate your hyperscaler preference and infrastructure specifications in the contract, not informally with your SAP account team.
Our RISE advisory team reviews every clause, models the true TCO, and builds your negotiation strategy. We work exclusively for buyers — we have no SAP revenue, no reseller agreement, and no incentive to close a deal that isn't right for you.