Is RISE with SAP Right for You? A Buyer-Side Evaluation Framework

What RISE with SAP Actually Is

RISE with SAP, introduced in January 2021 and substantially repackaged through 2024 and 2025, is a subscription bundle that combines S/4HANA software, private cloud infrastructure (managed by SAP on hyperscalers — AWS, Azure, or Google Cloud), base support, and a SAP Business Technology Platform (BTP) credit allocation. The July 2025 packaging changes unbundled several previously included features — SAP Datasphere, Joule AI advanced capabilities, and sustainability tools — requiring separate contracts and additional budget for organisations that need them.

The critical framing distinction: RISE is a procurement model, not a product. It bundles what were previously separate commercial relationships — software licence, infrastructure contract, and support agreement — into a single subscription invoice. Whether that bundling delivers value depends on your organisation's starting position, cloud readiness, and ability to negotiate the terms of what is actually in the bundle.

What SAP would prefer buyers not focus on: RISE with SAP is SAP's preferred transaction model because it converts what was a one-time perpetual licence revenue event into a recurring subscription revenue stream. The bundling also reduces buyers' ability to shop individual components competitively. This is commercially rational behaviour from SAP — but buyers who understand the unbundling economics are better positioned to negotiate the components they actually value.

The Four Scenarios Where RISE Is the Right Answer

There are genuinely compelling reasons to choose RISE with SAP Private Edition. Understanding where the model works — and being honest about where it does not — is the foundation of a sound evaluation.

Scenario 1: You Want to Exit the Infrastructure Business Entirely

RISE transfers infrastructure management to SAP, including hardware provisioning, OS patching, database management, and hyperscaler optimisation. For organisations with an undifferentiated internal SAP infrastructure team, limited cloud expertise, or a strategic priority to exit capital-intensive on-premise infrastructure, RISE removes a significant operational burden. The subscription model converts a CapEx-heavy infrastructure cycle into a predictable OpEx line, which is genuinely valuable for organisations where IT capital allocation is contested or constrained.

Scenario 2: You Have High Customisation Debt and Need Clean Core Discipline

Organisations with deeply customised ECC environments often lack the internal organisational willingness to rationalise that technical debt. RISE, with its Clean Core architectural mandate — which requires customisations to move from the ERP core to SAP BTP — imposes a structural discipline that purely on-premise S/4HANA migration does not. For organisations where the CIO and CFO alignment exists and the commitment to Clean Core is genuine, RISE provides an architectural forcing function that can be commercially valuable despite the BTP consumption costs it generates.

Scenario 3: You Need SAP's Managed Migration Support

RISE includes access to SAP's Business Transformation Services and RISE with SAP migration tooling. For organisations without experienced S/4HANA implementation partners or strong internal programme management capability, SAP's managed migration support reduces execution risk. The SAP Activate methodology and embedded tooling have improved substantially since RISE's 2021 launch — for genuinely greenfield or clean-slate implementations, these tools reduce the implementation timeline.

Scenario 4: You Are a Mid-Market Organisation with Standard Processes

RISE with SAP is structurally better suited to organisations whose processes align closely with SAP's standard industry configurations — those who will run S/4HANA as configured rather than as customised. SAP's embedded best practices deliver faster time-to-value for organisations willing to adapt their processes to SAP's model. Conversely, for organisations with highly differentiated processes that require deep customisation, RISE's Clean Core constraints can create more friction than value.

The Four Scenarios Where RISE Is Not the Right Answer

RISE with SAP is actively the wrong model in several common enterprise scenarios, and SAP's sales motion rarely acknowledges these limitations.

Scenario 1: You Already Have a Strong Hyperscaler Strategy

If your organisation has an established, negotiated relationship with AWS, Azure, or Google Cloud — including committed spend, enterprise discount rates, and internal cloud engineering capability — RISE creates an infrastructure layer that conflicts with your existing cloud economics. RISE's infrastructure is managed by SAP on a specific hyperscaler configuration that may not align with your existing cloud contracts. Running S/4HANA on your own hyperscaler relationship, using a certified cloud provider rather than SAP's managed infrastructure, can deliver equivalent capability at lower cost and with greater architectural flexibility.

Scenario 2: Your BTP Footprint Will Be Significant

Organisations planning substantial BTP adoption — for integration, automation, and AI capabilities — will find that the BTP credit allocation included in RISE rapidly becomes insufficient. BTP consumption costs are consumption-based and grow with usage. For organisations with large integration landscapes, significant custom development requirements, or aggressive Clean Core strategies that push extensive logic to BTP, BTP consumption can add 20 to 35% to the effective annual subscription cost. Understanding your BTP consumption trajectory before signing is essential — and for organisations with genuinely large BTP requirements, negotiating a BTP-first commercial structure may be more economical than RISE's bundled allocation approach.

Scenario 3: You Plan to Use Third-Party Maintenance in the Near Term

If your EHP 6–8 deadline is December 2027 and you have a credible multi-year migration plan that would benefit from additional runway, third-party maintenance from providers like Rimini Street — which covers tax, legal, and regulatory updates at up to 50% below SAP's standard maintenance cost — can extend your ECC runway without the immediate RISE commitment. Rimini Street's coverage model allows organisations to fund migration quality rather than migration speed, which is the right trade-off for organisations where a rushed RISE migration would create more operational risk than continued ECC operation.

Scenario 4: Your S/4HANA Requirements Are Greenfield Public Cloud

RISE with SAP Private Edition is for organisations migrating from ECC — it preserves compatibility with ECC-era customisations and processes. S/4HANA Public Cloud (the multi-tenant SaaS offering) is designed for organisations willing to adopt SAP's standard processes without legacy migration requirements. If your organisation is effectively starting fresh — a new business unit, a post-M&A integration, or a deliberate re-platforming away from all legacy customisation — S/4HANA Public Cloud may deliver a better commercial and operational outcome than RISE Private Edition.

The Seven Contract Risks You Must Address

Regardless of whether RISE is the right model for your organisation, the contract carries several structural risks that independent legal and commercial review must address before signature.

Lock-In Duration and Exit Rights

RISE contracts are typically 5-year commitments. Early termination provisions are limited and expensive. Organisations that sign RISE commitments without evaluating the exit economics at Year 3 or Year 4 — what does it cost to leave, what can you take with you, what happens to your data — are accepting contractual lock-in without understanding its true cost. Negotiate explicit data portability provisions, termination for convenience rights (even at a cost), and clear IP ownership for any custom developments deployed on BTP.

Infrastructure Sizing Risk

SAP's infrastructure sizing for RISE deployments has been a consistent pain point. Under-sizing creates performance issues post-go-live. Over-sizing wastes subscription fees on unused capacity. SAP's sizing assessments are performed by SAP, creating a structural conflict of interest — larger sizing means higher subscription fees. Require independent infrastructure sizing validation as a pre-signature deliverable, and negotiate performance SLAs tied to the agreed sizing that give you contractual recourse if under-sizing affects business performance.

BTP Credit Allocation Adequacy

As discussed above, the included BTP credit allocation is designed for standard configurations, not complex integration landscapes. Before signing, model your expected BTP consumption across all planned integration scenarios, custom extensions, AI feature use, and workflow automation. Negotiate additional BTP credits at contract rates — not consumption rates — if your modelled consumption exceeds the included allocation. Post-signature BTP overages are charged at list rates that are typically 30 to 50% higher than what can be negotiated at deal close.

Digital Access Coverage

RISE's "all-inclusive" narrative frequently implies that digital access (DDLC) obligations for third-party integrations are covered. They often are not — at least not for the integration landscape that will exist in production, which is almost always more extensive than the landscape at deal close. Secure explicit written coverage for your complete integration landscape as a condition of signature.

July 2025 Packaging Changes Impact

The July 2025 RISE packaging changes unbundled several AI and data tools. Organisations signing RISE agreements based on pre-2025 packaging descriptions may discover that features they expected — particularly Joule AI advanced scenarios and SAP Datasphere — require separate contracts. Verify the current scope of the included bundle against the July 2025 packaging before finalising commercial terms.

Annual Uplift Cap

SAP's standard RISE agreements include annual uplift provisions that allow subscription price increases year over year. Over a 5-year term, the difference between a 3% and a 5% annual uplift cap on a €2 million subscription is approximately €420,000. This is non-trivial and should be a hard negotiating point in any RISE deal.

Support Tier Clarity

RISE includes standard Enterprise Support. SAP's account teams frequently upsell Premium Engagement support at additional cost — $50,000 to $200,000 per year depending on deal size. Understand what standard Enterprise Support includes and what scenario would trigger a genuine requirement for premium support before agreeing to any upsell.

The Evaluation Checklist

Commercial Readiness: Have you modelled the full 5-year TCO including implementation, BTP consumption above inclusion, integration costs, change management, and contingency? Is the subscription fee you are being quoted benchmarked against peer transaction data, not SAP's list price? Have you secured migration credits at the maximum available rate given your migration timeline?

Technical Readiness: Have you completed a Clean Core assessment that identifies which customisations can move to BTP, which require rearchitecting, and which should be retired? Has infrastructure sizing been independently validated? Have you mapped your complete integration landscape and confirmed DDLC coverage for all third-party document creation scenarios?

Contract Readiness: Does the contract include explicit dual-use rights for your expected parallel-run period? Are data portability and exit rights clearly defined? Is the annual uplift capped at a level that protects your 5-year budget model? Are performance SLAs tied to agreed infrastructure sizing with meaningful financial remedies for breaches?

Organisational Readiness: Does your organisation have the change management capability and executive sponsorship to execute a SAP cloud ERP migration at the required pace and scope? Is there genuine alignment between IT, Finance, and Operations on the Clean Core strategy and its implications for process standardisation?