The single piece of advice procurement functions hear most often, from analysts and from advisors, is to apply competitive leverage in their SAP negotiation. The advice is sound. The execution is often not. In our portfolio, the buyers who claim to be evaluating alternatives but cannot produce a costed alternative document obtain no measurable concession from that claim. The buyers who produce a costed alternative, who route the document through procurement governance, and who can credibly act on it obtain a discount tier that buyers without the document do not. Competitive leverage is a function of documentation, not of posture.
What competitive leverage is, exactly
Competitive leverage is the buyer's documented capacity to substitute some or all of the SAP estate with an alternative. The alternative does not have to be a like-for-like ERP replacement. It can be a best-of-breed unbundling, a hyperscaler-native rebuild of a specific functional domain, a managed-service alternative for a sub-estate, or a contracted run-on of lapsed-maintenance for a defined window. The alternative has to be credible, costed, and routed.
Credibility is the precondition. SAP's account team, like any sales team, calibrates concession against the perceived probability of loss. A claim of evaluation that the team does not believe produces no concession. A documented evaluation routed through procurement governance produces concession measured against the discount tier the team has authority to release.
The five classes of credible alternative
Across our portfolio, five classes of credible alternative recur. Each produces a different style of leverage and a different style of concession.
Class 1: Like-for-like ERP replacement
The full replacement of SAP S/4HANA with an alternative ERP (Oracle, Microsoft Dynamics, Workday Financials for sub-estates) is the strongest theoretical alternative. It is also the most expensive to document credibly, because credibility requires a transition cost model, an implementation timeline, and a risk register. Full-replacement leverage works best in the longest renewal cycles, where the buyer has the runway to invest in the documentation.
Class 2: Best-of-breed unbundling
The unbundling of specific functional domains from SAP into best-of-breed alternatives (Workday for HR, Salesforce for CRM, Coupa or Ivalua for procurement) is a more achievable form of leverage. The documentation is narrower (one functional domain at a time), the transition cost is lower, and the operational disruption is smaller. Unbundling leverage works in renewal cycles where SAP has a weaker product fit in a specific domain.
Class 3: Hyperscaler-native rebuild
The rebuild of an SAP-adjacent capability on a hyperscaler stack (AWS, Azure, Google Cloud) is increasingly credible. The capability rebuilt is typically analytics, integration, or a specific business application rather than core ERP. The leverage is targeted at the SAP modules where the hyperscaler can credibly compete (BW, BPC, certain LoB applications). The renewal leverage strategies article sets out the modules where this leverage is currently strongest.
Class 4: Managed service substitution
The substitution of in-house SAP operations with a managed-service provider (Accenture, Infosys, Capgemini, TCS) does not replace SAP but changes the commercial relationship around it. The leverage works because the managed-service provider takes on the SAP licensing relationship as part of the engagement, and the buyer's licensing posture is renegotiated through the provider rather than directly. Managed-service leverage is most effective in mid-market and lower-large-enterprise.
Class 5: Run-on lapsed maintenance
The fifth alternative is the simplest and the most underused. The buyer can run on perpetual licenses with lapsed maintenance for one or two quarters, paying maintenance in arrears as a condition of restoration. The leverage works because SAP's account team has no concession to extract from a buyer who is paying for use of the software at the perpetual licence value. Run-on leverage is most effective in renewal cycles where the buyer's estate is stable and the maintenance value is concentrated in support rather than in upgrades.
What documentation looks like
A credible alternative document is a one- to three-page summary that sets out four sections. The first section names the alternative and sizes the addressable scope (which SAP modules, which user populations, which integrations). The second section sets out the transition cost model, with cost ranges by year and a confidence interval. The third section sets out the operational risk register, naming the risks and the mitigations. The fourth section sets out the decision criteria and the decision owner.
The document is signed by the procurement category owner and routed through procurement governance. Routing is the procedural step that transforms an analyst's spreadsheet into an institutional document. SAP's account team will, in our experience, ask for evidence of routing in the negotiation, and the absence of evidence is the moment leverage collapses.
When leverage is theatrical
The most common form of theatrical leverage is the mention of an alternative without documentation. "We are evaluating Oracle" produces no concession. "We are talking to Workday" produces no concession. The mention is, in the SAP account team's reading, calibrated by the absence of the document. The team has seen the same mention many times, and the absence of a routed document is the signal that the mention is not load-bearing.
Theatrical leverage produces an unintended effect: it lowers the team's perception of the buyer's negotiating sophistication. The next concession is then calibrated lower, not higher. The most expensive thing a procurement function can do in a renewal negotiation is to use the language of leverage without the documentation that backs it.
The walk-away credibility test
The internal credibility test for an alternative document is whether the procurement function would, in the absence of any concession, actually act on it. The test is run inside the procurement organisation, not against SAP. If the procurement function would not act on the alternative even at the worst-case SAP renewal price, then the alternative is not credible, and the document should not be deployed.
This test is the part of the leverage program most procurement functions skip. The result is that documents are deployed that the team would not act on, the SAP account team detects the gap, and the leverage collapses. The discipline is to deploy only documents that pass the internal walk-away test.
The two-vendor rule
The most consistent leverage pattern across our portfolio is the two-vendor rule. The buyer maintains, at any time, a costed alternative for at least one significant SAP module. The alternative does not have to be deployed. It has to be maintained as a current document. Maintaining the document inside the SAM and procurement function is the precondition for credible leverage when the renewal cycle arrives.
The two-vendor rule is operationally inexpensive (a small team, a periodic refresh) and commercially significant (a discount tier across every renewal cycle). The utility case file documents a renewal where the two-vendor rule produced an Ariba Network fee rollback that would not have been available without the documented alternative.
The RISE conversation
In a RISE conversion conversation, the relevant competitive alternatives are different. The alternatives are: stay on-premise on the existing perpetual estate, move to a hyperscaler-managed S/4HANA on a bring-your-own-licence model, or move to a competitor cloud ERP. The buyer-side documentation has to address all three. The RISE tactics article sets out the comparison structure.
The indirect-access conversation
In an indirect-access conversation, competitive leverage takes a different form. The buyer's alternative is rebuilding the integration topology to remove the indirect-access trigger, often by moving the integrating system to a different data source or by rearchitecting the integration to avoid the document creation that produces the exposure. The alternative is technical rather than commercial, but it is a credible alternative when documented, and SAP will calibrate the indirect-access settlement against the credibility of the rebuild option. Our Indirect Access Survival Guide describes the rebuild patterns.
Competitive leverage works when the alternative is documented, costed, routed, and credible. It does not work as a mention. The discipline is procedural rather than persuasive.
If you are entering a renewal cycle without a current alternative document, the first work is the two-vendor rule. Our contract negotiation service sets out how we structure the alternatives documentation, and the SAP RISE topic page covers the RISE-specific alternative analysis.
— 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.