SAP RISE Negotiation: Evaluating the Bundled Cloud Offer on Your Terms
A procurement framework for unpacking RISE's opaque pricing, benchmarking every component, and securing contractual protections across a long-term subscription commitment.
Executive Summary
RISE with SAP is SAP's flagship commercial vehicle for converting its installed base from perpetual on-premise licences to cloud subscriptions. It packages S/4HANA Cloud, hyperscaler infrastructure, Business Technology Platform, transformation services, and Business Process Intelligence into a single bundled subscription — and SAP is positioning it as the preferred, and eventually only, path forward for enterprise SAP customers.
The bundle is commercially elegant from SAP's perspective: it obscures per-component pricing, creates multi-layered dependency, locks in long-term subscription revenue, and makes it structurally impossible for procurement teams to benchmark individual elements against market alternatives. For buyers, this opacity translates directly into overspend — and the long-term contractual commitment means that overspend compounds over 3–5 years.
This paper unpacks the RISE commercial model in full. It identifies where genuine negotiation flexibility exists within the bundle, maps the service quality and exit provisions that most procurement teams overlook, and delivers a framework for securing RISE terms that protect your commercial interests across a long-term subscription commitment.
Five Key Findings
Anatomy of the RISE Bundle
Understanding what you are actually buying when you sign a RISE contract is the prerequisite for effective negotiation. The bundle contains five distinct commercial components, each with independent market pricing, independent delivery mechanisms, and — critically — independent negotiation surfaces. SAP's commercial strategy depends on these components remaining opaque and bundled. Your procurement strategy depends on unpacking them.
The "One Contract" Illusion
SAP markets RISE as the simplicity of a single contract and single vendor relationship. In practice, the single contract obscures multiple delivery chains. Infrastructure is delivered by a hyperscaler (not SAP). Transformation services vary dramatically in scope and quality. BTP credits deplete on unpredictable consumption curves. And the S/4HANA subscription itself carries different terms depending on whether you are on Private Cloud Edition (customer-specific instance) or Public Cloud Edition (multi-tenant).
The "one contract" is not a simplification — it is a consolidation that eliminates your ability to hold individual delivery components to independent commercial and performance standards. The first step in RISE negotiation is recognising this and insisting on component-level transparency.
"SAP calls RISE a 'business transformation as a service.' Procurement should call it what it is: five independent purchases wrapped in a single opaque contract. Unwrap it before you negotiate it."
— Redress Compliance, SAP PracticeUnbundling & Component Pricing
The most effective RISE negotiation strategy is to request — and if necessary, insist on — per-component pricing for every element of the RISE bundle. Then benchmark each component independently against market alternatives. The delta between the RISE bundle price and the sum of competitively-priced components is your negotiation target.
Component-Level Benchmark Approach
| Component | RISE Embedded Cost | Market Alternative Cost | Typical Delta |
|---|---|---|---|
| S/4HANA Subscription | $3,800–$5,200/FUE/yr (within bundle) | $2,800–$3,800/FUE/yr (standalone negotiated) | 20–30% above standalone |
| Infrastructure | SAP-managed; opaque pricing within bundle | Direct hyperscaler: 30–60% lower for equivalent compute/storage | 30–60% markup |
| BTP Credits | Included allocation; overage at rate card | Standalone BTP procurement: 35–50% below rate card with volume commitment | 35–50% above standalone |
| Transformation Services | Bundled; scope varies; quality variable | Independent SI or direct SAP services: scope-specific, competitively bid | Variable — scope clarity is the issue |
| Signavio / BPI | Included in RISE | Standalone Signavio: $15–$25/user/mo. Alternative: Celonis at competitive pricing | Low — but may not be needed at all |
The Unbundling Playbook
Ask SAP to provide a detailed cost allocation showing the proportion of total RISE fees attributable to each component. SAP will resist this request. Persist — and if necessary, make contract signature conditional on receiving component-level pricing transparency.
Price S/4HANA subscription as a standalone product. Obtain direct hyperscaler quotes for equivalent infrastructure. Price BTP as a standalone commitment. Evaluate Signavio against Celonis or other process mining tools. Build the bottom-up cost model.
The difference between SAP's RISE bundle price and your independently-benchmarked component total is the embedded margin. Present this analysis to SAP's commercial team as your negotiation starting point. Target 25–40% reduction from initial RISE pricing.
For the highest-markup components — particularly infrastructure — negotiate the right to procure directly from the hyperscaler while maintaining S/4HANA subscription through RISE. SAP resists this structure but has approved it for strategic accounts under competitive pressure.
"SAP will tell you the bundle can't be unbundled. It can. They will tell you per-component pricing isn't available. It is. They will tell you infrastructure carve-outs aren't possible. They are. Everything SAP says is non-negotiable has been negotiated before. We've seen it."
— Redress Compliance, SAP Practice LeadInfrastructure: Choice vs. Lock-In
Infrastructure is where RISE extracts its deepest margin — and where the most significant cost reduction opportunity exists. SAP procures hyperscaler capacity at enterprise discount rates and resells it within RISE at a 30–60% premium. The customer has no visibility into SAP's infrastructure costs, no direct relationship with the hyperscaler for the RISE workload, and no contractual right to migrate to self-managed infrastructure during the agreement term.
The Infrastructure Markup
SAP offers three hyperscaler options within RISE: Microsoft Azure, Amazon Web Services, and Google Cloud Platform. The customer selects the hyperscaler, but SAP manages the relationship, provisioning, and billing. This management layer is the justification for SAP's infrastructure markup — but the markup consistently exceeds the cost of equivalent managed services available directly from the hyperscalers.
| Infrastructure Element | Direct Hyperscaler Cost | RISE Embedded Cost | SAP Markup |
|---|---|---|---|
| Compute (S/4HANA production) | $0.08–$0.15/vCPU-hr (reserved) | Opaque — embedded in bundle | Est. 40–60% above direct |
| Storage (production + DR) | $0.018–$0.023/GB-mo (managed disk) | Opaque — embedded in bundle | Est. 30–50% above direct |
| Networking / Egress | $0.05–$0.09/GB (standard egress) | Opaque — embedded in bundle | Est. 20–40% above direct |
| Managed DB (HANA Cloud) | Self-managed HANA on IaaS: significantly lower | Bundled in RISE subscription | Largest single premium within infra layer |
| Disaster Recovery | Configurable — pay for what you use | Standard DR tier included; enhanced DR additional cost | DR flexibility significantly limited within RISE |
Negotiation Strategies for Infrastructure
Negotiate the right to procure hyperscaler infrastructure directly while keeping S/4HANA subscription through RISE. This is the highest-impact single negotiation lever in a RISE deal. SAP will resist aggressively — be prepared to make this a deal-breaker condition to force escalation.
If carve-out is not achievable, negotiate "bring your own rate" provisions where your existing hyperscaler enterprise agreement pricing applies to RISE infrastructure costs. This preserves SAP's management role while eliminating the resale markup on raw compute and storage.
Negotiate a contractual cap on infrastructure costs as a percentage of total RISE fees. This prevents infrastructure cost escalation during the agreement term when workload growth increases compute and storage consumption beyond initial sizing assumptions.
Secure the contractual right to change hyperscaler providers during the RISE term without commercial penalty. SAP's standard terms effectively lock you to the initial hyperscaler selection. A replatform right creates ongoing competitive leverage on the infrastructure component.
SLAs & Service Quality Provisions
RISE with SAP includes service level agreements for system availability, performance, and support response. On the surface, these SLAs appear reasonable. Under scrutiny, they contain measurement methodologies, exclusion windows, and remedy limitations that significantly reduce their practical value. Negotiating meaningful SLA improvements is essential for any RISE commitment.
RISE SLA vs. Direct Hyperscaler Comparison
SLA Gaps You Must Negotiate
SAP measures availability monthly, excluding planned maintenance windows, upgrade periods, and customer-requested changes. Actual experienced availability can be significantly below the stated 99.7% SLA when exclusions are factored in. Negotiate measurement based on total calendar time with limited, capped exclusion windows.
Standard RISE SLA remedies are capped at 10% of monthly subscription fees as service credits. For a $5M annual RISE contract, the maximum SLA credit for a catastrophic month-long outage is approximately $42K — commercially insignificant. Negotiate uncapped penalties or meaningful remedies tied to business impact.
Standard RISE contracts include availability SLAs but not performance SLAs. System response time, batch processing throughput, and reporting performance are not guaranteed. Negotiate specific performance baselines tied to your key business transactions with escalation triggers for degradation.
SAP's support SLA guarantees response time, not resolution time. A Priority 1 incident may receive a response within 1 hour but not be resolved for days. Negotiate resolution time targets for P1 and P2 incidents with escalation triggers and executive engagement commitments.
"An SLA that caps financial remedies at 10% of monthly fees is not a service level agreement — it's a disclaimer. The remedy must be proportional to the impact, or it provides no incentive for the vendor to prevent outages."
— Redress Compliance, SAP PracticeExit Terms & Contract Flexibility
RISE creates new forms of dependency that, in some respects, exceed the lock-in of traditional on-premise SAP licensing. Under the perpetual model, you owned your licences indefinitely and controlled your infrastructure. Under RISE, you subscribe to both the application and the infrastructure — and when the subscription ends, you retain neither unless you've negotiated otherwise.
Standard RISE Exit Provisions
| Exit Provision | SAP Standard Terms | Negotiated Alternative |
|---|---|---|
| Data Extraction Period | 90 days post-termination. Data provided in SAP-determined format. No guaranteed export to customer-specified format. | 12 months post-termination. Data in industry-standard formats (SQL, CSV, Parquet). SAP-funded extraction assistance. |
| Transition Support | No contractual obligation. Customer responsible for migration to alternative platform. | 180 days of transition support included. SAP provides technical assistance for migration to self-managed or alternative platform. |
| Licence Conversion Right | No automatic right to convert subscription back to perpetual licence. Requires new licence agreement at current list pricing. | Contractual right to convert to self-managed S/4HANA with credit for subscription fees paid during RISE term. |
| Early Termination | Remaining contract value due in full upon early termination. No pro-rata refund provisions. | Early termination with 12-month notice, penalty limited to 50% of remaining annual fees. Or termination-for-convenience clause at 24-month mark. |
| Mid-Term Seat Reduction | No mid-term FUE reduction. Can only reduce at contract renewal. | Annual reduction right of up to 15–20% of FUE count with 90-day notice. Price-per-FUE maintained at original negotiated rate. |
| Renewal Pricing | Renewal at SAP's then-current pricing. No contractual commitment to renewal pricing parity. | Renewal pricing capped at 5% above initial contract rates. Or contractual right to renew at CPI-adjusted rates with 3-year lookback. |
The "Subscription Trap" — Why Exit Terms Matter More Than Entry Terms
RISE contracts are typically 3–5 year commitments. The commercial terms you negotiate at entry determine your position at renewal — and SAP's renewal leverage is directly proportional to how difficult it is for you to exit. Every exit provision you fail to negotiate at signing becomes a leverage point for SAP at renewal.
The critical insight is that exit terms are entry negotiations. The time to negotiate licence conversion rights, data portability, transition support, and early termination provisions is before you sign the RISE contract — not when you're trying to leave. Post-signature modification of exit provisions is functionally impossible.
"In perpetual licensing, you owned the asset. In RISE, you rent it. And the rental agreement's termination clause determines how much leverage SAP has over you for the next decade. Negotiate exit terms as if your future self depends on it — because they do."
— Redress Compliance, SAP PracticeRISE Negotiation Traps & How to Avoid Them
RISE is SAP's most commercially sophisticated product. The following traps represent the patterns that extract the most value from buyers — and each is paired with its counter-strategy.
SAP positions RISE's bundled pricing as a simplification: "one contract, one price, one vendor." In practice, the bundle obscures per-component margin, prevents benchmarking, and eliminates your ability to hold individual service elements to independent performance standards. Simplicity is the sales pitch. Opacity is the commercial strategy.
SAP presents infrastructure as an included component of RISE, implying it's provided at no additional cost. In reality, infrastructure represents 20–30% of the total RISE fee and is marked up 30–60% above direct hyperscaler pricing. The word "included" is doing heavy commercial lifting.
RISE includes a BTP credit allocation that appears generous at signing. SAP's BTP consumption model is designed so that integration, extension, and analytics workloads exceed the included allocation within 12–18 months. Overage is charged at published rate card pricing — which is 35–50% above the effective per-unit cost within the RISE allocation.
SAP positions RISE Private Cloud Edition as preserving your ability to maintain custom code and custom configurations. In practice, Private Cloud Edition runs on SAP-managed infrastructure with SAP-controlled upgrade cycles, meaning your customisations must pass SAP's compatibility checks — and SAP can require remediation or removal of custom code that conflicts with their upgrade schedule.
SAP sales teams increasingly position RISE as the only commercially available migration path. In reality, S/4HANA on-premise perpetual licences remain available, standalone S/4HANA Cloud subscriptions exist outside the RISE bundle, and GROW with SAP offers an alternative for organisations willing to accept Public Cloud limitations.
RISE standard terms include a 3.3% annual price escalation clause (CPI-linked). On a 5-year $5M annual contract, this escalation adds $835K in cumulative cost above Year 1 pricing. SAP presents this as standard market practice. In reality, escalation rates are negotiable and multi-year cloud contracts routinely include fixed pricing or capped escalation.
Recommendations: 7 Priority Actions
Based on the analysis presented in this paper, we recommend the following seven priority actions for organisations evaluating, negotiating, or about to sign a RISE with SAP contract.
Make component-level pricing disclosure a prerequisite for contract negotiation, not a request you make during it. You cannot negotiate what you cannot measure. Require SAP to allocate the total RISE fee across S/4HANA subscription, infrastructure, BTP, transformation services, and BPI — then benchmark each independently.
Obtain direct quotes from Azure, AWS, or GCP for your S/4HANA workload specifications. Present the delta between direct pricing and RISE-embedded infrastructure costs. Negotiate infrastructure carve-out, bring-your-own-rate, or, at minimum, a contractual infrastructure cost cap as a percentage of total RISE fees.
Reject the standard 99.7% availability SLA with 10% service credit caps. Negotiate 99.9%+ availability measured on total calendar time, performance SLAs for key business transactions, support resolution targets (not just response targets), and financial remedies that create genuine incentive for SAP to prevent outages.
Negotiate 12-month data extraction periods in standard formats, transition support commitments, licence conversion rights (subscription-to-perpetual with credit for fees paid), early termination provisions, and mid-term FUE reduction rights. Exit terms negotiated at signing are worth 10× the effort of trying to modify them post-signature.
Project BTP consumption across integration, extension, and analytics use cases for the full contract term. Negotiate credit rollover, overage at in-bundle rates (not rate card), and the right to purchase additional credits at the same per-unit cost. BTP overage is the most common source of post-signature cost surprise in RISE contracts.
SAP's standard 3.3% annual escalation adds $835K in cumulative cost on a 5-year, $5M/year contract. Negotiate fixed pricing or a 0–2% cap. This is pure contractual value — no operational change required, no technical dependency, no implementation work. Just better contract terms.
RISE negotiation requires component-level benchmarking data that procurement teams do not have access to. Independent advisors with current RISE deal data, per-component pricing benchmarks, and no SAP partnership or reseller affiliations achieve $3–5M better outcomes on a 5,000 FUE deal. The advisory fee is typically recovered 15–25× in improved terms.
How Redress Can Help
Redress Compliance is a 100% independent enterprise software licensing advisory firm. We maintain zero vendor affiliations, no SAP partnership agreements, no reseller arrangements, and no referral fee relationships with SAP or any SAP implementation partner. Our SAP Practice provides vendor-neutral RISE procurement advisory with deep, current benchmarking data from live RISE negotiations.
RISE Commercial Negotiation
End-to-end RISE negotiation support from initial proposal review through contract execution. Includes component unbundling, per-element benchmarking, infrastructure carve-out negotiation, SLA improvement, exit term structuring, and escalation management through SAP's deal desk hierarchy.
RISE Unbundling & Benchmarking
Detailed decomposition of your RISE proposal into per-component costs. Independent benchmarking of each component against market alternatives and Redress's anonymised RISE deal database. Delivers a data-driven negotiation target for every element of the bundle.
Infrastructure Cost Analysis
Independent assessment of RISE infrastructure costs against direct hyperscaler pricing. Includes infrastructure sizing validation, markup quantification, and negotiation strategy for carve-out, bring-your-own-rate, or infrastructure cost cap provisions.
SLA & Contract Review
Comprehensive analysis of RISE contractual terms — SLAs, exit provisions, escalation clauses, renewal pricing, custom code protections, and BTP overage terms. Provides specific redline recommendations based on negotiated outcomes from comparable deals.
BTP Consumption Modelling
Forward-looking consumption model for BTP across your integration, extension, and analytics requirements. Identifies where included allocation will be exceeded and quantifies overage exposure. Informs BTP credit pool and overage cap negotiation.
Competitive Alternative Evaluation
Structured evaluation of non-RISE alternatives — standalone S/4HANA Cloud, on-premise perpetual, GROW with SAP, or competitive ERP options — designed to create negotiation leverage even if RISE is the preferred outcome. The credible alternative is the most powerful negotiation tool available.
"We don't implement SAP. We don't resell SAP licences. We don't take referral fees from SAP or its partners. We work exclusively for our clients — in every RISE negotiation, every renewal, every audit. That independence is not a tagline. It's the structural foundation of effective advisory."
— Redress ComplianceBook a Meeting
Discuss your RISE evaluation or negotiation with a Redress advisor. No obligation, no vendor affiliations, no sales pitch — just an informed conversation about what's actually in the bundle and how to negotiate it properly.
Our SAP Practice team has direct, current experience negotiating RISE contracts across mid-market and enterprise organisations. We can provide an initial assessment of your RISE proposal, identify unbundling opportunities, and benchmark your pricing against comparable deals in a 30-minute introductory call.