RISE with SAP Negotiation Tactics — Article Series

Key Takeaways

  • SAP's RISE sales team is trained to handle enterprise objections. Asking the right questions disrupts their playbook and forces transparency on pricing assumptions.
  • The most valuable questions concern itemised component pricing — demanding a line-by-line breakdown of what you are paying for in the bundle
  • Questions about BTP credit consumption, escalation mechanisms, and hyperscaler flexibility are the highest-value areas for RISE negotiation tactics
  • Many enterprises never ask about contract exit provisions, user reassignment rights, or Digital Access risk — clauses that become expensive problems in Years 3–5
  • How SAP responds to these questions tells you as much as the answers themselves — evasiveness signals a commercial pressure point

RISE with SAP negotiation starts with information. Before you can challenge a price, demand a concession, or deploy a counter-strategy, you need to understand how SAP has structured the deal you are being offered. The questions below are designed to do exactly that — extract the commercial, contractual, and technical assumptions behind your RISE proposal.

These are not polite discovery questions. They are designed to challenge SAP's pricing logic, expose inflated assumptions, and create the negotiating space for a materially better RISE deal. Ask them directly. Record the answers. Use them in subsequent negotiation rounds.

For the broader framework of how these questions fit into a complete RISE negotiation strategy, see our complete RISE negotiation tactics guide.

Questions About Pricing and Deal Structure

Question 1
"Can you provide an itemised breakdown of this RISE proposal — showing the cost of S/4HANA users, infrastructure, BTP credits, Enterprise Support, and Business Network separately?"
Why it matters: SAP bundles RISE components deliberately to obscure individual pricing. Demanding itemisation forces transparency and allows you to challenge each component against market benchmarks. SAP will often resist this — push hard. Without itemisation, you are negotiating blind.
Question 2
"What is the infrastructure cost component of this proposal, and how does it vary by hyperscaler — Azure, AWS, and GCP?"
Why it matters: RISE infrastructure costs differ by hyperscaler. SAP earns different economics from each provider, and infrastructure is frequently one of the most negotiable components of the deal. If you receive a single infrastructure figure regardless of hyperscaler choice, SAP is obscuring legitimate pricing variation. Our contract negotiation team models hyperscaler cost differences as part of every RISE engagement.
Question 3
"What user types are included in this pricing, and on what basis have the user counts been established?"
Why it matters: RISE user counts are derived from your current ECC landscape — which is almost always inflated. Active user counts, user type classifications, and the distinction between named users and Digital Access documents have a massive impact on pricing. If SAP cannot explain exactly how they derived the user mix in your proposal, the numbers are not grounded in your actual requirements.
Question 4
"How were the BTP credit volumes in this proposal determined? What specific use cases were they sized for?"
Why it matters: Most RISE proposals include BTP credits sized at 2–3× what the enterprise will actually consume. If SAP cannot articulate specific use cases that justify the BTP volume — integration scenarios, extension development, analytics workloads — the credits are oversized and you are paying for capacity you will not use. Right-sizing BTP is consistently one of the highest-return RISE negotiation tactics.
Question 5
"What annual price escalation is built into this contract, and is it tied to a specific index?"
Why it matters: Standard RISE contracts include escalators of 3–5% annually. On a €10M deal, a 4% escalator adds over €2M to the 5-year cost compared to a CPI-capped deal. Knowing the escalation mechanism upfront is essential — and the answer creates an immediate negotiation opportunity if the proposed rate exceeds inflation.

Questions About Contract Terms and Flexibility

Question 6
"What are the contract termination rights and exit provisions if we need to migrate off RISE before the contract ends?"
Why it matters: RISE contracts are typically 5 years. SAP's standard Order Form contains onerous exit provisions that create significant financial exposure if your business requirements change. Negotiating meaningful termination-for-convenience rights — even with a defined financial penalty — is critical for any enterprise that cannot guarantee its strategy will remain static for 5 years.
Question 7
"Can we reassign user licences freely within the organisation, and are there restrictions on user type changes without additional cost?"
Why it matters: Organisations change. People leave, roles evolve, and the user mix that made sense in Year 1 is rarely the right mix in Year 4. Standard RISE terms restrict user reassignment and user type changes in ways that force organisations to buy additional licences rather than reclassify existing ones. Negotiating flexible reassignment and reclassification rights upfront prevents expensive contract amendments later.
Question 8
"What happens to unused BTP credits at the end of each contract year — do they roll over, or are they forfeited?"
Why it matters: Many RISE contracts include annual BTP credit pools that expire if unused. If your BTP consumption is seasonal or project-based, annual credit expiry means you are effectively paying twice for credits you could not consume in time. Negotiating multi-year credit rollover — or a consumption-based model — eliminates this structural cost trap.
Question 9
"What Digital Access documents are included in this contract, and how is Digital Access compliance managed under RISE?"
Why it matters: Digital Access is one of the most significant sources of unexpected cost in SAP environments. When third-party systems create Orders, Deliveries, Invoices, or Materials in your SAP landscape, Digital Access document charges apply. A RISE contract that does not explicitly address your current third-party integrations is an undisclosed compliance liability. Our indirect access advisory team assesses Digital Access exposure as part of every RISE review.
Question 10
"What SLA guarantees are included for system availability, and what are the remedies if SAP fails to meet them?"
Why it matters: RISE SLAs are often presented as strong — 99.5% or 99.9% availability. But the devil is in the exclusions: planned maintenance windows, force majeure clauses, and limited financial remedies for SLA failures often mean the practical protection is far weaker than the headline figure suggests. Negotiate financial credits tied to actual business impact, not SAP's standard service credit formula.

Questions About Migration and Implementation

Question 11
"What migration assistance credits or transition funding is available, and what are the conditions attached to them?"
Why it matters: SAP has migration assistance budgets that are deployed strategically — typically when they believe a deal is at risk. The conditions attached to migration credits matter as much as the amount: credits tied to a specific hyperscaler, implementation partner, or timeline can negate the financial benefit. Always model the total value of a migration credit offer against its conditions before accepting.
Question 12
"Can we extend the migration timeline beyond 12 months if implementation complexity requires it, without triggering additional charges?"
Why it matters: SAP migration projects routinely take longer than planned. RISE contracts that set aggressive go-live timelines with financial penalties for delays create cost risk that belongs entirely to the enterprise. Negotiate reasonable migration extension provisions — at minimum, a 6-month no-penalty extension — before signing.
Question 13
"Are we required to use SAP-certified implementation partners for the RISE migration, and what are the cost implications of that restriction?"
Why it matters: SAP RISE contracts sometimes include preferred implementation partner requirements that restrict your ability to negotiate SI pricing or choose a partner on merit. If your contract restricts implementation partner choice, the cost of the SI work is effectively controlled by SAP — which creates a hidden cost that is not visible in the software and infrastructure pricing.

Questions About Commercial Precedents and Benchmarks

Question 14
"What discount has SAP offered to comparable enterprises — same industry, similar NLV — for equivalent RISE deals?"
Why it matters: SAP will not answer this question directly. But asking it signals that you have access to market benchmark data and are not negotiating against SAP's list price in isolation. It shifts the commercial framing from "what SAP will offer" to "what the market expects" — a much stronger basis for negotiation. For the benchmarking process itself, see our article on RISE with SAP cost optimisation tactics.
Question 15
"What is SAP's best and final offer if we sign before your fiscal year-end on September 30?"
Why it matters: This question deploys timing leverage explicitly. SAP's account team has deal-closing incentives tied to quarter-end and year-end. Asking for their best price tied to SAP's fiscal deadline signals that you are a serious buyer with a genuine decision timeline — and creates the space for SAP to deploy discretionary concessions that would not be available otherwise.

Questions About Audit and Compliance Risk

Question 16
"Does the RISE contract include any audit rights for SAP to measure our licence compliance, and how does that work in a cloud environment?"
Why it matters: RISE does not eliminate SAP's audit rights — it changes how they are exercised. In a managed cloud environment, SAP has access to system usage data that was previously unavailable in on-premise deployments. Understanding exactly what SAP can measure, how they will use it, and what the contractual consequences of a compliance gap are is essential before signing. Our SAP audit defence team reviews audit provisions as part of every RISE contract assessment.
Question 17
"How are third-party integrations handled under RISE — specifically, how does SAP's Digital Access model apply to our existing non-SAP systems?"
Why it matters: Third-party integration risk under Digital Access is one of the most common sources of unexpected cost in SAP environments. If your enterprise has non-SAP systems creating transactions in SAP — and most do — the Digital Access implications need to be explicitly addressed in the RISE contract, not left to a future audit cycle.
Question 18
"What is the contractual process for resolving a licence compliance dispute under RISE, and what external dispute resolution mechanisms are available?"
Why it matters: SAP's standard contracts give SAP significant latitude to define and enforce compliance findings, with limited external arbitration rights. Negotiating a defined dispute resolution process — including independent expert determination — before signature is far easier than challenging SAP's findings after a compliance gap is identified.

Questions About the RISE Advisory Relationship

Question 19
"If we engage an independent SAP licensing advisor to review this proposal, will SAP continue to work constructively with us through that process?"
Why it matters: SAP's reaction to this question is revealing. SAP will generally confirm they work with independent advisors — they have no choice. But how they frame the answer tells you whether they expect the independent review to create deal friction. Enterprises that bring independent RISE advisors into the process consistently achieve better outcomes — and SAP's account team knows it.
Question 20
"What additional value can SAP offer — credits, services, extended terms, SLA improvements — if we commit to this deal in this quarter?"
Why it matters: This is the closing leverage question. After deploying the 19 questions above to understand the deal, challenge the pricing, and identify the commercial pressure points, this question harvests the remaining discretionary value SAP can offer. Framing it as a closing commitment — tied to SAP's timing interests — activates deal-closing incentives that otherwise stay on the table.
Field Note — Typical SAP Response Patterns

When we accompany clients through RISE negotiations, we track how SAP responds to structured questioning. The most reliable signal that a deal has significant pricing room is SAP's reluctance to itemise components (Questions 1–2) or to explain how BTP credit volumes were sized (Question 4). In 80% of cases where SAP resists itemisation, subsequent negotiation rounds — deploying the structured negotiation strategies outlined in this series — produce savings of 20–35% versus the initial proposal.

The most powerful combination is Questions 1, 4, and 15 deployed together: itemisation, BTP right-sizing, and fiscal year-end leverage. This combination has produced the largest RISE deal savings in our experience — consistently unlocking concessions that were never part of SAP's standard negotiation playbook.

Frequently Asked Questions

When is the right time to ask these questions in the RISE sales process?
These questions should be asked across multiple rounds, not in a single session. Questions 1–5 (pricing structure) belong in your first formal proposal meeting. Questions 6–10 (contract terms) should be tabled when SAP presents their draft Order Form. Questions 11–13 (migration) should be addressed before any migration timeline is agreed. Questions 14–15 (leverage) are most powerful in Q3, when SAP's quarter-end pressure is highest.
What if SAP refuses to answer or deflects on these questions?
Deflection is information. If SAP refuses to itemise components, that signals the bundle pricing is concealing significant margin. If they cannot explain BTP credit sizing, the credits are likely oversized. Document every non-answer and use it to build the case for an independent review. Engaging an independent RISE advisor who can source market benchmark data externally closes the information gap that SAP's evasiveness is designed to create.
Are these questions appropriate for renewal negotiations, not just new RISE deals?
Yes — and in some ways they are even more powerful at renewal. At renewal, you have 5 years of actual consumption data that directly challenges SAP's pricing assumptions. Questions about BTP credit utilisation, actual user counts versus contracted counts, and Digital Access exposure become empirical rather than theoretical. Renewal negotiations where enterprises have accurate consumption data consistently achieve better outcomes than initial RISE deal negotiations.

RISE with SAP Advisory

Independent review of your RISE proposal, with the full question framework and benchmark data needed to challenge SAP's pricing.

Get Your RISE Deal Reviewed →

RISE Negotiation Strategies

Once you have the answers, here is how to deploy them — a structured approach to RISE contract negotiation that extracts maximum value.

Read the Strategies →

Get Expert Help Before You Sign

These questions are more powerful with independent benchmark data behind them. Our RISE advisory team provides the commercial intelligence SAP never shares — and deploys it on your behalf throughout the negotiation.

Book a Free RISE Consultation