A negotiated agreement is only as good as the alternative behind it. In enterprise software, your BATNA — the path you can credibly walk to if the deal collapses — is the single largest determinant of price. Across 340+ engagements, the deals that closed 25–50% below initial proposals had one thing in common: a BATNA the vendor took seriously.
Enterprise software pricing is not set by cost-plus or market reference; it is set by what the vendor believes you will pay. The vendor's estimate of your willingness-to-pay is anchored on one variable: their estimate of your BATNA. A buyer with no credible alternative is offered list-minus-token discount. A buyer with a board-approved alternative proposal in hand is offered the floor.
In our experience across 340+ engagements, the deals that closed 25–50% below initial proposals had a BATNA the vendor took seriously: a competing proposal, a documented migration plan, a budget line for the alternative, and an executive sponsor willing to authorise the walk. The deals that closed within 10% of initial proposals had a BATNA the vendor judged to be theoretical.
Modern account teams have telemetry: usage logs, deployment depth, integration count, switching cost models, and historical churn data on similar accounts. They calculate the probability of your walking with surprising accuracy. A BATNA constructed on paper but not in operations will be visible as such.
Three tests. First, an alternative vendor or solution that has been formally evaluated, not just shortlisted. Second, an internal owner authorised to execute the switch. Third, a budget and timeline approved at the right level. Without all three, the BATNA is a bluff.
We run BATNA development sprints in 8–12 weeks aligned to your renewal window.
BATNA construction starts 9–12 months before the renewal window. Compressed timelines produce theatre, not leverage. The work splits into four streams that run in parallel.
Full migration is rarely credible for entrenched platforms — Oracle databases, Microsoft 365, SAP ECC. The stronger BATNA is partial divestiture: a 30–40% footprint reduction over 18–24 months by migrating specific workloads. This threatens the account team's quota without requiring a full replatform commitment. Partial divestiture is the most under-used BATNA in enterprise software. Either way, the alternative only converts to dollars through disciplined software contract negotiation at the table.
Includes the BATNA construction template and the partial-divestiture framework.
The objective is to make the alternative visible enough to be believed, but not so visible that the vendor can match exactly. Three principles govern the signalling.
Confirm that an alternative vendor has been engaged. Decline to disclose the proposal value. The asymmetry — the vendor must price against an unknown — is the source of leverage. Disclose the value and you give them the target.
Frame the alternative as a procurement process the board has authorised, not a threat. "We have been instructed to evaluate alternatives before this renewal" lands differently than "we will switch if you don't move on price." The first is professional; the second is theatre.
The signal is more credible when it comes from procurement or finance, not from the IT team that owns the platform. The IT team has switching cost in its career; finance does not. Vendors read this difference accurately.
Our team runs the signalling cadence in tandem with your internal procurement.
Three failure modes account for most BATNA collapse in our experience.
The alternative is identified two months before renewal. There is no time to evaluate, mobilise, or evidence. The vendor knows the timeline and prices accordingly.
The BATNA depends on one champion — typically the procurement lead. That person's departure, illness, or political weakness collapses the alternative. Multi-threaded BATNAs survive personnel changes.
The TCO comparison ignores switching cost, training, integration rebuild, and run-rate inefficiency during transition. When the comparison is challenged, the alternative collapses. Honest switching-cost modelling is what makes the BATNA defensible internally — which is what makes it credible externally.
Our team has built credible BATNAs across 340+ engagements. We deliver the alternative the vendor takes seriously.
Weekly compliance intelligence for IT leaders.