RISE with SAP was sold to the market as simplicity: one contract, one vendor, one subscription price. What SAP's sales teams don't volunteer is that "one price" permanently embeds a support model that removes your commercial flexibility, eliminates your right to third-party support, and escalates relentlessly from year one.
The RISE with SAP support model is not the same as SAP Enterprise Support for on-premise systems. It has different SLA structures, different escalation mechanisms, different remediation timelines — and different commercial terms that overwhelmingly favour SAP. For enterprises migrating from ECC or already in a RISE contract, understanding the support model in forensic detail is the difference between a manageable annual cost and a spend line that doubles over the life of the contract.
This guide covers every significant aspect of the RISE with SAP support model: what it includes, what SAP builds in at the contract level, which questions expose the gaps in what you're being promised, and how enterprises are successfully negotiating better terms in 2026.
In a standard on-premise SAP agreement, you can switch to third-party support (Rimini Street, Spinnaker) and reduce annual costs by 50–60%. In RISE with SAP, this option is contractually removed. Support is bundled into the subscription. You cannot separate it. You cannot replace it. This is a permanent, structural cost embedded in every RISE contract — and SAP has no commercial incentive to make it cheaper.
RISE with SAP includes SAP Enterprise Support for Cloud as its standard support offering. This is not simply a renamed version of the on-premise SAP Enterprise Support — it is a distinct product with distinct boundaries. At its core, the RISE support model covers access to the SAP ONE Support Launchpad, support tickets via SAP for Me, system monitoring through Solution Manager or SAP Cloud ALM, and premium engagement through SAP's Mission Critical Support track (for qualifying contract tiers).
What it does not cover by default is just as important: proactive landscape reviews, dedicated support managers, enhanced SLAs beyond standard response-time commitments, and hands-on problem resolution for custom ABAP developments are all outside the base scope. SAP sells these as upgrade tiers — Premium Engagement, MaxAttention — at significant additional cost.
SAP structures RISE support in three commercial tiers, each with materially different SLA commitments:
SAP's commercial team will routinely present Premium Engagement or MaxAttention as essential for enterprises running complex S/4HANA environments — and for many large organisations they are. But the upsell happens post-signature, when your leverage is lowest. The correct approach is to identify your true support requirements before contract execution and negotiate inclusion at reduced rates as part of the initial RISE deal.
Most enterprises discover the gaps in their RISE support terms 12–18 months after go-live, when they face their first critical system issue. At that point, your only option is to buy up — at SAP's price. Our RISE with SAP advisory service includes a detailed support model analysis as part of every contract review, ensuring your SLA commitments, escalation paths, and support tiers are correctly scoped before signature.
Get a RISE Contract Review →The commercial framing of RISE support as "included" is technically accurate and practically misleading. SAP embeds the support cost within the subscription price — it is not an itemised line that you can challenge or remove, but it typically represents 20–25% of your total annual RISE subscription. For an enterprise paying €10 million annually in RISE fees, between €2 million and €2.5 million of that is support cost.
More significantly, this support cost escalates with the contract. RISE subscriptions typically include annual price increase clauses of 3–5%, which apply across the entire subscription value — including the support component. Over a five-year term at 3% annual escalation, your effective support cost increases by 16%. Over a ten-year programme at 5%, it nearly doubles. None of this is disclosed in the headline metrics SAP presents in deal negotiations.
SAP's standard support covers what SAP builds. Everything else — your custom configurations, industry extensions, third-party integrations, data migration decisions, process-specific workflows — is your responsibility or your SI's responsibility. Most enterprises discover post-go-live that a significant proportion of their system issues fall into this "not SAP's problem" category, generating demand for Application Management Services (AMS).
AMS is the ongoing operational support for everything outside SAP's direct remit. It is typically provided by SAP's implementation partner or a specialist managed services firm, and it adds materially to total SAP support spend. Enterprise AMS contracts commonly run at 15–20% of total implementation cost annually. For a €50 million implementation programme, that means €7.5–€10 million per year in AMS costs on top of the support embedded in RISE.
SAP's commercial teams do not include AMS cost in RISE TCO projections. Independent advisors consistently find that enterprises underestimate total support spend by 30–40% when relying on SAP's own cost modelling. The complete picture requires mapping both the embedded RISE support component and the expected AMS demand from day one of the programme.
Support SLAs in RISE contracts are written to protect SAP, not to guarantee enterprise outcomes. Understanding the specific language is essential before signing. SAP commits to response times, not resolution times — a critically important distinction. A P1 critical ticket with a 1-hour response SLA means SAP will acknowledge your ticket and provide initial triage feedback within one hour. It does not mean your system will be restored within one hour.
Resolution timelines depend on issue classification. SAP's support organisation classifies issues by category: SAP code defects, configuration issues, customer-side issues, and integration issues. If an issue is reclassified from an SAP code defect to a customer-side issue — something that happens frequently with complex customisations — SAP's SLA commitment resets. The clock stops. Your operations team continues to deal with the outage while SAP reclassifies.
SAP's standard RISE availability SLA is 99.5% uptime, measured monthly. This sounds robust — it equates to approximately 3.65 hours of permitted downtime per month. What the SLA documentation typically does not make clear is that scheduled maintenance windows, planned system updates (of which there are many in SAP's cloud model), and incidents caused by customer-side configuration changes are all excluded from the availability calculation. In practice, the actual operational availability experienced by complex enterprise deployments is often materially lower than the quoted 99.5%.
Enterprises negotiating new RISE contracts should push for 99.9% or higher availability SLAs, explicit exclusion carve-out definitions, and financial credits that activate at materially lower thresholds. SAP will resist — these commitments increase their operational liability — but in competitive deal situations or large contract renewals, they are achievable.
For enterprises accustomed to the on-premise SAP licensing model, the single most significant commercial change in RISE is the permanent removal of third-party support rights. In the ECC on-premise world, SAP's Enterprise Support is a charged line item — expensive, at 22% of net licence value annually, but separable. Enterprises have consistently used third-party support providers, most notably Rimini Street and Spinnaker, to reduce annual support costs by 50–60% while maintaining operational support quality.
RISE with SAP eliminates this option entirely. SAP's cloud subscription terms explicitly prohibit third-party support for the cloud-delivered S/4HANA environment. The support is part of the service — and the service can only be delivered by SAP. This is not a temporary commercial restriction. It is a permanent structural feature of the RISE model that SAP's pricing team has engineered to protect a revenue stream that third-party providers were rapidly eroding.
For enterprises entering RISE negotiations, this is a critical data point: the long-term cost of third-party support avoidance needs to be built into every RISE TCO model. Over a ten-year programme, the compound cost of embedded cloud support vs. the third-party alternative typically represents €5–15 million in additional spend for large enterprises, depending on contract size.
SAP's TCO presentations consistently exclude third-party support comparison cost, AMS projections, and support escalation costs. Our SAP support cost reduction service includes independent TCO modelling that incorporates all support layers — giving you a complete picture of what RISE will actually cost to run over the contract term.
Get Independent TCO Analysis →SAP's commercial teams treat the support component of RISE as non-negotiable — a bundled element of the subscription that "isn't priced separately." This framing is designed to prevent discussion of support cost, not to reflect commercial reality. The support component is absolutely priceable: SAP's own financial reporting separates cloud support revenue, and their implementation partners are fully capable of quoting AMS separately.
The leverage points for negotiating better support terms in RISE contracts cluster around three moments: initial contract execution, five-year renewal, and competitive situations where SAP is competing for your workload against Oracle, Microsoft, or other hyperscalers. Outside these windows, leverage is minimal — SAP has captured your infrastructure and your operating model, and their commercial incentive to improve your terms disappears.
Specific negotiation tactics that have proven effective in 2025 and 2026 include: requesting inclusion of Premium Engagement features at no additional cost as part of the base RISE contract; negotiating fixed support cost escalation caps below the headline subscription escalation rate; securing a defined period of zero escalation at contract initiation; and structuring the RISE subscription with a clearly defined support component that can be benchmarked independently at renewal.
For detailed negotiation strategies, see our companion article on RISE with SAP support model negotiation strategies, which covers specific tactics and the contractual language that delivers them.
SAP's RISE proposals are structured to answer the questions you ask — and nothing more. The support model documentation is dense, cross-referenced, and deliberately hard to parse without deep expertise. Asking the right questions, in writing, before contract execution forces SAP's commercial team to commit to specific terms that can be held to account post-signature.
Every enterprise evaluating a RISE contract should formally ask SAP to clarify: the exact percentage of total contract value allocated to support; the annual escalation mechanism applied to the support component specifically; the scope exclusions for custom ABAP code and third-party integrations; the process and timeline for SLA credit claims; and the conditions under which support tier upgrades become effectively mandatory. Full coverage of the questions and the responses to expect is available in our article on key questions to ask SAP about the RISE support model.
Despite the structural lock-in of RISE support, there are genuine optimisation levers available to enterprises — both before contract signature and within active contracts. Pre-signature, the most impactful lever is accurate scoping: enterprises that over-scope their RISE footprint pay inflated support costs from day one. Our detailed tactical guide on RISE support model cost optimisation tactics covers the specific approaches that deliver measurable savings.
Within an active RISE contract, optimisation focuses on AMS demand management: reducing the volume of post-go-live issues that generate AMS cost by investing in better programme governance during implementation, and systematically managing the custom code estate to reduce the support overhead that SAP won't cover. Enterprises that right-size their custom code before go-live consistently report AMS costs 20–30% below initial estimates.
SAP has made several changes to the RISE support model since its initial launch in 2021. The most significant for 2026 is the integration of SAP Cloud ALM as the mandatory application lifecycle management platform for RISE customers, replacing Solution Manager for new deployments. Cloud ALM delivers improved native monitoring and support ticket integration — but it also means that a critical operational tool is now fully controlled by SAP, with limited customer control over the data it generates and the visibility it provides.
SAP has also moved to harmonise its support SLAs across the RISE product family following the integration of GROW with SAP in the mid-market segment. This harmonisation has, in practice, created a ceiling effect — the most robust SLA terms are now reserved for MaxAttention customers, and enterprises on standard RISE support have seen their effective SLA commitments remain flat while SAP's infrastructure complexity has increased.
SAP's 2026 roadmap also accelerates the cadence of mandatory system updates. RISE customers are required to adopt SAP's quarterly release updates, which are non-optional and can materially affect custom developments. Enterprises with large custom code estates face increasing AMS costs as they must manage the compatibility impact of each mandatory update — a cost that sits entirely outside SAP's support scope.
For the most current guidance on RISE support terms, see our 2026 enterprise guidance on the RISE support model, which incorporates the latest contractual developments and negotiation intelligence from our advisory practice.
You cannot remove support from a RISE contract — it is contractually embedded as part of the subscription service. However, you can negotiate the effective rate, escalation caps, and what is included at the base level. Independent advisors typically achieve 20–35% reductions in effective support cost through pre-signature negotiation, inclusion of Premium Engagement features at no incremental cost, and securing favourable escalation terms. Post-signature, the primary lever is AMS demand management.
No. RISE with SAP's contractual terms explicitly prohibit third-party support for the cloud-delivered S/4HANA environment. This is one of the most significant cost differences between the RISE model and continuing on-premise ECC with third-party support — a cost differential that SAP's sales teams routinely omit from TCO comparisons.
SAP Enterprise Support applies to on-premise and private cloud licences. SAP Enterprise Support for Cloud (included in RISE) has different SLA structures, is delivered exclusively by SAP rather than through support partners, and cannot be substituted. The on-premise version gives you the right to switch providers; the cloud version does not. The effective cost rate is similar (approximately 22% annually) but the commercial flexibility is materially different.
SAP's standard RISE contracts include service credit mechanisms, but the credit values are typically small relative to business impact — often capped at a percentage of monthly subscription fees. Enterprises experiencing material SLA failures should document the impact rigorously and use it as negotiation leverage at the next contract review. For critical system failures, escalation to a named SAP executive is more effective than the standard service credit process.
Benchmarking RISE support cost requires decomposing the subscription to identify the support component, then comparing against SAP's own rate card (which is not publicly disclosed but is accessible to advisors with sufficient market visibility) and against comparable contracts in your industry and size tier. Independent advisors with active market presence can provide this benchmark analysis. Without independent benchmarking, enterprises have no basis to challenge SAP's embedded support pricing.
📬 SAP Licensing Intelligence
Expert analysis on RISE with SAP, audit defence, contract negotiation, and cost reduction. No vendor affiliation.
SAP Licensing Experts Advisory Team
Former SAP executives, auditors, and contract managers — now working exclusively for enterprise buyers. Learn about our team →
Independent SAP licensing advisory — not affiliated with SAP SE.
Our RISE with SAP advisory service protects enterprise buyers from the commercial structures SAP builds into every contract. No SAP affiliation. No reseller agenda. 100% buyer-side.
Book a Free Consultation →