Three case studies in choosing brownfield over RISE.

The RISE with SAP narrative often treats brownfield S/4HANA as a transitional path that buyers eventually abandon for cloud. The casebook tells a different story. In a meaningful proportion of engagements, the deliberate buyer side analysis concludes that brownfield is the correct destination for the contracting cycle in question, not a way station. The decision is rarely framed as a refusal to modernise. It is framed as a refusal to subsidise a deployment model whose total cost, operational coupling, and exit risk do not match the buyer specific situation. Three engagements illustrate the pattern. The buyers differ by industry, geography, and scale. The reasoning differs in each case. What unites the three is the rigour of the comparison and the willingness to defend a deployment selection that runs against the prevailing market direction.

Case one. The global industrial manufacturer that priced RISE at 2.4x brownfield TCO.

The first case involves a global industrial manufacturer with operations in 38 countries, approximately 22,000 SAP users across the ECC landscape, and a complex integration topology connecting the ERP to manufacturing execution systems, plant historians, warehouse management platforms, and a portfolio of buyer specific custom code accumulated over 18 years. The SAP account team presented a RISE proposal at the start of the renewal cycle, with the stated intent of converting the buyer to S/4HANA Cloud Private Edition over a 36 month transition.

The buyer side analysis built the seven year TCO comparison for three deployment scenarios. The first scenario was the SAP proposed RISE path with the indicated commercial terms. The second was a brownfield S/4HANA conversion using the existing infrastructure refreshed at the next normal cycle. The third was an extended ECC operation with selected S/4HANA capabilities deployed as side car services. The comparison covered subscription cost, infrastructure cost, conversion cost, ongoing operational cost, integration redesign cost, and the cost of operational disruption during the transition windows.

The RISE scenario delivered a seven year total of approximately 2.4 times the brownfield scenario. The cost differential was driven by three factors. The RISE subscription pricing included capacity tiers that exceeded the actual measured utilisation of the existing landscape by approximately 35 percent. The integration redesign cost required to operate the existing connected systems against a hyperscaler hosted RISE landscape totaled approximately 38 million dollars across the transition window. The operational coupling cost, measured by the additional internal resourcing required to coordinate with the SAP managed services rather than operating an integrated internal team, added approximately 4 million dollars per year on a steady state basis.

The brownfield selection produced a seven year savings of approximately 180 million dollars relative to the RISE proposal. The buyer retained operational control of the landscape, deferred the cloud transition to a future contracting cycle when the commercial terms and the deployment maturity might better align, and preserved optionality on the eventual destination including the possibility that a future cycle might select a non SAP path for parts of the application portfolio. The decision was approved by the audit committee on the basis of the financial comparison alone, with the operational considerations treated as supporting evidence rather than as the primary driver.

Case two. The European pharmaceutical company with regulatory data residency constraints.

The second case involves a European pharmaceutical company with operations across 14 countries, approximately 8,000 SAP users, and regulatory data residency obligations under several national and supranational frameworks. The pharmaceutical regulator in the buyer primary jurisdiction had issued formal guidance on the requirements for cloud hosted ERP supporting GxP processes, and the guidance required specific data residency, audit access, and operational control provisions that the RISE standard offering did not contemplate without bespoke contractual amendments.

The buyer side analysis began with the regulatory review rather than the financial comparison. The compliance team built a matrix of the GxP requirements against the RISE service description, the data processing addendum, and the operational security documentation that SAP makes available to RISE customers. The matrix identified 27 specific provisions where the RISE standard offering would not satisfy the regulatory requirement without bespoke amendment, and 9 of those provisions involved capabilities that SAP indicated were not available at any commercial term.

The brownfield scenario satisfied the regulatory requirements natively because the deployment operated within the buyer existing infrastructure under the buyer existing operational controls that had previously been validated by the regulator. The brownfield scenario carried lower regulatory risk, lower compliance overhead, and faster time to operational stability for the regulated processes. The RISE scenario would have required either the bespoke amendments that SAP could partially deliver, accepting compliance risk on the provisions where no amendment was available, or descoping the regulated processes from the RISE deployment.

The financial comparison showed the brownfield scenario at approximately 30 percent of the RISE seven year cost. The savings reflected the elimination of subscription pricing on the user population that would otherwise have moved to RISE, retention of the existing infrastructure investment, and avoidance of the bespoke compliance work that the RISE amendments would have required. The pharmaceutical company selected brownfield, with the explicit reservation of revisiting the question at the next renewal cycle in the event that SAP standardises the regulatory provisions sufficient to satisfy the requirements without bespoke amendment.

Case three. The North American utility with operational continuity and predictability requirements.

The third case involves a North American utility operating regulated electric and gas distribution across multiple state jurisdictions, with approximately 11,000 SAP users supporting customer service, work management, asset management, and back office finance and human capital management. The utility operated SAP across several decades, with the integration topology bound to the safety critical and regulated grid operations through a network of interfaces that the safety regulator and the public utility commission both reviewed during periodic audits.

The buyer side analysis foregrounded operational continuity as the primary consideration rather than cost. The utility could not accept material risk to the operational continuity of the safety critical systems, and the integration topology connecting ERP to those systems would require substantial redesign under any RISE scenario. The redesign would itself introduce risk during the transition window, and the operational coordination model under RISE would change the accountability structure that the safety regulator had reviewed.

The financial comparison produced numbers in the same range as the other two cases. The brownfield scenario was approximately 40 percent of the seven year RISE cost when the integration redesign and the operational transition were costed at realistic levels. The financial comparison alone justified the decision, but the operational continuity dimension provided the dispositive argument that the audit committee and the board could rely on when defending the decision externally.

The utility selected brownfield with an extended maintenance commitment from SAP and a deliberate program of incremental capability additions through S/4HANA components deployed as side car services where the operational risk profile permitted. The approach preserved operational continuity, maintained the regulatory posture, and provided an evolutionary path toward eventual S/4HANA adoption on a timeline that the utility controlled rather than one that SAP commercial pressure imposed.

The pattern across the three cases.

The three cases share a structural pattern despite the surface differences. Each buyer built the comparison on the buyer specific operational and regulatory reality rather than on the SAP narrative. Each buyer included the cost of integration redesign, operational transition, and ongoing operational coordination at realistic levels rather than at the levels the SAP business case typically assumes. Each buyer included the cost of optionality lost under a long term RISE commitment, measured against the optionality that brownfield preserves. Each buyer arrived at a seven year financial comparison where brownfield delivered material savings against the RISE proposal, and in each case the savings were large enough to justify the decision on financial grounds alone before operational and regulatory considerations entered the analysis.

The pattern also includes a deliberate framing of the decision as a defence of buyer interest rather than a refusal to modernise. The three buyers articulated explicit conditions under which a future cycle could reach a different conclusion. Those conditions included specific changes in RISE commercial terms, specific evolution of the RISE service description toward better support for the buyer regulatory or operational requirements, and specific maturation of the buyer organisation that would reduce the operational transition cost. The brownfield decision in each case was a decision for this contracting cycle, not a permanent rejection of the cloud direction.

Choosing brownfield is not a refusal to modernise. It is a refusal to subsidise a deployment model whose total cost, operational coupling, and exit risk do not match the buyer specific situation in the current contracting cycle.

Conclusion.

Three case studies in choosing brownfield over RISE illustrate how rigorous buyer side analysis arrives at the brownfield conclusion when the operational, regulatory, and financial considerations align. The global industrial manufacturer found a 2.4x cost differential favouring brownfield and saved approximately 180 million dollars across the seven year horizon. The European pharmaceutical company found that the regulatory framework imposed requirements the RISE standard offering could not satisfy without bespoke amendments that were either unavailable or impractical at commercial terms. The North American utility found that operational continuity and safety regulator considerations required the predictability that brownfield offered. Across the three cases, the brownfield decision was defended on financial grounds, supported by operational and regulatory considerations, and framed as a decision for this contracting cycle rather than as a permanent rejection of cloud adoption. The pattern across the three cases is replicable for any buyer who builds the comparison on the buyer specific reality rather than on the SAP narrative, and who is prepared to defend a deployment selection that runs against the prevailing market direction when the analysis warrants that defence.