The SAP RISE Negotiation Guide

RISE is not a product; it is a contractual repackaging

RISE with SAP is sold as the modernisation path to S/4HANA. The technical product inside RISE is the same S/4HANA you can license on premise. What is different is the commercial wrapper: a single subscription bundling software, infrastructure (on hyperscaler of SAP's choice), and managed services into one consolidated contract. The bundle simplifies procurement; it also obscures the price of each component. The simplification is real for some organisations and a trap for others.

This matters because the comparison customers should run is not RISE versus ECC; it is RISE versus on premise S/4HANA versus hybrid versus extended ECC maintenance. The first comparison is the one SAP wants. The second is the one that produces a defensible decision. Customers who frame the choice as binary almost always end up paying more than necessary.

The 2027 ECC deadline is the leverage moment

SAP's mainstream maintenance for ECC 6.0 ends December 31, 2027. Extended maintenance is available to 2030 at a premium, third party support to 2030 and beyond. Until 2027, SAP's commercial position is strong because every ECC customer must decide. After 2027, SAP's commercial position weakens because the customers who have not migrated have actively chosen alternatives.

The leverage moment is therefore the eighteen months before your individual decision date, which may be earlier than 2027 if your project timeline requires it. Customers who arrive at SAP's negotiation table inside that window with a credible alternative path (extended maintenance, hybrid, on premise S/4HANA) negotiate from strength. Customers without an alternative negotiate from compliance.

FUE conversion: where the user metric inflation hides

RISE prices users in Full User Equivalents (FUEs), a normalisation across what used to be Professional User, Limited Professional User, Employee Self-Service, and Developer named user types. The FUE conversion ratios SAP publishes look reasonable on the surface (1 Professional = 1 FUE, 5 ESS = 1 FUE). The conversion arithmetic, applied across a real customer license inventory with classification drift accumulated over many years, often inflates the apparent FUE count by twenty to forty percent compared with what a clean reclassification would produce.

The fix is to reclassify users by actual usage before any FUE conversation. Pull the SAP transaction frequency data per user, classify each user against the documented FUE thresholds, and produce the correct count yourself. SAP will not volunteer the corrected number; SAP's commercial interest is in the higher conversion total.

Indirect access and the digital access reset

SAP's 2018 digital access pricing model converted indirect access charges from per user to per-document. Documents are counted across nine categories (sales orders, purchase orders, invoices, etc.) at varying rates. Inside RISE, the digital access pricing model travels with you. The bundle does not eliminate the exposure; it changes how the exposure is measured.

The contractual demarcation that determines what counts as digital access is the single most under negotiated provision in any RISE contract. The default contract treats almost every external system integration as triggering digital access. The negotiated contract specifies which integration patterns are permitted, which trigger documents, and which do not. Without the demarcation, you sign up to an open ended exposure that can produce six and seven figure true up bills mid term.

The RISE versus S/4HANA total cost of ownership

A serious comparison between RISE and on premise S/4HANA covers five years across six cost categories: software license or subscription, infrastructure (hyperscaler or on premise), managed services or internal operations, implementation services, ongoing maintenance and support, and migration cost. RISE bundles three of those (software, infrastructure, managed services) into a single subscription line. On premise unbundles them.

The bundling makes RISE look simpler in year one. Across five years, the bundling has a cost: the implicit premium for the bundle, the loss of optionality on infrastructure pricing, and the absence of the cost reduction you would otherwise capture as the on premise estate matures. Customers who model only the first two years routinely select RISE. Customers who model five years more often select a hybrid. The arithmetic depends on the size and shape of the estate. The framework runs the comparison in detail.

The hybrid pattern is real, and often the answer

The framing of the decision as RISE versus on premise forces a binary that the contract does not require. In practice, many of the largest RISE evaluations we have closed produced a hybrid: core ERP modules in RISE for the operational simplicity, ancillary modules on premise for the cost control, with a contractually defined demarcation between them. The hybrid is operationally more complex than either pure path but commercially superior in roughly half of cases.

The hybrid is contractually achievable but commercially difficult. SAP account teams resist hybrid structures because they fragment the commercial relationship. The customer side push for hybrid succeeds when the customer arrives with the workload partition, the cost model, and the contractual demarcation already drafted. Account teams negotiate hybrids when the customer brings the structure; they refuse them when the customer asks for one.

The contractual flexibility provisions that matter

Three contractual provisions determine whether RISE is genuinely flexible or only superficially so. First, the right to reduce subscription quantities at annual checkpoints, with caps on the reduction percentage. Second, the right to migrate workloads between hyperscalers during the term, with the cost responsibility for the migration. Third, the indirect access demarcation discussed earlier. None of these appear in the standard RISE template at meaningful strength. All of them are negotiable for customers who ask.

Without these provisions, the RISE subscription is a fixed quantity, fixed hyperscaler, open ended exposure contract. With them, RISE becomes the flexible commercial wrapper SAP markets it as. The difference is in the appendix. Customers who negotiate the headline subscription discount but not the appendix flexibility lose the value of any discount they secured.

SAP's counter moves and how to handle them

SAP account teams have a small set of repeatable counter moves they deploy when a customer signals serious negotiation. The first is the 2027 deadline acceleration, in which the maintenance end of life is presented as a more urgent constraint than it actually is. The second is the partner ecosystem framing, in which the implementation partner (rarely SAP itself) intermediates the commercial conversation in ways that align with the partner's revenue rather than the customer's cost. The third is the executive sponsorship, in which a senior SAP regional leader engages directly with the CIO to reframe the conversation strategically rather than commercially.

None of these are illegitimate. All of them are negotiation. The guide includes the standard responses we deploy: deadline reframing that documents the actual maintenance options, partner management that distinguishes implementation choice from commercial negotiation, and executive handling that keeps the commercial conversation in the commercial team. Customers who have read the responses in advance handle the moves; customers who encounter them for the first time often do not.