SAP · RISE · Services
RISE with SAP, services explained. What sits inside the bundle, and what sits outside.
The buyer side breakdown of every service inside RISE with SAP, every product outside it, and the negotiation seams before signing.
The buyer side breakdown of every service inside RISE with SAP, every product outside it, and the negotiation seams before signing.
RISE with SAP is a bundled service contract that includes the S/4HANA software, the infrastructure, the managed services, and a thin BTP allocation. Knowing the seam between included and excluded is the negotiation gate.
RISE with SAP is the publisher's umbrella program for moving customers from on premise S/4HANA or older ECC platforms to the managed S/4HANA Cloud Private Edition. It is bundled. It is multi year. It is the contractual centre of any SAP renewal cycle from 2024 onward.
The services inside RISE are real and meaningful. SAP runs the infrastructure, the database, and the operating system layer. The customer keeps responsibility for the application configuration, the customizations, and the data.
RISE breaks into four principal bundled components, each priced through the same Full User Equivalent (FUE) metric.
The bundle defines the negotiation surface. Anything inside the bundle competes for the same discount budget.
Anything outside the bundle runs on its own renewal clock and its own discount table.
SAP offers three managed service tiers under RISE. Each carries different SLA commitments and different pricing.
SAP defaults most proposals to Premium. The Premium tier carries a thirty to forty percent premium over Base on the same scope.
Many customers run workloads where Base is sufficient. The buyer side move is to right size the tier against the actual SLA requirement.
The tier multiplier applies to the entire RISE contract. Splitting workloads between tiers requires multiple RISE contracts.
Negotiating tier mix at signing is significantly easier than renegotiating mid term. Right size before the signature.
RISE managed service tier comparison
| Tier | SLA target | Support hours | DR posture | Pricing premium |
|---|---|---|---|---|
| Base | 99.5% | Business hours | Single region | Baseline |
| Premium | 99.7% | 24/7 | Multi region | +30 to 40% |
| Premium Plus | 99.9% | 24/7 + TAM | Enhanced DR | +60 to 80% |
| Custom | Negotiated | Negotiated | Custom DR | Variable |
Under RISE, SAP contracts the hyperscaler infrastructure directly. The customer has no relationship with AWS, Azure, or GCP for the RISE workload.
This simplifies operations but limits portability. The hyperscaler choice is locked at the contract effective date.
Customers with existing hyperscaler discount agreements often want to apply that discount to the RISE infrastructure.
The standard RISE contract does not allow this. The buyer side play is to negotiate a discount pass through clause before signing, especially on AWS EDP or Azure MACC commits.
Region is locked at signing. Region change mid term is rare and requires a contract amendment.
Portability clauses are negotiable. The standard contract has no portability rights. Buyer side practice is to add a hyperscaler portability clause at signing.
The published SLA varies by tier. Premium typically guarantees 99.7 percent availability. Premium Plus typically guarantees 99.9 percent.
Service credits are the financial remedy for breach. The credits are real but rarely meaningful in size. The negotiation move is to widen the credit table and to add a sustained breach exit clause.
RISE is not one contract. It is four cost lines bundled into one signature. The negotiation goes well only when each line is dimensioned, capped, and renewable on its own terms.
RISE prices on Full User Equivalents (FUE). Every SAP user type converts to a FUE total through published ratios.
The ratios are asymmetric. A Self Service user converts at 0.2 FUE. A Professional user converts at 1.0 FUE. The conversion math drives the contract value.
RISE contracts run three or five year. Five year terms carry the deepest discounts, often eight to twelve points better than three year.
Volume discount steps are published. Movement above the next FUE band materially shifts the per FUE price.
Standard RISE renewals carry a published escalator, typically four to six percent annual.
The escalator is negotiable. Capping it at a defensible CPI proxy is a standard buyer side play.
The bundled BTP allocation is typically not enough for an enterprise integration estate.
The overrun is billed at retail or triggers a separate BTP enterprise contract. Read the related SAP BTP knowledge hub for the credit framework.
RISE does not include digital access licensing. Indirect access from non SAP systems still incurs document or user based fees.
The digital access conversation runs in parallel to the RISE renewal but on a different clock.
Customers with heavy ECC customization frequently underestimate the conversion effort to S/4HANA Cloud Private Edition.
RISE does not include the conversion work. Systems integrator engagement is separate and often runs into the millions on complex estates.
Open the RISE conversation no later than twelve months before the desired effective date.
The contract has four interacting cost lines and the negotiation needs time to land each one.
S/4HANA Cloud Private Edition software, hyperscaler infrastructure (AWS, Azure, or GCP), SAP managed services (OS, DB, monitoring, backup, DR), and a small BTP credit allocation.
No. Digital access (indirect use) is billed separately on documents or users. The conversation runs in parallel to the RISE renewal.
Yes, at signing. Choice of AWS, Azure, or GCP. After signing, the hyperscaler is locked unless a portability clause was negotiated.
Premium adds 24/7 support, tighter SLA targets (99.7 vs 99.5 percent), and multi region disaster recovery. Premium typically carries a 30 to 40 percent pricing premium over Base.
Yes, but the conversion from on premise S/4 or ECC to RISE S/4HANA Cloud Private Edition is customer led and not included in the RISE fee.
Rarely. The bundled allocation is small. Most enterprises carry a separate BTP commit on top of RISE to handle integration and extensibility workloads.
Not by default. The standard RISE contract does not allow hyperscaler discount pass through. Negotiate the clause before signing.
No later than twelve months before the desired effective date. The contract has four interacting cost lines and the negotiation needs time to land each one.
SAP RISE pricing benchmarks, the CVR framework, indirect access posture, and the buyer side moves across the full SAP estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
RISE looked simple on the cover page. The reality was four contracts pretending to be one. Redress unpicked the tier mix, capped the BTP overrun, locked hyperscaler portability, and added a sustained breach exit. The total run rate dropped fourteen percent over five years.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
RISE renewal moves, FUE conversion intelligence, BTP carry forward, indirect access framework, and the wider SAP leverage signals.
