How to use RFP processes at RISE renewal.

The renewal RFP is one of the most powerful and most misunderstood instruments in the RISE with SAP renewal negotiation. A credible RFP shifts the SAP commercial position by surfacing alternative platform pricing, alternative implementation paths, and alternative operating models that the SAP account team has to model into the renewal proposal. A theatrical RFP, run without serious intent or without credible bidders, collapses under the weight of its own posture and hands the SAP commercial team confirmation that the buyer organisation has no real alternative. The difference between the two outcomes is process discipline. This piece walks the scoping work that precedes the RFP, the bidder list construction that makes the RFP credible, the questions that produce useful market pricing data, the parallel SAP negotiation that runs alongside the RFP, and the decision criteria that the buyer organisation has to define before the bids come back.

The renewal RFP is leverage, not procurement theatre

The renewal RFP serves a specific commercial purpose. It produces market pricing data that the buyer organisation can use to test the SAP renewal proposal. It surfaces alternative platforms that could carry portions of the SAP estate if the renewal does not land at an acceptable commercial level. It signals to the SAP account team that the buyer organisation has committed time, money, and executive attention to evaluating the alternatives, which forces the SAP commercial position to model a probability of execution rather than treating the renewal as a foregone conclusion. The RFP is not the renewal negotiation itself, but the RFP shapes the negotiation by producing the reference data and the alternative path that the negotiation can hold the SAP proposal against.

The renewal RFP fails when the buyer organisation treats it as procurement theatre. SAP account teams have seen many theatrical RFPs across the firm engagement base, and they recognise the patterns. A theatrical RFP has narrow scope, a thin bidder list, a compressed timeline, and no executive sponsorship behind the alternative path. The SAP commercial team detects these signals quickly and discounts the RFP as a negotiating posture. The renewal proposal then comes back at the unfavourable end of the benchmark distribution because the SAP team has correctly assessed that the buyer organisation has no realistic alternative to the renewal.

Scoping the renewal RFP honestly

The scope of the renewal RFP determines its credibility. The scope has to cover a meaningful portion of the SAP estate, with the workloads identified, the user populations defined, the integration surface mapped, and the data volumes estimated. A renewal RFP that scopes only the peripheral workloads, leaving the core financial and supply chain processes inside RISE, will not produce material leverage because the SAP team knows that the core remains captive. A renewal RFP that scopes the core, with a credible path for the core processes to migrate to an alternative platform, produces real leverage because the SAP team has to model the consequences of losing the core.

The scoping work has to be honest about the migration cost from the current RISE environment to the alternative platforms. A renewal RFP that ignores the migration cost will produce headline pricing data that looks attractive on the surface but collapses under realistic total cost modelling. The buyer organisation has to scope the migration cost alongside the alternative platform pricing, with the seven year total cost calculation including the migration project, the parallel run period, the change management programme, the consulting cost, and the operational risk premium that the migration carries. The honest seven year total cost is the figure that the renewal negotiation can hold the SAP proposal against.

Structuring the bidder list for credibility

The bidder list construction shapes the RFP credibility more than any other variable. A credible bidder list includes alternative platforms that the buyer organisation could realistically operate, not aspirational platforms that no buyer organisation of comparable scale has migrated to. The credible alternatives at the platform level include Oracle Cloud ERP, Microsoft Dynamics 365 Finance and Operations, Workday Financial Management, and Infor CloudSuite, with the relevance of each alternative determined by the buyer organisation industry and the workload pattern. The credible alternatives at the hosting level include the brownfield S/4HANA migration on a chosen hyperscaler, with the operating model selected from the available implementation partner options.

The bidder list has to include the implementation partner ecosystem alongside the platform options. A renewal RFP that asks only for platform pricing, without asking for implementation pricing and operating model pricing, will produce incomplete data because the platform cost is only a portion of the total seven year commitment. The bidder list should include the major global system integrators, the regional system integrators with strong SAP capability, and the boutique advisory firms that can construct the operating model around a brownfield or alternative platform path. The full bidder list produces the full cost picture that the renewal negotiation requires.

The questions the renewal RFP should ask

The renewal RFP questions determine the quality of the data that comes back. Generic questions produce generic responses that are not commercially useful. Specific questions, anchored against the buyer organisation consumption pattern and operating model, produce specific responses that the renewal negotiation can use. The RFP should ask for the seven year total cost of ownership at the buyer organisation specific user count and module footprint, the seven year cost projection under three growth scenarios, the migration cost from the current RISE environment, the parallel run cost during the migration period, and the operating cost differential between the current state and the proposed state.

The RFP should also ask for the commercial protections that the bidders would offer against the cost projections. The protections include the user growth uplift cap, the renewal uplift cap, the price protection mechanism against macro inflation, the service level commitments at the technical layer, and the exit protections at the end of the proposed term. The protections are as commercially relevant as the headline pricing because the headline pricing without protections produces an unbounded total cost commitment that the buyer organisation cannot underwrite to the board.

Running the parallel SAP negotiation

The renewal RFP runs in parallel with the SAP renewal negotiation, not as a sequential process that replaces the SAP conversation. The parallel structure produces the leverage. The SAP account team has to model the RFP probability against the renewal proposal, and the renewal proposal has to improve as the RFP advances through its milestones. The buyer organisation manages the parallel structure by sharing the RFP milestone schedule with the SAP team, by referencing the RFP data inside the SAP negotiation conversations, and by allowing the SAP team to respond to the RFP findings with revised renewal terms.

The parallel structure has to be managed honestly. The buyer organisation that runs the RFP purely as a negotiating prop, with no intent to consider the alternatives even at significantly improved pricing, will be detected by the SAP commercial team. The detection collapses the RFP leverage and produces a renewal proposal at the unfavourable end of the benchmark distribution. The buyer organisation that runs the RFP with documented executive sponsorship, scoped alternatives, and a defined decision criteria will produce the leverage that the renewal conversation requires. The honest construction is the leverage, and the leverage is what shifts the SAP commercial position from the standard proposal to the negotiated outcome.

Decision criteria before the bids return

The decision criteria have to be defined before the RFP bids come back, not afterwards. Defining the criteria after the bids return allows the bids to shape the criteria, which produces a confirmation bias toward the bid that the buyer organisation already wanted to accept. Defining the criteria in advance forces the buyer organisation to be honest about what it actually values across the renewal decision, with the criteria covering the total seven year cost, the migration risk, the operating model fit, the strategic alignment with the broader technology roadmap, and the executive sponsorship that each path can attract. The criteria produce a defensible decision that the board can underwrite, regardless of whether the decision is to renew with SAP, to migrate to an alternative, or to construct a hybrid path that uses different platforms for different portions of the estate.

The work is the leverage

The renewal RFP produces leverage in proportion to the work that the buyer organisation invests in it. A serious RFP, with honest scoping, credible bidders, specific questions, parallel SAP engagement, and predefined decision criteria, shifts the SAP commercial position by ten to twenty percentage points against the original renewal proposal. A theatrical RFP produces no leverage, consumes the buyer organisation procurement cycles, and signals to the SAP team that the renewal can be priced at the unfavourable end of the benchmark distribution. The difference is process discipline, and the process discipline begins eighteen months before the renewal date. The work is the leverage, and the leverage produces the renewal outcome that the buyer organisation needs from the next term of the RISE with SAP commitment.