⚡ Key Takeaways
- SAP opens the RISE renewal window 18–24 months before expiry — earlier than most enterprises realise
- The first renewal proposal is almost always inflated by 15–30%; the real number is negotiable
- Critical questions around escalation caps, BTP credits, exit rights, and scope changes can save millions
- SAP's fiscal year deadlines create artificial urgency — you have more time than SAP implies
- Independent advisory before signing saves enterprises an average of 25–35% on RISE renewal value
The RISE with SAP renewal window is the most commercially significant moment in any enterprise's SAP relationship after the initial signing. SAP knows this. That's why their commercial team starts engaging 18–24 months before contract expiry — not to give you time to think, but to shape your thinking before you've had a chance to challenge their numbers. Asking the right questions during the RISE with SAP renewal window separates enterprises that sign inflated multi-year commitments from those that negotiate from genuine strength.
What makes this window so dangerous is its appearance of simplicity. RISE is positioned as a single contract, one vendor, one price. But the renewal is anything but simple. Scope has almost certainly changed since you signed. Your BTP credit usage may be well below what was included. The infrastructure layer costs may have shifted. And SAP's initial renewal proposal will reflect none of these realities in your favour.
Our RISE with SAP advisory team has reviewed dozens of renewal proposals across industries. The pattern is consistent: SAP's first number is not the final number. The difference between the two is determined by the questions you ask before you sign. This guide gives you those questions.
Why Questions Are Your Primary Weapon in RISE Renewal
SAP's commercial process is built around momentum. The bigger the deal, the more SAP invests in keeping that momentum moving in one direction — toward signature. Every delay in their renewal process represents a loss of leverage for SAP and a gain of leverage for you. Questions do two things: they slow down SAP's process, and they force SAP to justify positions that were never meant to be justified.
SAP's renewal proposals typically bundle together components that have very different negotiating dynamics. The licence component, the BTP credits allocation, the infrastructure cost pass-through, the support fees, and the professional services wrapper all have different pricing logic — and different amounts of flexibility. When SAP presents a single number, you lose visibility into each component's negotiability. Breaking the proposal apart with targeted questions is how you recover that visibility.
Watch for this tactic: SAP often presents renewal proposals just before or during their fiscal year-end (September 30) or quarter-end. The implied message is "sign now or lose this pricing." This is almost always artificial urgency. SAP's pricing in January is not materially different from their pricing in October. Don't let fiscal calendar pressure substitute for proper due diligence.
Section 1: Questions About Pricing and Scope
The pricing questions are the ones SAP least wants to answer in writing. Ask them anyway — and ask for written responses.
Question 01
"What is the itemised breakdown of the renewal price — by licence component, BTP credits, infrastructure, and support?"
SAP presents a bundled number because it obscures which components carry the most margin. Breaking it down reveals where SAP has the most flexibility and where your usage data gives you negotiating leverage.
Question 02
"How does the proposed renewal price compare to our actual consumption over the past 12 months?"
If your actual S/4HANA Private Cloud usage, BTP consumption, or named user count has changed since signing, the renewal price should reflect that. SAP will rarely volunteer this comparison.
Question 03
"What price escalation mechanism is built into this renewal, and what is the annual cap?"
Many RISE contracts embed automatic price escalators tied to CPI or SAP's own defined metrics. Without a negotiated cap — typically 3–5% — you could face 8–12% annual increases in an inflationary environment. This must be negotiated at renewal, not discovered mid-contract.
Question 04
"Has the scope of our RISE contract changed since signing — and if so, how is that reflected in the renewal pricing?"
Enterprises frequently add modules, expand geographies, or change hyperscaler preferences since their original RISE signing. Scope changes can go either direction — and both can be used as negotiating leverage in a renewal discussion.
Question 05
"What discount is SAP offering on the renewal, and what discount tier were we placed in at original signing?"
Enterprise discount positioning is a critical lever. SAP assigns accounts to discount tiers based on revenue, strategic importance, and competitive dynamics. Understanding your tier — and whether you should have been placed in a different one — is foundational to any renewal negotiation. See our analysis of
SAP licence price benchmarking in 2026 for reference points.
Section 2: Questions About BTP Credits and Cloud Services
BTP (Business Technology Platform) credits are the most systematically misunderstood component of RISE contracts. SAP includes a block of BTP credits in every RISE deal — but 70% of enterprises never fully consume them. At renewal, unused credits become invisible, and SAP proposes a new block at full price. These questions change that dynamic.
Question 06
"What was our BTP credit utilisation rate over the life of the current contract?"
If you consumed 40% of your BTP credits, you have a strong argument that the renewal allocation should be reduced — or that unused credits should carry forward. SAP will not volunteer this data. You need to request it explicitly and in writing.
Question 07
"Can unused BTP credits from the current contract be carried forward into the renewal term?"
This is almost never offered proactively. It is negotiable. Depending on the volume of unused credits, the value can be significant. Our
RISE BTP credits cost optimisation guide covers the tactics in depth.
Question 08
"What new SAP cloud services are included in RISE that were not available at our original signing?"
SAP's RISE bundle has expanded significantly since 2021. Innovations like SAP Business AI capabilities, Joule integrations, and additional Signavio modules have been added. If you're renewing, you should be paying for what's included — not what existed when you first signed.
Question 09
"What is the hyperscaler infrastructure cost for our current deployment, and how has it changed since original signing?"
SAP passes through hyperscaler costs (AWS, Azure, GCP) as part of RISE pricing. Hyperscaler costs have generally declined over time due to competition and efficiency improvements. If SAP hasn't passed through those savings, you have grounds to negotiate.
Section 3: Questions About SLAs and Service Quality
Renewal is your best opportunity to renegotiate service level agreements that may not have performed to expectations. The moment of renewal — when SAP wants your signature — is the moment they're most flexible on SLA commitments. After signature, you lose that leverage entirely.
Question 10
"What has been our actual service uptime and SLA performance over the current contract term, and what remedies have we received for missed SLAs?"
SAP's RISE SLAs typically guarantee 99.5% or 99.7% uptime. If actual performance was below that, any SLA credits you're owed are directly negotiable against the renewal price. Get the data from SAP For Me before the negotiation starts.
Question 11
"Can we strengthen the SLA commitments in the renewal — particularly around RTO, RPO, and support response times?"
Recovery Time Objectives (RTOs) and Recovery Point Objectives (RPOs) for critical production systems should be explicit in the contract. SAP's standard RISE SLAs are often weaker than what a direct hyperscaler arrangement would offer. Renewal is the time to close that gap.
Question 12
"What is the escalation path and contractual remedy if we experience a major outage during the renewal term?"
Standard RISE contracts provide minimal remedies for outages. Most enterprises discover this only when they need to use it. At renewal, negotiate specific financial remedies tied to downtime duration and business impact. Our
RISE SLA and RACI guide covers what's achievable.
Section 4: Questions About Exit Rights and Flexibility
RISE contracts are long-term commitments — typically 5 years — and exit provisions in the standard contract are extremely restrictive. Renewal is the moment to negotiate exit terms that provide genuine flexibility, not just the appearance of it.
Question 13
"What are the termination for convenience provisions in the proposed renewal contract, and what penalties apply?"
Most standard RISE contracts require payment of all remaining fees upon termination for convenience. This creates a financial lock-in that makes competitive evaluation economically impossible. Negotiating a graduated termination fee structure (declining over time) materially changes your exit economics.
Question 14
"What data portability and migration assistance is included if we decide to exit RISE at contract end?"
The cost of exit from RISE extends far beyond contract termination penalties. Data extraction, format conversion, migration services, and re-implementation costs can dwarf the remaining contract value. Understanding these costs upfront changes your renewal leverage calculation. Our
RISE exit strategy guide covers the full cost picture.
Question 15
"Does the renewal contract include a technology refresh guarantee — i.e., that we'll receive the latest S/4HANA Private Cloud Edition release within a specified timeframe?"
Some RISE customers have found themselves running releases that are 12–18 months behind current, while paying for the latest capabilities. A contractual technology refresh obligation protects your investment and gives you SLA teeth when SAP is slow to update.
Section 5: Questions About Commercial Terms and Contract Structure
Question 16
"What is the minimum commitment volume for the renewal, and what happens if our actual usage falls below that?"
RISE pricing is based on a minimum committed volume of users, transactions, or revenue. If your business contracts or you implement automation that reduces user counts, you may be paying for capacity you no longer need. Understanding the true floor of the commitment is essential.
Question 17
"Can we include a mid-term review clause that allows renegotiation if our business changes materially during the renewal term?"
Five-year contracts in a period of business volatility carry significant risk. A mid-term review clause — triggered by defined criteria such as headcount change greater than 25%, M&A activity, or revenue decline — gives you a contractual right to renegotiate without triggering termination penalties.
Question 18
"What additional discounts or concessions is SAP prepared to offer in exchange for early renewal or an extended term?"
SAP values revenue certainty. If you're willing to commit earlier or for a longer term, they have an economic basis to offer additional concessions — better pricing, enhanced credits, additional services. But they won't offer unless you ask. Our guide to
RISE renewal negotiation strategies details how to structure this conversation.
Section 6: Questions About Support and Maintenance
Question 19
"What is the Enterprise Support fee as a percentage of the renewal price, and is it negotiable?"
SAP's Enterprise Support fee is typically 22% of the net licence value annually. In a RISE context, this is often embedded in the overall RISE price rather than called out separately — which makes it harder to challenge. Forcing visibility on this component often reveals room for negotiation, particularly for customers with low support usage.
Question 20
"What SAP Enterprise Support credits are we entitled to, and have we used all of them in the current contract?"
Enterprise Support includes access to various SAP programmes — SAP MaxAttention, SAP Activate methodology tools, SAP Learning credits, and others. Many enterprises never claim these. At renewal, unused entitlements can be traded for concessions or carried forward. See our article on
negotiating SAP Enterprise Support credits.
Section 7: Strategic Questions to Ask Before Any Negotiation
Question 21
"What is SAP's competitive alternative — i.e., what would it cost us to migrate to Oracle, Workday, or a hyperscaler-native ERP — and has SAP priced their renewal with this in mind?"
SAP's pricing strategy assumes most customers won't seriously evaluate alternatives. Demonstrating that you have — or are prepared to — changes the commercial dynamic entirely. You don't need to threaten a switch; you need to demonstrate you understand the comparative economics. Our
RISE advisory service includes competitive benchmarking for exactly this purpose.
Question 22
"Will SAP confirm in writing that the proposed renewal price represents their best available pricing for an enterprise of our size and profile?"
This question rarely gets a direct answer — but asking it signals that you know pricing is not fixed, that you're prepared to benchmark externally, and that you expect SAP to act in good faith. It shifts the burden of proof onto SAP's commercial team and often precipitates a conversation about additional discounting that was never on the table before the question was asked.
How to Use These Questions Effectively
These questions are not a checklist to run through in a single meeting. They are a structured discovery process that should unfold over multiple interactions with SAP's commercial team. The sequence matters. Start with pricing transparency questions (Section 1) before moving to exit and flexibility questions (Section 4). Establish the data foundation before you begin negotiating concessions.
Document every response in writing. SAP's verbal commitments in renewal discussions rarely survive to the final contract without being explicitly captured. When SAP says "that's included" or "we'll honour that arrangement," your response should always be: "Can you confirm that in writing as part of the contract amendment?"
For cost optimisation tactics specific to RISE renewals, and for the broader context of RISE renewal strategy in 2026, see the other articles in this series.
The independent advisor advantage: Enterprises that engage independent SAP licensing advisors before renewal discussions achieve materially better outcomes than those that negotiate directly with SAP. The reason is simple: SAP's commercial team does this every day. Your procurement team does it once every five years. Equalising that expertise gap is the single highest-return investment in any RISE renewal process.
📬 SAP Licensing Intelligence
Independent SAP Licensing Insights — Free
Expert analysis on RISE renewals, contract negotiation, and SAP cost reduction. No vendor affiliation. Corporate email required.
Frequently Asked Questions
When should we start asking these questions — how early is too early?
Start no later than 18 months before contract expiry. SAP begins their internal renewal process 24 months out. If you wait until 12 months out, SAP has already shaped the commercial framing and your initial proposal will be harder to challenge. Starting early gives you time to gather usage data, benchmark externally, and build a negotiating position before SAP's process has momentum.
Will asking these questions damage our relationship with SAP?
No. SAP's commercial team expects and respects professional buyers who ask rigorous questions. What damages the relationship is unreasonable demands made without evidence, last-minute renegotiation of signed terms, and public disputes. A structured, evidence-based renewal process actually builds commercial credibility with SAP's negotiators — who are evaluated on their own ability to close deals at appropriate margins.
Should we send these questions in writing or ask them in meetings?
Both. Use meetings to establish the topics and understand SAP's initial response. Then follow up with formal written requests for documentation on pricing breakdowns, consumption reports, and SLA performance data. Written requests create a paper trail and put SAP in the position of either providing documentation or explicitly declining to — both of which are useful commercial signals.
What if SAP refuses to answer some of these questions?
Document the refusal. SAP declining to provide consumption data, pricing breakdowns, or SLA performance reports is itself commercially significant. It tells you where SAP's position is weakest and where independent benchmarking will have the most impact. A refusal to answer is not the end of the conversation — it's the beginning of a deeper investigation.
How different are RISE renewal terms from the original signing?
Significantly. The commercial environment has changed since RISE was first introduced in 2021. Hyperscaler competition has intensified. SAP's own profitability targets have shifted. Your usage data is now real rather than projected. And the market has developed benchmarks that simply didn't exist at original signing. Treat the renewal as a new negotiation, not a formality.
Get Expert Support
Ready to Enter Your RISE Renewal Window?
Our independent RISE advisory team has negotiated over 50 RISE renewals. We help enterprises build the evidence base, ask the right questions, and achieve outcomes SAP's commercial team didn't plan for.
Book a Free Consultation →
Case study: A European financial services firm facing RISE renewal was presented with a proposal 28% above their current contract value. By documenting BTP credit underutilisation, benchmarking infrastructure costs against direct hyperscaler rates, and challenging the escalation mechanism, our team helped them achieve a renewal 18% below the initial proposal — while securing stronger SLA commitments and a mid-term review clause. Read more case studies →
Independent SAP licensing advisory — not affiliated with SAP SE. SAP, RISE with SAP, and all SAP product names are trademarks of SAP SE.