Hybrid models. Brownfield core plus RISE for new entities.

The hybrid SAP configuration, with a brownfield core and a RISE periphery for new entities, has emerged as the practical middle path for organisations that value the control of an owned core but face the operational reality of an active acquisition pipeline. The configuration is not the SAP account team's default recommendation, because the commercial structure carries both a perpetual licence on the core and a RISE subscription on the periphery, which makes it less straightforward to position. The configuration is, however, the right answer for a growing number of large multinational and mid market buyers, because it answers the operating reality of a business that is buying companies, opening regions, or spinning up new divisions on a faster cadence than the brownfield estate can absorb. This article walks through how the hybrid posture works, what the commercial terms should look like, and what the governance needs to hold for the configuration to deliver.

Why the hybrid posture exists at all

The hybrid posture exists because the brownfield core is rarely the right platform for a newly acquired entity. The core has been tuned across years, carries deep customisation, and runs against a release calendar that the parent organisation owns. A newly acquired entity that joins the core inherits the release calendar, the customisation footprint, the integration estate, and the operating burden. The inheritance is often a poor fit for the size of the acquisition and slows the post acquisition integration.

RISE for the new entity offers a faster path. A subscription deployment of S/4HANA Cloud Private Edition, sized to the acquired entity's actual user count, can be stood up in weeks rather than the months a brownfield extension would require. The entity carries its own commercial line, its own operating model, and its own integration boundary, with a defined interface to the core for the consolidated reporting and the master data flows that the parent organisation needs.

The hybrid posture trades the architectural simplicity of a single platform for the operational agility of a two platform estate. The trade is worthwhile when the acquisition pipeline is active enough to justify the standing capability to deploy a new entity quickly, and when the parent organisation has the architectural maturity to run two postures in parallel.

The commercial structure of a hybrid deal

The commercial structure of a hybrid deal has two halves. The first half is the perpetual licence on the brownfield core, with the standard annual maintenance at the SAP rate of 22 per cent. The licence is sized against the user population of the core entities, which is the parent organisation and the entities that have been integrated into the core.

The second half is the RISE subscription for the new entities. The subscription is sized against the user population of each new entity, with the FUE count built up entity by entity. The subscription carries the standard RISE bundle, including the BTP allocation, the hyperscaler infrastructure, and the services wrap. The subscription is structured as a single contract that can absorb new entities through defined amendment clauses, with a price per FUE that is locked at signature and a defined cap on the year over year change in total FUE.

The negotiation lever that matters most on the hybrid commercial is the amendment mechanism. A well structured amendment clause lets the parent organisation add a new entity to the RISE subscription at the original signature pricing, without re opening the underlying commercial. The clause is rarely offered without explicit request. The clause is the single feature that makes the hybrid posture commercially competitive against an alternative path of one off RISE deals per entity.

The architecture that holds the two halves together

The hybrid architecture is built around a defined boundary between the brownfield core and the RISE periphery. The boundary carries the integration flows for consolidated reporting, master data, intercompany trading, and the analytics roll up. The boundary is rarely simple, but it is also not unique to hybrid, because the same boundary exists in every multi instance SAP estate.

The integration runs on a single integration platform that serves both halves. The platform is typically BTP, because the RISE subscription includes a BTP allocation and the brownfield core can extend onto the same BTP tenant. The unified BTP layer simplifies the integration governance, reduces the cognitive load on the integration team, and lets the parent organisation hold a single integration backlog across both halves.

The master data flows in one direction, from the core to the periphery, for the master data that the consolidated organisation owns. The transactional data flows in both directions, with the periphery sending its consolidated trial balance to the core and the core sending the intercompany positions back. The release calendar of each half operates independently, with a defined synchronisation point at the period close.

The governance that makes hybrid work

The hybrid posture requires a governance model that holds both operating rhythms at once. The brownfield core operates on the parent organisation's release calendar, with the upgrade cadence, the patching cadence, and the customisation backlog owned by the parent's architecture team. The RISE periphery operates on the SAP managed cadence, with the upgrade calendar set by SAP and the customisation footprint kept minimal by design.

The governance model carries a single architecture authority that holds the boundary, a single integration authority that holds the unified BTP layer, and two operating authorities that hold the respective halves. The architecture authority resolves the conflicts that arise when the SAP release calendar moves a feature into the standard product that the brownfield core has customised. The integration authority resolves the conflicts that arise when the BTP layer requires changes for one half that affect the other.

The governance model also carries a defined entity onboarding playbook. The playbook covers the user mapping into the FUE construct, the master data alignment with the core, the integration setup, the security model alignment, and the change management for the entity's users. A mature playbook brings a new entity from acquisition to RISE live in eight to twelve weeks, which is the speed that justifies the hybrid posture in the first place.

The economics of hybrid against the alternatives

The economics of hybrid against pure brownfield are mixed. Hybrid costs more in the first year, because the RISE subscription begins immediately while the brownfield core continues to carry its perpetual licence. Hybrid costs less in years three through seven on the entity footprint, because the RISE subscription absorbs the entity without the brownfield extension cost that the core would have required.

The economics of hybrid against pure RISE are favourable in the early years and roughly neutral in the later years. The brownfield core retains its perpetual licence economics for the core users, which is cheaper across the term than moving the core into a RISE subscription. The RISE subscription for the new entities is priced at the same rate it would have carried as a pure RISE deal, with the amendment clause preserving the economics for subsequent entities.

The economics are rarely the deciding factor on hybrid. The deciding factors are the speed of deployment for new entities, the preservation of control on the core, the optionality on the renewal cycle, and the governance maturity to run both halves in parallel. The economics support the decision but rarely drive it.

Common mistakes that compromise the hybrid posture

The first common mistake is to negotiate the perpetual licence and the RISE subscription as separate deals, with separate timing and separate teams. The separation gives SAP the chance to optimise each commercial independently against its own incentives, which usually produces worse terms on both sides than a single integrated negotiation. The right approach is a single negotiation that prices the two halves against each other.

The second common mistake is to under invest in the integration boundary. The boundary is the load bearing element of the hybrid posture. An under invested boundary creates friction at every period close, drives shadow integration footprints, and erodes the operational simplicity that justified the hybrid posture in the first place. The boundary deserves the same architectural attention as the core itself.

The third common mistake is to let the RISE subscription absorb entities that should have been integrated into the core. The amendment clause is convenient. The cumulative cost of a sprawling RISE subscription that holds entities better placed on the core is often higher than the cost of the brownfield extension that should have happened. The discipline of deciding entity by entity which half each new entity belongs in is part of the governance the hybrid posture requires.

The fourth common mistake is to skip the renewal preparation on the RISE side. The renewal cycle on the RISE half operates in the same way it does on a pure RISE deal, with the same year five preparation requirement. The buyer that does not begin renewal preparation in year five enters the year six negotiation without leverage, regardless of the hybrid posture.

Conclusion: hybrid is the answer when the operating reality demands it

The hybrid posture, with a brownfield core and a RISE periphery for new entities, is the right answer for organisations that face an active acquisition pipeline, that value the control of the core, and that have the governance maturity to run two postures in parallel. The posture is not the SAP default recommendation, because the commercial structure is more complex than either pure option. The complexity is, however, the price of an operating model that delivers fast entity deployment, preserves the core control, and keeps the renewal optionality open. The buyer that builds the commercial, the architecture, and the governance correctly secures a configuration that holds across the seven year horizon and beyond. The buyer that treats hybrid as a default rather than a deliberate choice usually ends up with the cost of both postures and the benefits of neither. The work of hybrid is the work of architectural and commercial discipline, applied consistently across the term.