What BATNA Is — and Why It Changes Everything
BATNA is a concept from the Harvard Negotiation Project, introduced in Roger Fisher and William Ury's seminal work "Getting to Yes." It defines your best course of action if the current negotiation fails to produce an acceptable agreement. In enterprise software negotiations, your BATNA is typically the best alternative vendor, platform, or approach you could realistically deploy if you walked away from the current vendor.
BATNA matters because it defines your power position in a negotiation. A strong BATNA — a credible alternative that you could actually execute — means the vendor must compete for your business. A weak BATNA — no realistic alternative, high switching cost, deep integration dependency — means the vendor knows you will ultimately accept their terms. This is why vendors invest so heavily in switching cost creation: they are building your weak BATNA into their product architecture.
Understanding and improving your BATNA position is part of the core preparation framework in our IT Contract Negotiation Strategy Handbook. This guide goes deeper into the mechanics of BATNA development and application for enterprise software specifically.
Free Guide
IT Vendor Contract Clauses Checklist
22 must-have contract clauses for enterprise software deals — covering pricing caps, audit rights, and exit provisions.
The BATNA Principle: You should never enter a significant negotiation without knowing your BATNA. And you should never assume your BATNA is worse than it actually is. Most enterprises systematically underestimate both their alternatives and the feasibility of exercising them — which means they negotiate with weaker leverage than they actually have.
BATNA vs. Reservation Point vs. Target
Three distinct concepts govern negotiation position. Conflating them is a common mistake that weakens enterprise buyers' positions.
Your BATNA is what you do if negotiations fail — your outside option. It is not a price or a set of terms; it is an alternative course of action. Your reservation point (sometimes called the walk-away price) is the minimum acceptable terms within the current negotiation — the point at which you are indifferent between accepting the deal and executing your BATNA. Your target position is the optimistic but realistic outcome you aim to achieve. In negotiation, your target should be ambitious, your reservation point should be based on your BATNA value, and your BATNA should be as strong as you can make it before negotiations begin.
The relationship between BATNA and reservation point is direct: a better BATNA raises your reservation point, which means you can walk away from proposals that would previously have been acceptable. This is why BATNA improvement is essentially equivalent to negotiation leverage improvement — strengthening your BATNA raises the floor of what you will accept.
Stay Ahead of Vendors
Get Negotiation Intel in Your Inbox
Monthly briefings on vendor pricing changes, audit trends, and contract tactics. Unsubscribe any time.
No spam. No vendor affiliations. Buyer-side only.
Assessing Your Current BATNA Strength
Before building a stronger BATNA, you need an honest assessment of your current position. The following matrix illustrates the range of enterprise software BATNA positions.
Multiple credible alternatives
You have conducted genuine technical evaluations of alternative vendors or approaches. The alternatives are operationally viable within your infrastructure and budget. Migration timelines are understood and acceptable. The vendor knows you have done this work.
One credible alternative with constraints
A viable alternative exists but requires meaningful migration effort, timeline, or investment. The cost of switching is understood but not prohibitive. The alternative has been evaluated at a technical level if not fully proven. The vendor is aware you are evaluating alternatives.
Theoretical alternative, not validated
Alternatives exist in theory but have not been evaluated. Migration timelines and costs are unknown. There is significant organisational resistance to switching. The vendor knows the switching cost is high and believes your alternative is not real.
Complete dependency
No credible alternative exists within any reasonable commercial or operational timeline. Deep integration, regulatory requirement, or technical dependency eliminates realistic switching options. You will accept the vendor's terms because there is no viable alternative.
Most enterprises are in the "weak BATNA" or "moderate BATNA" position for their major software vendors — not because alternatives do not exist, but because they have not invested in validating them. This is the gap that BATNA development closes.
Building a Strong BATNA: The Five-Step Process
BATNA development is not a passive activity — it requires deliberate investment. The following process transforms a theoretical alternative into a credible negotiation position.
Identify Your Alternatives
For every major vendor relationship, identify all realistic alternatives — other vendors, in-house development, open-source alternatives, cloud-native replacements, or reduced-scope deployments. At this stage, cast a wide net. A SAP alternative might include Oracle, Workday, Microsoft Dynamics, or a best-of-breed SaaS combination. A VMware alternative might include Nutanix, Azure Stack HCI, Hyper-V, or KVM. Do not pre-filter by perceived feasibility — that comes in the next step.
Evaluate Technical Feasibility
Conduct a genuine technical assessment of the most promising alternatives. This does not require a full migration proof-of-concept — a structured RFI process, vendor briefings, reference conversations with comparable enterprises, and an architect-level capability assessment is sufficient to understand whether the alternative is technically viable for your use case. The output should be a documented feasibility assessment, not a vague opinion.
Cost the Transition
Understand the total cost of executing your BATNA — migration effort, professional services, staff training, productivity impact, dual-running costs, and licence or subscription costs of the alternative. This produces your BATNA value: the total cost you would incur by executing the alternative. This number directly informs your reservation point — you should not accept a deal that costs more than your BATNA value over the contract term.
Make the Evaluation Visible to the Vendor
A BATNA that the vendor does not know about provides no negotiation leverage. The commercial impact of your alternative evaluation comes partly from the vendor's awareness that you are seriously evaluating it. You do not need to disclose which alternative or what you found — simply confirming that you are actively evaluating alternatives and have engaged other vendors changes the commercial dynamic. Vendors track competitive activity in their accounts; being in that pipeline has commercial consequences for how they price your renewal.
Maintain and Update Your BATNA
BATNA is not a one-time exercise — it decays as technology and markets evolve. An alternative you evaluated two years ago may have improved materially (Nutanix, Azure Stack HCI, and open-source alternatives have all strengthened significantly in recent years). Maintaining an updated view of your alternatives keeps your negotiating position current and prevents vendors from assuming your BATNA has weakened without testing.
BATNA Development by Major Vendor
The specific alternatives and their credibility vary substantially by vendor. Here is a summary of the BATNA landscape for the major enterprise software categories.
Oracle BATNA
Oracle's switching costs are among the highest in enterprise software, particularly for Oracle Database, which is deeply embedded in application architectures. However, BATNA options have strengthened materially: open-source alternatives (PostgreSQL, MySQL, Aurora) have enterprise-grade capabilities for many workloads; cloud-native databases (Azure SQL, BigQuery, Snowflake) provide alternatives for specific use cases; and Microsoft SQL Server and SAP HANA are credible alternatives for the database tier. For Java licensing specifically, OpenJDK distributions from Eclipse Adoptium, Amazon Corretto, and Azul provide genuine alternatives to Oracle Java SE. See our Oracle negotiation guide for vendor-specific BATNA development.
Microsoft BATNA
Microsoft's BATNA landscape is dominated by Google Workspace for productivity and collaboration — a genuinely credible alternative for most organisations, though migration complexity is real. For Azure infrastructure, AWS and GCP provide competitive alternatives. The M365 vs. Google Workspace BATNA is explored in our Microsoft vs. Google Workspace comparison. Hybrid strategies — maintaining Microsoft for some workloads while deploying Google or alternatives for others — create partial BATNA that still influences Microsoft's commercial posture.
SAP BATNA
SAP ERP has traditionally been regarded as having weak BATNA due to deep integration. This is changing: Oracle Fusion, Microsoft Dynamics 365, and Workday (for HCM/Finance) are credible alternatives for organisations with sufficient migration runway. The SAP RISE migration pressure itself creates BATNA opportunity — enterprises evaluating cloud alternatives to RISE (Azure SAP, AWS SAP, third-party SAP hosting) can use this as leverage in RISE commercial negotiations. See our RISE negotiation guide.
Salesforce BATNA
Salesforce BATNA is stronger than many enterprises realise. Microsoft Dynamics 365 and HubSpot are credible CRM alternatives with significant market penetration. The Salesforce vs. alternatives comparison provides a cost-based analysis. For Salesforce shelfware — unused licences — the BATNA is reduction or partial replacement of specific modules, not necessarily full platform migration.
VMware BATNA
VMware BATNA has strengthened substantially post-Broadcom acquisition, as the cost increase has motivated genuine alternative evaluation across the industry. Nutanix, Azure Stack HCI, and open-source KVM are all credible for specific segments of VMware estate. Our VMware Alternatives guide provides a detailed comparison. The partial migration BATNA — moving non-critical workloads to alternatives and retaining VMware for production security workloads — is particularly viable and commercially powerful.
BATNA Caveat: Do not claim a BATNA you have not genuinely evaluated. Experienced vendor negotiators test BATNA claims with specificity: "Which alternative are you evaluating? What's your timeline? Who is the decision-maker?" A BATNA claim that collapses under questioning does more damage than no BATNA claim at all — it reveals that you have not done the preparation work and that your walk-away threat is not credible.
Strategically Using Your BATNA in Negotiations
Knowing your BATNA is necessary but not sufficient — using it effectively in the negotiation requires strategic judgment.
When to Reveal Your BATNA
You should not reveal your full BATNA or its value in early negotiation stages. Instead, signal that alternatives exist without specifying which ones or how advanced your evaluation is. "We are actively evaluating alternatives" and "we have engaged with other vendors at a technical level" convey the existence of a BATNA without revealing its strength. More specific disclosure — "we have a Nutanix POC running" — is appropriate later in negotiations when maximum leverage is needed.
When Not to Use BATNA as a Threat
BATNA threats that you do not intend to execute are dangerous. Vendors test threats — "if that's your position, let's pause negotiations and you can execute your alternative" is a standard counter to empty BATNA claims. Only use your BATNA as an explicit threat if you are genuinely prepared to execute it, or if your BATNA is strong enough that the vendor knows it is real. Empty threats damage credibility and weaken your position.
When to Actually Execute Your BATNA
The purpose of BATNA development is not to avoid ever switching vendors — it is to negotiate from strength. There are scenarios where the right outcome is to execute your BATNA: when the vendor's terms are genuinely worse than your alternative, when the vendor calls your bluff and will not improve their commercial position, or when the relationship has broken down beyond repair. Having a credible BATNA means that walking away is a genuinely viable outcome — not the outcome you want, but one you can execute without catastrophic business impact.
Improving Your BATNA Before the Next Negotiation
The most important BATNA insight for enterprise IT organisations is that BATNA improvement is a continuous activity, not a pre-renewal preparation exercise. The time to start building BATNA for a major vendor renewal is 18–24 months before the renewal date — not 90 days before, when you have insufficient time to conduct genuine alternative evaluation.
Treat BATNA development as a standing agenda item in your vendor management programme. For each major vendor: maintain awareness of the competitive landscape, conduct annual feasibility assessments of primary alternatives, refresh migration cost estimates as technology evolves, and ensure the vendor's account team is aware that alternatives are being tracked. This continuous BATNA programme is the foundation of consistent negotiation performance across your software portfolio.
IT Negotiations supports BATNA development as part of our vendor management advisory service and as a standalone preparatory engagement for major renewal negotiations. The free consultation includes an initial assessment of your BATNA position across your major vendor relationships.
Build the Leverage to Negotiate on Your Terms
A strong BATNA changes every negotiation. We help enterprises build credible alternatives, cost the transition, and use that leverage to achieve consistently better commercial outcomes.
Free Consultation Download Negotiation Playbook