Skip to content

borghei/Claude-Skills / legal/contract-review

contract-review

Verified

Contract review assistant analyzing agreements against playbooks. GREEN/YELLOW/RED severity. Use when reviewing vendor contracts, SaaS agreements, service agreements, or generating redline suggestions.

references/negotiation_playbook.md

View on GitHub
# Negotiation Playbook

Strategic framework for contract negotiation. Organizes redline priorities into tiers, provides trading strategies, and documents common pitfalls with resolution approaches.

---

## Table of Contents

- [Priority Tier Framework](#priority-tier-framework)
- [Tier 1: Deal-Breakers](#tier-1-deal-breakers)
- [Tier 2: Strong Preferences](#tier-2-strong-preferences)
- [Tier 3: Concession Candidates](#tier-3-concession-candidates)
- [Negotiation Strategy Guide](#negotiation-strategy-guide)
- [Redline Format Template](#redline-format-template)
- [Common Pitfalls](#common-pitfalls)
- [Negotiation Tactics by Clause Type](#negotiation-tactics-by-clause-type)
- [Concession Trading Framework](#concession-trading-framework)

---

## Priority Tier Framework

Every redline falls into one of three priority tiers. This classification drives negotiation strategy, sequencing, and fallback decisions.

| Tier | Label | Definition | Negotiation Posture | Walk-Away? |
|------|-------|-----------|---------------------|------------|
| 1 | Must-Have | Fundamental protections without which the deal creates unacceptable risk | Firm; present first; do not concede without executive approval | Yes |
| 2 | Should-Have | Material improvements that significantly reduce risk or improve position | Push hard; accept reasonable fallbacks; trade for Tier 1 wins | No |
| 3 | Nice-to-Have | Improvements that add value but are not critical to risk profile | Propose early; concede strategically to gain Tier 1-2 items | No |

### Tier Assignment Criteria

| Criterion | Tier 1 | Tier 2 | Tier 3 |
|-----------|--------|--------|--------|
| Financial exposure | Unlimited or uncapped | Capped but unfavorable | Minor or well-bounded |
| Legal/regulatory risk | Non-compliance with law | Best-practice gap | Preference only |
| Operational impact | Blocks business operations | Creates friction | Minor inconvenience |
| Reversibility | Irreversible (IP transfer, waiver) | Difficult to reverse | Easily modified later |
| Market position | Far below market standard | Below market standard | At or near market |

---

## Tier 1: Deal-Breakers

These items must be resolved before signing. If counterparty refuses, escalate to executive/legal leadership for go/no-go decision.

| Item | Trigger | Preferred Position | Walkaway Threshold |
|------|---------|-------------------|--------------------|
| Liability Cap | No cap or cap exceeds 36 months of fees | 12 months of fees, mutual | Accept 24 months; reject no cap |
| IP Assignment | Blanket assignment of all IP including pre-existing | Deliverable assignment only; background IP licensed | Accept exclusive license; reject blanket assignment |
| Data Breach Notification | No notification obligation | 72-hour notification | Accept 5 business days; reject no notification |
| Perpetual Term | No termination path | Fixed term with renewal | Accept perpetual with convenience termination; reject perpetual with no exit |
| Missing Data Protection | No DPA when personal data involved | Full DPA as exhibit | Accept reference to standard DPA; reject no data protection |

### Tier 1 Escalation Protocol

1. Present preferred position with rationale
2. If rejected, offer fallback position
3. If fallback rejected, pause negotiation
4. Escalate to legal leadership with analysis
5. Legal leadership makes go/no-go decision
6. Document decision and rationale regardless of outcome

---

## Tier 2: Strong Preferences

Push firmly on these items. Accept reasonable counteroffers but do not concede without receiving something in return.

| Item | Trigger | Preferred Position | Acceptable Fallback |
|------|---------|-------------------|---------------------|
| Mutual Indemnification | One-sided indemnification | Mutual, scoped to breach and negligence | One-sided if capped and with procedures |
| Cure Period | No cure or immediate termination | 30-day cure for material breach | 15-day cure with notice |
| Consequential Damages | Not excluded | Mutual exclusion with limited carveouts | Mutual exclusion with broader carveouts |
| IP Non-Infringement | No vendor warranty | Vendor warrants non-infringement | Vendor indemnifies for IP claims |
| Governing Law | Unfavorable jurisdiction | Home jurisdiction | Neutral jurisdiction (Delaware, NY, England) |
| Warranty | Complete as-is disclaimer | Conformance + workmanship + authority | 90-day conformance warranty |
| Confidentiality Survival | No survival or <1 year | 3-year survival post-termination | 2-year survival |
| Sub-Processor Controls | Unlimited sub-processing | Prior written consent | List with objection right |

### Tier 2 Trading Strategy

- Trade Tier 3 concessions to win Tier 2 items
- Bundle Tier 2 items: "We'll accept your position on X if you accept ours on Y and Z"
- Use comparative market data: "Industry standard is mutual indemnification"
- Offer creative alternatives: "If you can't do mutual indemnification, cap the obligation at 2x fees"

---

## Tier 3: Concession Candidates

These items improve the agreement but can be conceded strategically. Use them as trading chips for Tier 1 and Tier 2 wins.

| Item | Preferred Position | Concession Value | Trade For |
|------|-------------------|------------------|-----------|
| Auto-Renewal Terms | 60-day opt-out window | Low | Tier 2 cure period or warranty |
| Jury Waiver | Remove waiver | Low | Tier 2 governing law |
| Audit Frequency | Annual only | Medium | Tier 2 sub-processor controls |
| Force Majeure Scope | Narrow definition | Low | Tier 1 liability cap |
| Venue Selection | Home venue | Medium | Tier 2 governing law |
| Attorney Fees | No prevailing party clause | Low | Any Tier 2 item |
| Notice Period | 90-day notice | Low | Tier 2 cure period |

### Concession Sequencing

1. **Open with all tiers** -- present the full redline so counterparty sees the complete picture
2. **Concede Tier 3 first** -- "We can be flexible on audit frequency and notice periods"
3. **Bundle Tier 3 concessions** -- "We'll withdraw items X, Y, Z if you accept A and B"
4. **Hold Tier 3 reserve** -- keep 1-2 Tier 3 items for final round horse-trading
5. **Never concede Tier 1** without executive approval

---

## Negotiation Strategy Guide

### Before the Negotiation

| Step | Action | Purpose |
|------|--------|---------|
| 1 | Run contract analysis and generate redlines | Identify all issues and classify by tier |
| 2 | Research counterparty's standard positions | Anticipate pushback and prepare responses |
| 3 | Identify your BATNA (best alternative) | Know your walkaway point |
| 4 | Prepare fallback positions for every Tier 1 and 2 item | Avoid being caught without options |
| 5 | Identify Tier 3 concession chips | Plan what to give away and when |
| 6 | Set internal approval thresholds | Know when you need to escalate |

### During the Negotiation

| Phase | Strategy | Tactics |
|-------|----------|---------|
| Opening | Present full redline; explain tier framework | "We've categorized our comments into must-haves, preferences, and nice-to-haves" |
| Middle | Address Tier 1 items first | Resolve deal-breakers before spending time on details |
| Trading | Bundle concessions for wins | "We can withdraw items 5, 7, and 9 if you accept items 2 and 3" |
| Closing | Confirm all open items resolved | Walk through the issues log; ensure nothing is forgotten |
| Documentation | Memorialize all agreements in writing | Email summary of agreed positions before markup |

### After the Negotiation

| Step | Action | Purpose |
|------|--------|---------|
| 1 | Update issues log with final positions | Record what was agreed |
| 2 | Compare final contract to redline positions | Verify all changes are reflected |
| 3 | Flag any reopened issues | Counterparty may try to walk back concessions in markup |
| 4 | Document lessons learned | Improve playbook for next negotiation |

---

## Redline Format Template

Use this format when preparing redline comments for counterparty delivery.

### Single Redline Entry

```
SECTION: [Section number and title]
ISSUE: [Brief description of the issue]
PRIORITY: [Must-Have / Should-Have / Nice-to-Have]
CURRENT: "[Quote the current contract language]"
PROPOSED: "[Your proposed replacement language]"
RATIONALE: [Why the change is needed, referencing market standard or legal requirement]
FALLBACK: "[Alternative language if counterparty rejects preferred position]"
```

### Example

```
SECTION: 8.1 Limitation of Liability
ISSUE: No aggregate liability cap
PRIORITY: Must-Have
CURRENT: "Liability under this Agreement shall not be limited."
PROPOSED: "The aggregate liability of either party under this Agreement
shall not exceed the total fees paid or payable by Customer in the twelve
(12) month period immediately preceding the event giving rise to the claim."
RATIONALE: Uncapped liability creates unlimited financial exposure for both
parties. Market standard for SaaS agreements is 12 months of fees.
FALLBACK: "Aggregate liability shall not exceed the greater of (a) fees
paid in the prior 24 months or (b) $2,000,000."
```

---

## Common Pitfalls

| Pitfall | Impact | Prevention |
|---------|--------|------------|
| Negotiating without a prioritized list | Wastes time on low-value items; may miss critical issues | Always run contract analysis and tier classification before negotiation |
| Conceding Tier 1 items to "close the deal" | Creates unacceptable legal or financial exposure | Require executive sign-off on any Tier 1 concession |
| Accepting verbal agreements without written confirmation | Verbal concessions are forgotten or denied in final markup | Email summary of all agreed positions within 24 hours |
| Negotiating clause-by-clause in order | Counterparty controls pacing; no ability to bundle or trade | Group issues by tier and negotiate thematically |
| Ignoring clause interactions | Winning on liability cap but losing on uncapped indemnification | Review clause interaction matrix before finalizing |
| Revealing your tier classifications to counterparty | Counterparty knows which items you will concede | Share priorities by theme, not by explicit tier labels |
| Failing to prepare fallback positions | Stuck when counterparty rejects preferred position | Document fallback for every Tier 1 and 2 item before negotiation |
| Making unilateral concessions without reciprocity | Establishes pattern of one-sided movement | Always pair a concession with a request |
| Treating all contracts the same | Low-value contracts get over-negotiated; high-value under-negotiated | Scale negotiation effort to contract value and risk |
| Not documenting lessons learned | Repeating the same mistakes across negotiations | Update playbook after each significant negotiation |

---

## Negotiation Tactics by Clause Type

| Clause | Opening Move | Common Counterparty Response | Counter-Tactic |
|--------|-------------|------------------------------|----------------|
| Liability Cap | "We need 12 months of fees" | "Our standard is no cap" | "Show us your insurance coverage; we'll align the cap" |
| Indemnification | "This should be mutual" | "Vendor only indemnifies for IP" | "We'll accept IP-only if it's uncapped and has procedures" |
| IP Ownership | "We need assignment of deliverables" | "We own everything" | "License model works if exclusive and perpetual for deliverables" |
| Data Protection | "We need a full DPA" | "Our standard DPA is non-negotiable" | "We can accept your standard DPA if it includes X, Y, Z" |
| Governing Law | "Our home jurisdiction" | "Our home jurisdiction" | "Neutral ground: Delaware or arbitration under ICC rules" |
| Term | "Annual with convenience termination" | "3-year minimum commitment" | "Accept 3-year if we get favorable pricing and 90-day convenience exit after Year 1" |

---

## Concession Trading Framework

Use this matrix to identify equivalent-value trades across tiers.

| Give (Tier 3) | Get (Tier 2) | Rationale |
|---------------|-------------|-----------|
| Accept auto-renewal | Win cure period | Auto-renewal is manageable with calendar reminder; cure period prevents surprise termination |
| Accept jury waiver | Win home jurisdiction | Jury waiver matters less when you control the venue |
| Accept broader force majeure | Win liability cap | Force majeure is rarely invoked; liability cap protects daily |
| Accept vendor audit rights | Win sub-processor consent | Audits are infrequent; sub-processor control is ongoing |
| Accept shorter notice period | Win warranty improvements | Notice is procedural; warranty is substantive |

| Give (Tier 2) | Get (Tier 1) | Rationale |
|---------------|-------------|-----------|
| Accept one-sided indemnification (capped) | Win liability cap | Indemnification risk is bounded by cap |
| Accept as-is warranty (with conformance) | Win IP assignment of deliverables | Warranty is secondary if you own the work product |
| Accept unfavorable jurisdiction | Win data breach notification | Jurisdiction matters only in disputes; breach notification is regulatory |
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall