A credible BATNA is the single largest determinant of SAP renewal price. The Admodum read on the four BATNA classes (third-party support, deferred S/4 conversion, partial RISE adoption, lift-and-shift to a competing core), the timing discipline and the publisher-side response.
BATNA is the best alternative to a negotiated agreement: the position the buyer can credibly walk to if the renewal terms do not move. The BATNA is not the negotiating position; it is the position outside the negotiation that gives the negotiating position its weight. A credible BATNA shifts the publisher-side default outcome away from the publisher's preferred renewal-price level; a non-credible BATNA does not shift the default outcome and the renewal closes at the publisher's preferred level.
The principal mistake is to confuse the BATNA with the threat: a named alternative without architecture, cost model and stakeholder buy-in is a threat, not a BATNA. The publisher reads the architecture, the cost model and the stakeholder buy-in; the threat alone does not move the renewal price. The wider SAP renewal cycle spoke reads the renewal-side process inside which the BATNA operates.
The third-party maintenance support BATNA is the most-used SAP renewal-time BATNA. Rimini Street and Spinnaker Support are the two principal third-party providers. The construct is: the buyer discontinues SAP maintenance at the renewal anniversary, the buyer retains the perpetual on-prem licences (the licences do not return to the publisher), the buyer transitions to the third-party provider for tax-and-regulatory updates, security patches and incident support. The economics are typically forty to sixty percent below the SAP maintenance baseline; the operational risk is the loss of access to SAP-issued updates (SAP Notes), new releases and the SAP support portal.
The BATNA is most credible on the ECC estate (the on-prem-perpetual licence base is the position-of-record). It is less credible on the RISE estate (the subscription does not retain a perpetual licence position). The wider SAP third-party support spoke reads the third-party-support class in depth.
The deferred S/4HANA conversion BATNA is the position that the buyer continues to operate ECC through and beyond the published end-of-mainstream date. The publisher has extended ECC mainstream maintenance to 2027 and offers extended maintenance to 2030 (with the corresponding extended-maintenance fee), so the deferred-conversion position is technically supportable into the early 2030s on the publisher's own track. The publisher would prefer the conversion to RISE or to the S/4HANA private edition at the published anniversary; the buyer's BATNA is the deferred position.
The deferred-conversion BATNA is credible when the buyer has the operational and stakeholder readiness to operate ECC for the additional period. It interacts directly with the third-party-support class: a buyer that defers the S/4HANA conversion may also discontinue SAP maintenance and transition to third-party support. The wider ECC end of mainstream spoke reads the publisher's mainstream-maintenance timeline; the wider S/4HANA conversion planning spoke reads the conversion-side architecture.
The partial RISE adoption BATNA is the position that the buyer adopts RISE on a non-core workload (a regional subsidiary, a divestiture entity, a project-based business unit) while retaining ECC or S/4HANA on-prem on the core workload. The construct gives the publisher the RISE-adoption signal that the publisher's executive narrative requires while denying the publisher the all-in RISE conversion at the contracted price level. The partial-RISE position becomes the buyer's leverage to retain the on-prem licensing rights on the core workload (in particular, the perpetual-licence retention, the third-party-support optionality, and the S/4HANA private-edition path-not-RISE optionality).
The partial-RISE BATNA is most credible when the architecture is specific (the named non-core entity, the named workload scope, the published transition timeline). The wider RISE versus on-prem spoke reads the RISE-on-prem disposition framework.
The lift-and-shift BATNA is the position that the buyer migrates the digital-core workload to a competing publisher: Oracle Fusion ERP, Workday Financial Management, Microsoft Dynamics 365 Finance and Supply Chain, or in narrower-scope cases NetSuite or Microsoft Business Central. The lift-and-shift is the highest-leverage BATNA class but also the longest-timeline (the architecture, the migration cost model and the executive-stakeholder buy-in typically run twenty-four to thirty-six months ahead of any actual cutover). The publisher reads the seriousness of the lift-and-shift work against the visible signals: the named competing-publisher selection, the named systems-integrator engagement, the published programme governance and the named executive sponsor.
A lift-and-shift BATNA that is visible at the start of the renewal-price discussion is too late. The BATNA work runs eighteen to thirty-six months ahead of the renewal anniversary. The competing-publisher comparators sit in the wider Oracle, Workday and Microsoft practices on the site (Oracle, Workday, Microsoft); the publisher-side reading is the same across the three.
At the close of the renewal, the buyer holds either the BATNA outcome (the alternative position has executed and the SAP renewal has not closed at the publisher's preferred level) or the BATNA-improved renewal (the SAP renewal has closed at a price level shifted away from the publisher's preferred level by the BATNA pressure). The BATNA-improved renewal is the more common outcome; the BATNA-executed outcome is the lower-probability outcome and is, in practice, the disposition of last resort.
The wider engagement sits in the SAP practice; the aggregated reading list sits in the SAP knowledge hub; active renewal moments route to the Renewal Programme; active audit moments route to Audit Defence.
A senior Admodum SAP advisor will read your BATNA-class candidates, your architecture readiness, your migration cost model and your executive-stakeholder buy-in on a private call. Active renewal moments route to the Renewal Programme.