SAP RISE Evaluation Framework

What RISE with SAP Actually Is — and What It Isn't

SAP launched RISE with SAP in January 2021 as its flagship cloud transformation offering. The marketing positions it as a "business transformation as a service" — a single contract that moves your ERP to S/4HANA Cloud while providing infrastructure, tools, and support. In practice, it is a commercial bundling strategy designed to lock customers into a long-term, SAP-managed environment while increasing total licence and service spend.

RISE bundles five core components into a single subscription: S/4HANA Cloud (Private Edition), SAP Business Technology Platform (BTP) credits, hyperscaler infrastructure management, SAP-managed services, and access to SAP's Business Network. Each component has its own pricing logic, and each is priced at a premium within the bundle.

A critical distinction: RISE with SAP is not simply "SAP in the cloud." Customers who already run S/4HANA on-premise on AWS or Azure are not RISE customers. RISE customers have contracted SAP to manage their infrastructure — a service layer that costs 15–25% above self-managed hyperscaler deployment for most organisations above 2,500 FUE.

Decoding the RISE Commercial Model

SAP prices RISE on a Full Use Equivalent (FUE) basis. FUE is a normalisation metric that converts all SAP user types into a single unit: one Professional Named User equals one FUE, one Limited Named User equals 0.3 FUE, and so on. The FUE count in your RISE proposal is almost always higher than your current on-premise user count — because SAP reclassifies users during the transition process.

The three commercial levers that determine your annual RISE subscription price are FUE count, S/4HANA Edition tier (Cloud vs. Cloud Private), and BTP credit allocation. SAP's standard RISE proposals allocate BTP credits at 1.5–2x actual expected consumption, then price those credits at 15–20% above standalone BTP list price. The effect: you pay a premium for capacity you'll never use.

Named User types matter enormously in RISE. SAP has been progressively reclassifying previously "Limited" users as "Professional" users through contract language changes in RISE agreements — particularly for users who access SAP Fiori apps, run analytical reports, or interact with SAP through integrated third-party systems. Before signing a RISE contract, conduct a full user classification audit against SAP's current RISE user type definitions.

The Hidden Cost Multipliers

The three cost elements that most frequently cause RISE TCO to exceed initial proposals are Digital Access charges, Clean Core compliance costs, and integration fees — none of which appear prominently in SAP's commercial proposal templates.

Digital Access Charges

Digital Access was introduced in SAP's licence model in 2018 and has been progressively applied within RISE contracts. It charges for indirect/digital access — when a third-party application (a custom mobile app, a customer portal, an IoT device) reads or writes data into S/4HANA via APIs or interfaces. The charge is applied per document type created, not per user. A manufacturing company that creates 10 million production orders annually via MES system integration could face Digital Access charges of $500K–$2M per year that were never disclosed in the RISE sales process.

Clean Core Compliance Costs

SAP's Clean Core strategy requires RISE customers to remove ABAP custom code modifications from the S/4HANA core and reimplement them as BTP-side extensions. This is technically sound but commercially significant: every custom process that moves to BTP consumes BTP credits. If your RISE proposal doesn't account for your current custom code volume — which most don't — you will face either significant BTP credit top-up costs post-migration or programme delays while the scope is renegotiated.

Integration Fees

RISE includes a fixed allocation of SAP Integration Suite capacity within BTP. For organisations running complex landscapes with 15+ integrated systems, this allocation is typically insufficient. Additional Integration Suite capacity is priced at a significant premium within RISE vs. standalone contracts. Get your integration landscape mapped before the RISE contract is signed — not after.

RISE vs. Self-Managed S/4HANA: A Genuine TCO Comparison

SAP's RISE TCO model — which SAP will present as a neutral comparison — is not neutral. It uses list prices for hyperscaler infrastructure and inflated SAP Basis/managed services costs for the self-managed scenario, while applying optimistic assumptions to RISE delivery timelines and ongoing support costs.

An independent 5-year TCO model for a mid-size enterprise (3,000–8,000 FUE range) typically shows the following split between RISE and self-managed S/4HANA on a hyperscaler:

RISE makes economic sense when: your organisation lacks internal SAP infrastructure capability, you have no existing hyperscaler discount or EDP in place, and your S/4HANA migration is genuinely greenfield with limited custom code complexity. For most large enterprises, at least two of those three conditions are not met.

Contract Red Flags: What to Negotiate in Every RISE Deal

Based on reviewing hundreds of SAP RISE contracts, the following clauses appear consistently and consistently favour SAP. Each should be challenged before signature.

SAP Negotiation Playbook: Proven Commercial Levers

SAP's sales motion for RISE typically involves a scarcity narrative ("this pricing is only available until quarter-end"), a bundled discount that obscures individual component pricing, and a multi-year commit in exchange for upfront concessions. Understanding this motion is the first step to countering it effectively.

The most powerful negotiation levers available to RISE buyers are: credible competitive alternatives (Workday, Oracle Fusion, Microsoft Dynamics), your existing hyperscaler relationship depth (an Azure MACC or AWS EDP weakens SAP's infrastructure story significantly), maintenance revenue retention (SAP strongly prefers not to lose S/4HANA maintenance revenue while you're in transition), and SAP's quarter-end and year-end commercial pressure windows.

On pricing benchmarks: RISE contracts for organisations in the 2,000–5,000 FUE range should target 28–35% discount off SAP list price. Organisations above 5,000 FUE should target 35–45% off list. Anything below 25% off list is a poor deal regardless of what SAP presents as "standard" — and their first offer is virtually always 10–18% off list at most.