Memory

BATNA & ZOPA

Try it

Structured framework to analyze your alternatives and acceptable deal range before you commit

What it does

Applies BATNA (Best Alternative to a Negotiated Agreement) and ZOPA (Zone of Possible Agreement) analysis to any non-trivial negotiation. Computes your walk-away value, estimates the other side's floor, checks whether overlap exists, and outputs a structured markdown analysis. Two modes: Engine mode runs the full 5-step process on a concrete deal; Coach mode guides novices one question at a time with hard stops. Handles salary negotiation, term sheets, vendor contracts, M&A, and compute/AI contracts where FOMO pressure distorts judgment.

When to use it

  • Evaluating a job offer or salary package with multiple variables
  • Deciding whether to take a term sheet or raise from an AI investor
  • Negotiating a vendor or cloud compute contract under scarcity pressure
  • Assessing whether a deal can happen before investing negotiation effort

The skill document

BATNA & ZOPA

Overview

BATNA (Best Alternative to a Negotiated Agreement) is the value of your best fallback if no deal happens — the floor below which you walk away. A negotiator without a clear BATNA negotiates from fear; with one, from position.

ZOPA (Zone of Possible Agreement) is the overlap between what each side will accept. If it exists, a deal is possible; if not, the question is structural change — not harder negotiating.

Composes with anchoring, signaling-games, repeated-games-reputation, and prisoners-dilemma.

When to Use

  • Any non-trivial negotiation: term sheets, salary, partnership, M&A, vendor contracts, customer pricing
  • You feel pressure to take a deal that "feels bad" — usually a sign your BATNA is weak or not modeled
  • Assess whether a deal can happen before investing time in tactics
  • Raising in the 2024–2026 AI market (term sheets, SAFEs) or committing to a GPU-cloud / compute contract, where FOMO and "capacity is scarce" pressure obscure your real alternative

Not when: purely emotional/non-transactional disputes; cultures where direct BATNA discussion is taboo.

Coaching Novices (Adaptive Front Door)

  • Engine mode: user has a concrete deal → run The Process directly.
  • Coach mode: user is unfamiliar → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

  1. One-line: BATNA = your walk-away value; ZOPA = the range where both sides say yes.
  2. Check fit: relationship-only situations → point elsewhere.
  3. "What negotiation are you in right now?"

[WAIT — do not advance until user responds]

  1. One question at a time: What's your BATNA? What's theirs? Where's the overlap?

[WAIT — do not advance until user responds]

  1. Name the specific opening offer and walk-away point they've identified.

[WAIT — do not advance until user responds]

The Process

Step 1 — Compute your BATNA: specific alternative + dollar value + timeline + probability → risk-adjusted value. "Going elsewhere" is not a BATNA. Strengthen before negotiating (parallel processes, extended runway).

Step 2 — Set reservation & aspiration: Reservation > BATNA (with buffer). Opening offer > aspiration, but defensible.

Step 3 — Estimate their BATNA: Ask directly; research alternatives; observe behavior (patient = strong, pressured = weak). Their reservation caps your ceiling.

Step 4 — Find the ZOPA: Overlap of reservation prices. If none exists → structural move (add issues, extend time, find new counterparty). Not "negotiate harder."

Step 5 — Distribute within ZOPA: Open at your favorable boundary (anchoring). Make small concessions — don't split. Trade variables when single-issue stalls. Walk at reservation, not earlier or later.

Output: BATNA & ZOPA Analysis

# BATNA & ZOPA Analysis: 
## My side:  BATNA  | Reservation $__ | Aspiration $__ | Opening $__
## Their side: Est. BATNA <…> | Est. reservation $__
## ZOPA: $__ to $__ | Exists? yes/no
## Strategy: [if ZOPA] open at __; walk at __; concede via __
##            [if no ZOPA] structural move: __
## Falsifier: observation that would tell me my estimates are wrong: __

→ Method in Action: Fisher and Ury, 1981 — The Harvard Negotiation Project · Camp David Accords, 1978 → 2026 lens: An AI startup's term sheet & compute contract (2024–2026) — build your BATNA before you negotiate the raise.

Pack: BATNA & ZOPA Patterns

NegotiationYour BATNATheir BATNA
Term sheetOther investors / bridge / status quoOther pipeline deals
SalaryOther offers, current job, savings runwayNext candidate, leave role open
Vendor contractOther vendors, build in-house, deferOther customers, lower revenue
M&AContinue independent, alternative acquirerBuild in-house, acquire competitor

Applying It Well

  • Compute BATNA before any negotiation session — mid-session computation is slow and biased
  • Model their BATNA with the same rigor as your own — it sets your ceiling
  • Multi-issue deals: identify what each side values most and trade across variables

→ Primary sources: references/sources.md

Common Rationalizations

[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.

Fake moveReality
[D] "My BATNA is strong" without specificsWhere exactly, with what offer, by when? If you can't answer, BATNA is weak.
[D] No estimate of their BATNATheir BATNA caps your aspiration — without it you over-ask or under-ask.
[D] ZOPA non-existence = "they're being difficult"Sometimes no deal exists. Structural change, not harder negotiation.
[D] Splitting the differenceSignals you have room. Make small concessions instead.
[D] Walking at aspiration, not reservationWalking early leaves money on the table.
[D] Staying past reservation (sunk costs)Negotiation effort is irrelevant. If deal < BATNA, walk.
[D] Bluffing about BATNAIf discovered, credibility collapses.
→ Add [O] entries here after each real use — paste the actual failure patternWhat went wrong and why

Red Flags

  • "My BATNA is going elsewhere" without specifics — No estimate of their BATNA
  • Pressure to close before BATNA computation is done — ZOPA not explicitly checked
  • Reservation price not pre-committed before negotiating

Verification

  • BATNA: specific alternative, value, timeline, risk-adjusted
  • Reservation > BATNA (with buffer); opening > aspiration
  • Their BATNA estimated with reasoning; ZOPA checked
  • If no ZOPA: structural move identified
  • If ZOPA: opening, concession pattern, walk-point pre-committed

Part of deciqAI Knowledge Skills — 227 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/c/batna-zopa · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.

Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/batna-zopa.json

Questions people ask

What's the difference between BATNA and a walk-away point?
BATNA is your specific, risk-adjusted fallback alternative — with a dollar value, timeline, and probability. A walk-away point is a price threshold. The skill computes your BATNA first, then sets your reservation price above it with buffer, so you don't confuse the two.
What if there's no ZOPA — no overlap between what each side will accept?
The skill identifies this explicitly and redirects to structural moves: adding issues, extending timeline, or finding a new counterparty. It explicitly advises against trying to negotiate harder when the math doesn't work.
Does this work for multi-issue negotiations like partnership deals?
Yes. The process includes guidance on trading across variables when single-issue negotiations stall, and identifying which issues each side values most so you can redistribute value within the ZOPA.

Related skills

Diagnose whether a competitive situation is truly zero-sum before committing to a strategy.

by deciqai1 installs2 stars

Diagnoses when decisions are distorted by loss aversion and prospect theory — then re-tests them on explicit expected-value terms.

by deciqai1 installs3 stars

Diagnose why people know what to do but don't do it, then design a behavior-changing nudge without mandates or incentives.

by deciqai1 installs3 stars

Audit strategies and portfolios for hidden assumptions that break under extreme events.

by deciqai1 installs3 stars

Know whether you're qualified to make a decision before you make it

by deciqai1 installs3 stars

Make irreversible life decisions by projecting to 80 and naming which regret you'd rather live with.

by deciqai1 installs2 stars

More from deciqai

Browse all skills

Diagnose your organization's strategic phase and spot misaligned initiatives before they drain momentum.

by deciqai7 installs2 stars

When multiple explanations all fit the evidence, pick the one that assumes the least.

by deciqai5 installs2 stars

Identify catastrophic failure paths before you commit — and design your plan around eliminating them.

by deciqai4 installs2 stars

Trace decisions past the obvious effect to catch the consequences that reverse it.

by deciqai4 installs2 stars

A structured interview and analysis process that uncovers the actual job customers hire your product to do — and who they're really competing against.

by deciqai3 installs3 stars

Diagnose why learners are struggling and redesign instruction to stay within working memory limits.

by deciqai2 installs3 stars