What makes BATNA & ZOPA notable?

999 downloads. Trust evidence available

How should BATNA & ZOPA be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

BATNA & ZOPA

Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-shee... Skill: BATNA & ZOPA Owner: deciqai Summary: Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-shee... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T17:52:27.725Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/batna-zopa.json) v1.0.4 | 2026-07-14T06:44:01.889Z | auto - A

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

999

Updated

Oct 11, 2026

Version

1.0.5

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 999 downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 999 downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.5release · observed Jul 16, 2026
Handshake status: UNKNOWNsecurity

What changed

Newest first. Only changes that point at a source are listed.

Release 1.0.5release
Description tail link + agents machine-readable metadata line (deciqai.com/s/batna-zopa.json)
Observed Jul 16, 2026 · source

Install and run

Setup complexity: low.

clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:batna-zopa

Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-deciqai-batna-zopa/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

120,068 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: batna-zopa
description: "Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-sheet/vendor/M&A negotiation where stakes are non-trivial. Do NOT activate when: the situation is a purely emotional relationship dispute with no transactional dimension; cultural context makes explicit BATNA discussion taboo. More: deciqai.com/c/batna-zopa"
---

# 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]**
4. One question at a time: What's your BATNA? What's theirs? Where's the overlap?
> **[WAIT — do not advance until user responds]**
5. 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

_meta.json

{
  "ownerId": "kn754b8sk22s8c6gjxt02bftbn88q7ye",
  "slug": "batna-zopa",
  "version": "1.0.5",
  "publishedAt": 1784224347725
}

references/sources.md

# Sources — batna-zopa

> *Primary sources for the [batna-zopa](../SKILL.md) skill.*

- Fisher, R., & Ury, W. (1981/1991). *Getting to Yes: Negotiating Agreement Without Giving In* (2nd ed.). Penguin. ISBN 978-0140157352. The founding text; BATNA defined on pp. 99-108.
- Lax, D. A., & Sebenius, J. K. (1986). *The Manager as Negotiator.* Free Press. The first systematic extension into business negotiation. ISBN 978-0029187706.
- Quandt, W. B. (1986). *Camp David: Peacemaking and Politics.* Brookings Institution. The definitive scholarly account of the 1978 Camp David negotiations — the framework's canonical diplomatic case.
- Mnookin, R. H. (2000). *Beyond Winning: Negotiating to Create Value in Deals and Disputes.* Harvard University Press. The framework applied to legal and business disputes. ISBN 978-0674008830.
- Malhotra, D., & Bazerman, M. (2007). *Negotiation Genius: How to Overcome Obstacles and Achieve Brilliant Results at the Bargaining Table and Beyond.* Bantam. Modern operational synthesis. ISBN 978-0553804881.
- Harvard Program on Negotiation: https://www.pon.harvard.edu/ — continues active research and case-study development.
- Feld, B., & Mendelson, J. (2019). *Venture Deals: Be Smarter Than Your Lawyer and Venture Capitalist* (4th ed.). Wiley. Standard reference for term-sheet mechanics (liquidation preference, option pool, pro-rata, board control) that make up the multi-issue ZOPA in a fundraising negotiation — used in the 2024–2026 AI term-sheet example. (Round sizes and valuations vary by deal and period; not asserted as specific figures.)
- Lax, D. A., & Sebenius, J. K. (1986). *The Manager as Negotiator.* Free Press. https://www.pon.harvard.edu — the value-creation / multi-issue "structural move" applied when no single-issue (price-only) ZOPA exists, e.g. widening a valuation stalemate into a trade across preference, pool, and pro-rata.

examples/ai-startup-term-sheet-and-compute-negotiation-2024-2026.md

# Method in Action: An AI Startup's Term Sheet & Compute Contract (2024–2026)

> *Example for the [batna-zopa](../SKILL.md) skill.*

The 2024–2026 AI funding market was bifurcated: a handful of "hot" AI startups fielded competing term sheets at rich valuations, while most founders negotiated from a weaker spot than the headlines suggested. BATNA/ZOPA cuts through the FOMO in both directions. This walks the five steps through a Series A raise, then a shorter compute-contract case — the two negotiations that most often decide an AI startup's fate. Figures are illustrative; the discipline is the point.

### Case 1 — a Series A term sheet

**Step 1 — Compute your BATNA.** A founder feeling flattered by one interested fund has no BATNA — "they might pass" is not an alternative. The real BATNA is concrete: *a second term sheet at $X*, or *18 months of runway at current burn that lets us raise later from a stronger revenue position*, each with a dollar value, timeline, and probability. The single highest-leverage move in the whole raise happens *before* any negotiation: run a **parallel process** so more than one fund is live at once, and extend runway so "no deal now" is survivable. A founder with 3 months of cash and one term sheet has, in effect, no BATNA — and the term sheet's terms will show it.

**Step 2 — Set reservation & aspiration.** Reservation is the worst valuation/terms you'd still sign versus your BATNA — and terms are not just the number: liquidation preference, option-pool shuffle, board control, and pro-rata can swamp headline valuation. Aspiration is a defensible high anchor grounded in comparable 2024–2026 rounds, not a wish. Open above aspiration but justifiable.

**Step 3 — Estimate their BATNA.** The VC's BATNA is *their next-best deal* plus the cost of missing a category winner. In a hot AI sub-sector, fund FOMO is real leverage *for the founder* — a fund that has already missed one breakout is negotiating against its own regret. Read behavior per the skill: a patient investor is signalling a strong BATNA (they have other deals); a fund pushing to sign before you can run your process is signalling a weak one (or is managing *your* BATNA down). Their reservation — the most dilution/price they'll accept — caps what you can get.

**Step 4 — Find the ZOPA.** Overlap of the two reservation prices. If a fund's ceiling is below your floor, negotiating "harder" is wasted motion — make a **structural move** instead: add issues to trade (a smaller round at a better price + more pro-rata; a SAFE bridge to reach a metric that resets comps; a different lead). No ZOPA on valuation often has a ZOPA once you widen past the single number.

**Step 5 — Distribute within the ZOPA.** Open at your favorable, defensible boundary (this composes with [anchoring](../anchoring/SKILL.md)). Concede in small steps; never "split the difference" reflexively. Trade variables — give on board observer seats to hold valuation, or accept a standard 1x non-participat

examples/camp-david-accords-sinai-1978.md

# Method in Action: The Camp David Accords — Egypt, Israel, and the Sinai (1978)

> *Example for the [batna-zopa](../SKILL.md) skill.*

The thirteen-day Camp David summit (September 5–17, 1978) between Egypt's Anwar Sadat and Israel's Menachem Begin, mediated by US President Jimmy Carter, is the canonical diplomatic demonstration of the framework. Fisher and Ury themselves use the Sinai dispute as the flagship example of "focus on interests, not positions" in *Getting to Yes*, and the summit's mediation process as the leading real-world application of the one-text procedure.

**The BATNAs.** Israel had occupied the Sinai Peninsula since the 1967 war. For both sides, no-deal meant continued belligerency:

- Egypt's fallback: keep bearing the economic and political cost of a lost peninsula, plus the standing risk of another war — the 1973 war was only five years past.
- Israel's fallback: keep bearing the cost of occupation, permanent mobilization on the southern front, and mounting international isolation.

Both BATNAs were bad, specific, and mutually understood — which is precisely why both leaders accepted Carter's invitation. Weak BATNAs on both sides do not guarantee a deal, but they widen the potential ZOPA.

**Reservation prices — and an apparent empty ZOPA.** On the single issue as first framed — *where to draw the line in the Sinai* — the reservation prices did not overlap. Egypt's stated position: every inch of the Sinai returns to full Egyptian sovereignty. Israel's stated position: retain part of the Sinai — settlements, airfields, strategic depth — as a security buffer. No line on the map satisfied both reservations. On positions alone, the ZOPA was empty, and years of positional bargaining had confirmed it.

**The structural move.** The mediating team did not "negotiate harder." It unbundled positions into interests:

- Egypt's underlying interest was *sovereignty* — a matter of national dignity after centuries of foreign control. It did not need tanks on the border to have its flag on the territory.
- Israel's underlying interest was *security* — no Egyptian armor massed within striking distance. It did not need to own the land to keep the buffer.

Those interests were compatible even though the positions were not. The solution: the entire Sinai returns to Egyptian sovereignty, while large zones of it are demilitarized, with monitoring arrangements. Egypt got the flag; Israel got the buffer. Adding issues — phased withdrawal timelines, diplomatic normalization, evacuation of Israeli settlements and airfields, and US assistance to both parties — further expanded the deal space. This is Step 4's prescription executed at state scale: when no ZOPA exists, change the structure (reframe the issue, add variables), not the pressure.

**Distributing within the new ZOPA.** Carter's team used the one-text procedure: the mediator drafts a single negotiating text, each side criticizes it, and the mediator revises through repeated rounds — rather

Github ReposUpdated 3d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.

MCPOPENCLAW

Github ReposUpdated 7mo agoRank 70

CopilotKit

The Frontend for Agents & Generative UI. React + Angular