SAP's RISE Proposal Is a Bundle β and Bundles Favour the Seller
The client β a global insurance group running S/4HANA on-premises β was evaluating migration to RISE with SAP (SAP's managed cloud transformation offering). SAP's account team had presented a comprehensive five-year proposal priced at $18.7M, covering the S/4HANA cloud licences via FUE (Full Use Equivalent) pricing, BTP (Business Technology Platform) capacity for integration and automation, GROW with SAP components for their smaller subsidiary entities, and included infrastructure hosting on Hyperscaler of SAP's preference.
The FUE pricing model is where most of the value extraction happens in a RISE proposal. SAP bundles all users β including low-activity users such as claims processors, finance approvers, and report viewers β under a single FUE metric that reflects the pricing of the highest-value user type. The insurer's proposal included approximately 3,400 users priced at a blended FUE rate that did not reflect the actual activity distribution across their user base. Additionally, the BTP capacity bundled into the proposal was sized at 200% of what the insurer's current integration use cases required, with SAP citing "transformation capacity" as the justification.
The insurer's IT leadership was under board pressure to complete the RISE migration within the fiscal year. SAP's account team was aware of this timeline dependency β and had priced accordingly, knowing that a delayed negotiation carried real programme risk. We were engaged after the client's internal procurement team received SAP's first and "final" offer, which had been presented as non-negotiable due to a quarter-end pricing window.
Evaluating SAP RISE?
SAP's RISE proposal bundles are designed to maximise FUE consumption and BTP attachment. Our SAP negotiation service has restructured RISE proposals across financial services, manufacturing, and healthcare β delivering an average of 28% savings. We work on a 25% gainshare basis. Get your free RISE assessment before you sign.
Right-Sizing FUE and Eliminating Bundled Overcapacity
SAP's "quarter-end window" and "non-negotiable" framing are standard negotiation tactics. We've seen them on every significant SAP engagement. The window is real β but so is SAP's desire to close the deal. The question is whether you have the independent analysis to make their position untenable before the window closes.
FUE User Activity Classification
We conducted a full user activity analysis across the insurer's current S/4HANA on-premises deployment, classifying all 3,400 users by transaction type, module access, and frequency. The analysis revealed that approximately 1,100 users were "limited users" β finance approvers, HR self-service users, and report consumers β who under a properly structured FUE agreement would qualify for a lower-cost user type. SAP had priced all users at the full FUE rate. Reclassifying these users to Limited User access reduced the licence cost by $2.1M over five years.
BTP Capacity Right-Sizing
We reviewed the insurer's current integration architecture β including the volume of API calls, event mesh requirements, and workflow automation in production β and modelled their realistic BTP consumption over the five-year RISE term based on their digital transformation roadmap. SAP had bundled BTP at double the required capacity. We negotiated a right-sized BTP package with contractual capacity extension rights at fixed pricing, eliminating $1.6M in BTP overcapacity charges while preserving the flexibility to scale.
GROW with SAP Scope Challenge
The insurer's three subsidiary entities had been included in the RISE proposal under GROW with SAP β SAP's pre-configured cloud ERP offering for smaller organisations. We challenged whether GROW was the appropriate vehicle for these subsidiaries or whether lighter-weight S/4HANA Cloud Public Edition licences would be more cost-effective. The analysis showed that GROW was being used as a licence vehicle for entities whose requirements were better served by the Public Edition model at a 22% lower per-user cost, saving $680K over five years.
Hyperscaler Neutrality Clause
SAP's proposal specified infrastructure hosted on SAP's preferred hyperscaler. The insurer had an existing AWS EDP (Enterprise Discount Programme) commitment and preferred AWS hosting to maximise their EDP drawdown. We negotiated a hyperscaler neutrality clause allowing the insurer to deploy RISE infrastructure on AWS without infrastructure cost uplift β preserving approximately $340K in annual AWS EDP credits over the contract term.
Price Escalation Cap and LAW Audit Protection
SAP's standard RISE contract included a 5% annual price escalation clause and did not include explicit LAW (Licence Auditing Workbench) audit rights limitations. We negotiated a 3% annual price cap β saving $420K over the term in escalation avoidance β and included contractual language limiting SAP's right to initiate a LAW audit to once per contract period, with 90 days' notice, and capping any settlement to licences consumed in the preceding 12 months only.