What a BATNA Is — and Why It Sets Your Floor
Your BATNA in IT negotiations — your Best Alternative To a Negotiated Agreement — is the course of action you will take if the deal on the table collapses. It is the single most important number in any negotiation, because it sets the floor beneath which no agreement is worth signing. A buyer with a strong BATNA can hold firm or walk away; a buyer without one is, in effect, negotiating against themselves and will accept whatever the vendor decides to offer.
The commercial value is measurable. In cloud and software engagements, buyers who bring a documented competitive alternative to the table consistently achieve 8–15% better pricing than comparable buyers negotiating against list price alone — and they capture that improvement even when they ultimately renew with the incumbent. The alternative does not have to be exercised to be worth money. It only has to be credible. This is why the BATNA underpins every other technique in our IT negotiation techniques handbook: anchoring, timing and concession-trading all rest on a floor you are genuinely prepared to defend.
Three Credible Alternatives You Can Build
A BATNA is rarely a single dramatic threat to rip out a platform. In practice it is one of three artefacts, each of which can be assembled inside the standard twelve-month renewal runway.
A documented migration cost analysis. What would it actually cost — in licences, services, retraining and elapsed time — to move to a named competitor? A credible analysis quantifies the switching cost rather than asserting it, and it tends to surprise both sides: switching is often cheaper than the incumbent assumes and dearer than the buyer fears. Either way, the number reframes the conversation around value rather than loyalty.
A competing proposal with real pricing. Run a genuine parallel commercial conversation with at least one alternative supplier and obtain written pricing. A real quote is far harder for the incumbent to dismiss than a hypothetical one, and it gives you a precise figure to anchor against — the mechanics of which are covered in our guide to anchoring in software negotiations.
A partial-workload move. Where a full migration is impractical, moving a single workload, region or business unit demonstrates capability rather than merely claiming it. A vendor that has watched you migrate 10% of an estate treats your leverage very differently from one hearing a threat. This is also where the renewal-versus-replacement decision becomes a live lever rather than a rhetorical one.
| BATNA type | Effort to build | Credibility to vendor | Typical pricing impact |
|---|---|---|---|
| Verbal threat to switch | None | Very low | Negligible |
| Migration cost analysis | 2–4 weeks | Moderate | 5–10% improvement |
| Competing written proposal | 4–8 weeks | High | 8–15% improvement |
| Executed partial-workload move | 1–3 months | Very high | 15%+ and structural concessions |
Making the Alternative Believable
The vendor's account team will test whether your alternative is real. They have seen hundreds of bluffs and are trained to call them. AWS, to take one example, will not believe a threat to move to Azure or Google Cloud unless you demonstrate it — and the same scepticism applies across every major vendor. Believability therefore rests on three things: documentation that withstands scrutiny, a sponsor senior enough to make the alternative plausible, and a timeline that allows the switch to actually happen.
Timing is the quiet enabler here. A BATNA developed three months before renewal is rarely credible, because there is no longer time to execute it; one developed nine to twelve months out is. This is why we treat alternative development as a discrete phase of the negotiation timeline, and why a structured competitive bidding process is the most reliable way to manufacture a believable alternative rather than a hopeful one.
Credibility also depends on internal alignment. If finance privately signals that the budget is already approved at the incumbent’s renewal figure, the alternative evaporates the moment the vendor senses it. A BATNA is only as strong as the weakest internally-briefed stakeholder, which is why the alternative and the internal mandate to use it must be developed together rather than in sequence.
A BATNA does not require the intention to switch. It requires the vendor to believe you credibly could. That belief is built from documentation and time — not from bravado in the room.
Presenting a BATNA Without Bluffing
How you present the alternative matters as much as having it. The objective is not to threaten but to inform: you are explaining, calmly, that you have a viable path that does not involve this vendor, and inviting them to compete for your business. Introduce the alternative after the vendor's first proposal, not before — deploying it too early lets them dismiss it as posturing, while deploying it as a considered response to an unsatisfactory offer makes it a credible escalation.
Keep the presentation factual and written. A short, evidenced summary — here is the competing quote, here is the migration cost, here is the timeline — is more powerful than any verbal ultimatum, and it sits naturally alongside the written commercial position recommended throughout our work on multi-party deals. For organisations managing several vendors at once, the cross-portfolio version of this discipline is set out in the Multi-Vendor Strategy white paper.
The Most Common BATNA Mistakes
Three errors recur. The first is the empty threat: claiming an alternative that does not exist, which collapses the moment the vendor probes it and costs you credibility for the rest of the negotiation. The second is developing the BATNA too late, leaving no time to execute and therefore no real leverage. The third is over-disclosure — revealing every detail of your alternative, which lets the vendor address each point individually and defuse the pressure rather than respond to the whole.
A fourth, subtler error is confusing a strong BATNA with a hostile posture. The point of an alternative is leverage, not aggression: the most effective negotiators present their alternative quietly and let the vendor draw the obvious conclusion. A buyer who has clearly done the work to build a real option rarely needs to raise their voice — the documentation does the talking, and the account team escalates internally because they can see the deal is genuinely at risk.
Used well, a BATNA quietly reshapes the entire negotiation: it converts a one-sided renewal into a genuine competition for your business, and it gives you the confidence to anchor precisely and trade concessions rather than surrender them. To build a credible alternative for a specific upcoming renewal — or to have us run the competitive process on your behalf — explore our software licensing negotiation practice or request a confidential briefing.