Risk profile of RISE versus brownfield.

A RISE with SAP contract and a brownfield S/4HANA deployment carry materially different risk profiles. The two options are often framed in terms of capability or cost, but the more decision relevant comparison is risk. Vendor risk, integration risk, cost overrun risk, exit risk, and governance risk all shift weight when the buyer moves from a self managed brownfield estate to a SAP managed cloud subscription. This article maps the five categories side by side, with the field data that the firm has collected across 500 plus engagements, so that the buyer can price the risk into the seven year TCO model rather than discovering it inside the contract.

Vendor concentration risk and the single throat to choke

The brownfield deployment carries a distributed vendor risk profile. SAP supplies the application licence. The hyperscaler supplies the infrastructure. The system integrator supplies the implementation and the run time managed service. Each vendor is independently contracted, and each can be replaced without disturbing the other two relationships. The distributed profile increases the contract administration overhead, but it caps the vendor concentration at any single point.

RISE consolidates the three vendor relationships into one. SAP supplies the application, the infrastructure layer through a sub contracted hyperscaler, and the cloud operations service. The single contract simplifies the day to day administration, but it concentrates the vendor risk at SAP. A SAP service disruption affects the application layer and the cloud operations layer simultaneously, with limited buyer ability to switch one without the other. The concentration is the structural property of the RISE option.

The buyer counter is to negotiate the contractual right to switch the underlying hyperscaler at defined points in the term, with the right exercisable without invoking the termination clause. The right exists in principle inside the RISE template, but the standard wording leaves the timing and the cost open ended. The negotiated counter pins the timing to defined contractual checkpoints, with the cost capped against a published rate. The right does not remove the vendor concentration, but it does restore a partial degree of optionality at the infrastructure layer.

Integration risk and the boundary of the subscription

Integration risk is the risk that the deployment fails to connect cleanly to the surrounding application estate. The brownfield deployment carries the conventional integration risk of any on premise S/4HANA project, which is bounded by the data centre boundary and addressed by the SI partner with standard integration tooling. The integration cost is known and the integration scope is contained.

RISE introduces a new boundary, which is the boundary between the SAP managed environment and the buyer managed estate. The boundary affects every integration point. The custom code that ran inside the brownfield instance has to be inspected for compatibility with the BTP extension model. The data flows that previously ran through the database have to be re routed through the published APIs. The shadow IT integrations that the IT team did not know about have to be inventoried and re engineered. The integration cost on a RISE migration is typically twice the integration cost on a comparable brownfield project, with the cost concentrated at the boundary.

The buyer counter on the integration risk is to scope the integration inventory before the RISE signature, not after it. The inventory has to identify every inbound flow, every outbound flow, every custom code component, every reporting integration, and every operational handover. The inventory is the input to the integration plan, and the integration plan is the input to the contractual scope of the implementation. A RISE deal that closes without the inventory closes without the cost certainty, and the cost is recovered through change orders against the implementation contract.

Cost overrun risk and the variable expense lines

The headline cost on a RISE subscription is the FUE based fee, which is fixed for the contract term. The headline implies low cost overrun risk. The field data contradicts the headline. Across the firm engagement base, the actual seven year RISE TCO runs between twelve and twenty four percent above the headline subscription cost, with the spread driven by four variable expense lines.

The first variable line is the BTP consumption charge, which is metered against actual use rather than committed against the contract. The second variable line is the additional FUE purchase that the buyer triggers when the user count grows past the contracted volume. The third variable line is the indirect access fee that the buyer triggers when a third party application generates SAP activity through the published interface. The fourth variable line is the professional services fee on the work that the bundled implementation does not cover.

The brownfield equivalent has its own variable lines. The hyperscaler infrastructure charge is metered. The SI partner change order schedule is variable. The licence true up at the audit cycle is variable. The hardware refresh at the mid term is variable. The variable cost profile is comparable in magnitude, but the variable cost is more visible inside the brownfield model because each vendor invoices independently. Inside RISE, the variable lines all flow through the same SAP invoice, and the visibility is concentrated at a single point. The buyer counter is to require itemised invoicing across the variable lines, with the itemisation reported monthly rather than annually.

Exit risk and the structural lock in

The exit risk profile of RISE differs structurally from the exit risk profile of brownfield. The brownfield deployment carries the conventional exit cost of standing up a replacement environment, which the buyer controls because the buyer owns the existing environment and the existing database. The exit cost is bounded by the SI partner rate and the parallel run duration, neither of which is contracted to a third party.

The RISE deployment introduces a contractual early termination penalty, which sits between the buyer and the exit. The penalty is typically priced at fifty to eighty percent of the remaining contract value, with the recovery rate scaling against the time remaining. The penalty plus the bundled transition assistance scope sets the floor on the exit cost. The floor on the RISE exit cost is typically two to three times the floor on the brownfield exit cost at the equivalent point in the term, with the gap driven by the contractual penalty rather than the operational cost.

The exit risk has a present value, which the firm captures in the seven year TCO model as a separate line alongside the cost line. The exit risk present value runs between four and twelve percent of the seven year contract value across the engagement base, with the brownfield option carrying a lower exit risk present value because the brownfield exit cost is structurally lower. The exit risk present value flips the comparison in deals where the financial cost is close. The buyer counter is to negotiate the early termination penalty at the signature, with the goal of moving the year three exit cost from the upper end of the range to the lower end.

Governance risk and the audit posture

Governance risk is the risk that the deployment exposes the buyer to a compliance, audit, or regulatory finding. The brownfield deployment carries the conventional audit posture of any on premise SAP estate. The audit is triggered annually or biannually by SAP, with the scope covering the licence consumption, the indirect access exposure, and the user classification. The audit posture is well documented and the audit defence playbook is well rehearsed.

RISE shifts the audit posture in two ways. The first shift is the consolidation of the audit into the SAP managed environment, which reduces the buyer ability to control the audit boundary and the audit scope. The audit is run by SAP against the SAP environment, with the buyer in a reactive posture rather than a proactive posture. The second shift is the introduction of the FUE based licence model, which replaces the named user model with a usage based model. The FUE model carries its own audit complexity, with the FUE classification varying by user activity and the classification subject to interpretation at the audit point.

The buyer counter on the governance risk is to negotiate the FUE classification methodology at the signature, with the methodology documented in a schedule that the contract references. The methodology has to define what counts as which FUE category, with the boundaries documented against the published SAP guidance and against the buyer specific usage pattern. The schedule is the audit defence document at the renewal cycle and at any interim audit. A RISE contract without the schedule is a RISE contract that is audit exposed across the term.

Where the risk lands and how to price it

The risk profile of RISE concentrates vendor risk, increases integration risk, redirects cost overrun risk into less visible variable lines, increases exit risk through the contractual termination penalty, and shifts governance risk into the FUE classification methodology. The risk profile of brownfield distributes vendor risk, contains integration risk inside the data centre boundary, exposes cost overrun risk through visible vendor invoices, contains exit risk inside the operational cost envelope, and exposes governance risk through the conventional audit posture.

The comparison is not that one option is risky and the other is safe. The comparison is that the two options place the risk in different categories, and the buyer has to price the differential into the seven year TCO model. The firm uses a risk weighted TCO methodology that scores each option against the five risk categories, with the scores combined with the financial cost to produce the decision relevant total cost.

Across the engagement base, the risk weighted TCO comparison flips the headline cost comparison in roughly thirty percent of the deals. A RISE option that looks cheaper on the headline cost can land more expensive on the risk weighted total. A brownfield option that looks more expensive on the headline cost can land cheaper on the risk weighted total once the optionality, the integration certainty, and the audit posture are priced in. The flip is not predictable from the headline cost. It has to be calculated from the risk profile of the specific deal.

Closing position. Risk is the variable that decides the close calls

The deal that looks close on the financial comparison is the deal where the risk profile decides the outcome. The buyer who priced the risk into the seven year model walks into the RISE versus brownfield decision with a defensible number on each side. The buyer who priced only the financial cost has a number on each side that is missing the four to twelve percent risk premium that the structural differences carry. The discipline of pricing the risk is the discipline that converts a binary deployment debate into a quantitative investment decision, and it is the discipline that the senior decision makers consistently ask for at the board level.