A persistent misconception around RISE with SAP is that its single-contract, all-inclusive framing means an organisation no longer needs a systems integrator to get to S/4HANA. That assumption is wrong in a way that has caused genuine planning problems for organisations that budgeted a RISE subscription without also budgeting for the separate implementation work RISE was never designed to include.
What the RISE Subscription Actually Covers
SAP’s own product documentation is clear about the boundary, even though marketing language around the offering does not always make this obvious. The RISE subscription covers software, infrastructure, and platform services including S/4HANA Cloud and BTP, while services for assessment, migration, implementation, integration, and consulting are provided separately by an implementation partner to configure the standard system to meet an organisation’s specific business processes.
This division holds regardless of deployment size or complexity. Advisory, implementation, and application managed services require separate contracts to be executed by a systems integrator, unless performed directly by the customer, and even certain technical managed services areas within SAP’s own RISE contract are delineated between what SAP performs directly and what remains available for an SI to execute.
Why the Confusion Persists Despite Clear Documentation
The confusion is understandable given how RISE is actually marketed. Single contract, single owner, and unified procurement are genuine and valuable features of the offering, and they do meaningfully simplify the commercial relationship with SAP itself compared to the fragmented licensing and infrastructure procurement that preceded it. What gets lost in that simplification message is that the commercial relationship being simplified is specifically the relationship with SAP, not the entire scope of work required to actually complete a migration.
An organisation reading RISE’s marketing materials in isolation, without separately scoping the implementation work, is genuinely likely to underestimate the total project cost and timeline, since the RISE subscription figure alone was never intended to represent the full cost of getting from a legacy system to a live S/4HANA environment.
What Genuinely Changes Between Brownfield and Greenfield Scope
The implementation partner’s scope of work varies considerably depending on migration approach, and that variation directly affects how much of the total project cost sits outside the RISE subscription itself. A brownfield conversion, carrying forward existing customisations and configuration, typically requires more extensive implementation partner involvement to assess, migrate, and validate that existing logic against the new environment. A greenfield implementation, building fresh against SAP’s standard configuration, generally requires less bespoke implementation work but still requires a partner to manage the build, data migration, testing, and rollout regardless of how standardised the target configuration is.
Understanding which approach a given migration will actually follow, before requesting implementation quotes from prospective SI partners, is essential to getting comparable quotes back, since a brownfield-scoped proposal and a greenfield-scoped proposal from different partners are not directly comparable unless both are pricing the same underlying migration approach.
The Question Worth Asking Before Signing a RISE Agreement
Given this division of responsibility, the practical step worth taking before signing any RISE agreement is scoping the implementation partner engagement in parallel, not sequentially after the RISE contract is already signed. SAP’s own RISE product page describes a range of AI-assisted tools available to support the most complex, time-intensive transformation activities, spanning system analysis, custom code modernisation, data management, configuration, test management, and rollout, all explicitly framed as support for the transformation work rather than a replacement for it, which confirms directly that even SAP’s own tooling is designed to assist an implementation partner’s work rather than substitute for the partner relationship entirely.
Organisations that sign a RISE subscription first and only then begin sourcing an implementation partner frequently discover the true combined cost and timeline considerably later than would have been useful for their own internal budget and stakeholder planning process.
Running both procurement processes in parallel, and treating the implementation partner selection with the same rigour applied to the RISE commercial negotiation itself, is increasingly standard practice among organisations that have already been through this process once. Many Tier I and Tier II systems integrators offer specialised services that complement and add significant value to a RISE with SAP programme, and selecting the right one is a genuinely separate decision from negotiating RISE’s own commercial terms.
Building a Combined Budget That Actually Holds
The most reliable way to avoid the underestimation problem described here is building a single combined budget line spanning both the RISE subscription and the anticipated implementation partner engagement before either is finalised, rather than tracking them as two entirely separate budget conversations owned by different internal stakeholders. That combined view is what actually gets presented to whoever needs to approve the overall transformation spend, and presenting the RISE subscription figure in isolation to that approver, even unintentionally, sets an expectation that the rest of the project will later have to correct.
Conclusion
RISE with SAP genuinely simplifies the commercial relationship with SAP itself, bundling software, infrastructure, and platform services into a single subscription. It does not eliminate the need for an implementation partner, and organisations that treat the RISE subscription figure as the full cost of migration consistently underestimate both the total budget and the timeline required to actually go live.
Scoping the implementation partner engagement in parallel with, rather than after, the RISE commercial negotiation, and understanding clearly whether a migration will follow a brownfield or greenfield approach before requesting partner quotes, are the two most practical steps toward an accurate combined budget for the full project.
