BATNA: building your best alternative to a negotiated agreement.
The single most powerful concept in enterprise software negotiation is your BATNA. Without a credible alternative you are not negotiating — you are asking for mercy. This note sets out where negotiating leverage actually comes from, how to quantify it, how to signal it so vendors believe it, and the errors that quietly destroy it.
Your negotiating power is set by how attractive your walk-away option is, not by how well you argue. Most buyers arrive at renewal with no credible alternative and are duly ignored. A BATNA the vendor believes you would actually execute is worth more than any tactic — and in our engagements is the difference behind roughly 38% average savings on major renewals.
01 Key findings
Leverage comes from your alternative, not your argument. BATNA — Best Alternative to a Negotiated Agreement, from Fisher and Ury’s Getting to Yes — holds that power flows from how good your fallback is if the deal collapses. The better it is, the less you need this deal, and the more you can demand.
Most enterprise buyers have no real BATNA. They need the software to run operations, have no short-term substitute, and have made that dependence visible through years of integration. Then they attempt to negotiate. The outcomes are predictable.
A BATNA only counts once it is developed. Having an alternative in principle is worthless; the vendor must have reason to believe you might act on it. Migration assessments, competitor proposals and third-party maintenance quotes convert a concept into pressure.
Third-party maintenance is the highest-return, lowest-cost lever. A formal support quote from Rimini Street or Spinnaker Support is inexpensive and fast to produce, yet reliably reframes incumbent support-fee negotiations — support substitutes commonly cut those fees 40–60%.
Timing decides whether the BATNA lands. Revealed too early, the vendor discounts it; revealed too late, after you have signalled dependence, it has no effect. Build quietly, signal selectively, and make it specific only when you must.
02 Sources of leverage
For any major platform the realistic alternatives fall into a handful of categories. Each generates leverage differently, costs a different amount to make credible, and applies best in different conditions. Score them honestly — an alternative neither you nor the vendor believes is real provides no bargaining power at all.
| Source | What it is | How to make it credible | Leverage | Best when |
|---|---|---|---|---|
| Competitor bid | A named rival platform with a formal commercial proposal | Run an active procurement; obtain written pricing and terms | Highest | A genuine functional substitute exists |
| Status quo | Renew flat, freeze scope, or run the current version unchanged | Model the cost of doing nothing; remove growth the vendor assumed | Moderate | Roadmap and headcount are stable |
| Delay | Defer the purchase, expansion or upgrade past the vendor’s quarter | Decouple your timeline from the vendor’s fiscal calendar | Moderate | No hard compliance or renewal cliff |
| Open source / self-host | Replace licensed modules with open-source or in-house builds | Stand up a proof of concept on the alternative stack | Situational | Strong internal engineering capability |
| Third-party maintenance | Independent support (Rimini Street, Spinnaker) in place of the vendor’s | Obtain a formal support assessment and quote | High | Legacy, stable, heavily-customised estates |
03 The weak-BATNA trap
The most common and most expensive failure is mistaking a stated alternative for a developed one. Buyers tell the vendor they are “evaluating options” while doing nothing to make those options real. Vendor account teams have seen this a thousand times and price it accordingly — a vague threat costs them nothing to ignore, and they know it.
A BATNA you would not actually execute is not a BATNA — it is a bluff, and vendors are professionally equipped to call it. The credibility test is concrete: your legal and commercial team could genuinely execute the alternative within 6 to 12 months without catastrophic disruption, and you can hand the vendor specific evidence — a migration assessment, a competitor proposal with terms, a third-party maintenance quote. Absent that, silence would serve you better than an empty claim, because a called bluff teaches the vendor exactly how little leverage you hold.
04 Quantifying your BATNA
A BATNA is only useful once it carries a number. “We could move to a competitor” is rhetoric; “switching to the alternative costs $4.2M over 18 months and lands 22% below the renewal quote” is a negotiating position. Quantify the full switching cost — migration, retraining, dual-running, risk contingency — and set it against the incumbent’s proposal. The gap between the two is the ceiling on what the vendor can credibly charge before your alternative becomes the rational choice.
The same arithmetic runs in reverse for the vendor. Negotiation outcomes are set by the interplay of both parties’ alternatives, so estimate what losing you costs them: customer-concentration exposure, net revenue retention pressure, and quarterly targets all weaken a vendor’s BATNA. A local VAR with 20% of revenue in your account is in a very different position from a hyperscaler for whom you are 0.01%.
Weight your value to the specific team you face. If you are a reference logo, a target-vertical win or the proof case for a new product, the vendor’s BATNA is weaker and your leverage is correspondingly greater — even when your raw spend is modest.
05 Building your BATNA
Development is what separates a concept from a lever. Four activities, run in the 9 to 12 months before renewal, convert an alternative into something the vendor can verify and must therefore respect.
Migration assessment
A formal, vendor-neutral study of what moving to an alternative platform would cost, require and deliver. Conducted by a credible third party and captured in a documented finding the vendor cannot dismiss.
Proof of concept
An actual technical demonstration on the alternative, even for a functional subset. Vendors can and do verify through their own channels whether a PoC is genuinely under way.
Competitor engagement
Live commercial discussions with a named rival that produce a formal proposal. A competitor quote with real terms changes the dynamic the moment it exists.
Third-party maintenance
For legacy estates, a formal assessment from an independent support provider. Cheap, quick, and highly effective at reframing incumbent support-fee negotiations.
Not every alternative is viable for every platform. A 20-year, heavily-customised SAP ERP deployment has fewer credible options than a two-year-old Salesforce instance. Oracle buyers can develop AWS RDS or Azure SQL migration assessments, PostgreSQL evaluations and Rimini Street support; SAP buyers can weigh Oracle Fusion, Dynamics 365 or Infor plus third-party ECC support; Microsoft buyers can model Google Workspace, hyperscaler alternatives and selective E5-to-E3 downgrades. Match the lever to the estate.
06 Signalling it credibly
Framing and timing matter as much as the alternative itself. Build quietly in the 9 to 12 months before renewal; signal selectively in the 3 to 6 month window — a leader noting the organisation is “looking more broadly at platform strategy” registers without overcommitting. In the final 60 to 90 days, if terms are still unacceptable, make it specific: name the alternative, reference the proposal, provide a timeline.
Evidence-backed signal Credible
A specific counter-proposal accompanied by a real artefact — migration assessment, competitor quote or maintenance proposal. The vendor now runs a binary calculation: the cost of you leaving versus the cost of conceding. Your job is to make that maths favour you.
Empty threat Weaker
“We’re evaluating alternatives,” with nothing behind it. The account team discounts it, holds firm, and if you fold once, prices every future renewal knowing your threats are hollow.
07 Our recommendation
The most powerful BATNA and the most costly to make credible. Reserve it for strategic platforms where a genuine substitute exists and the spend justifies a real migration assessment and competitor process.
The default first move for legacy, stable estates. A formal support quote is inexpensive, quick, and reliably compresses incumbent support fees 40–60% without touching the platform.
Move specific workloads or user populations while trimming incumbent commitment. Often more achievable than a full switch and still enough to reset the commercial conversation.
08 Deployment sequencing
Sequence the programme so the BATNA is built before it is needed and revealed only when it will bite. Build quietly, signal selectively, execute if called — and be genuinely willing to execute, because that willingness is the ultimate source of the leverage. Vendors who call a bluff and find it was not one typically return with materially improved terms once a migration is visibly under way.
Enter your next renewal with a real alternative
Our negotiation practice builds credible BATNAs — migration assessments, competitor proposals and third-party maintenance options — and runs the deal, in weeks not months.
The Licensing Edge
Weekly vendor intelligence, negotiation tactics and BATNA strategies for enterprise IT leaders. 3,000+ subscribers.