Final comparison checklist. Brownfield versus RISE versus hybrid.

By the time a buyer reaches the final decision between brownfield S/4HANA, RISE with SAP, and a hybrid model, the analysis is usually months deep. Spreadsheets have been built, vendor meetings have happened, internal stakeholders have voiced opinions. What is often missing is a disciplined checklist that forces the decision team to confirm every dimension before the recommendation is presented. This article provides that checklist, organised across the commercial, technical, operational, regulatory, organisational, and strategic dimensions. The structure is simple. Walk each section, score each option, document the rationale. The output is not a pre determined answer. It is a defensible decision that the executive committee can sign off on without surprises later.

Commercial dimension

The commercial dimension covers the seven year total cost of ownership, the cash flow profile, the discount level achieved, and the exit cost. The brownfield path typically shows a lower upfront cost but a meaningful annual maintenance run rate that compounds. The RISE path shows a higher initial subscription but a flatter cost profile across the term. The hybrid path produces a blended profile that depends on the allocation between the two architectures.

The checklist asks the team to confirm that the TCO model spans seven years rather than three, includes all infrastructure costs across both paths, includes the migration cost honestly, includes the integration rebuild cost, and includes the exit cost at the end of the term. The team should also confirm that the discount level achieved on RISE has been benchmarked against the firm's experience across comparable engagements, where the average reduction against initial RISE proposals is 68 percent. A team that has not pressure tested the discount level is signing without leverage.

Cash flow profile matters separately from TCO. A CFO who needs predictable annual spend may favour RISE even at a slightly higher total cost. A CFO who needs to preserve capital may favour the path that delays the largest spend. The team should confirm that the cash flow profile fits the financial governance posture, not just the lowest number.

Technical dimension

The technical dimension covers the custom code estate, the integration topology, the data volume, the performance characteristics, and the upgrade compatibility. The team should confirm that the custom code remediation has been scoped against both paths, not assumed away. The integration rebuild cost has been priced rather than estimated. The data volume has been measured against the RISE pricing thresholds. The performance characteristics of the existing workload have been compared against the RISE technical specification.

Upgrade compatibility is the dimension that catches buyers later. The team should confirm that the planned roadmap functionality is available in both architectures within the term horizon, and that the upgrade cadence fits the buyer change capacity. A buyer that needs a specific module in eighteen months should not sign a contract that delivers it in thirty.

Operational dimension

The operational dimension covers run book ownership, incident response cadence, change management calendar, vendor governance capability, and integration management. The team should confirm that the operating model has been designed for the chosen architecture, with team structure, headcount plan, skill requirements, and tooling investment defined. A buyer that signs a RISE contract without redesigning the team carries duplicate capability and overpays.

The incident response cadence should be measured against the business impact, not the SAP default. The change management calendar should include the black out windows the business actually needs. The vendor governance function should be staffed and ready before contract signature. The integration management capability should be funded as part of the operating model, not assumed as an extension of existing capacity.

Regulatory dimension

The regulatory dimension covers data residency, audit rights, retention obligations, and industry specific compliance. The team should confirm that the hyperscaler region selected under RISE meets the data residency obligations across every jurisdiction in scope. The audit rights inside the RISE contract should allow the regulator visibility that the buyer commitments require. The retention obligations should be addressable inside the RISE archiving model. The industry specific compliance requirements, GxP for pharmaceuticals, SOX for public companies, ITAR for defence, should be addressed by the chosen architecture without compromise.

A buyer that signs RISE with an unresolved regulatory question discovers it during the first regulator engagement. The cost of remediating the question after signature is higher than the cost of resolving it before. The team should confirm regulatory approval, not just regulatory consultation, before recommending the architecture.

Organisational dimension

The organisational dimension covers change capacity, executive alignment, business sponsorship, and team readiness. The team should confirm that the broader organisation has the change capacity to absorb the migration in the planned window. A buyer competing with three other major programs for the same change capacity will struggle to deliver any of them on time. The executive alignment should be confirmed at the level required for the decision, not assumed from earlier meetings. Business sponsorship should be documented per workstream, not collected from a single executive sponsor.

Team readiness includes the skill gaps that the architecture choice creates. A brownfield team moving to RISE needs service management capability that may not exist. A RISE team that has to retain brownfield knowledge for the transition needs both skill sets in parallel. The team plan should confirm that the readiness gap is funded and that the timeline accommodates the ramp.

Strategic dimension

The strategic dimension covers the corporate development pipeline, the innovation roadmap, the supplier relationship posture, and the longer term technology direction. The team should confirm that the architecture choice fits the expected M&A activity over the seven year horizon. An active acquirer needs RISE contract flexibility for entity additions, divestitures, and restructuring. The innovation roadmap should fit the upgrade cadence the chosen architecture supports. The supplier relationship posture should reflect the leverage profile, with diversification away from SAP where strategic, or deeper integration where the relationship is foundational.

The longer term technology direction is the most difficult dimension to assess and the most important. A buyer that expects to consolidate ERP estates within five years should choose the architecture that supports the consolidation. A buyer that expects to spin off a major business unit should choose the architecture that supports the separation. The strategic context shapes the architecture choice in ways that the commercial spreadsheet does not capture.

Synthesis and recommendation

The final step is the synthesis. The team aggregates the scores, weights the dimensions by importance to the executive committee, and presents the recommendation. The recommendation should be defensible across every dimension, not just the financial one. Brownfield wins on operational continuity and cost control for some buyers. RISE wins on standardisation and roadmap alignment for others. Hybrid wins when the estate is too heterogeneous for a single architecture or when the migration sequence requires both in parallel. The right answer depends on the buyer, and the checklist is the discipline that gets the team to the right answer rather than to the answer that was already in mind.

Conclusion

The decision between brownfield, RISE, and hybrid is not made well through advocacy. It is made well through disciplined comparison across every dimension that matters. The checklist forces the conversation, surfaces the trade offs, and produces a defensible answer. A buyer that walks through the framework arrives at a decision the executive committee can support and the board can review. A buyer that skips the discipline arrives at a decision that holds until the first regret, which usually arrives within eighteen months of signature.