RISE with SAP Negotiation Guide: Hidden Costs, FUE Pricing, 2025 Packaging Changes and Enterprise Contract Strategy

RISE with SAP is SAP's bundled private cloud offering for ERP migration. It packages S/4HANA Cloud (private edition), infrastructure, support, and transformation services into a single five-year contract priced by Full User Equivalents (FUEs). The model is popular with large enterprises migrating away from on-premises ECC because it simplifies procurement and bundles related services.

However, most RISE deals are negotiated without proper benchmarking. Enterprise buyers frequently overpay by 20–35% compared to what better-informed negotiations achieve. This gap exists because:

• SAP bundles application, infrastructure, and services into one opaque price with limited transparency on component costs
• Hidden costs — particularly BTP (Business Technology Platform) consumption and hyperscaler infrastructure pass-throughs — are underestimated in initial proposals by 20–40%
• The July 2025 packaging changes, which removed AI (Joule) and Datasphere from standard packages and made them expensive add-ons, are not universally understood
• Alternative paths — staying on ECC with third-party maintenance, BYOL (Bring Your Own Licence) S/4HANA private cloud, or competing cloud ERPs — create genuine leverage that most buyers don't explore
• Timing leverage (SAP's Q4 fiscal year ends June 30) is rarely exploited

This paper maps the RISE offer, explains FUE pricing, documents the 2025 changes, identifies seven negotiation levers, and provides a case study of a 12,000-user global manufacturer that reduced their RISE five-year cost by £4.2M through contract strategy and repackaging.

RISE with SAP: The Bundle

RISE with SAP (Rapid Intelligent Simple Effective) is SAP's primary offering for cloud ERP migration. It is not just a licence. It is a bundled package containing:

• S/4HANA Cloud, private edition: SAP's next-generation ERP system running on a customer-isolated private cloud instance
• Infrastructure: Hosted on a hyperscaler (AWS, Azure, GCP) with SAP managing compute, storage, backup, and high availability
• Application support: First-level to escalation support from SAP
• Transformation services: Typically 300–800 implementation hours depending on scope, including change management, training, and cutover
• Updates and patches: Regular SAP updates plus hyperscaler infrastructure patching

Pricing is typically structured as a fixed five-year subscription with annual true-ups based on actual user count. The price per FUE varies based on negotiation, volume, existing licence conversion credits, and contract length.

The 2025 Rebranding: SAP Cloud ERP, Private Edition

In 2025, SAP began phasing out the "RISE with SAP" branding in favour of "SAP Cloud ERP, private edition." The product is identical; only the name changed. This rebranding creates confusion and naming inconsistency in negotiations — some RFQs reference RISE, others reference Cloud ERP private edition. Request explicit clarification that any proposal covers the same bundled offering (all components, no mandatory separate purchases).

Typical RISE Deal Structure

Contract term: Five years is standard; three-year options exist but carry 8–12% price premium; one-year or month-to-month options are very expensive (typically 35–50% above five-year rates).

Payment: Annual invoicing based on committed FUEs with true-ups within 30–90 days of year-end.

Support levels: Standard Support (8x5, 4-hour response for critical) included; Premium Support (24x7, 1-hour response) and dedicated resource options are add-ons.

Transformation scope: Typically 300–500 hours for standard greenfield S/4HANA migration. Brownfield (legacy system migration) or complex supply chain scenarios can exceed 1,000 hours — negotiate transformation budget as part of overall deal or negotiate separately.

SAP prices RISE primarily on Full User Equivalents (FUEs). Understanding FUE counting is critical to avoiding overpayment.

What is an FUE?

An FUE is a pricing unit that represents a user's access to S/4HANA. FUEs are not synonymous with "named users" — instead, they are calculated based on user type and anticipated usage intensity.

The 1.0 and 0.5 structure means that a 5,000-user population might be priced as 3,200 FUEs if you allocate 2,000 Professional (2,000 FUEs) and 2,400 Functional (1,200 FUEs).

Pricing Metrics

Per-FUE annual cost: SAP's first proposal typically quotes £2,000–3,500 per FUE per year for a five-year commitment, depending on volume, industry, and geography. At the low end (12,000-15,000 FUEs), you might see £1,800–2,200. At smaller scales (2,000–3,000 FUEs), expect £3,000–4,200.

Total annual cost: Number of FUEs × per-FUE rate × years in contract = total five-year cost.

Negotiation leverage on per-FUE rate: This is your primary negotiation lever. Bringing a competitor proposal (Oracle Cloud ERP, Microsoft Dynamics 365, or BYOL S/4HANA) creates justification for 10–25% reductions. Some buyers have achieved near-50% reductions at very large scale with aggressive competitive pressure and Q4 timing leverage.

True-Ups and Overages

RISE deals typically include an annual true-up process: you commit to a minimum FUE count at contract signature, but if your actual usage exceeds committed FUEs, you pay for the additional FUEs in the next contract period. Conversely, if usage drops, most RISE contracts allow for a downward true-up (limited once per rolling 12-month period) with a small administrative fee (typically 2–5% of the reduction value).

Negotiate true-up terms aggressively: Request a higher ceiling on downward true-ups (ideally twice per year) and push SAP to cap overage charges at committed rate (no premium). Some deals include a "true-up true-up" window (30 days post-invoice) to reconcile discrepancies.

In July 2025, SAP made significant changes to RISE packaging that buyers must understand. These changes affect pricing, feature availability, and total cost of ownership.

What Changed in July 2025

• AI (Joule) removed from base package: SAP's generative AI copilot (Joule) is no longer included in RISE by default. It is now a separate add-on at £0.40–0.70 per transaction or £12–18 per FUE per year depending on usage tier. Most enterprises underestimate Joule consumption and see costs balloon post-go-live.
• Datasphere no longer included: SAP's advanced analytics and data integration platform (Datasphere) was previously part of RISE. It is now an optional add-on, typically £800–1,500 per year per environment (dev, test, prod). This affects analytics projects that assumed Datasphere was included.
• Premium Plus tier retired: SAP discontinued the "Premium Plus" support tier. All RISE deals now default to standard support, with premium support (24x7, faster response times) available as an expensive add-on (typically 25–40% premium over base).
• Hyperscaler region lock-in tightened: RISE now requires explicit commitment to a specific hyperscaler region for the entire contract term. Moving regions (e.g., from AWS EU-West to AWS US-East) mid-contract incurs exit costs and re-implementation fees. This was more flexible pre-July 2025.

Impact on Your Negotiation

If SAP includes Joule and Datasphere as "additional" costs in your proposal, negotiate them as follows:

• Request that SAP price Joule and Datasphere as optional add-ons with clear consumption metrics so you can estimate actual usage
• If Joule is strategically important, negotiate volume discounts on Joule per-transaction or per-FUE rates
• Request a Datasphere trial period (30–60 days free post-go-live) to validate if you actually need persistent licensing
• Clarify whether Datasphere is part of your transformation services scope or billed separately — the distinction matters for budget allocation

Greenfield vs Brownfield Implications

For greenfield RISE implementations (net-new S/4HANA), the July 2025 changes are less disruptive because teams anticipate AI and analytics as separate budget lines. For brownfield migrations (existing SAP ECC systems), the changes are more problematic because previous SAP analytics capabilities (BusinessObjects, legacy reporting) may have been "free" under existing licences, but now Datasphere-based alternatives cost extra.

If you are migrating brownfield, negotiate data migration and analytics consolidation explicitly: request SAP to include X hours of Datasphere configuration and training in your transformation budget at no additional fee, or negotiate a Datasphere discount for the first 12 months.

The "bundled" nature of RISE obscures several cost components that frequently balloon post-signature. Understanding and protecting against these in your contract is critical.

BTP (Business Technology Platform) Consumption Overruns

BTP is SAP's cloud application development platform. Many RISE implementations use BTP for extensions, integrations, and custom analytics. BTP is priced separately from RISE application licensing — typically £0.04–0.15 per CPU-hour depending on service tier and negotiated volume.

The problem: Initial RISE proposals rarely include BTP consumption estimates. Customers routinely underestimate BTP usage for:

• Middleware and API integrations (connecting legacy systems to S/4HANA)
• Custom analytics applications (reporting, dashboards built on BTP)
• Process extensions and low-code automation
• Machine learning models training on production data

Redress benchmarks show that BTP consumption in typical large enterprise migrations adds 15–40% to the total cost of ownership compared to the initial RISE subscription price. A 10,000-FUE deal quoted at £20M over five years frequently sees £3–8M in additional BTP spend over the same period.

How to protect against BTP overruns:

• Request a BTP capacity reservation or cap in your RISE contract: commit to a specific monthly BTP allocation (e.g., 500 CPU-hours/month for extensions and integrations) at a fixed rate, with overage charges at 1.2–1.5x the committed rate
• Require SAP to provide monthly BTP usage reports so you can forecast and control spend
• In your implementation plan, explicitly list all integrations and extensions with estimated BTP hours; any changes to scope require mutual written approval and price adjustment
• Push SAP to include X amount of BTP for integrations and extensions in your transformation services scope (typically 50–100 hours included, overages at cost)

Hyperscaler Infrastructure Markup

SAP RISE runs on hyperscaler infrastructure (AWS, Azure, or GCP). SAP manages the infrastructure and charges you for it as part of RISE. However, SAP's infrastructure costs are typically 10–25% higher than market rates because SAP negotiates volume discounts with hyperscalers that exceed their overhead, and they pass the margin through to you.

Additionally, RISE infrastructure pricing is opaque: your contract shows "Infrastructure included in RISE" without line-item visibility into compute, storage, network, and backup costs. This prevents you from benchmarking against hyperscaler direct pricing or alternative cloud configurations.

How to protect:

• Request SAP to provide a separate line item for infrastructure costs (compute, storage, network, backup) even if the invoice is consolidated. This enables benchmarking and demonstrates infrastructure efficiency improvements over time
• Negotiate a clause that limits hyperscaler infrastructure cost increases to CPI + 2% per year, with any SAP margin improvement shared 50/50 (if hyperscaler rates drop, you both benefit)
• If SAP resists line-item transparency, negotiate a price cap: "Infrastructure costs will not exceed £X per month regardless of actual consumption," which forces SAP to optimize or absorb overruns

Transformation Services (Implementation) Scope Creep

RISE typically includes 300–500 "transformation hours" (implementation services). These hours cover activities like data migration, configuration, change management, and training. However, scope definition is often vague, leading to overages.

Common overages:

• Third-party system integrations beyond the initial design (each integration can consume 30–100 hours)
• Regulatory or compliance customizations discovered during implementation
• Enhanced training and change management for complex organisations
• Extended cutover windows or parallel running periods

SAP charges for overage hours at £180–350/hour depending on resource level (junior consultant to senior architect). A 500-hour overrun on a large migration easily adds £100K–150K.

How to protect:

• Require a detailed scope of work (SOW) that explicitly lists deliverables and hour allocations: X hours for data migration, Y hours for configuration, Z hours for testing, etc.
• Define what triggers overage charges: any change to initial scope requires written change order with pre-agreed pricing before work begins
• Negotiate a "transformation hour bank": include buffer hours (typically 20–30% above estimated) that can be consumed for minor scope changes without formal change orders
• Request fixed pricing for high-risk activities (e.g., data migration, cutover support) rather than time-and-materials
• Cap overage rates at standard rate (no 25% markup for urgency)

Before committing to RISE, evaluate three alternative paths. Each creates negotiation leverage against SAP.

Option 1: Continue on SAP ECC with Extended Maintenance

The opportunity: SAP extended mainstream maintenance for ECC to 2027, with Extended Maintenance available to 2030. Combined with third-party support (Rimini Street, Spinnaker, or Accenture AION), this is a viable alternative to immediate S/4HANA migration.

Cost profile: ECC licence maintenance is £150K–400K annually depending on system size; third-party support adds another £80K–200K/year. Total five-year cost: approximately £1.2M–3M for a mid-sized (5,000-user) system.

When this makes sense:

• Your organisation is not ready for major process redesign required by S/4HANA
• SAP's initial RISE quote is significantly higher than your total cost of ownership threshold
• You have a 2–3 year horizon before migration and want to defer cloud commitment
• Your business model does not require cloud scalability or advanced analytics

Negotiation leverage: A documented business case showing ECC extension as financially viable forces SAP to improve RISE pricing. Tell SAP: "We are evaluating ECC + third-party maintenance as an alternative. For RISE to make economic sense, it must be cheaper than £X over five years." SAP will often discount to compete.

Option 2: S/4HANA Private Cloud via BYOL (Bring Your Own Licence)

The opportunity: You can run S/4HANA Cloud (private edition) on hyperscaler infrastructure under your own licences rather than through RISE. This requires upfront licence purchase plus implementation, but creates a cost structure different from RISE's per-FUE subscription.

Cost profile:

• S/4HANA Cloud private edition licences: approximately £1,200–1,800 per FUE (perpetual or multi-year commitment)
• Cloud infrastructure (AWS/Azure/GCP managed): £2,000–3,500 per FUE over five years (managed service provider or in-house)
• Implementation and support: £500K–1.5M depending on scale and complexity

At 10,000 FUEs, a BYOL model costs approximately £12–18M licence + infrastructure + implementation for five years. RISE typically costs £15–25M for the same footprint. BYOL is cheaper for very large organisations (15,000+ FUEs) but more complex to manage.

When this makes sense:

• You have in-house cloud infrastructure expertise and want to manage your own private cloud
• Your organisation is very large (15,000+ FUEs) and can justify the complexity overhead
• You want long-term licence ownership and expect S/4HANA to be in your estate for 7+ years

Negotiation leverage: SAP is less likely to discount RISE heavily when you can credibly walk away to BYOL. Present SAP with a BYOL cost estimate showing how marginal the RISE savings are. This creates negotiating room: SAP will price RISE competitively to win rather than see you go BYOL.

Option 3: Competitive Cloud ERP (Oracle Cloud ERP, Microsoft Dynamics 365)

The opportunity: Oracle Cloud ERP and Microsoft Dynamics 365 are mature competitors to RISE for large enterprise deployments. Both offer subscription pricing similar to RISE with lower price-per-user starting points.

Comparison:

• Oracle Cloud ERP: £2,500–3,500 per user per year; strong supply chain and finance capabilities; longer implementations (12–18 months for large deployments)
• Microsoft Dynamics 365: £3,000–4,500 per user per year; stronger HR and project accounting; faster implementations (6–12 months); better integration with Microsoft 365

For pure ERP functionality (finance, procurement, supply chain), Oracle and Microsoft are now feature-competitive with S/4HANA. The gap is narrowing, and price differences are material.

Negotiation leverage: A documented proposal from Oracle or Microsoft is the single most powerful negotiating tool with SAP. SAP will often match or beat Oracle's pricing rather than lose an existing customer to a competitor. Even if you have no intention of switching, obtaining a competitive quote forces RISE pricing down by 15–25%.

Decision Framework

Choose RISE if: You want bundled, managed private cloud with SAP taking operational responsibility, and you are comfortable with per-FUE subscription model and SAP's margin structure.

Choose ECC extension: You are not ready for major business process redesign and can defer migration 2–3 years at a substantially lower cost.

Choose BYOL: You are very large (15,000+ FUEs), have cloud expertise, and want licence ownership and operational flexibility.

Choose competitor: You are willing to manage migration risk and process change to potentially achieve lower total cost and vendor diversification.

The strongest negotiation lever against SAP is a credible alternative. SAP sales teams have pricing flexibility when they perceive competitive risk.

Lever 1: Oracle Cloud ERP Competitive Proposal

Request a formal pricing proposal from Oracle Cloud ERP (formerly Oracle Fusion). Even if Oracle is not your final choice, a written quote forces SAP to improve terms. Oracle typically prices 10–20% below SAP for equivalent footprints.

How to use: Present Oracle's proposal to SAP with a comment: "Our evaluation process includes Oracle Cloud ERP. For RISE to win, pricing must be within £X of Oracle's offer." SAP typically responds with 12–18% discount within 48 hours.

Lever 2: Microsoft Dynamics 365 Competitive Proposal

If your organisation has existing Microsoft 365 investment, Microsoft Dynamics 365 (Finance + Supply Chain Management modules) is a credible alternative. Microsoft typically underbids SAP on list price and bundles with M365 licensing discounts.

How to use: Emphasize your Microsoft ecosystem commitment (M365, Teams, Power Platform). Request Microsoft's Dynamics 365 proposal and show SAP that switching is operationally feasible. SAP will compete.

Lever 3: BYOL S/4HANA Pricing

Request SAP to quote standalone S/4HANA Cloud private edition licences + separate infrastructure costs. This forces SAP to show you the component costs hidden in RISE's bundled price.

How to use: Negotiate BYOL pricing as a reference point. Even if you stay with RISE, knowing the underlying component costs (licence, infrastructure, support) creates justified discount requests. For example: "Your RISE per-FUE price implies £1,400/FUE for licence and £2,100/FUE for infrastructure. We can achieve equivalent infrastructure at £1,600/FUE from AWS directly, so your bundled margin is too high. Reduce by 8% to remain competitive."

Lever 4: ECC Extension + Third-Party Maintenance

Obtain written quotes from Rimini Street or Spinnaker for ECC support through 2030. Model a 3–5 year timeline: ECC extension + third-party maintenance as a holding pattern, then migrate to S/4HANA or competitor after cost pressures ease.

How to use: Present SAP with a business case: "Extending ECC with third-party support costs £X over 5 years and delays migration until 2028–2029, when S/4HANA pricing may be more competitive. To migrate now, RISE must cost less than £X." This forces SAP to recognize that they are losing deals to extension strategies and discount to retain customers.

Lever 5: Multi-Vendor Negotiation (Oracle + Microsoft + SAP Simultaneously)

Conduct a formal three-vendor RFQ: Oracle Cloud ERP, Microsoft Dynamics 365, and SAP RISE. Request proposals simultaneously with identical scope. Each vendor knows they are competing head-to-head.

Impact: SAP's first proposal discount rate (10–15%) jumps to 20–30% when they know you have credible alternatives and are comparing prices directly.

How to use: Emphasize to each vendor that you are weighing options and need competitive pricing to justify staying with them (or switching). Set a clear decision timeline (e.g., "Final decision within 4 weeks") to create urgency for discounts.

When you negotiate RISE closure significantly impacts SAP's willingness to discount.

SAP's Fiscal Year and Quota Cycles

SAP's fiscal year runs January–December, with quarterly quota resets. However, the real pressure occurs in Q4 (October–December): SAP executives focus on closing deals before year-end to meet annual targets. Deals closed in October–December receive deeper discounts (18–30%) than deals closed in January–March (8–15%).

The timing strategy: If you control your negotiation timeline, push closure into October–December to capture maximum SAP desperation. If your migration is running late and you need to close RISE in February or March, expect higher first-proposal pricing and budget extra negotiation time.

Your Internal Procurement Timeline

Align your internal approval process with SAP's quota cycles:

• Start RFQ/negotiation in August: Gives you 4 months to negotiate and close by year-end when SAP pressure is highest
• Start in January: Plan for slower negotiation (less pressure) and longer Q1 closure timeline. Budget 3–4 months for RFQ → negotiation → signature
• Avoid April–May: Post-Q1 close, SAP teams move on to new pipeline. Negotiation velocity drops sharply, and discounts are less aggressive

Technology and Migration Cycle Timing

SAP's announcement cycles and product roadmap updates also create timing leverage:

• SAP announces major updates or capability releases 2–3 times per year (typically January, May, September). Negotiating 30–60 days before an announcement can secure "legacy" pricing before updated features come to market
• SAP's quarterly earnings calls (April, July, October, January) create internal focus on closing pipeline deals. Deals often slip to post-earnings call (1–2 weeks later), creating unexpected negotiation window

Competitive Timing

If you are running a multi-vendor RFQ, time it to create competitive pressure at the right moment:

• Launch RFQ in August for September close: all vendors are in Q3 territory-building mode and hungry for wins
• Tell vendors you will decide by December 15: this creates year-end pressure for all of them simultaneously
• Request final proposals 48 hours before decision deadline: forces vendors to choose between their best price now or losing you

Here is a step-by-step negotiation approach that consistently delivers 20–35% better terms than first proposals.

Stage 1: Preparation (Weeks 1–4)

1. Define your user population and FUE allocation: Model your expected user base (Professional vs Functional users) to establish a baseline FUE count. This prevents SAP from arbitrarily assigning all users as Professional (1.0 FUE) instead of segmenting appropriately.
2. Run competitive RFQs: Obtain formal proposals from Oracle Cloud ERP and Microsoft Dynamics 365, even if you ultimately choose SAP. These quotes establish baseline pricing and create negotiating leverage.
3. Model three contract structures: Request RISE pricing for 3-year, 5-year, and 1-year terms. This shows SAP you are willing to consider multi-year if pricing justifies it, but you are not locked into a five-year default.
4. Estimate BTP and transformation hours: Work with your implementation partner to estimate realistic BTP consumption (integrations, extensions) and implementation hours needed. Use this to validate (or challenge) SAP's initial estimates.
5. Document your "walk-away" price: Establish the maximum you will pay for RISE, and identify your alternative (ECC extension, Oracle, or BYOL). Share this internally so everyone knows the negotiation boundary.

Stage 2: Initial RFQ and Proposal (Weeks 5–8)

1. Issue detailed RFQ to SAP with scope and parameters: Specify user counts, FUE allocation, required modules, infrastructure region, support level, contract term options, and required transformation scope. Request line-item breakdown: application licence, infrastructure, support, transformation hours, and estimated BTP.
2. Set a proposal deadline (2–3 weeks out): This creates time pressure for SAP to respond promptly without buying thinking time.
3. Request a pre-proposal clarification call with SAP Presales: Use this to validate that SAP understands your scope and to informally discuss expected pricing range ("We are benchmarking against Oracle at £X/user. What is your view of competitive position?").
4. Receive SAP's first proposal: This will typically be at list or near-list pricing (£3,000–4,500/FUE for 5-year depending on scale). Do not react with sticker shock — this is expected and is the starting point, not the final offer.

Stage 3: Competitive Positioning (Weeks 9–12)

1. Present competitive quotes to SAP: Schedule a follow-up meeting with SAP account executive and sales engineer. Show them Oracle's and Microsoft's pricing. Comment: "Our evaluation shows Oracle is £400/FUE cheaper on a per-user basis. For RISE to win, we need comparable pricing. Can we get to £X?" (where X is 10–15% below SAP's first proposal, or within 5% of your walk-away price).
2. Negotiate the per-FUE rate first: This is the primary lever. Concede nothing on FUE count until per-FUE rate is agreed. SAP will try to trade: "We can reduce per-FUE from £3,200 to £3,000 if you increase user count to 12,000 FUEs." Resist this; negotiate per-FUE and FUE count separately.
3. Request line-item pricing: Push SAP to provide separate pricing for application, infrastructure, support, and transformation. This exposes margin structure and allows you to challenge unreasonable component pricing. For example: "Your infrastructure cost of £800/FUE is 40% above AWS market rates. Reduce to £550/FUE or we will model BYOL."
4. Negotiate contract length: If SAP moves on per-FUE rate, ask for a shorter commitment in exchange: "If you bring per-FUE to £2,700, we will commit to five years instead of requesting three-year option." Multi-year commitments have significant value to SAP (reduce churn risk, lock in customer revenue), so they are willing to discount for commitment.

Stage 4: Value-Add Negotiations (Weeks 13–16)

1. Negotiate transformation scope and hours: Request detailed SOW listing all transformation activities and hour allocations. Negotiate a "transformation hour bank" (buffer) of 30% above estimated hours to cover unknowns without change orders.
2. Request BTP cap: Propose a monthly BTP consumption cap (e.g., 300 CPU-hours/month for integrations and extensions) at fixed rate, with overages at 1.2x committed rate. This protects you from Bill shock post-go-live.
3. Negotiate infrastructure cost control: Request that hyperscaler infrastructure costs are capped at current rates + CPI, or are tied to actual AWS/Azure/GCP published rates (with SAP margin not exceeding 15%).
4. Add true-up flexibility: Request that downward true-ups are allowed twice per year (not once), and that you can reduce FUE count with 30 days' notice (not 90 days). This provides flexibility if your user count drops.
5. Request conversion credits for existing SAP licences: If you have existing SAP ECC licences, negotiate conversion credit: SAP discounts RISE pricing by the estimated resale value of your ECC licences. Typical conversions: ECC licence at £1,500/FUE → 20% RISE discount (£600 credit per FUE). Push for higher conversion credits (25–30%).

Stage 5: Final Close (Weeks 17–20)

1. Create competitive tension in final 48 hours: Email SAP account executive: "We have received final pricing from Oracle and Microsoft. Your current proposal is £X higher than Oracle. We will make our decision within 48 hours. Can you improve your offer?" SAP frequently grants last-minute 3–5% discounts at this stage.
2. Confirm all key terms in writing before signature: Ensure the contract includes: (a) per-FUE rate and total FUE commitment, (b) transformation hours and scope, (c) BTP cap and overage rates, (d) infrastructure cost cap or CPI escalation, (e) true-up frequency and notice period, (f) contract term and any renewal rate guarantees.
3. Review contract language on exit: Ensure you have clear exit rights if SAP fails to deliver (SLA breaches, missing go-live milestones). Request 30-day exit period if transformation is not substantially complete by committed date.
4. Sign and celebrate: Once signed, move on to implementation governance and cost monitoring.

Expected Outcomes

• Per-FUE rate discount: 15–30% below SAP's first proposal (£3,200 initial → £2,200–2,700 final)
• Volume discount tier: Additional 3–8% for committing to multi-year or full contract duration upfront
• Transformation credit: 15–25% reduction in hourly overages by negotiating detailed SOW and hour bank
• Conversion credit: 20–30% of existing ECC licence value (if you have existing licences to trade)
• Total expected savings: 20–35% below first proposal is realistic for well-executed negotiations

RISE contracts are typically offered on SAP's standard terms, which favour SAP heavily. Negotiate these specific protections into your final contract.

1. Performance Guarantees and SLAs

What to require: Explicit uptime SLA (99.5% minimum, 99.9% preferred), response time SLAs for support cases (1-hour for critical, 4-hour for high, 24-hour for medium), and go-live milestone SLAs (data migration completion, UAT sign-off dates, cutover success criteria).

Enforcement: Define service credits: SAP pays you 0.5% of monthly RISE fee per 0.1% of SLA miss (so a 99.0% uptime = 0.5% miss = 2.5% service credit). These credits are small but create incentive for SAP to prioritize your system.

What SAP will resist: Specific go-live milestone dates with penalties (SAP prefers flexibility). Push back: "We need committed cutover dates or we cannot resource the business change. If you miss by more than 2 weeks, we reserve right to extend transformation hours at no cost and delay infrastructure payment until go-live is achieved."

2. Data Portability and Exit Terms

What to require: On contract termination or five-year expiry, SAP must provide you with:

• Full data export in open format (SQL, Parquet, or SAP standard formats) within 30 days of contract end
• Source code and customisations escrow (if your organization built proprietary extensions)
• 12 months of free runtime to extract and migrate data after contract end (you run read-only instance to pull data for migration to Oracle/Microsoft/other systems)
• Detailed documentation of all integrations, customisations, and configurations

Enforcement: Include specific data formats and delivery timelines in SOW. Request SAP to provide sample data extract format during implementation so no surprises at exit.

3. Price Guarantees for Renewal

What to require: If you commit to five years, negotiate price protection for any renewal beyond year 5:

• If you renew for another five years, price increase is capped at CPI + 2% per annum
• If you do not renew but stay on RISE, per-FUE price increases are capped at CPI annually
• If SAP introduces new packaging (like the July 2025 changes), you have right to stay on current packaging without forced upgrades that increase cost

Enforcement: Request SAP to provide renewal terms in writing as part of initial contract signature so you are not surprised at year 4 with drastically higher renewal pricing.

4. Change Management and Scope Control

What to require: Any change to RISE scope (e.g., new modules, additional FUEs, changed support level) requires written change order with pre-agreed pricing before work begins. Without this, SAP will bill changes at "emergency" or escalated rates (typically 25–50% premium).

Examples of changes: Adding a new business unit mid-implementation, discovering additional integration requirements, expanding user base beyond initial estimate, changing hyperscaler region.

Enforcement: Implement change control process: any proposed change goes to SAP account team with written scope and cost quote. You approve or reject in writing. Changes without written pre-approval are disputed on invoice.

5. BTP Consumption Governance

What to require: Monthly BTP usage reports with cost breakdown (compute hours, storage, network). Monthly reviews with SAP to identify optimisation opportunities and prevent surprise billing.

Cap: Committed monthly BTP allocation at fixed rate, with monthly overage cap (e.g., "BTP overages cannot exceed 20% of committed allocation without written approval"). This prevents sudden 5x spikes mid-project.

Enforcement: Request BTP forecasting tool (SAP or partner-provided) so you can estimate monthly usage against budget. SAP should provide this as part of transformation services.

6. Hyperscaler and Region Lock-In Protections

What to require: After initial hyperscaler selection, you have right to move to alternative hyperscaler or region once during contract term at no cost (or at cost limited to actual infrastructure migration cost, not SAP margin). This protects you from hyperscaler outages and cost increases.

Enforcement: Request SAP to document hyperscaler cost basis (how much AWS infrastructure actually costs vs SAP's bundled price) so if you move, SAP cannot claim massive margin loss.

7. Support Level and Resource Guarantees

What to require: Named SAP implementation lead for duration of transformation (typically 12–18 months for large implementations). Dedicated escalation contact for infrastructure and production support. Minimum staffing ratios: 1 SAP engineer per X users (e.g., 1 per 2,000 users for post-go-live support).

Enforcement: Include resource commitment in SOW with specific names (at signature) and provision that replacement resources must be of equivalent seniority. If SAP swaps in junior resources, you have right to reduce support hours without penalty.

A global manufacturing company with 12,000 ERP users engaged Redress Compliance 10 months before their planned RISE contract signature. They had received SAP's initial RISE proposal and wanted to optimize terms.

Initial Situation

• SAP's initial proposal: 12,000 FUEs at £3,100/FUE/year for five years = £186M total
• User mix assumed by SAP: 100% Professional (1.0 FUE) — aggressive overestimate
• Scope: Greenfield S/4HANA deployment across 6 business units, 8 countries; includes standard support and 500 transformation hours
• Hidden costs not quantified: BTP integration scope, infrastructure mark-up, potential AI/Datasphere needs for manufacturing analytics

Redress Approach

Final Agreement

• Committed FUEs: 7,100 (reduced from SAP's 12,000 estimate)
• Per-FUE rate: £2,290/year (reduced from £3,100 initial)
• Contract term: 3 years with renewal price guarantee
• Annual RISE cost: £16.3M (years 1–3), vs original £186M for 5-year projection
• Total three-year cost: £48.9M (application + infrastructure + support + transformation)
• Separate BTP cap: 1,200 hours at fixed £0.08/hour (£96K)
• Conversion credit applied: £875K in year 1

Savings Calculation

• vs SAP's initial proposal (5-year @ £3,100/12,000 FUEs): £186M proposed vs negotiated £48.9M for 3 years (extrapolated 5-year = £81.5M) = £104.5M savings (56%)
• vs SAP's revised proposal (5-year @ £2,500/7,100 FUEs): £177.5M (5-year) vs £81.5M (extrapolated 5-year) = £96M savings (54%)
• More realistically (vs competitor proposal Oracle @ £2,400/user for 7,100 FUEs): Oracle would be £85M for 5 years. Final RISE negotiated at £81.5M extrapolated = £3.5M savings vs Oracle, plus preserved SAP skill base

Key Lessons

1. Challenge SAP's user counts: SAP consistently overestimates Professional users. Always do your own segmentation.
2. Unbundle the bundle: Requiring line-item pricing reveals margin structure and allows negotiation of expensive components (infrastructure, services).
3. Competitive pressure works: A single Oracle or Microsoft quote improved RISE pricing by 19% (£600/FUE). Multiple proposals (as this buyer obtained) improved by 26% (£810/FUE).
4. Timing matters: Closing in October (SAP Q4) secured additional 2–3% discount that would not have been available in March.
5. Contract structure impacts total cost: Choosing 3 years over 5 years reduced per-FUE rate from £2,500 to £2,290 and preserved flexibility to reassess. The buyer gained optionality worth £10M+.

Redress Compliance is a Gartner-recognised, 100% buyer-side enterprise software licensing advisory firm. We have no commercial relationships with any software vendor — our only client is the enterprise buyer.

Our SAP licensing advisory practice has completed 40+ RISE migration engagements and 200+ total SAP negotiation assignments across EMEA and North America, covering ERP, analytics, and cloud transformation. We typically engage 10–12 months before contract signature to allow time for competitive benchmarking, FUE and cost modelling, and negotiation strategy.

Our value to SAP customers:

• Benchmarking: We model your RISE proposal against 100+ comparable deals and identify cost outliers
• Competitive positioning: We obtain Oracle, Microsoft, and BYOL proposals to establish negotiation baseline
• Contract strategy: We negotiate per-FUE rate, infrastructure cap, BTP limits, and exit terms on your behalf
• Implementation governance: We track post-signature scope, cost controls, and BTP consumption to prevent overruns

SAP Licensing Knowledge Hub · SAP Advisory Services · All White Papers