RISE with SAP Renewal Negotiation: What to Demand Before You Sign Another 3-Year Term

SAP's RISE renewal team will contact you 12 months before your term expires. They will come armed with upgrade proposals, enhanced tier offerings, and just enough new features to distract from the core commercial question: are you being charged the right amount for what you actually receive? Most enterprises sign RISE renewals on terms that are structurally worse than what independent negotiation would achieve. This article gives you the framework to change that.

The RISE with SAP renewal negotiation is qualitatively different from a first-time RISE signature. You now have operating history — actual consumption data, actual SLA performance records, and actual cost-per-user figures — that SAP's original proposal obscured behind projections and packaging. Use that information asymmetry in your favour.

Why the RISE Renewal Is the Most Important SAP Negotiation You Will Have

A RISE renewal isn't a routine contract extension. It's a multi-year commitment that typically represents your single largest SAP spend item, often running to eight or nine figures annually for mid-to-large enterprises. The terms you agree at renewal will govern your SAP costs for the next 3–5 years, including pricing escalators, infrastructure scope, and the exit provisions that determine how costly it will be if you want to change course later.

SAP knows you are less likely to exit RISE at renewal than to renegotiate it. Your team is embedded in the platform, your integrations are live, and the migration cost to leave is real. SAP's renewal team prices for this inertia. Their first renewal offer will almost always contain pricing increases framed as "standard escalation" or "enhanced value additions" — and almost always includes terms less favourable than what was achievable at first signature.

The counter to this is preparation, alternatives, and time. Enterprises that begin their RISE renewal analysis 18 months before term end — not 3 months — consistently achieve materially better outcomes than those who allow SAP to control the timeline.

SAP's Renewal Playbook — Know It Before They Use It

The tier upgrade pitch. SAP will propose moving you from your current RISE tier (Base, Premium, or Cloud ERP Private) to the next tier up. This is presented as a value enhancement but is structurally a price increase. The additional capabilities in the higher tier are rarely things you have asked for or will use.

The AI upsell. SAP's 2025 AI licensing changes — the introduction of SAP Business AI Base and Premium packages, and SAP AI Units — are being used aggressively in renewal conversations to add new line items to RISE contracts. Unless you have a specific, quantified business case for AI capabilities, resist being bundled into AI consumption commitments at renewal.

The escalator normalisation. SAP will present annual escalators of 3–5% as standard and non-negotiable. They are not. Escalator caps, alternative indexing mechanisms (CPI-linked rather than fixed percentage), and step-down clauses for scope reductions are all negotiable — but only if you challenge them explicitly.

The term extension pressure. SAP will push for a 5-year renewal to lock in revenue. Your commercial interests are better served by a 3-year term with renewal options, which preserves flexibility and creates a renegotiation window sooner.

The 12 Commercial Demands to Make at RISE Renewal

These are the specific commercial asks our advisory team has achieved in RISE renewal negotiations. Not all will apply to every situation, but each should be evaluated explicitly rather than conceded by default.

• Price freeze or reduction on the subscription base — particularly if your user count has declined or you have underutilised components
• Annual escalator cap at CPI or 2%, whichever is lower — not a fixed 3–5% increase
• Explicit right to return unused BTP credits for subscription credit or cash equivalent
• Ramp-down provision allowing reduction of user licences by up to 15% per year without penalty
• Perpetual licence reinstatement rights if RISE is not renewed at next term end
• Written SLA commitments with financial remedies (service credits) for availability failures below 99.5%
• Infrastructure tier flexibility — ability to right-size production and non-production environments annually
• Data portability commitment with defined timelines and cost allocation for migration support at contract end
• No mandatory AI unit minimums unless you have an agreed consumption forecast supported by a business case
• Most Favoured Customer (MFC) clause — if SAP offers a similarly-situated customer better pricing, you receive the same
• No SAP-initiated audit for the term of the agreement, or a defined audit frequency cap
• Executive escalation and named account team with response time commitments for critical issues

SLA and Service Commitments to Lock In

RISE contracts include an SLA, but the standard SAP SLA is structured to protect SAP, not customers. Before signing a renewal, conduct a forensic review of your SLA performance over the prior term. How often did SAP miss availability targets? What was the average response time on P1 incidents? Were there infrastructure incidents that caused application downtime that didn't formally breach the SLA due to exclusion clauses?

The standard RISE SLA excludes a significant number of downtime causes from the availability calculation — planned maintenance windows, force majeure, customer-caused incidents, and hyperscaler outages that SAP classifies as outside their control. In practice, these exclusions mean that enterprise customers regularly experience availability below 99.5% while SAP reports SLA compliance.

At renewal, challenge these exclusion clauses. Push for a broader availability definition that captures actual customer impact rather than SAP's managed availability metric. Demand financial remedies — service credits worth real money, not nominal percentage rebates — for availability failures. And establish escalation procedures that guarantee named SAP executive involvement for incidents lasting more than four hours.

Challenging Pricing Escalators

The annual escalator embedded in RISE contracts is SAP's most powerful revenue growth mechanism. A 4% annual escalator on a €10M RISE contract produces an additional €2.16M in revenue for SAP over a 5-year term — before any scope additions. For the customer, it's a cost that compounds year after year regardless of whether your usage, headcount, or commercial requirements have grown.

The justification SAP typically offers for fixed escalators — "investment in platform development" and "infrastructure cost increases" — doesn't withstand scrutiny. Hyperscaler infrastructure costs have fallen significantly over the past five years. SAP's platform investment produces SAP revenue through AI and feature upsells; there is no principled reason why existing customers should fund it through mandatory price increases.

Challenge the escalator directly. Propose CPI indexing with a cap of 2%. Reference the market reality that cloud platform costs are generally declining, not increasing. If SAP insists on a fixed escalator, negotiate a corresponding right to scope reduction that offsets the increase — so your overall RISE spend remains stable if your business requirements don't grow.

Scope Rationalisation: Returning What You Don't Use

One of the most underused negotiation tools in RISE renewals is scope rationalisation — systematically identifying and returning RISE components that you are paying for but not using. RISE bundles are designed to include more than most enterprises need, partly to simplify SAP's sales process and partly to ensure you're paying for upside capacity that SAP hopes will drive future consumption.

Conduct a consumption audit before your renewal negotiation. Specifically, review: BTP credit consumption (the majority of RISE customers use less than 60% of their allocated BTP credits), SuccessFactors or other HCM modules bundled into the RISE agreement, Signavio or Joule capabilities that were included as "innovation incentives" at first signature but never deployed, and infrastructure tier sizing relative to actual peak load usage.

Every unused component you identify is a negotiation item. SAP will not proactively offer to reduce your RISE scope — the commercial incentive runs entirely in the other direction. But in a renewal negotiation, presenting evidence of systematic underutilisation and requesting corresponding price relief puts SAP on the defensive and creates room for concessions on other commercial terms. For more detail on scope optimisation, see our guide on SAP licence optimisation.

Term Structure and Flexibility Rights

The term structure of your RISE renewal is a commercial decision with long-term implications. SAP strongly prefers 5-year terms because they lock in revenue and reduce the frequency of negotiation opportunities. The customer's interest is typically the opposite: shorter terms with more frequent renegotiation windows preserve flexibility and ensure pricing reflects market conditions.

If SAP insists on a longer term as a condition of improved pricing, negotiate flexibility rights that partially offset the lock-in: annual scope adjustment provisions (right to reduce user counts and infrastructure within defined parameters), mid-term renegotiation trigger clauses (automatic renegotiation if SAP's pricing for comparable new customers is materially lower), and explicit renewal non-extension rights with notice periods of no more than 90 days.

For a complete framework on managing SAP contract structures, see our SAP Contract Guide and our detailed article on SAP contract amendments and mid-term renegotiation.