Introduction: What CIOs and Procurement Leaders Need to Know About RISE

RISE with SAP is not a product. It is a commercial framework — a single subscription that bundles S/4HANA Cloud Private Edition software, hyperscaler infrastructure, cloud managed services, and a collection of additional SAP tools including SAP Signavio, SAP LeanIX, and SAP Business Technology Platform starter credits. SAP positions this bundle as a simplified path to cloud ERP, offering one contract, one vendor relationship, and one subscription price.

The simplification is real. The commercial implications, however, are substantial and require careful analysis. When you sign a RISE contract, you are simultaneously agreeing to a software subscription, an infrastructure commitment, a managed services scope, an indirect access settlement, a price escalation mechanism, and an exit framework — all in a single document, negotiated against a vendor whose account team is exclusively focused on maximising Annual Contract Value.

CIOs and procurement leaders who have navigated this negotiation effectively share a common characteristic: they treated the RISE negotiation as a strategic programme, not a procurement transaction. They assembled cross-functional teams, built independent commercial models, established benchmark references, and engaged SAP from a position of preparation and knowledge. This guide documents what that looks like in practice.

Part 1: Understanding the RISE Commercial Structure

What Is and Is Not Included in RISE

Understanding RISE requires disaggregating the bundle. The core RISE subscription includes SAP S/4HANA Cloud Private Edition software licences, hyperscaler infrastructure (AWS, Azure, or Google Cloud — SAP negotiates the hyperscaler relationship on your behalf), and SAP Cloud Managed Services covering basis operations, patching, and system availability. These three elements are non-negotiable components of every RISE deal.

The RISE bundle also includes a set of additional tools that vary by package tier. Current RISE packages include SAP Signavio (process analysis and redesign), SAP LeanIX (enterprise architecture management), SAP Master Data Governance, and a BTP starter credit allocation. Historically, SAP also offered Datasphere and certain AI tools in premium tiers; as of mid-2025, SAP restructured its cloud ERP packaging, removing some items from the base bundle and selling them as add-ons.

What RISE does not include — but organisations often assume it does — are third-party application licences (Vertex, Concur, SuccessFactors unless separately purchased), implementation and migration services (SAP's migration support is advisory, not delivery), and BTP consumption beyond the included starter allocation. These omissions consistently appear as budget surprises in underprepared RISE programmes.

The FUE Pricing Model

RISE subscriptions are priced using the Full Use Equivalent (FUE) metric. Rather than charging a flat per-user fee, SAP assigns each user type a FUE weight: Advanced users count as 1.0 FUE (full system access), Core users count as 0.2 FUE (limited functional access), and Self-Service users count as 0.05 FUE (basic interaction, such as employee self-service). The total subscription cost is the total FUE count multiplied by the contracted per-FUE rate.

The per-FUE list price for S/4HANA Cloud Advanced users is approximately $150 to $180 per user per month. Negotiated rates for large enterprise deals are significantly lower — typically $80 to $130 per FUE per month depending on volume, term, and competitive dynamics. The total annual subscription for a 2,000-user enterprise with a typical FUE mix can range from $4 million to $12 million per year depending on the FUE composition and the negotiated rate.

SAP account teams consistently propose FUE compositions that overweight Advanced users. Independent role analysis — mapping each named user's actual transaction patterns against S/4HANA user tier definitions — reliably identifies over-classification of 20 to 35 percent. This analysis must be completed before SAP presents its commercial proposal, because challenging the FUE composition after SAP has anchored the deal value is commercially and psychologically harder.

The DDLC Indirect Access Framework

Indirect access is the use of SAP data by third-party systems without direct user login. SAP measures this under the Document-Driven Licensing Concept (DDLC). The DDLC framework classifies indirect access by document type: each time a non-SAP system creates, reads, updates, or deletes a qualifying document in SAP — an order, an invoice, a delivery, a production order, a goods movement — SAP can assert that a Digital Access licence is required.

In a RISE context, indirect access transitions from the on-premise indirect access exposure to a Digital Access subscription line. This is commercially important for two reasons. First, the Digital Access subscription must be scoped and priced at contract origination; post-contract, SAP's account team conducts periodic consumption reviews and raises supplemental charges for undiscoped digital access activity. Second, the DDLC metric — document volumes by type — is inherently difficult for buyers to measure independently, which creates an asymmetric information environment that favours SAP in post-go-live disputes.

The strategic response is to complete a comprehensive integration mapping exercise before signing the RISE contract. This mapping should identify every third-party system that interacts with SAP, document the document types and estimated annual volumes for each interaction, and produce a Digital Access sizing that you propose as the contractual baseline. Requiring SAP to agree, in the contract, that the mapped scope is exhaustive eliminates the primary mechanism for post-go-live supplemental claims.

Part 2: Building the Pre-Negotiation Foundation

The Internal Alignment Requirement

The most common failure mode in RISE negotiations is internal misalignment within the buyer organisation. SAP's account team is experienced at identifying and exploiting disagreements between IT, procurement, finance, and legal stakeholders. When these functions are not aligned before negotiations begin, SAP navigates between them to find the path of least commercial resistance.

Before entering negotiations, assemble a cross-functional negotiation team with clear decision authority. IT provides technical requirements and migration timeline parameters. Procurement owns the commercial process and maintains the relationship with SAP's account team. Finance validates the TCO model and owns the budget authority. Legal reviews contract terms and flags risk exposures. One person — typically the CIO or a designated programme director — must have final decision authority and serve as the single point of contact for SAP's commercial team.

This team should define, in writing and before engaging SAP, four items: the technical minimum requirements (number of environments, BTP needs, infrastructure specifications), the maximum acceptable subscription cost with breakdown by component, the minimum acceptable contract terms (uplift caps, exit rights, DDLC scope), and the walk-away position — the point at which you will decline the deal and pursue an alternative path.

The TCO Baseline Model

SAP's ROI models for RISE consistently project significant total cost of ownership savings versus on-premise continuation. These models are not fraudulent, but they contain assumptions that systematically favour the RISE outcome. The assumed reduction in basis team headcount is typically overstated. The assumed elimination of hardware refresh costs is only valid for organisations with material infrastructure capital expenditure cycles. The assumed elimination of third-party maintenance costs requires the organisation to have actually been considering third-party maintenance, which is not universal.

Build your own TCO baseline before seeing SAP's model. Your model should project the five-year and seven-year cost of three scenarios: continued on-premise with current support arrangements, continued on-premise with third-party maintenance, and RISE at different subscription levels. This model becomes your reference point when SAP presents its commercial case and allows you to identify exactly where SAP's assumptions diverge from your actual cost structure.

The TCO model also serves as negotiating leverage. If your model shows that the RISE economics are marginal at SAP's initial price, that analysis gives you factual grounds for a lower price. If your model shows that third-party maintenance is viable and would reduce your on-premise cost materially, communicating that option signals a credible BATNA (Best Alternative to a Negotiated Agreement) that SAP will want to prevent.

Establishing Commercial Benchmarks

Your commercial position is strongest when you can reference market data. Benchmark data for RISE deals includes per-FUE subscription rates at different volume tiers, BTP credit pricing, Digital Access document pricing by document type, and the discount levels achieved by comparable organisations. This data is not publicly available from SAP, but it is available from advisors with RISE transaction experience.

Redress Compliance maintains current benchmark data across 80+ RISE engagements. The range of negotiated per-FUE rates for large enterprise deals spans a wide band — but the midpoint of well-negotiated deals is approximately 30 to 40 percent below SAP's initial proposal. Organisations that enter negotiations without independent benchmark data accept the first proposal as the market reference, which consistently results in above-market pricing.

Part 3: The RISE Negotiation Playbook

Phase 1 — Signal Preparation, Not Urgency

SAP's account team reads buyers' body language accurately. An organisation that expresses urgency to close, excitement about RISE, or pressure from a board or transformation programme timeline communicates reduced price sensitivity. An organisation that is visibly prepared — presenting its own FUE analysis, referencing benchmark data, asking specific questions about contract terms — communicates competence and reduces SAP's expectation of a quick close at above-market pricing.

In the first substantive commercial meeting, present your own FUE composition analysis before SAP presents its proposal. State clearly that you are evaluating RISE as one of several options — including third-party maintenance continuation and alternative migration paths — and that your decision will be based on the commercial terms achieved. This framing positions you as a prepared buyer with alternatives, which is the posture that extracts the best outcomes from SAP's commercial process.

Phase 2 — Negotiate the FUE Composition First

The subscription baseline is determined by FUE composition multiplied by the per-FUE rate. A 25 percent reduction in FUE count from Advanced to Core reclassification is more valuable than a 10 percent reduction in the per-FUE rate on the original FUE count. Negotiate FUE composition before negotiating rate, because SAP will attempt to concede rate in exchange for keeping the FUE count high.

Your FUE analysis should be role-specific, transaction-based, and documented. For each role category, identify the S/4HANA user type that corresponds to the actual transaction usage — not the aspirational access that IT administrators want to grant or that users request. Core user classification is appropriate for users who perform a limited set of transactions in a defined module; the Core user tier is a legitimate classification for a large proportion of enterprise user populations.

Phase 3 — Negotiate Annual Uplift Caps

RISE contracts include annual price escalation clauses. SAP's default mechanism is typically CPI-based or a fixed percentage in the three to five percent range. Over a five-year contract at $5 million per year base, a three percent annual uplift adds approximately $800,000 in cumulative cost. A five percent uplift adds approximately $1.4 million. Over seven years, these numbers are larger still.

The target negotiating position is a zero-uplift clause for the initial contract term, transitioning to a capped escalation mechanism at renewal. SAP will resist, but zero-uplift initial terms have been agreed on large strategic deals. Fallback positions include a cap of one to two percent per year (which is materially better than three to five percent) or a fixed dollar cap per year (which protects proportionately more value as the subscription grows).

Link the uplift negotiation to the broader deal structure. SAP may accept a zero-uplift provision in exchange for a longer initial term (seven years instead of five) or a larger initial FUE count. Evaluate these trade-offs carefully: a longer term reduces flexibility but may be commercially superior if the subscription cost is materially below market and the uplift protection is strong.

Phase 4 — Scope and Price Digital Access Explicitly

As covered in the DDLC section above, the Digital Access scope within your RISE contract must be explicitly defined, not left open-ended. Present your integration mapping as a proposed Digital Access schedule, specifying the included systems, document types, and volume parameters. Request that SAP confirm in the contract that this schedule is exhaustive and that no additional Digital Access charges will be raised for activity within the defined scope for the contract term.

SAP will typically seek to retain the right to audit and adjust Digital Access annually based on actual consumption. The counter-position is a fixed price for defined scope with an agreed mechanism for expansion if new integrations are added. This structure creates predictability for both parties while preserving SAP's right to revenue from genuinely new indirect access activity.

Phase 5 — Negotiate BTP Credits and Dual-Use Provisions

BTP credits purchased at contract origination benefit from deal-level discounts. Model your BTP consumption requirements for the first two years of post-go-live operation — not just the migration period — and negotiate the full credit requirement upfront. The incremental cost of adding BTP credits to an initial deal is lower than buying them post-contract.

A dual-use provision covers the period during which you are running both your legacy SAP environment and the RISE environment during migration. Without a dual-use clause, SAP can charge you both on-premise annual support (approximately 22 percent of net licence value) and the RISE subscription simultaneously. Negotiate a minimum six-month dual-use window included in the RISE subscription; large migrations should target twelve months. This provision can represent hundreds of thousands to millions of dollars of avoided double-payment cost depending on your on-premise licence base.

Phase 6 — Protect Exit Rights

RISE is a long-term commitment. The commercial logic assumes you will remain on the platform for the full contract term. The contract terms should not assume this. Before signing, negotiate three exit protections. First, explicit data portability rights — the right to export your data in a standard, machine-readable format within 60 to 90 days of contract termination at no additional charge. Second, capped early termination fees — if the contract includes a termination for convenience provision, ensure the fee is a defined amount, not an open-ended calculation. Third, a defined non-renewal notice period that is commercially reasonable — 90 to 180 days is appropriate; 12 months is not.

Part 4: Timing and Leverage

Exploiting SAP's Fiscal Year Calendar

SAP's fiscal year ends December 31. This is the single most important commercial calendar fact for RISE negotiations. SAP account teams face the strongest internal pressure to close deals in October and November, when they are working towards full-year quota attainment and when senior deal approval is faster. The commercial concessions available in November are typically larger than those available in February.

To exploit this leverage effectively, your organisation must be genuinely ready to close by the end of November — not simply negotiating. Readiness means your FUE analysis is complete, your DDLC mapping is done, your TCO model is validated, your legal team has reviewed contract terms, and your internal stakeholders are aligned on walk-away terms. An organisation that arrives prepared in October can credibly signal that it will close in Q4 at acceptable terms, or walk into Q1 of the following year if terms are not acceptable. This creates the commercial tension that produces best-in-class outcomes.

Establishing a Credible BATNA

BATNA — Best Alternative to a Negotiated Agreement — is the most important negotiating concept in a RISE transaction. SAP negotiators are trained to assess whether the buyer has a viable alternative. If they conclude that the buyer must have RISE (because the CIO has committed to it publicly, because the board has approved the budget, because the deadline is non-negotiable), they will hold price. If they believe the buyer has a credible alternative, they will make commercial concessions to avoid losing the deal.

The credible alternatives in a RISE negotiation include third-party maintenance on the current SAP estate (vendors like Rimini Street can reduce annual support from 22 percent of net licence value to 10 to 15 percent, extending the economic viability of the on-premise environment), migration to an alternative cloud ERP, or deferral of the migration by 12 to 18 months while market conditions develop. You do not need to intend to pursue these alternatives. You need to communicate credibly that you could, and that you have evaluated them seriously.

Part 5: Post-Contract Protections

Establishing Commercial Governance

The relationship with SAP does not end at contract signature. Large RISE contracts include ongoing commercial interactions: annual consumption reviews, renewal conversations, add-on purchase decisions, and change order negotiations. Establishing a formal commercial governance framework — designating a licence management owner, scheduling quarterly SAP relationship reviews, and maintaining an internal record of contract entitlements and actual consumption — prevents the cost creep and scope drift that erodes the commercial value of the initial negotiation over the contract term.

Managing the Renewal Cycle

RISE renewal negotiations typically begin 12 to 18 months before contract expiry. At renewal, your leverage changes: you are an existing customer on the platform, with transition costs associated with change, and SAP's account team knows this. The commercial dynamics at renewal favour SAP relative to initial contract signature. The most effective protection is using the initial contract term to reduce dependency and diversify optionality: mature your BTP capability, maintain data portability readiness, and evaluate the renewal against the alternatives available at that time, not just against the prior contract.

The tactics described in Part 3 — FUE analysis, DDLC mapping, benchmark referencing, and uplift negotiation — are all applicable at renewal. A well-prepared buyer at renewal consistently outperforms a buyer who treats the renewal as an administrative process rather than a commercial negotiation.

How Redress Compliance Supports RISE Negotiations

Redress Compliance has supported over 80 RISE with SAP negotiations as an independent, buyer-side advisor. Our team brings no conflicts of interest: we have no SAP partnership, no referral relationship, and no economic interest in the outcome of the RISE decision itself. Our interest is in the quality of the commercial outcome for our clients.

Our RISE negotiation services include independent FUE modelling (mapping current user populations to S/4HANA tiers using actual transaction data), DDLC indirect access mapping (identifying all third-party integrations and sizing the Digital Access requirement), commercial benchmarking (validating your proposed subscription against market references from comparable deals), contract review (identifying unfavourable terms and proposing buyer-protective alternatives), and negotiation support (participating in commercial discussions as an independent advisor alongside the internal team).

If you are preparing for a RISE negotiation, we recommend engaging support at least three months before your target contract signature date — early enough to complete the readiness work that determines the negotiating position, not just late-stage contract markup. Contact us through our SAP commercial advisory specialists or request a consultation directly.

You can also download our SAP Audit Defence Framework, which includes structured DDLC mapping templates and FUE role analysis tools directly applicable to the readiness phase of a RISE negotiation.