The CFO conversation has changed
For two decades the SAP renewal conversation in the Middle East went one way. Finance saw a line item, signed it, moved on. The platform was understood as a fixed cost of running the business. The number went up every three years. The number was not negotiated; the price book was.
That conversation is changing. Not because the AI hype told CFOs to disrupt their ERP — the hype produced almost nothing useful on this question — but because the economics of the RISE with SAP contract have become visible in a way they were not before. The bundle is opaque on purpose. Once you see the shape, you cannot unsee it.
This piece is what we tell CFOs when they ask us to read the renewal before they sign.
What the RISE bundle actually contains
RISE with SAP is sold as a managed migration to S/4HANA. In practice it is three contracts in a single SKU.
Contract one — the licence. S/4HANA list pricing is per Full User Equivalent, not per named seat. The conversion ratios are buried in the deal sheet. A user who hits the system twice a month from a tablet often counts more than the procurement controller writing purchase orders all day. The conversion math is reviewed every renewal cycle and trends the same direction.
Contract two — the infrastructure. RISE bundles the cloud hosting, sized against a baseline you do not own. SAP picks the hyperscaler. SAP picks the region. SAP picks the resilience tier. The hosting line is a pass-through with a margin you cannot inspect.
Contract three — the change-management overlay. RISE includes a "transformation services" envelope priced as a percentage of total contract value. It is not the same as the SI work — your integrator still bills separately — and it is not negotiable line by line. It funds the SAP-side advisory hours that come with the migration.
Each of those is defensible in isolation. Stacked together, they describe an envelope where about a third of the spend is not software the business uses. That is the part CFOs start asking about.
The indirect-access exposure most Middle East CFOs don't know they carry
The licensing audit nobody enjoys is the indirect-access conversation. If your ECC or S/4HANA data is accessed by another system — a custom reporting tool, a portal, an AI agent, an integration that runs nightly — the licence model can be interpreted to require additional FUEs for the upstream system's user base. The mechanic has been litigated publicly in Europe. The principle survives.
In a Middle East enterprise that has invested in a modern data stack, this is the largest unbudgeted exposure on the contract. We have read renewal terms that would, on a strict reading, require licensing every data scientist whose dashboards touch a table sourced from S/4HANA. The remedies offered by the account team are usually "buy more FUEs" or "buy the SAP Data product instead." Both deepen the relationship.
The renewal mechanic
RISE contracts in the Middle East typically run 5 years with a price-protection clause that caps annual increases below a stated CPI threshold. The clause sounds protective. It is the mechanism that locks the conversation. The protected price is the price you pay for renewing. The price for not renewing — moving off S/4HANA — is a different conversation entirely, in a different commercial framework, on a different timeline.
CFOs reading this carefully start asking the right question: what is the contractual cost of leaving inside the protection window, and what is the cost of leaving outside it? The answers, when modelled honestly, often show that delaying the exit is the expensive option.
The saasinator perspective
A Middle East enterprise that has signed an SAP renewal in the last two cycles has the data to model the next twenty years of SAP spend more accurately than SAP will model it for them. The exercise takes a week. We do it as part of every diagnostic where SAP is in scope.
The number that comes out is not the number on the renewal sheet. It is the number after the FUE escalation, the indirect-access exposure, the bundled hosting margin, and the carrying cost of three more transformation cycles. Once a CFO has seen that number, the question stops being "what is the SAP cost" and starts being "what is the portfolio of workflows we want to own outright."
What CFOs are actually doing
Three patterns are emerging across the engagements we have run in the Middle East.
Pattern one — workflow-by-workflow exit. The CFO and CIO pick the two or three workflows where the per-FUE cost is highest relative to business value, and start replacing those first. The SAP contract continues to run; the workflows retire from it on a fixed timeline. The renewal at the end of the cycle is a smaller number on a smaller surface.
Pattern two — freeze and assess. The CFO refuses the next RISE step-up, extends the existing ECC contract under extended maintenance, and uses the bought time to run the diagnostic across the estate. This is the slowest path; it is also the lowest-risk one.
Pattern three — full portfolio rationalisation. The CFO sets a board-approved target for SaaS spend reduction across the technology portfolio — not just SAP — and the SAP renewal becomes one input into a larger conversation. We have seen this pattern hold the most leverage in the renewal negotiation itself: the moment the SAP account team understands they are competing for a piece of a portfolio decision, the price book moves.
The decision in front of you
If your SAP renewal sits in the next 18 months, the conversation worth having is not "how do we negotiate a better RISE deal." It is "what does our software portfolio look like in 2032, and where does SAP sit inside it." The answer is rarely "everywhere it sits today."
Book a diagnostic. Bring the renewal sheet, the FUE schedule, and the last two indirect-access audits if you have them. Ten working days. We tell you what the next twenty years of SAP spend looks like on the current trajectory — and what owning the load-bearing workflows would actually cost instead.