RISE without SAP discounts. Building the alternative case.

SAP account teams occasionally signal that the headline discount conversation is closed. The proposal is framed as a take it or leave it commercial position, with reference to internal pricing policy, regional approval ceilings, or the strategic value of the migration that the buyer is told justifies the price. In a meaningful share of these conversations, the SAP position is genuine. In a larger share, the position is a negotiation posture that depends entirely on the buyer accepting the absence of a credible alternative. The work of the buyer side advisory team is to build the alternative case at sufficient depth that the SAP commercial conversation reopens. Across 500 plus RISE engagements, the firm has tracked the gap between the no discount opening and the eventual close, and the gap has averaged 41% of initial commitment value when the alternative case was built and presented with discipline. The discipline does not depend on bluffing. It depends on assembling a real, executable alternative with verified pricing and a defensible operating model, then letting the existence of that alternative do the commercial work.

When SAP frames the conversation as price closed.

The no discount framing arrives in two characteristic forms. The first is the structural framing, where the account team references internal SAP pricing policy. The buyer is told that the proposed configuration sits at a discount level already approved at the highest authority layer, that no further discount approval is available, and that the buyer is receiving the deepest pricing the SAP commercial system supports. The second is the strategic framing, where the account team references the value of the transformation. The buyer is told that the migration unlocks operating model benefits, BTP innovation capacity, and S/4HANA Cloud Private Edition functional depth that justifies the headline price independent of discount comparison.

Both framings are calibrated to close the commercial conversation rather than to inform it. The structural framing presumes the buyer has no way to verify the approval ceiling claim, and indeed the buyer cannot audit SAP internal policy. The strategic framing presumes the buyer has no alternative path to the same business outcome, and the buyer often does. The buyer who accepts either framing without testing the underlying assumption ends the negotiation in the position the account team prefers. The buyer who builds an alternative case introduces evidence that the assumption is testable and that the buyer is prepared to act on the alternative if the commercial position does not move.

The signal that a no discount framing is a posture rather than a final position is consistent across deals. The framing is delivered late in the cycle, often after months of conversation, and the SAP team continues to invest meeting time in the buyer despite the closed framing. A commercial position that is genuinely closed does not require continued sales investment to maintain. The continued investment indicates the position is open in fact, even when it is closed in language.

The brownfield extension as a credible alternative path.

The most accessible alternative case is the brownfield ECC extended maintenance path. SAP has committed to mainstream maintenance on ECC 6.0 through the end of 2027 and extended maintenance through 2030, with optional further extension at additional premium. For a meaningful portion of the SAP installed base, the brownfield extension is a fully supportable operating posture that requires no transformation expenditure in the near term and preserves the option to revisit RISE at any later point. The case for the alternative depends on documenting the operating cost of brownfield, the upgrade obligations that arrive on a defined timeline, and the residual life of the existing landscape against the buyer business plan.

The brownfield case is built around four components. The first is the maintenance fee trajectory across the extended maintenance window, including the extended maintenance premium that applies from 2028 forward. The second is the infrastructure operating cost of the existing landscape, including hardware refresh on the published depreciation cycle, basis support, and the data center or colocation footprint. The third is the application support cost, including the basis team, the ABAP team, and the functional configuration team that maintains the existing system. The fourth is the capital expenditure schedule for hardware refresh, OS upgrades, and database release upgrades through the brownfield window.

Assembled together, the brownfield extension case typically presents an operating cost that is 30 to 50 percent of the equivalent RISE commitment for the same time window, with the operational trade off that the buyer carries the operational risk of the legacy stack and the obligation to plan the eventual migration. Presented to SAP, the brownfield case demonstrates that the RISE proposal is competing against a real alternative with a real operating cost, not against the buyer abstract preference for transformation.

Greenfield deployment with hyperscaler native services.

The second alternative path is a greenfield S/4HANA deployment on a hyperscaler, with the buyer contracting separately for compute, storage, and managed services. The path requires the buyer to assemble the deployment from S/4HANA Cloud Private Edition licensed independently of the RISE bundle, hyperscaler infrastructure contracted at the buyer hyperscaler discount rate, and managed services contracted from a system integrator or independent managed services provider. The total cost of the assembled greenfield deployment is comparable to RISE, often within 10 to 15 percent of the RISE commitment, with the operational trade off that the buyer carries integration responsibility across the assembled stack.

The greenfield alternative is most credible for buyers who already operate substantial hyperscaler footprints, who have existing reserved instance commitments at competitive pricing, and who have system integrator relationships that can absorb the managed services scope. The case is less credible for buyers who would be standing up new hyperscaler relationships and new managed services contracts as part of the alternative, since the assembly cost of those new relationships erodes the commercial advantage. The buyer side discipline is to assemble the greenfield case using verified hyperscaler pricing from the buyer existing relationships and verified managed services pricing from the buyer existing integrator panel.

Presented to SAP, the greenfield case introduces a different commercial pressure than the brownfield case. The brownfield case threatens delay of the RISE commitment. The greenfield case threatens loss of the RISE commitment to a competitor managed services provider, with SAP receiving only the underlying software revenue. The discount approval response to the greenfield case is typically deeper than the response to the brownfield case for that reason, often in the range of 8 to 15 additional percentage points of reduction.

Functional substitution and best of breed assembly.

The third alternative path applies to specific functional scopes within the broader SAP footprint. Where SAP RISE is being proposed as a single bundle covering core ERP plus adjacencies such as procurement, expense, talent management, or analytics, the buyer can build a case for substituting one or more of the adjacency scopes with a best of breed alternative. Coupa, Workday, Tableau, and ServiceNow each offer functional alternatives to specific SAP modules that are widely adopted in the enterprise market and that can be procured outside of the RISE bundle.

The functional substitution case requires the buyer to assemble pricing for the substitute, integration cost for connecting the substitute to the remaining S/4HANA core, and operating model adjustments for managing the additional vendor relationship. For some scopes, the substitution case is dominant on a five year TCO basis. For others, the substitution case is closer to neutral but introduces vendor diversity that the buyer values for strategic reasons. The pricing for the SAP module that the substitute replaces becomes the commercial benchmark that SAP must reduce against to retain the scope inside the RISE bundle.

The functional substitution case is most powerful when assembled across multiple modules in parallel. A buyer who can credibly substitute procurement with Coupa, talent with Workday, and analytics with a separate platform places SAP in a position where the RISE bundle is competing for each scope individually rather than retaining the scope by virtue of the bundle. The discount response across the bundle is typically deeper when each scope is contested than when the bundle is treated as indivisible.

The cost of building the alternative compared with the savings it unlocks.

The work of assembling the alternative cases is not free. For a major enterprise RISE negotiation, the alternative case assembly typically requires four to eight weeks of advisory effort across the brownfield, greenfield, and functional substitution paths, with the cost typically in the range of $150,000 to $400,000 depending on scope. The cost is concentrated in the analytical work of building the operating models, validating pricing with the relevant vendors, and packaging the comparison into a format that supports the SAP commercial conversation.

The savings unlocked by the alternative case, in the firm casebook, runs typically between 35 and 55 percent of the initial RISE commitment, against the assembly cost cited above. On a $40 million seven year RISE commitment, the alternative case investment of $300,000 typically unlocks $14 to $22 million of commercial movement. The ratio of investment to savings, across the casebook, runs above 40 to 1. The buyer who declines to invest in the alternative case on cost grounds typically accepts a commercial position that the alternative case would have moved.

The savings depend on the alternative case being credible to SAP, not on it being executed. In the meaningful majority of cases where the alternative case is built and presented, the SAP commercial position moves and the RISE deal closes at a reduced commitment. The alternative case is not the path the buyer ultimately chooses. It is the path the buyer is prepared to choose if the RISE commercial position does not adjust.

How presenting the alternative changes the SAP conversation.

The presentation discipline is as important as the analytical discipline. The alternative case is presented to the SAP account team in writing, with the operating models attached, the vendor quotes referenced, and the executive committee resolution authorising the alternative path documented in the cover. The presentation makes clear that the alternative is approved internally for execution, that the comparison is rigorous, and that the buyer commercial team has the mandate to proceed with the alternative if the RISE commercial position does not move within a defined window.

The conversation that follows the presentation is structurally different from the conversation before it. The SAP account team escalates the deal internally to a higher approval level, typically to regional or divisional finance, since the deal is now competing against a documented alternative rather than against the buyer abstract preference for the SAP path. The higher approval level brings deeper discount authority. The discount response, when it arrives, is typically calibrated to close the gap between the RISE commitment and the alternative path operating cost over the same window.

The buyer side discipline at this stage is to hold the position, document the SAP response, and continue the work of refining the alternative case in parallel. The negotiation that follows often closes within four to eight weeks of the alternative case presentation, with the closing commitment substantially below the no discount opening. The discipline that delivers the result is not aggressive negotiation. It is rigorous preparation of the alternative.

The no discount framing depends entirely on the buyer accepting the absence of a credible alternative. Building the alternative is the entire commercial lever, and it works because it is real.

Conclusion.

RISE proposals framed by SAP as commercially closed are, in the meaningful majority of cases, open to substantial commercial movement when the buyer presents a credible alternative path. The alternative may be the brownfield extension, a greenfield deployment on a hyperscaler with assembled managed services, or functional substitution of one or more bundle scopes. The path that ultimately wins commercial movement varies by deal, but the discipline is the same. The buyer assembles the alternative with rigorous operating models, verified vendor pricing, and documented internal approval to execute. The buyer presents the alternative in writing with the supporting evidence attached. The SAP commercial position then moves to a level that closes the gap between RISE and the assembled alternative. The savings unlocked by this discipline, in the firm casebook, run between 35 and 55 percent of the initial commitment, against an analytical investment that rarely exceeds 1 percent of the commitment value. The buyer who is prepared to do the alternative case work is the buyer who captures the commercial movement.