RISE with SAP Add-On Licensing: Cost Optimisation Tactics

Why RISE Add-On Optimisation Matters More Than Base Contract Savings

Most enterprise RISE negotiations focus heavily on the base subscription rate — the per-user, per-month S/4HANA Cloud PE fee that forms the headline number in SAP's proposal. This is understandable, and achieving 10–20% savings on the base rate is achievable with proper preparation. But in practice, the base subscription is often a smaller proportion of total five-year RISE cost than the accumulated add-on commitments.

BTP capacity overruns, optional module renewals, digital access overages, AI credit packages, and support tier escalations collectively account for 40–60% of total RISE programme cost for a typical enterprise of 5,000+ users over a five-year term. That is where the real cost optimisation opportunity lives, and it is the territory where SAP's sales team is least transparent and most aggressive.

Our RISE with SAP advisory service conducts financial modelling on both base and add-on components before any client engagement with SAP's commercial team. The add-on analysis consistently surfaces 20–35% in avoidable spend that would have been locked in had the enterprise negotiated without independent support. See our broader RISE with SAP licensing guide for the complete framework.

BTP Cost Optimisation: The Highest-Return Focus Area

The Business Technology Platform credits bundled into RISE are the most significant and most frequently mismanaged add-on cost category. The optimisation approach operates on three levels: consumption modelling, contractual protections, and operational governance.

Consumption modelling requires SAP to provide detailed BTP service consumption data from comparable deployments — anonymised, but statistically representative — before you commit to a credit package. SAP will resist this, citing confidentiality. Push through the resistance: you have the right to make an informed commercial decision. If SAP cannot provide consumption benchmarks, require that the included credit package be sized based on your own integration landscape analysis rather than their estimates.

Contractual protections begin with carryover rights. Any unused BTP credits at the end of a subscription year should roll forward for a defined period — 12 to 24 months is achievable. This single provision eliminates the artificial pressure to consume credits before expiry, and removes the mechanism SAP uses to justify top-up purchases on unfavourable terms.

Price cap provisions on mid-term top-ups are equally important. If your BTP consumption exceeds the included allocation, the rate at which you purchase additional capacity should be no higher than 110% of your original contracted rate, indexed to an agreed price floor. This prevents the mid-contract top-up conversation from becoming a rate shock event. Our contract negotiation team builds these provisions into every RISE engagement.

User Classification: The Fastest Route to Immediate Savings

RISE with SAP user pricing follows the same classification framework as traditional SAP Named User licensing, and the same optimisation logic applies. SAP defaults to proposing the maximum number of Professional users possible, because Professional users carry the highest price point. The buyer's job is to challenge that classification aggressively — with evidence.

A Professional user, in SAP's definition, is anyone who accesses the system to perform end-to-end business transactions. A Limited Professional user performs more restricted transactional activities within a single business process area. An Employee user accesses the system for self-service activities — travel, expenses, HR workflows — without performing substantive ERP transactions.

In the average RISE proposal, 70–80% of the proposed user count is classified as Professional. An independent classification review — mapping actual job functions against SAP's metric definitions — typically reveals that 20–35% of those proposed Professional users legitimately qualify as Limited Professional or Employee. At the price differential between tiers (Professional users typically cost 3–5× more than Limited Professional), this reclassification delivers immediate, recurring annual savings.

The key is to conduct this review with independent expertise, not relying on SAP's classification guidance. SAP's user type documentation is deliberately ambiguous in ways that consistently favour upward classification. Our SAP licence optimisation service has resolved user classification overclassification in every RISE engagement we have supported.

Optional Module Rationalisation: What to Keep, What to Phase Out

The RISE add-on landscape of 2025–2026 includes modules that were bundled into proposals as standard during the early RISE phase (2021–2023) without enterprises fully evaluating whether they were genuinely required. Signavio, in particular, was included in the majority of RISE proposals as a process intelligence and value realization tool, often at attractive bundled rates. Three years into deployment, many enterprises have not achieved meaningful adoption of Signavio's capabilities and are facing renewal pricing that reflects SAP's standard list rates rather than the introductory bundle pricing.

The optimisation tactic here is direct: if module adoption is low, use that data in the renewal conversation to justify a significant price reduction or an outright discontinuation of the module. SAP will try to renegotiate rather than lose the revenue, and a well-documented low-adoption case gives you real leverage. The credible threat to discontinue is one of the few genuine commercial levers RISE customers possess post-signature.

Apply the same logic to SAP Analytics Cloud if your enterprise has maintained Tableau, Power BI, or another analytics platform alongside the SAP offering. SAP will argue for consolidation onto SAC; the enterprise should counter with adoption data and alternative pricing as evidence that the SAC investment is not delivering value at its current cost point.

For modules that are genuinely critical to operations — analytics, integration automation, sustainability reporting — the optimisation approach shifts from rationalisation to right-sizing. Work with your implementation team to produce a documented consumption forecast, then use that forecast to negotiate volume discounts or modified metrics that better align the cost model with your actual usage pattern.

Digital Access: Containing the Most Volatile Add-On Cost

Digital access — the per-document pricing applied to third-party system interactions with S/4HANA — is the most volatile and least predictable add-on cost in the RISE landscape. Unlike named user pricing, which is relatively stable once classified, digital access volume scales with business operations. The more orders, deliveries, invoices, and material movements your enterprise processes via non-SAP systems, the higher the digital access obligation.

Cost optimisation in this category begins with a document volume audit. Before any RISE renewal conversation, produce a complete count of digital access events from the previous 12 months, broken down by document type (Order, Delivery, Invoice, Material) and by originating system. This data becomes the basis for a flat-fee negotiation — a single annual fee covering your documented volume plus a reasonable buffer — rather than a per-unit pricing model that exposes you to linear cost growth.

Flat-fee digital access packages are achievable in RISE negotiations. SAP prefers per-unit pricing because it captures growth; buyers benefit from predictability. The negotiating mandate is to demonstrate your volume data, model growth realistically, add a 20% buffer, and demand a flat fee for that modelled volume. Our indirect access advisory service has secured flat-fee digital access terms in the majority of RISE negotiations where this has been a focus area.

Support Tier Rationalisation: Enterprise Support vs. Standard

RISE with SAP includes SAP Enterprise Support as the standard support tier. Enterprise Support is priced at 22% of net licence value annually — significantly higher than the 18% Standard Support rate. SAP positions Enterprise Support as delivering premium value through Technical Quality Managers, incident management SLAs, and proactive advisory services.

For enterprises operating RISE at scale, the Enterprise Support tier may genuinely be justified. But for smaller RISE deployments, or for enterprises with strong internal SAP capability, Standard Support — where SAP still offers it — or third-party support from providers like Rimini Street or Spinnaker Support represents a meaningful cost reduction. Third-party support for RISE components where it is technically feasible can deliver 30–50% support cost savings.

Our SAP support cost reduction service evaluates the full range of support options for RISE environments, including the technical and contractual viability of third-party support for specific components. This is a nuanced area — not all RISE components are eligible for third-party support — but the analysis is always worth conducting before committing to SAP Enterprise Support for a five-year term.

The At-Renewal Optimisation Playbook

RISE renewals are the moment when the leverage balance shifts most significantly. SAP knows you have invested in S/4HANA Cloud PE, your data is there, your processes run on it, your users depend on it. The switching cost is real, and SAP's renewal team will rely on that dependency to resist pricing concessions.

The counter-strategy requires three elements: timeline, alternatives, and data. Start the renewal process at least 18 months before contract expiry. This gives you time to credibly explore alternatives — competing cloud ERP platforms, S/4HANA on-premise, or hyperscaler-hosted deployments — and to communicate that exploration to SAP's account team. SAP's response to a buyer who has initiated a competitive evaluation is categorically different from their response to a buyer who presents a renewal request 90 days before expiry.

The data requirement means assembling three things: actual add-on consumption vs. entitlement (to identify over-contracted capacity you can reduce), a competitive pricing benchmark from at least one alternative (to establish a credible outside option), and a documented list of service and value gaps SAP has not resolved during the contract term (to justify price concessions on grounds of non-performance).

Armed with these three elements, the renewal conversation becomes a negotiation between informed parties rather than a SAP-driven renewal process. See our companion article on RISE add-on negotiation strategies for the full tactical framework, and our complete RISE add-on licensing guide for the strategic overview.

Frequently Asked Questions

More RISE with SAP Add-On Licensing Articles