An SAP renewal that arrives at the table without a competing alternative on paper is a sole-source negotiation. The buyer is asking the incumbent to price more generously than they need to. The buyer has no second number in hand. The SAP account team knows this, the renewal proposal reflects it, and the discount band that comes back is the discount band SAP gives to buyers who have nowhere else to go. The structured RFP is the single intervention that changes the geometry of the conversation. It is also the intervention buyers run least often, because it is procedurally heavier than calling the account team back with a counter.
What the RFP is and is not
The renewal RFP is not a bluff. It is a structured procurement exercise that takes the renewal scope, defines a target architecture, and asks two or three alternative providers to price it. The exercise has to be real enough that the alternatives respond seriously. If the RFP is read by the market as a bluff — if the scope is implausibly narrow, the timelines are implausibly tight, or the buyer’s engagement is implausibly shallow — the responses do not arrive, or they arrive in a form that is not usable.
The RFP is also not a migration plan. A buyer who runs an RFP at renewal is not committing to leave SAP. The buyer is committing to having a second price in hand and an architectural alternative documented well enough to be commercially credible. Whether the buyer ever uses the alternative is a separate decision made after the renewal negotiation has played out.
The discount-band evidence
Across the renewal engagements we have benchmarked, a credible RFP moves the incumbent SAP discount band by ten to eighteen percentage points relative to the sole-source baseline. The movement is not uniform. The largest moves happen where the alternative architecture is plausible to implement inside the renewal cycle. The smallest moves happen where the alternative is technically possible but operationally impractical — for example, an ERP replacement that would require an eighteen-month implementation against a six-month renewal window.
The size of the move is correlated with the credibility of the alternative on three dimensions: operational fit, implementation timeline, and total cost of ownership. The license optimization framework white paper documents the discount-band movement in detail.
What the RFP scope covers
The RFP scope mirrors the renewal scope on a comparable-functionality basis. For an SAP ECC or S/4HANA renewal, the RFP covers the core ERP footprint — finance, controlling, procurement, sales, and the relevant operational modules. For a SuccessFactors renewal, the RFP covers the core HR cloud. For an Ariba renewal, it covers the procurement-network functionality. The scope is comparable, not identical — if the alternatives offer the same business outcome through a different functional model, that is acceptable.
The scope explicitly does not cover speculative future expansion, edge integrations that would be unique to a particular technology stack, or transformation work that is outside the renewal cycle. A scope that includes too much speculative future is read as a roadmap exercise rather than a procurement exercise, and the credibility on the SAP side declines.
What to include
The RFP package includes a scoped functional specification, the target volume metrics (named-user counts, transactional volumes, document counts), the integration topology, the implementation timeline, and the commercial response template that allows direct comparison across alternatives. The volume metrics need to be conservatively counted, not the inflated USMM numbers. A summary of the relevant counting protocol is in the SAP S/4HANA topic page.
The timing of the RFP
The RFP runs in parallel to the SAP renewal conversation, not after it. The timing is critical. If the RFP is launched after the SAP renewal price is on the table, the SAP account team reads it as a tactic and the discount band does not move. If the RFP is launched twelve to fifteen months before the renewal expiry, with the SAP team aware that the buyer is in a structured procurement exercise, the discount band moves materially in the SAP proposal itself.
The fifteen-month window is not arbitrary. It is the window the major SAP-renewal alternatives need to respond seriously, and it is the window that SAP’s commercial leadership uses to plan account-level forecast. The renewal timing article covers the window mechanics in more detail.
What SAP does when the RFP is credible
When the RFP is read on the SAP side as credible, three things happen inside the SAP commercial process. The account team escalates to the regional commercial leadership to obtain non-standard discount approval. The renewal proposal is rebuilt to include clause exchanges that the account team would not normally offer — price-protection caps, audit-rights re-balancing, indirect-access clarifications. And the renewal timeline is held open to allow the buyer to consider the proposal alongside the alternatives.
None of these things happen at the same scale in a sole-source renewal. The clauses that buyers want to negotiate are the clauses the SAP account team cannot offer without escalation, and the RFP is what triggers the escalation. The SAP contract negotiation service page describes the clause-exchange agenda we typically pursue under RFP conditions.
The case for running the RFP even when staying
Most renewal RFPs end with the buyer staying with SAP. This is not a failure of the RFP. It is the most common outcome and the outcome SAP’s account team will plan for. The buyer that runs the RFP and stays at a fifteen-point improved discount band has captured the savings the RFP was designed to deliver. The buyer that does not run the RFP and stays at the sole-source band has not.
The argument we hear against running the RFP — that it “sends a bad signal” to the SAP account team — is not borne out in our engagement data. SAP’s account teams are routinely involved in RFP responses. The signal a credible RFP sends is that the buyer’s procurement function is functioning, which is the signal that triggers the commercial escalation in the first place. The bank-RISE case file documents a renewal RFP that closed with a fourteen-point improvement and the contract clauses the buyer needed.
The resource cost and how to manage it
The RFP costs the buyer organisation real time. A typical SAP-renewal RFP runs four to six months from scope definition to final response, requires fifteen to thirty per cent of one senior procurement professional’s time, and consumes meeting time from the business owners on the buyer side. The cost is real and should not be understated.
The cost is also small relative to the savings. A fifteen-point improvement on a renewal in the eight-figure range pays for an order of magnitude more procurement time than the RFP consumes. The recurring pattern we see is that buyers who would have happily approved the consulting spend to drive the savings hesitate to approve the internal time, even though the internal time is what does the work.
What does not work
Two recurring approaches that do not move the discount band. The first is the “shadow RFP” that the buyer claims to be running but never actually issues. The SAP commercial process can tell the difference. The second is the RFP issued to alternatives that are not plausible at the buyer’s scale — small regional providers or niche specialists who cannot credibly support the buyer’s footprint. The alternatives have to be at the right scale to be commercially credible.
A renewal without an RFP is a sole-source conversation. The price is the price the incumbent gives to buyers who do not have another number. The RFP is the cost of admission to a real negotiation.
If you are inside twelve to fifteen months of an SAP renewal, the most efficient next step is a scoping conversation about whether your renewal supports a credible RFP. We work alongside in-house procurement teams under engagement letter. The first conversation is at no cost.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.