The pitch and the reality
SAP markets RISE with S/4HANA as a path to lower total cost of ownership over five years compared with the on-premises ECC estate that most Middle East enterprises are still running. The pitch is coherent. The infrastructure modernisation is real. The cloud hosting reduces some of the burden the customer's own infrastructure team carries. The integrated services envelope simplifies the procurement conversation. SAP cites 20% TCO savings over five years in its standard customer-facing materials.
The reality at a Middle East enterprise is more complicated. The cost analysis we run at the start of every diagnostic where RISE is on the table starts from a different baseline than the SAP pitch. Our baseline includes the integrator's services that SAP's TCO model does not. It includes the change-management envelope the customer carries internally. It includes the data-residency overlay that Middle East customers increasingly require. It includes the renewal-cycle escalation that the published RISE contracts permit. The number we land on is not the SAP number.
For a Middle East enterprise running an ECC estate at mid-market scale, the five-year RISE envelope on our model lands materially higher than the SAP-published savings would suggest.
The difference is not in the licence. It is in everything around the licence. This piece is the working version of that model.
What RISE contains, what it does not
The RISE envelope as sold contains four components. The S/4HANA licence at the Full User Equivalent count SAP has scoped against the customer's user base. The cloud hosting at the resilience tier SAP has scoped against the customer's operating expectations. The technical managed services covering the platform operation, the upgrades, and the security baseline. The transformation services envelope SAP describes as the change-management overlay.
What the envelope does not contain is the system integrator's work. The customer's chosen integrator — whether one of the global firms or a regional specialist — bills the work to migrate the data, configure the workflows, build the integrations, manage the customer change, and deliver the parallel-run period. This work is the largest single line in the customer's total investment, and it is not in the RISE price the customer signs. The customer carries it separately.
The customer's own internal cost is also not in the RISE envelope. The internal change-management staff, the subject-matter experts taken off business operations to support the migration, the parallel-run overhead for the duration of the transition, and the productivity dip the operations teams absorb as the new platform stabilises. None of those land on the RISE invoice. All of them land on the CFO's actual cost.
The data-residency overlay matters at a Middle East enterprise specifically. Saudi Arabia, the UAE, Qatar, and Bahrain each have evolving expectations on where customer data must reside. The RISE hosting choice — whether the hyperscaler region in the home market, a regional partner cloud, or a sovereign-cloud arrangement — has different commercial terms in each case. The customer's cybersecurity and regulatory team is the appropriate signatory on that choice, and the commercial terms typically add to the RISE envelope rather than reducing it.
The renewal escalation
The clause that hurts most over the five-year horizon is the renewal-cycle escalation. Published commentary places typical RISE annual escalation at 5 to 7 percent. Applied annually and uncapped, that rate compounds across the term rather than resetting, so the renewal number is not the signing number. The escalation applies to the licence, the hosting, the managed services, and the transformation envelope. The integrator's separate retainer compounds at its own rate, which is usually slower but not zero.
A Middle East enterprise that signed a RISE contract in 2024 and is looking at the 2029 renewal is staring at a number that is materially higher than the original signing number, against an operating reality that has changed substantially. The cloud-services choice the customer made in 2024 may not be the cloud-services choice the customer would make in 2029. The data-residency requirements that landed in 2026 and 2027 may not match the residency arrangement the original contract reflects. The integrator landscape has consolidated. The customer's own platform team has matured. The institutional appetite for direct hyperscaler arrangements has grown.
The renewal in 2029 is the moment where the alternative conversation lands. The alternative is not "ditch SAP." The alternative is "what workflows would we own outright at the 2029 renewal that we did not own at the 2024 signing."
The Middle East dimension
Three dimensions are specific to the Middle East market.
The hyperscaler footprint is now mature. AWS, Microsoft Azure, Google Cloud, and Oracle Cloud all operate regional data centres in the Middle East. The data-residency posture that drove some Middle East enterprises into private-cloud arrangements in the previous cycle is now satisfiable on the public hyperscalers. The direct hyperscaler option is genuinely available in a way it was not three cycles ago.
The sovereign-cloud direction is formal. The CBUAE's Sovereign Financial Cloud Services Infrastructure is the regulated-sector specific example. The broader national-cloud strategies in KSA and UAE point in the same direction. The Middle East enterprise that wants to operate under sovereign-cloud terms has a path that did not exist when the original RISE conversation happened.
The integrator ecosystem in the region is consolidating. The number of credible RISE-capable integrators is finite. The leverage that the customer carries at the integrator-negotiation table is structurally limited. The leverage that the customer carries against the SAP commercial team grows the moment the customer demonstrates an alternative path.
What the alternative looks like at the five-year mark
The CIO running a Middle East enterprise on RISE has three credible options at the five-year renewal moment.
Renew on improved commercial terms. The leverage at the table comes from demonstrating that the alternative is real. Customers who have moved one or two workflows onto owned software, even at the margins of the estate, command a different commercial conversation than customers who have not.
Move to a hyperscaler-direct arrangement. Operate S/4HANA on the public hyperscaler of choice, with the integrator's services contracted directly, and with the technical managed services either insourced or contracted with a regional partner. The published reductions on this path against the RISE envelope sit in the 15 to 25 percent range when the customer brings a credible threat to the table.
Migrate the workflows that should not be on S/4HANA in the first place. The S/4HANA core continues to handle the financial postings, the procurement workflow, and the regulated transaction recording. The workflows around the core — the customer-facing surfaces, the operational dashboards, the specialty workflows that the integrator has been billing for repeatedly — move to owned software. The S/4HANA footprint shrinks. The renewal at year ten is a smaller surface area than the renewal at year five.
The third option is the one this firm helps customers execute. It is also the one that creates the most leverage on the first two options. The customer who has a working REFORGE sprint behind them by the time the renewal conversation lands is in a different commercial position than the customer who does not.
The saasinator perspective
We are not arguing that every Middle East enterprise should retire S/4HANA. The platform is the system of record for many of the financial and regulated workflows the institution depends on. The argument is that the workflows around the platform do not all need to be inside the platform, and the renewal economics improve when the institution demonstrates that capability.
The RISE conversation is not adversarial. The SAP commercial team is well-prepared and the relationship is institutional. The conversation that lands well at the renewal moment is the conversation where the customer brings a credible alternative and the SAP team responds with substantive commercial movement. That conversation does not happen by accident. It happens when the customer has invested in the alternative.
What to bring to the diagnostic
If your Middle East enterprise is operating on ECC, planning the S/4HANA migration, or sitting between the first and second RISE renewal cycle, the conversation worth having is which workflow you would test against in a two-week pilot. Bring the latest RISE contract, the integrator retainer schedule, the data-residency posture, and a list of the workflows where the operational team complains most consistently.
The diagnostic is ten working days. The output is the workflow recommendation, the architecture sketch, and the five-year envelope under three scenarios. The decision sits with the CIO and the CFO. The conversation is the one worth having before the next renewal.