RISE with SAP vs On-Premise: Key Questions to Ask SAP
The 15 essential questions your SAP account executive won't answer unless pressed—and what their responses really mean for your enterprise.
Key Takeaways
- SAP will present RISE as the obvious choice—"one contract, one price, one vendor"—but this framing serves SAP's revenue model, not your enterprise interests.
- The 15 questions in this guide target the opacity SAP deliberately maintains around SLAs, user licensing, exit clauses, and hidden cost escalations.
- Vague or evasive answers on infrastructure accountability, BTP credit expiration, and migration costs are red flags requiring immediate legal review.
- You need independent buyer-side advisory before signing. Your system integrator and SAP partners profit from RISE adoption—they are not your advocates.
- The contract negotiation window is narrow. Ask these questions early, get them in writing, and escalate to SAP's legal team if sales avoids specificity.
Table of Contents
What Is SAP Actually Selling You in RISE?
SAP will present RISE with SAP as the obvious choice. One contract, one price, one vendor to manage your entire S/4HANA journey. But the questions SAP's sales team won't answer—unless pressed—are the ones that determine whether RISE is the right decision for your enterprise or simply the most profitable outcome for SAP.
Before you ask the hard questions, understand what you're actually buying:
The Anatomy of the RISE Bundle
S/4HANA Private Cloud Hosting: SAP hosts your S/4HANA instance on its hyperscaler infrastructure (AWS, Azure, Google Cloud). You don't own the hardware; you rent a slice of SAP's environment. This removes the operational burden of managing the ERP core—but ties you firmly to SAP's infrastructure choices, pricing tiers, and regional availability.
Infrastructure Services & Support: SAP provides 24/7 monitoring, patching, and basic infrastructure support. The devil is in the SLA details—what uptime percentage do they guarantee? Who pays when they miss? What is the incident response time? SAP's standard answers are vague until forced into a legal document.
Enterprise Support: SAP's technical support for your S/4HANA instance. This is not negotiable in RISE; it's bundled and priced as part of the overall deal. You cannot choose a lower-tier support level to reduce costs.
BTP Starter Credits: SAP Business Technology Platform credits are thrown into most RISE contracts as a sweetener. These credits expire if unused. They are worth far less than SAP claims, and many enterprises discover they've paid for unused compute resources when their BTP credits vanish.
What "One Contract" Really Means Commercially: A single contract that consolidates all these elements into a single line item pricing model. SAP controls the arithmetic; you control nothing. Price escalations are contractually baked in. Annual increases often run 3–5% minimum, and SAP reserves the right to adjust pricing on user count, storage consumption, and undefined "consumption metrics."
The S-User Classification Trap
In RISE, every user accessing S/4HANA must be classified as an SAP "S-User." SAP defines S-Users based on functional role, not technical login credentials. This distinction matters enormously: an employee who accesses S/4HANA through a third-party integration tool, a dashboard, or a mobile app can be counted as an S-User even if they never directly use the S/4HANA interface.
SAP measures your S-User population quarterly or annually. Licensing reconciliation can become adversarial. You need to know in advance exactly how SAP will count users and what recourse you have if their count exceeds your projection.
The 15 Questions Your SAP Account Executive Won't Volunteer Answers To
1
What is the exact infrastructure SLA and who is accountable when it fails?
Most RISE contracts specify 99.5% uptime as standard. That sounds reasonable until you realize 99.5% equals 22 hours of downtime per year. More critically: when SAP misses the SLA, what is your remediation? A 5% service credit on one month's bill? A credit that doesn't accumulate? You need written guarantees of specific remediation amounts tied to breach duration. Without this, SAP's liability for missed SLAs is nearly zero.
2
How are my existing Named User licences treated in the RISE migration?
If you have perpetual SAP licenses today, SAP will decommission them upon RISE go-live. You lose the sunk cost. Ask SAP explicitly: will you receive credit for the remaining license value based on a pro-rata calculation of your maintenance contract end date? Most enterprises negotiate a "buyout" credit—a one-time payment based on remaining license depreciation. Without this, you absorb the full loss of legacy perpetual license value.
3
What happens to my BTP credits if I don't consume them?
SAP typically grants 12–24 months of BTP credits. If your enterprise doesn't use them—perhaps because you're focused on stabilizing the ERP migration—they expire worthless. Ask SAP: can unused credits roll over annually? Can you trade unused credits for a price reduction in year two? The standard answer is no. This is a cost buried in your overall RISE bill.
4
Can I use third-party hyperscaler infrastructure (AWS/Azure/GCP) instead of SAP's?
RISE binds you to SAP's cloud infrastructure choices. SAP's Private Cloud offering runs on hyperscalers, but you have no contractual negotiating power over which region, which availability zones, or which hyperscaler SAP uses. If SAP decides to move you from AWS to Azure, you have limited recourse. Ask whether your contract permits explicit hyperscaler choice and regional lock-in, or if SAP retains unilateral infrastructure change rights.
5
What are the contract exit provisions if I want to leave RISE?
RISE contracts are typically multi-year (3–5 years). Early exit clauses are restrictive. Ask SAP: what is the cost of early termination? Do you owe the full remainder of the contract, or does SAP have a sliding scale based on the termination date? Is there a buyout mechanism? Can you exit with 90 days' notice for cause if SAP breaches SLA or misses a major milestone? Without clear exit provisions, you're locked in even if RISE fails to deliver.
6
How does RISE handle indirect access and digital access measurement?
Indirect access occurs when non-S-Users access S/4HANA data through third-party tools (BI tools, portals, mobile apps, integrations). SAP's definition of indirect access is notoriously fluid. In RISE, you must ask: will SAP measure indirect access separately, and if so, how will it be priced? Will you be charged per indirect user, or is indirect access bundled into your S-User count? The answer determines whether a customer portal or analytics tool triggers unexpected licensing costs.
7
What user types (Professional, Limited Professional, FUE, Employee) apply in RISE?
SAP distinguishes user types by functional role and permitted system actions. Professional users can execute all transactions; Limited Professional users are restricted; FUE (Full-time Equivalent) users are contractors or temporary staff; Employees are internal staff. In RISE, some vendors argue that all S-Users must be licensed as Professional users regardless of their actual functional scope, which inflates costs. Ask SAP: will you permit user type differentiation in RISE, or is it "Professional or nothing"? Get this in the contract.
8
Will my current integration landscape trigger digital access charges?
If your enterprise has integrations between S/4HANA and external systems (Salesforce, Workday, third-party e-commerce platforms, or customer data platforms), these integrations can be measured as "digital access." SAP has been aggressive in charging for digital access beyond a baseline. Ask SAP for a pre-engagement audit of your integration footprint and written confirmation that existing integrations will not trigger incremental digital access fees during the RISE term.
9
What price escalation clauses are built into the RISE contract?
Most RISE contracts include an annual price adjustment tied to an inflation index (CPI) or an SAP-defined consumption metric. A 3% annual escalation over a 5-year contract equals a 16% increase by year five. Ask SAP: what is the exact escalation formula? Is there a cap? Does SAP reserve the right to increase pricing for "new services" outside the escalation clause? Request a 5-year price forecast in writing before signing.
10
What exactly is included in the "SAP Enterprise Support" component?
Enterprise Support covers S/4HANA incident resolution and preventive maintenance. But what is not covered? Custom code defects? Third-party integration failures? Configuration errors? Demand a detailed scope statement. Most enterprises discover post-signature that SAP's definition of a "covered incident" is narrower than expected. Ask SAP to provide a written service scope document and clarify boundaries around custom developments, plug-in issues, and integration troubleshooting.
11
How is the "RISE with SAP" price benchmarked against on-premise alternatives?
SAP will claim RISE is cost-competitive with on-premise S/4HANA plus maintenance. Ask SAP to provide a detailed cost comparison: on-premise license amortization (5-year model), on-premise support, on-premise infrastructure (or AWS/Azure costs), versus RISE. Request SAP's own benchmarking study. Most independent analyses show RISE is 20–40% more expensive than on-premise alternatives for mid-market and large enterprises, especially over a 7-year horizon. SAP will resist providing this comparison because it's unfavorable.
12
What migration costs are included vs separately charged?
RISE pricing typically covers SAP's portion of the S/4HANA migration (the ERP core go-live). System integrator costs, custom development, data migration, and integration work are separately charged. Ask SAP: what is explicitly in scope for the RISE price? Who is accountable for migration timeline delays? What happens to your RISE bill if the go-live extends into year two? Demand a detailed statement of work that separates SAP-delivered services from partner-delivered work.
13
Can I port my RISE subscription to a different cloud region?
RISE instances are often provisioned in a single region (US-East, EU-Central, etc.). If your enterprise expands into a new geography and wants to add a new S/4HANA instance in a different region, can you do so under your existing RISE contract, or does SAP require a separate regional subscription? Some vendors require separate RISE contracts per region, tripling costs. Ask SAP whether multi-region RISE deployments are supported under a single contract with pro-rata pricing.
14
What happens to Ariba, Concur, SuccessFactors integration in RISE?
Many enterprises run SAP's cloud suite products (Ariba for procurement, Concur for expense, SuccessFactors for HR) alongside S/4HANA. These tools integrate with S/4HANA via APIs and middleware. In a RISE contract, does SAP charge for this integration as "digital access"? Are the integration connectors pre-built by SAP or do you build custom ones? Ask for written confirmation that existing Ariba, Concur, and SuccessFactors instances will not trigger incremental licensing fees due to their integration with RISE-hosted S/4HANA.
15
What is SAP's process if I dispute the measured user count in RISE?
SAP measures your S-User population and charges annually based on headcount. Disputes over user classification (is this person a Professional or Limited Professional user?) can be contentious. Ask SAP: what is your dispute resolution process if you believe their user count is inaccurate? Is there a third-party audit mechanism? How long does a dispute take to resolve? Without a clear dispute process, you're forced to accept SAP's count even if it's demonstrably wrong.
Red Flag Answers from SAP
When SAP's account executive responds to these 15 questions, watch for these patterns:
- "We'll handle that in the implementation phase." This defers specificity to after the contract is signed. Demand written answers before signature.
- "That's standard for all RISE customers." Standard doesn't mean favorable. Ask for the written standard and demand exceptions where they benefit your enterprise.
- "Your system integrator will manage that." System integrators profit from ambiguity. If it's your money, it's your question to SAP, not your SI's problem to solve.
- "We don't have visibility into those details yet." If SAP can't specify infrastructure SLAs, cost escalations, or exit clauses before signing, walk away. These are foundational contract terms.
- "Let me circle back with our legal team." This is appropriate for contract-specific questions, but SAP should have off-the-shelf answers to user licensing, SLA, and pricing escalation questions. If they don't, they're unprepared to negotiate.
How to Use These Questions in Contract Negotiations
These 15 questions are not negotiation opening bids; they're diagnostic tools. Here's how to deploy them:
Timing: Ask Early, Not Late
Raise these questions in the first contract review meeting with SAP's sales team, not after you've verbally committed. SAP's willingness to provide specific, written answers to these questions is a strong signal of their contract negotiation posture. If they defer or evade, escalate immediately to SAP's legal or deal management office.
Demand Written Responses
Verbal assurances from your account executive are worthless once the contract is signed. Every answer to these 15 questions must be documented in an addendum to the master RISE agreement or in a detailed statement of work. If SAP won't commit answers in writing, their answer is "no," and you need to understand the implications.
Link Questions to Specific Contract Clauses
Each question maps to a contract clause: SLA to the Service Level Agreement section, pricing escalation to the Pricing Schedule, exit provisions to the Termination section. As SAP responds, reference the actual contract language and demand alignment. If SAP's verbal answer differs from the written contract language, the contract language wins. Make them reconcile the gap.
Engage a Buyer-Side Advisor
You should not negotiate RISE contracts unilaterally with SAP. An independent SAP licensing advisor (not an SI, not an SAP partner) can contextualize these 15 questions within the broader landscape of your enterprise IT environment. They can benchmark SAP's responses against other RISE contracts, identify leverage points, and escalate to SAP's legal office on your behalf. The cost of a buyer-side advisor is recovered in the first negotiated concession on pricing or contract terms.
Getting Independent Validation Before You Sign
Your system integrator will push you toward RISE because SAP partners profit from cloud adoption. Your CFO may want RISE for operational simplicity. But neither your SI nor your CFO is accountable for the licensing risks or cost overruns that RISE can create.
Before you sign a RISE contract:
- Commission an independent SAP licensing audit. Have a buyer-side advisor conduct a baseline audit of your current SAP environment: license inventory, current support costs, current infrastructure spend. Use this baseline to benchmark RISE pricing against your true current state.
- Request a cost sensitivity analysis. Ask SAP for a 7-year total cost of ownership (TCO) projection including escalations, migration costs, and transition costs. Then have your advisor stress-test that projection with conservative assumptions about user growth and storage consumption.
- Negotiate a pilot or proof-of-concept. Don't migrate your entire S/4HANA estate to RISE in year one. Propose a limited pilot: one module, one business unit, or one geographic region on RISE while you retain on-premise instances elsewhere. This gives you operational experience and negotiating leverage to renegotiate terms before full migration.
- Demand transparency on hidden cost drivers. Push SAP to break down their pricing: S-User costs, infrastructure, support, BTP credits, and any consumption-based fees (storage, data transfer, API calls). Once disaggregated, you can identify which components are negotiable.
Ready to Negotiate RISE with Confidence?
These 15 questions are your starting point. But RISE negotiation requires deep knowledge of SAP's pricing models, contract tactics, and your own licensing posture. We've defended dozens of enterprises in RISE negotiations, challenged SAP's user counts, negotiated exit provisions, and secured millions in pricing reductions.
Schedule a Free ConsultationRelated Articles in This Cluster
Frequently Asked Questions
Why does SAP push RISE so aggressively?
RISE is SAP's strategic pivot toward recurring cloud revenue. Under RISE, SAP locks customers into 5-year contracts with annual price escalations. The predictability of recurring cloud revenue increases SAP's stock valuation compared to volatile license and maintenance revenue. For SAP shareholders, RISE is a financial home run. For enterprise customers, RISE is often a cost increase. SAP's aggressive RISE sales tactics reflect this misalignment of incentives.
Are these questions relevant for GROW with SAP too?
GROW with SAP is SAP's entry-level cloud offering for mid-market enterprises. It's less customizable than RISE, but the licensing and cost risks are similar. Most of these 15 questions apply to GROW: SLA accountability, user classification, indirect access measurement, and price escalation all manifest in GROW contracts. The main difference is scale: GROW is typically priced lower but offers less flexibility. Ask these questions for GROW with the same rigor as RISE.
How long does a RISE contract review typically take?
A thorough RISE contract review by an independent advisor takes 2–4 weeks: baseline audit (1 week), SAP contract analysis and Q&A (1 week), cost modeling and benchmarking (1 week), negotiation execution (1–2 weeks). Many enterprises compress this to avoid perceived delays, which is a mistake. The cost of a rushed contract is typically 5–10x the cost of the advisor's fee. Plan for a full cycle of review and negotiation before signing.
Can I ask these questions through my system integrator?
Not effectively. System integrators profit from RISE adoption: more cloud revenue means more implementation and managed services revenue for the SI. If you ask these questions through your SI, they have an incentive to soften your concerns or defer to SAP's answers. These questions must be asked directly by your procurement, legal, and finance teams—or by an independent advisor on your behalf. Don't let the SI filter your questions to SAP.
Disclaimer: SAP Licensing Experts is an independent advisory firm. We are not affiliated with, endorsed by, or partnered with SAP SE or any SAP subsidiary. Our advice is 100% buyer-side and focused exclusively on protecting enterprise customers from licensing overreach and contract complexity. We do not benefit from RISE adoption; we benefit from helping you make the right decision for your enterprise.