What Is SAP RISE and How It Differs from Traditional Licensing
RISE with SAP is delivered as a single subscription contract that bundles SAP S/4HANA Cloud (your core ERP in the public or private cloud), cloud infrastructure hosted on a hyperscaler of your choice (AWS, Azure, or GCP), managed services including system availability, technical support, and updates, SAP Business Technology Platform (BTP) credits for extensions and integrations, and a Business Network Starter Pack (Ariba). Instead of purchasing perpetual licences and running SAP on your own infrastructure, you pay SAP an annual subscription fee to provide and operate the entire stack under a single SLA. SAP takes responsibility for system availability, upgrades, and technical operations — shifting its role from software vendor to full-service provider.
The shift from traditional licensing is fundamental. Under the traditional model, enterprises bought perpetual licences (CapEx), paid annual maintenance (22% of licence value), and managed their own infrastructure and operations. With RISE, licensing moves to a subscription (OpEx) model — you do not own the software outright. SAP introduced the Full User Equivalent (FUE) metric for RISE, which consolidates the traditional named user types (Professional, Limited Professional, Developer, etc.) into a single flexible metric. This simplifies licence management but also makes direct cost comparison with on-premises licensing more complex. Infrastructure and basic technical services are included in the subscription price, eliminating separate hosting or data centre costs but also bundling SAP’s margin into a single line item that is harder to benchmark component-by-component.
“RISE with SAP is not mandatory — it is one option for obtaining S/4HANA. You can still run S/4HANA on-premises or in the cloud without RISE. Understanding RISE’s value relative to these alternatives is essential before committing. The enterprises that achieve the best RISE outcomes are those that decompose the bundle, benchmark each component independently, and negotiate from a position of informed comparison rather than accepting SAP’s packaged pricing at face value.”
Key Choices Before Committing to RISE
Before entering RISE negotiations, CIOs and procurement teams must make several foundational decisions that directly affect both cost and operational flexibility.
Public Cloud vs Private Cloud Edition
Public Cloud (multi-tenant) offers standardised processes and lower cost but limited customisation. Private Cloud Edition (single-tenant) allows more customisation and is typically chosen by enterprises with complex, industry-specific configurations. Private Edition is priced approximately 20–25% higher. The choice fundamentally affects both flexibility and cost trajectory. See RISE Private vs Public Cloud.
Contract Length and Renewal Terms
RISE contracts are typically 3 or 5 years. Longer terms yield better pricing (5–10% additional discount) but reduce flexibility. Before committing to a 5-year term, ensure you understand and have negotiated the renewal conditions — including escalation caps, true-down rights, and the ability to renegotiate scope at renewal. A 3-year term with strong renewal protections may be preferable to a 5-year term with weak ones.
Perpetual Licence Conversion Strategy
Existing SAP customers must decide how to handle perpetual licences. SAP offers credits or incentives to convert, but surrendering perpetual rights creates dependency. Evaluate the trade-in value carefully — the credits SAP offers for perpetual licence conversion are typically 30–50% of the licence’s book value. Consider retaining perpetual rights as an exit strategy. See RISE Impact on Existing Licences.
Additional decisions include hyperscaler selection (AWS, Azure, or GCP — based on latency, data residency, and existing cloud relationships), included services scope (clarify whether dev/QA environments, disaster recovery, and enhanced support are included or additional), and BTP credit allocation (understand how many credits are included and whether they cover your planned extension and integration requirements). Each decision affects the total cost and should be resolved before negotiation begins.
SAP RISE Negotiation Strategies
Entering a RISE contract involves negotiating software, cloud services, and managed operations simultaneously — a fundamentally different negotiation from traditional SAP licence purchases. The following areas are critical.
Pricing and discounts. RISE pricing is quoted as an annual subscription based on FUE count and selected services. Push for transparency — ask SAP to decompose the subscription into software, infrastructure, and services components so you can benchmark each independently. SAP typically has 20–35% pricing flexibility, especially when competing against a credible on-premises or self-managed cloud alternative. Use your existing ECC maintenance spending as leverage — SAP’s internal business case for RISE depends on converting maintenance revenue to subscription revenue, and they will often discount aggressively to win the conversion. Ensure that any additional FUE purchases during the term inherit the same discount percentage as the initial deal.
Renewal and escalation caps. These are arguably the most critical terms in the entire agreement. Without a negotiated cap, SAP can increase fees significantly at renewal when you are already dependent on the platform. Negotiate a fixed annual escalation cap — target 3% or less (SAP often proposes 5–8%). Require that SAP provide renewal pricing at least 6 months before term expiration. Include a clause that renewal pricing cannot exceed the current subscription plus the cumulative escalation cap — preventing SAP from resetting to list price at renewal. These protections are non-negotiable for any well-structured RISE deal. See SAP Contract Negotiation Service.
Usage flexibility and scaling. Negotiate predefined rates for adding FUEs, additional environments, or BTP credits during the term. Equally important, discuss options for downsizing — SAP’s standard terms typically do not allow mid-term reductions, but you may negotiate annual true-down rights (e.g., the ability to reduce FUE count by up to 15% at each anniversary) or the ability to repurpose unused subscriptions between modules. For enterprises with M&A activity, ensure the contract accommodates entity additions and divestitures.
Service Level Agreements. SAP’s standard RISE SLA (approximately 99.5% uptime) may not meet your business requirements. Negotiate a higher SLA (99.7–99.9%) for production environments if your operations require it. More importantly, ensure the SLA includes meaningful financial remedies — not just service credits, but escalation to termination rights for sustained SLA failures. Clarify support response times for Priority 1 (critical) issues and ensure they are contractually binding, not aspirational.
Exit and termination terms. Plan for a possible exit before you sign. Negotiate data portability rights (your data in a standard, machine-readable format with reasonable extraction timelines), transition assistance provisions at end of term, and ideally the right to purchase a perpetual S/4HANA licence at the end of the contract as a fallback. If you are surrendering perpetual licences as part of the RISE conversion, the exit terms become even more critical — without perpetual fallback rights, you have no alternative to renewal on SAP’s terms. See RISE vs BYOL Contractual Differences.
Cost Analysis: Decomposing the RISE Bundle
RISE pricing bundles multiple cost components into a single subscription line item. To evaluate whether RISE represents good value, you must decompose the bundle and benchmark each component independently.
| Cost Component | What It Covers | Benchmark Approach |
|---|---|---|
| Software subscription | S/4HANA licence rights (replaces perpetual licence + maintenance) | Compare against perpetual licence amortisation + 22% maintenance over the contract term |
| Infrastructure & hosting | HANA database instances, compute, storage, backups, environments | Price equivalent resources directly on AWS/Azure/GCP for comparison |
| Managed services | System monitoring, patching, upgrades, basic administration | Obtain quotes from managed service providers (MSPs) for equivalent scope |
| BTP credits | Platform credits for extensions, integrations, analytics | Assess actual planned consumption vs allocated credits — unrealised credits are wasted value |
| Business Network | Ariba starter pack (basic documents/trading partners) | Estimate actual procurement network usage — heavy use requires additional fees beyond starter |
| Implementation (not included) | Data migration, integration, testing, change management | Budget separately — RISE does not include implementation services |
The critical comparison is RISE subscription total vs the sum of the individual components purchased independently. If your analysis shows that self-managed S/4HANA on a hyperscaler with a third-party MSP is 15–25% cheaper, you have strong negotiation leverage — and SAP will typically close the gap to win the deal. Conversely, if RISE is cost-competitive after accounting for reduced internal IT operations burden, the convenience premium may be justified. The key principle is that you cannot evaluate RISE pricing without decomposing it first.
RISE vs On-Premises vs Self-Managed Cloud
To make an informed commitment, compare RISE against two alternatives: retaining SAP on-premises (with eventual S/4HANA migration) and running S/4HANA on a hyperscaler without RISE (self-managed or MSP-managed).
Vendor-Managed Cloud (Single Contract)
Pros: Single contract and accountability, faster time to S/4HANA value, reduced internal infrastructure burden, automatic access to innovation and upgrades, predictable OPEX. Cons: Potentially 15–30% higher total cost (you pay for convenience and SAP’s margin), loss of perpetual licence ownership, dependency on SAP for environment standards and timelines, limited customisation in Public Cloud edition, risk of renewal price increases without strong contractual protections.
Traditional Perpetual Licence Model
Pros: Full ownership of licences (CapEx asset), maximum control over environment, customisation, and upgrade timing, no dependency on SAP for infrastructure, lower annual cost if hardware is amortised. Cons: Requires internal infrastructure and operations capability, periodic hardware refresh costs, upgrade project costs every 5–7 years, SAP’s 2027 maintenance deadline creates pressure to migrate. See Managing ECC Maintenance Before 2027.
S/4HANA on AWS/Azure/GCP (BYOL or New Licence)
Pros: Retain licence ownership while benefiting from cloud infrastructure, choice of hyperscaler and MSP independently, potentially 15–25% lower cost than RISE for equivalent scope, full control over environment configuration and customisation. Cons: Multiple vendor relationships to manage, requires internal or MSP capability for SAP operations, upgrade responsibility remains with the customer. See RISE vs Own Infrastructure Cost Comparison.
For a robust comparison, conduct a multi-year TCO analysis covering at least the proposed RISE contract term. Include all subscription fees plus projected overage costs for RISE, licence amortisation plus maintenance plus infrastructure plus personnel for on-premises, and licence costs plus hyperscaler bills plus MSP fees plus internal operations for self-managed cloud. The analysis should also account for the opportunity cost of surrendering perpetual licences (which have residual value) and the risk premium of vendor lock-in under RISE.
Specific Contract Clauses to Negotiate
Beyond pricing, several contractual provisions require careful attention in any RISE negotiation.
Bundling and scope definition. The contract must explicitly list every product, service, and environment included. Verify whether dev/QA/sandbox environments are included or additional, whether disaster recovery is covered, and whether interface maintenance and monitoring are in scope. Ambiguities resolved in SAP’s favour after signing are expensive to correct.
Price escalation mechanics. If the contract includes an automatic annual uplift (e.g., 3% per year), try to remove or minimise it. If escalation is unavoidable, ensure it is applied to the base subscription only (not to any additions purchased during the term at already-current rates). Negotiate that additional FUE purchases inherit the same discount percentage as the initial deal, preventing SAP from charging higher rates for growth.
Data ownership and portability. Ensure the contract affirms that your data is yours and that you can obtain a complete copy in standard, machine-readable format at any time — not only at contract end. For custom developments on BTP, ensure you retain intellectual property rights even if you leave RISE. These provisions are essential for exit planning and regulatory compliance.
Renewal notice requirements. Include a clause requiring SAP to provide written renewal pricing at least 6 months (ideally 9–12 months) before term expiration. This gives you time to evaluate, benchmark, negotiate, or plan an alternative — avoiding the last-minute pressure that favours SAP in renewal discussions.
Liability and compliance. Review how responsibilities are allocated for data breaches, compliance failures, and service outages. SAP’s standard contracts limit their liability significantly. For regulated industries (financial services, healthcare, government), negotiate specific compliance commitments and audit rights that align with your regulatory obligations.
Recommendations for CIOs and Procurement
Based on our experience advising enterprises on RISE negotiations across multiple industries and geographies, we recommend the following approach.
1. Decompose before you negotiate. Break the RISE bundle into its component parts and benchmark each independently. Price equivalent infrastructure on your preferred hyperscaler. Obtain MSP quotes for managed services scope. Calculate the perpetual licence plus maintenance equivalent for the software subscription. This analysis gives you the informed baseline that makes meaningful negotiation possible.
2. Maintain a credible alternative. SAP negotiates most aggressively when the customer has a credible alternative — whether that is staying on-premises, running S/4HANA on a hyperscaler without RISE, or considering a third-party support provider to extend ECC beyond 2027. The alternative does not need to be your preferred outcome — it needs to be credible enough that SAP believes you would pursue it. This leverage is the single most important factor in securing competitive RISE pricing.
3. Prioritise renewal protections over initial pricing. An attractive first-year price means little if it doubles at renewal. Cap annual escalation at 3% or less, require advance notice of renewal pricing, and negotiate that renewal pricing cannot exceed the current subscription plus cumulative escalation. These terms protect you when SAP has maximum leverage (at renewal, when you are already dependent on the platform).
4. Negotiate exit terms before you sign. Data portability, transition assistance, and ideally the right to purchase a perpetual licence at contract end should be negotiated upfront. Once you have surrendered perpetual licences and moved to RISE, your negotiating position on exit terms diminishes dramatically.
5. Right-size before you commit. Conduct a thorough user access review before determining FUE requirements. Many enterprises over-provision RISE subscriptions based on current named user counts without assessing whether all users are active or whether their roles justify the assigned licence type. Right-sizing FUE requirements before negotiation reduces the subscription base against which all other costs are calculated. See SAP Named User Licence Optimisation.
6. Engage independent advisory support. RISE negotiations involve software licensing, cloud infrastructure pricing, managed services scope, and multi-year commercial terms simultaneously. This is not a standard procurement exercise. Independent advisory firms with SAP negotiation expertise and access to benchmarking data can identify 20–35% savings opportunities that internal teams without comparable deal data would miss. The advisory fee is typically recovered many times over in improved deal terms.