RISE with SAP Renewal Window: Cost Optimisation Tactics

Named user licences in RISE with SAP Private Cloud Edition follow the same user type hierarchy as on-premise SAP: Professional, Limited Professional, Employee, ESS, and Developer. The key insight for renewal is that SAP's initial proposal will typically maintain your current user mix — even if actual usage patterns have shifted significantly since original signing.

Before renewal, audit your user base using USMM data and access reports from SAP For Me. Specifically: identify users who haven't logged in for 90+ days (candidates for deactivation); identify Professional users whose actual role-based transactions qualify them for Limited Professional classification; and identify Employee users who are actually accessing only ESS self-service functions.

SAP Professional licences cost 3–5x more than Limited Professional. Moving 100 users from Professional to Limited Professional on a €1,200/user Professional rate to a €350/user Limited Professional rate saves €85,000 annually — €425,000 over a five-year renewal term. Do the arithmetic on your own user population, then present it as a structured reclassification proposal rather than a simple price reduction request. Our SAP named user reclassification guide provides the methodology.

SAP Business Technology Platform (BTP) credits are bundled into every RISE contract. At original signing, the credit allocation was typically sized against projected integration, extension, and analytics use cases that often weren't fully realised in Year 1 or 2. SAP's renewal proposal will almost always maintain the same credit allocation at an inflated price.

Request a detailed BTP consumption report from SAP covering credit usage by service category: Integration Suite, Extension Suite, Data & Analytics, and AI services. If your consumption is below 60% of the contracted allocation, you have a clear basis to right-size the renewal allocation. The argument: "We're happy to commit to the credits we'll actually use. We're not willing to pay for credits we've demonstrated we don't consume."

If SAP pushes back, propose a consumption-based BTP model for the renewal with a committed floor and automatic top-up if you exceed it. This aligns your incentives (you pay for what you use) with SAP's (they want you using more BTP services). Our article on RISE BTP credit cost optimisation covers the detailed mechanics.

RISE with SAP includes SAP-managed infrastructure on AWS, Azure, or GCP. SAP passes through hyperscaler costs with a margin. The direct hyperscaler market has seen consistent price reductions of 5–10% annually as competition intensifies and efficiency improves. If SAP hasn't passed through these savings — and in most cases they haven't — your renewal infrastructure cost is inflated relative to market.

Request a detailed breakdown of the infrastructure cost component in your renewal proposal. Compare it against published AWS, Azure, or GCP pricing for equivalent compute, storage, and networking capacity running SAP-certified configurations. The comparison won't be exact — SAP's managed service includes management overhead — but the directional gap will be visible and negotiable.

Use the comparison to negotiate either a direct price reduction or a commitment from SAP to pass through hyperscaler cost reductions annually — a clause that is particularly valuable in a five-year renewal. See our analysis of RISE hyperscaler choice and pricing implications for detailed benchmark data.

SAP's Enterprise Support fee of 22% of net licence value annually is one of the highest support cost ratios in enterprise software. In a RISE context, this is often embedded in the overall price rather than called out — but the economics are the same. At renewal, you have 12 months of actual support usage data to challenge this fee against.

Pull your SAP support ticket data for the current contract year: total ticket volume, priority breakdown (P1/P2/P3/P4), average resolution time, SLA breach count, and SAP-initiated advisory sessions consumed. Compare this against what SAP's 22% fee implies in terms of service value. For most enterprises, the ratio is deeply unfavourable.

While eliminating or significantly reducing the Enterprise Support fee is rarely achievable at renewal, using the data to negotiate enhanced service commitments, additional SAP learning credits, or SAP MaxAttention access at no incremental cost — all of which have genuine economic value — often is. Our detailed guide on SAP support cost reduction covers the full range of approaches.

Price escalation clauses are the most financially consequential cost optimisation opportunity in any RISE renewal, because their impact compounds over the full contract term. SAP's standard contracts include CPI-linked or SAP-defined escalators that can increase contract value by 5–10% annually. Over a five-year renewal, an uncapped 8% annual escalator converts a €10M base contract into a €14.7M Year 5 contract — a 47% cost increase from the passage of time alone.

Negotiating an escalation cap is therefore the highest-value single action in any renewal. The negotiating approach: frame it as a mutual risk management tool, not a cost reduction request. "We're prepared to commit to a multi-year renewal, but we need pricing predictability for our internal budgeting. A cap of 3% gives us that predictability while allowing SAP to maintain real pricing growth above CPI."

SAP will counter with their standard escalator or propose a higher cap. Push back with documented evidence that your current infrastructure costs (which SAP passes through) have been flat or declining, and that your user count has not grown at the rate projected at initial signing. The goal is 2–3% for large enterprise accounts; 3–5% is achievable for mid-market. Never accept an uncapped escalator in a multi-year contract.

RISE contracts frequently include bundled SAP cloud applications — SuccessFactors, Ariba, Concur, SAC, Signavio — that were included because they appeared in the initial sizing model but have not been deployed or adopted. At renewal, each of these represents a cost line that can be challenged.

Audit every SAP application in your current RISE scope against active user adoption data. Any application with fewer than 10% of licensed users actively using it is a candidate for scope reduction at renewal. SAP will argue that you need to maintain scope for future adoption; your response is that you'll pay for adoption at the point it occurs, not years before it might happen.

This tactic requires careful sequencing: don't signal scope reduction intentions early, or SAP will price the remaining scope higher to compensate. Raise it as a commercial position once overall renewal economics are on the table.

SAP's commercial team is incentivised to protect headline price by offering non-cash concessions — additional credits, professional services days, training allocation, implementation support. These concessions have genuine economic value but are often underweighted by buyers who focus exclusively on the headline number.

Build a concession portfolio before your renewal negotiations: calculate the market value of every non-cash item SAP might offer. SAP Learning credits typically retail at €500–€1,500 per credit. SAP MaxAttention access costs €200,000–€500,000 per year for enterprises that don't include it in their standard contract. Professional services days at SAP's published rates run €1,500–€3,000 per day.

Present a package request: "We'd accept the renewal at X price if SAP would include Y credits of SAP Learning, Z days of Premium Support Advisory, and a commitment to include the next major S/4HANA release within 6 months of general availability." Packaging multiple asks in a single proposal makes it harder for SAP's commercial team to decline each individual item.