RISE with SAP vs On-Premise: Cost Optimisation Tactics

The Real TCO of RISE with SAP vs On-Premise

The SAP-built TCO comparison starts with a false premise: that you're comparing RISE to today's on-premise environment. You're not. You're comparing RISE to an imaginary on-premise scenario designed to look expensive. The real comparison requires unpacking every component.

RISE Components and Actual Costs

A RISE contract bundles five distinct cost categories, but SAP presents them as inseparable. They're not:

• S/4HANA Subscription: The core licence. Priced per user or per FUE (Full Use Equivalent). Includes Named Users, Professional Users, and Limited Professional Users. Reclassification risk is built into SAP's model — they often misclassify during migration, forcing you to overpay.
• BTP Credits: Cloud platform credits. Typically 30-50% of the RISE bundle by list value, almost never fully consumed. SAP's allocation assumes you'll build heavy applications. Most enterprises use 20-30% of allocated credits and don't know it.
• Enterprise Support (22% of ACV): Mandatory bundled support. 22% of your annual contract value. Negotiable downward with leverage, but rarely negotiated.
• Infrastructure (30-40% of RISE ACV): SAP's hosted environment, typically on AWS but sold at a 20-30% premium to equivalent AWS pricing. This is the softest component and easily benchmarkable.
• Migration Costs: €2-5M for large enterprises, often underestimated. Database conversion, code migration, testing. Rarely included in RISE contracts but essential to TCO.

On-Premise Components (The Realistic Baseline)

Compare RISE to this, not to a strawman:

• Perpetual Licences (Already Owned): If you're on ECC, you own these outright. No further licence cost for staying on-premise or migrating to S/4HANA on-premise. The comparison should assume you've already spent this money.
• Maintenance (22% but Negotiable): SAP Enterprise Support at 22% of ACV is standard. But if you switch to Rimini Street or Spinnaker for on-premise systems, maintenance drops to 5-8% of SAP's list. That's a 50-70% saving you can bank.
• Hyperscaler Hosting (IaaS): AWS, Azure, or GCP hosting of on-premise S/4HANA costs €3-8M annually for large environments, depending on infrastructure. This is cheaper than RISE's bundled infrastructure by 20-30%.
• Internal IT (Unchanged): Your DBAs, system administrators, and infrastructure teams. If you own the talent, on-premise costs don't scale with this.

The Hidden RISE Costs No One Discusses

RISE bundling creates costs that don't appear in the contract:

• Scope Creep: SAP uses RISE contracts to sell you add-ons: SAC (analytics), Signavio (process mining), Ariba (procurement), all sold separately from the bundle. Typical cost: €500K-2M annually once migration is "stabilized."
• User Reclassification Risk: SAP's definition of "Named User" vs "Professional User" vs "Limited Professional User" is vague. During migration, they often recategorize users upward to extract higher fees. You discover this 12 months in when reconciliation happens. Cost: €200K-500K per reclass cycle.
• Digital Access Measurement: RISE's cloud model makes indirect access harder to measure. Your exposure to licence violations increases. SAP knows this and uses it tactically — they can claim you're accessing SAP functionality through other systems and demand additional licensing.
• Lock-in and Exit Costs: If you want to exit RISE (back to on-premise or another cloud platform), you face re-licensing fees and migration costs. Data portability clauses are weak. Budget €1-3M for exit.

Now, a proper TCO comparison. For a large enterprise (1,000+ users, €10M ERP spend):

That's not a SAP-built model. That's a realistic one. The takeaway: RISE is 60-80% more expensive than on-premise S/4HANA over 5 years if you negotiate on-premise properly. But 70% of enterprises never negotiate on-premise costs. They assume SAP's maintenance rates and don't explore third-party alternatives. That's where RISE wins — not on merit, but on apathy.

The 7 Cost Optimisation Tactics for RISE Customers

If you've decided RISE is the right path (not all should), these tactics will extract real savings. Each one targets a specific lever SAP controls.

Tactic 1: Right-Size Your Named User Count Before Migration

This is the easiest win and the one SAP most actively opposes. Why? Because user reduction directly cuts their revenue.

How:

• Run the SAP User Status and Material Management (USMM) report on your current ECC system 90 days before any RISE commitment. This shows actual active users in the past 90 days.
• Cross-reference with your HR system. Many "users" are inactive: people who left, transferred, or only accessed SAP once per quarter for approval workflows.
• Reclassify Professional Users to Limited Professional Users. A Limited Professional User (€1.5K-2K annually) versus a Professional User (€4K-5K annually) is a 60% saving per user. Test qualification in the current system before committing.
• Calculate FUE (Full Use Equivalent) impact. Not all users are FUEs. SAP's definition is intentionally broad, but licensing manuals allow reclassification.

The Savings: A 1,000-user environment reclassifying 150 users from Professional to Limited Professional saves €350-450K annually. Over 5 years: €1.75-2.25M.

SAP's Counter-Tactic: They'll argue reclassification is risky and create ambiguous language in the contract about "future flexibility to upgrade." Don't let them. Lock in the user classification in writing and include reclassification parameters.

Tactic 2: Challenge the BTP Credit Allocation

SAP allocates €500K-2M in annual BTP (Business Technology Platform) credits as part of RISE. Most enterprises use 20-30% of this allocation. The credits expire at year-end. SAP's model: you think you got value, you didn't, they keep the margin.

How:

• If you have existing BTP usage (Analytics Cloud, Process Mining, Extension Platform), request credit-to-cash conversion. SAP's cost to deliver credits is near-zero. They'll negotiate if you have leverage.
• Request credit portability. Negotiate that unused credits roll forward to the next year or convert to cash rebates. Standard clauses lock credits to annual cycles and forbid rollover.
• Demand transparency on credit consumption. SAP's billing on BTP is opaque. Require monthly reports on consumption and remaining allocation. Many enterprises pay for unused capacity.

The Savings: If 60% of your allocated credits go unused (€300K-1.2M annually), credit-to-cash conversion or portability saves €1.5-6M over a 5-year contract.

Tactic 3: Unbundle and Benchmark the Infrastructure Component

RISE infrastructure costs are opaque and overpriced. They're a black box bundled into the contract, but they're separable and benchmarkable.

How:

• Request an itemized infrastructure cost breakdown from SAP. They'll resist. Push back with an RFI (Request for Information) from your cloud procurement team. Frame it as due diligence, not negotiation. Most SAP reps will provide a rough number (typically €4-6M annually for large environments).
• Run an equivalent pricing exercise with AWS, Azure, or GCP. Use the SAP hyperscaler pricing pages (SAP publishes these under NDA). You'll typically find equivalent infrastructure at 20-30% below RISE rates.
• Negotiate RISE infrastructure against hyperscaler benchmarks. SAP will offer a 10-15% discount if you reference competitor pricing. Hold firm: demand parity with your chosen hyperscaler or the right to host RISE on your own cloud account with SAP's SLA.
• Explore hyperscaler-hosted RISE. SAP now offers RISE on your preferred cloud account (AWS, Azure, GCP) with an SLA. Push for this option — you control hosting costs and can optimize instances independently.

The Savings: A 15-20% infrastructure reduction on €5M annual cost saves €750K-1M annually. Over 5 years: €3.75-5M.

Tactic 4: Switch to Third-Party Maintenance on On-Premise Assets

If you retain any on-premise SAP systems (non-ERP, legacy applications, or a hybrid footprint), switching maintenance to Rimini Street or Spinnaker is powerful leverage with SAP and saves 50-70% on support costs.

How:

• Identify all retained on-premise systems. Even if you move ERP to RISE, you likely keep CRM, HR, analytics, or regional systems on-premise or on hyperscaler IaaS.
• Get quotes from Rimini Street or Spinnaker for those systems. Typical cost: 5-8% of SAP's list price (vs SAP's 22%). A €1M on-premise system under SAP support (€220K annually) becomes €50-80K with Rimini Street.
• Use this quote as leverage. Tell SAP: "We're moving ERP to RISE, but we're moving on-premise support to Rimini Street." SAP will counter with a special Enterprise Support rate for your on-premise systems. You now have a market-driven price instead of their list rate.
• Address SAP's objection tactics: They'll claim Rimini Street provides inferior support or creates license compliance risk. Both are false. Rimini Street is SAP's largest third-party competitor; their SLAs are equivalent. License compliance risk is low if you manage it.

The Savings: A €2M on-premise footprint under SAP support costs €440K annually. Switching to Rimini Street: €100-160K. Annual saving: €280-340K. Over 5 years alongside RISE negotiation: €1.4-1.7M savings, plus leverage that cuts RISE costs by 5-10% (€500K-1M).

Tactic 5: Leverage the 2027 ECC Deadline Against SAP

SAP's support for ECC ends in 2027. SAP will use this urgency to pressure you into RISE at inflated prices. The counter-tactic: use a credible alternative path to delay the decision and extract concessions.

How:

• Explore extended ECC maintenance. SAP offers extended support beyond 2027 (at premium cost, typically 150-200% of standard rates). It's expensive but not as expensive as a bad RISE deal. Use this as your "walkaway" scenario.
• Evaluate Rimini Street's ECC support or IBM's (they acquire ECC customers). Both offer cost-competitive alternatives to RISE that keep you on ECC beyond 2027. Get quotes — these are credible alternatives.
• Build a legitimate "stay on ECC" strategy. Have your finance and operations teams present the case: ECC is stable, tested, understood. S/4HANA migration is risky. Extended ECC + third-party support could be justified for another 3-5 years.
• Use this strategy to delay RISE decision and create negotiating time. SAP will discount RISE heavily if they believe you have a credible alternative. Your delay costs SAP more than a discount because they need your decision for their pipeline.

The Savings: A credible delay tactic + extended ECC on third-party support buys you time and typically extracts 10-20% off RISE pricing. On a €50M 5-year commitment, that's €5-10M savings.

Tactic 6: Negotiate Annual Price Escalation Caps

RISE contracts include price escalation clauses. Standard SAP language: "Annual increases indexed to CPI, capped at 7-10%." That sounds reasonable until year 3, when CPI is 5% and you're paying 7-10% anyway.

How:

• Propose a hard cap of 3-5% annual increases, regardless of CPI. SAP will resist. Counter with a case: if you commit to a 5-year contract with no user count increases and demonstrable usage reporting, a lower escalation cap aligns incentives. If you grow users, SAP gets revenue growth. If you shrink, they shouldn't raise prices.
• Freeze user pricing per type for the contract term. Propose: Professional User price remains €4.5K per year for all 5 years, no escalation. SAP's cost to serve you hasn't increased; your proposal is fair.
• Use escalation relief to offset reclassification risk. If you commit to user count transparency (monthly reporting), lower escalation rates should follow.

The Savings: On a €50M 5-year RISE commitment, a 3% vs 7% annual escalation cap saves €7-10M over the contract term (compounding effect).

Tactic 7: Structure Multi-Year Deals with Back-Loaded Payments

SAP has internal revenue recognition targets. A 5-year deal gives them revenue visibility but creates cash timing optionality. This is negotiating room.

How:

• Propose a 5-year RISE deal instead of a 3-year deal. Longer commitments signal confidence and reduce SAP's re-sale risk. They'll offer better pricing: typically 20-35% better unit rates on a 5-year deal vs 3-year.
• Structure payment timing to back-load SAP's cash. Propose: Years 1-2 at 80% of annual amount, Years 3-5 at 100% of annual amount (with escalation), then Year 5 at 110%. This smooths your cash but requires SAP to have cash flow confidence. They typically accept because 5-year lock-in justifies the trade.
• Use front-loaded discounting. SAP's revenue recognition targets create urgency in year 1. If you commit upfront (10-20% annual prepayment or lump-sum year 1), SAP will discount Year 1 rates by 5-15%. Bank this saving for negotiation leverage in Years 2-3.

The Savings: A 5-year deal at 25% better unit pricing vs a 3-year deal saves 10-15% of total RISE cost. On a €50M commitment, that's €5-7.5M. Add back-loaded payment timing discounts: another 2-5% (€1-2.5M).

On-Premise Cost Optimisation — The Alternative Path

Not all enterprises should choose RISE. For some, the on-premise path — extended ECC, S/4HANA on-premise, or hyperscaler-hosted SAP — is financially and operationally superior. Here's how to cost-optimize that path.

Extending ECC Lifecycle with Third-Party Support

If you're on ECC and don't need S/4HANA's innovations, extending ECC to 2032-2035 on third-party support is viable and cheaper than RISE:

• Rimini Street ECC Support: €50-100K annually (vs SAP's €220K on a €1M licence base). Includes security patches, bug fixes, and compliance updates. SLA: 1-4 hour response. You sacrifice new features but retain stability.
• Cost Impact: €250-500K over 5 years vs €1.1M with SAP Enterprise Support. Saves €600-850K.
• Risk Mitigation: For non-mission-critical systems or regional deployments, this is low-risk. For core ERP, consider hybrid: SAP support on core, Rimini on peripheral systems.

Hyperscaler Migration of On-Premise SAP (IaaS)

Migrate your on-premise S/4HANA to AWS, Azure, or GCP as Infrastructure-as-a-Service (IaaS). No licence reclassification, no cloud premium, just hosting:

• Licence Requirement: You already own S/4HANA licences (perpetual). Migration to hyperscaler IaaS doesn't trigger new licence costs. SAP's RISE licensing model assumes they host. IaaS hosting assumes you host on AWS/Azure/GCP.
• Cost Comparison: AWS/Azure/GCP hosting of large SAP environments: €3-6M annually. RISE infrastructure component: €5-8M. Savings: 25-40% on hosting alone.
• Operationally: You maintain SAP, but on hyperscaler infrastructure. Your DBA team now manages cloud instances instead of data centers. Skill set transition required but not radical.
• Risk: Higher operational complexity (you manage patches, updates). Hyperscaler support for SAP is good but not SAP-specific. If you lack internal SAP operations capability, this path has cost and risk.

S/4HANA On-Premise vs RISE Pricing Differential

The perpetual vs subscription choice is financial:

• S/4HANA Perpetual Licence: €2-4M upfront (one-time), then €440K-880K annually in maintenance (22% of licence cost). 5-year cost: €4.2-8.4M.
• RISE Subscription: €3M annually upfront (example), with 5-7% escalation. 5-year cost: €15-17.5M (using mid-range escalation).
• Differential: Perpetual is 40-60% cheaper than subscription if you own the operational capability.
• But: Perpetual requires more internal IT investment upfront. If you lack infrastructure, this model shifts burden to you.

The Five-Year On-Premise Case

A properly negotiated on-premise path saves enterprises £5-15M over 5 years vs RISE. Here's a realistic model for a €10M ERP spending enterprise:

• S/4HANA Perpetual Licence: €3.5M (one-time in Year 1)
• Annual Maintenance (third-party): €300K (5-8% of licence)
• Hyperscaler Hosting (AWS/Azure): €4.5M annually average
• Internal IT (incremental): €500K annually
• 5-Year Total: €18-20M

vs RISE 5-year total (from earlier table): €32-38M. Difference: €12-18M in favor of on-premise.

The Hybrid Model Some Enterprises Choose

RISE doesn't have to be all-in. Some enterprises split the difference: RISE for core ERP + on-premise or hyperscaler for peripheral systems. This hybrid approach balances risk and cost.

Typical Hybrid Architecture

• RISE for S/4HANA ERP Core: Finance, Procurement, Manufacturing. High-volume, mission-critical. SAP's support is strong here.
• On-Premise or Hyperscaler for: Analytics (custom BI, SAC), CRM (legacy or non-SAP), HR (Workday, Successfactors), Compliance/Audit.
• Indirect Access Risk Management: The challenge: if your Analytics system (on-premise) accesses S/4HANA RISE through APIs, you've created an indirect access vector. SAP's licensing can claim you're "accessing" SAP functionality through another system and demand additional cloud licensing.

Cost Model for Hybrid

Let's say RISE for ERP (€15M over 5 years) + on-premise BI, CRM, HR (€5M over 5 years) = €20M total. This is 50% cheaper than full RISE but requires integration discipline and risk management.

Structuring the Hybrid Deal

• Clarify indirect access in RISE contract. What systems can access S/4HANA data? At what layer? If your on-premise BI tool reads financial data from RISE, is that indirect access? SAP's definition varies by contract. Lock this down in writing.
• Request API SLAs from SAP. If you're integrating on-premise systems to RISE, SAP should commit to API uptime, throttling limits, and data freshness.
• Budget for integration engineering. Hybrid architectures require middleware (SAP Cloud Platform Integration, MuleSoft, or Zapier). Cost: €200-500K upfront, €50-100K annually for maintenance.

What to Do This Quarter

If you're evaluating RISE or mid-contract, here are the immediate actions that drive results:

Before Any RISE Discussion with SAP

1. Run USMM Report: Get your actual active user count from ECC in the last 90 days. SAP's baseline will be 10-20% higher. You now have negotiating ground.
2. Get Third-Party Maintenance Quotes: Rimini Street, Spinnaker, or IBM for any retained on-premise systems. This is your leverage. SAP will discount if you credibly move support elsewhere.
3. Benchmark RISE Infrastructure Against Hyperscaler Pricing: Use AWS/Azure/GCP pricing pages (SAP's hyperscaler rates are published on SAP's website under NDA). Calculate equivalent monthly cost. RISE is typically 20-30% higher.
4. Build Your Extended ECC Case: Finance, operations, and IT align on: "We can run extended ECC on third-party support for 3-5 more years at lower cost than RISE Year 1." This is your walkaway scenario.
5. Identify BTP Usage: Do you have existing BTP deployments (Analytics, Process Mining)? Get actual consumption data. This is your opening for credit-to-cash conversion.

The 3 Numbers You Must Know Before Negotiating

1. Your Actual Active User Count (from USMM): Not SAP's estimate, your data. Example: 850 users, not SAP's proposed 1,000. This saves €150-250K annually immediately.
2. Your Retained On-Premise Support Cost (third-party quote): Example: Rimini Street quote of €75K annually for your CRM system vs SAP's €220K. Difference: €145K annually. Show this to SAP.
3. Your Hyperscaler Infrastructure Benchmark: Example: AWS S/4HANA equivalent to RISE proposal costs €4M annually. RISE infrastructure component is €6.5M. Demand a €1.5M discount or the right to host on your AWS account.

Armed with these three numbers, you have negotiating power. SAP's initial proposal assumes you don't know these benchmarks. You now do.