Negotiate With Structured Thinking, Not Guesswork
20 Claude prompts for salary negotiations, vendor deals, contract reviews, and difficult conversations — grounded in BATNA, ZOPA, and anchoring frameworks Claude reasons through.
In short: This page contains 20 copy-paste ready prompts, organized into 4 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Drafted with AI writing assistance and checked against our editorial policy.
Salary & Offers
5 promptsSalary Negotiation Script
1/20✨ What it does
Claude builds a salary negotiation with a target and walk-away, a data-backed opening anchor, three "above range" replies, a counter-offer script, and non-base options. Add [alternatives, skills, wins] and [paste] market data, then rehearse the opening before the call.
<task>Build salary negotiation strategy</task> <offer>[describe]</offer> <leverage>[alternatives, skills, wins]</leverage> <market_data>[paste]</market_data> <output> 1. Target + walk-away with reasoning 2. Anchor opening (confident, data-backed) 3. 3 objection-handlers for "above range" 4. Counter-offer script 5. Non-base items to negotiate (bonus, equity, PTO, remote) </output>
Pro tip: First number spoken = anchor. Flip recruiter's "what's your range?" to your own anchor: "Based on market data, I'm looking at $X-Y. Workable?"
Counter-Offer Email
2/20✨ What it does
Claude writes a counter-offer email that thanks them without groveling, states [target] with 2-3 reasons, and closes with confidence and no apology. [describe] the offer you received, then send the email after you check every number.
<task>Write counter-offer email</task> <offer>[describe]</offer> <counter>[target]</counter> <output> - Gratitude without groveling - Specifically counter with reasoning - 2-3 reasons (experience, competing interest) - End with confidence No apology.
Pro tip: Never apologize when negotiating. "I know this is more than discussed, but..." signals weakness. Replace with "I've reflected on scope and market — $X works."
Raise Request Script
3/20✨ What it does
Claude prepares a raise request with a pre-meeting case, a 60-second opening, how to frame the ask, replies to "not in budget," and a follow-up email. List [specifics with numbers], then walk in with the case printed and send the follow-up the same day.
<task>Prepare raise request</task> <role>[describe]</role> <accomplishments>[specifics with numbers]</accomplishments> <output> 1. Pre-meeting case document 2. Opening 60 seconds 3. How to frame ask 4. Objection-handlers ("not in budget", "not this year") 5. Follow-up email </output>
Pro tip: Raises aren't given for effort — for impact. Your case should be "here's what I delivered worth $X" not "here's how many hours I worked." Quantify.
Multiple Offer Leverage
4/20✨ What it does
Claude maps how to use multiple offers with a tactful disclosure email, non-ultimatum phrasing, asks for base, signing, or equity, a "can't match" reply, and a no-bluff rule. [describe] each offer and the preferred one, then send the disclosure only if every offer is real.
<task>Leverage multiple offers</task> <offers>[describe]</offers> <preferred>[describe]</preferred> <output> 1. Tactful disclosure email 2. Non-ultimatum phrasing 3. Specific asks (base, signing, equity) 4. Handling "can't match" 5. Ethical boundaries — never bluff </output>
Pro tip: Never bluff about offers. Industry is small; getting caught destroys relationships. Use real offers; negotiate on merit otherwise. One lie undoes ten years of reputation.
Remote/Flexibility Negotiation
5/20✨ What it does
Claude builds a flexibility ask for remote work, a 4-day week, or a sabbatical, with a business case, safeguards, objection replies, trial-period framing, and a written proposal. [specify] the ask and [describe] your leverage, then send the proposal after you pick a trial length.
<task>Negotiate remote work / 4-day week / sabbatical</task> <current>[describe]</current> <ask>[specify]</ask> <leverage>[describe]</leverage> <output> 1. Business case framed in their benefit 2. Proposed structure with safeguards 3. Objection-handlers 4. Trial-period framing 5. Written proposal template </output>
Pro tip: Frame flexibility asks as mutual benefit. "I can deliver better outcomes with X" beats "I want X personally." Same ask, different response.
Vendors & Contracts
5 promptsVendor Price Negotiation
6/20✨ What it does
Claude builds a vendor negotiation with an anchored opening, ranked asks, concessions you will trade (longer term or prepay), objection replies, a walk-away, and a call script. Add [alternatives, volume] and [describe] the quote and target, then open with the rank-one ask.
<task>Negotiate vendor contract</task> <vendor>[describe]</vendor> <quote>[describe]</quote> <leverage>[alternatives, volume]</leverage> <target>[describe]</target> <output> 1. Anchored opening 2. Specific asks ranked 3. Concessions willing (longer contract, prepay) 4. Objection-handlers 5. Walk-away 6. Email/call script </output>
Pro tip: Most quotes include 10-20% padding for negotiation. Never accept first price. "Is there flexibility?" recovers margin without conflict.
Contract Review Checklist
7/20✨ What it does
Claude reviews a contract for leverage: unfavorable clauses, red-flag language, missing protections, what is boilerplate, and a priority order. Paste [describe key terms] and mark [buyer / seller], then negotiate the top items first.
<task>Review contract for negotiation leverage</task> <contract>[describe key terms]</contract> <our_role>[buyer / seller]</our_role> <output> 1. Unfavorable clauses 2. Red-flag language 3. Missing protections to request 4. Leverage points 5. Boilerplate vs negotiable 6. Priority order </output>
Pro tip: Contracts are 80% boilerplate, 20% deal-specific. Focus on indemnification, payment, termination, IP. Boilerplate disputes eat time without real benefit.
SaaS Renewal
8/20✨ What it does
Claude prepares a SaaS renewal talk with a script, asks for a reduction, feature unlock, or multi-year lock, leverage from competitor quotes, and when to start. [describe] the vendor, spend, and alternatives, then begin the talk before the auto-renew window.
<task>Negotiate SaaS renewal</task> <vendor>[describe]</vendor> <current_spend>[describe]</current_spend> <alternatives>[describe]</alternatives> <output> 1. Renewal conversation script 2. Specific asks (reduction, feature unlock, multi-year lock) 3. Leverage points (competitor quotes, budget pressure) 4. Timing — when to start 5. Escalation path </output>
Pro tip: SaaS vendors dread losing accounts. Start renewal conversations 60-90 days before expiration. Mention you're "evaluating alternatives" — price almost always moves.
Scope Change Negotiation
9/20✨ What it does
Claude scripts a scope-change talk with yes-and framing, pricing for the extra work, a change-order note, and how to handle a client who thought extra work was already included. Spell out the original scope and the new request in [describe], then send the change order before you start the extra work.
<task>Negotiate scope change with client</task> <original>[describe]</original> <new_request>[describe]</new_request> <output> 1. "Yes and" framing script 2. Pricing for additional work 3. Change order documentation 4. Relationship preservation 5. "Thought it was included" handling </output>
Pro tip: Scope creep kills service businesses. "Yes, we can do that — it'll add $X and extend 2 weeks" beats both "no" and silent acceptance.
Partnership Terms
10/20✨ What it does
Claude drafts partnership terms covering a fair split, decision rights, exit clauses, IP and confidentiality, and non-compete boundaries. [describe] each side's contribution, then mark the clauses you still need a lawyer to review.
<task>Negotiate partnership terms</task> <our_contribution>[describe]</our_contribution> <their_contribution>[describe]</their_contribution> <output> 1. Fair split proposal 2. Rights + decision-making clauses 3. Exit clauses 4. IP + confidentiality 5. Non-compete boundaries </output>
Pro tip: Partnerships die on exit clauses, not opening terms. Negotiate divorce when everyone's in love. "What if one of us wants out in 2 years?" is most valuable JV question.
Difficult Conversations
5 promptsPerformance Conversation
11/20✨ What it does
Claude prepares a performance conversation with a direct non-accusatory opening, specific examples, impact, the change needed, dated next steps, and a follow-up email. [describe] the issue and the desired outcome, then hold the meeting and send the recap the same day.
<task>Prepare performance conversation with employee</task> <issue>[describe]</issue> <desired_outcome>[describe]</desired_outcome> <output> 1. Direct non-accusatory opening 2. Specific examples to cite 3. Impact on team/business 4. Change needed 5. Agreed next steps with dates 6. Follow-up email </output>
Pro tip: Vague performance talks fail. Specific observations with clear impact ("X happened, Y broke, Z behind") are undeniable. Data prevents emotional debates.
Difficult Email
12/20✨ What it does
Claude writes a difficult email about [issue] that states the message in 1-2 sentences, explains briefly, names a path forward, and closes warmly without a wall of apology. [describe] the recipient and the goal, then send the short version if it still sounds like you.
<task>Write difficult email about [issue]</task> <recipient>[describe]</recipient> <goal>[describe]</goal> <output> Acknowledge context (not excessive apology) → state message directly 1-2 sentences → explain briefly → path forward → close warmly. No passive voice, no walls of justification.
Pro tip: Difficult emails are shorter than you think. Long emails signal anxiety, invite nit-picking. Say it in 2 sentences; explain briefly.
Saying No Gracefully
13/20✨ What it does
Claude writes a 2-3 sentence no to [request] with one specific reason, a genuine alternative if you have one, pushback replies, and written versus spoken variants. Note [boss / peer / client] and [describe] the context, then say the no once and stop adding reasons.
<task>Say no to [request]</task> <context>[describe]</context> <relationship>[boss / peer / client]</relationship> <output> 2-3 sentence no script, one specific reason, alternative if genuine, pushback handling, variations for written/verbal. No excessive apology.
Pro tip: Over-apologizing for no weakens it and invites pressure. "Thanks for thinking of me — can't take this on right now" is enough.
Termination Script
14/20✨ What it does
Claude prepares a termination conversation with a direct opening, a final decision, last-day and severance logistics, how to handle emotion, phrases to avoid, and a post-meeting checklist. [describe] the context and [describe] severance, then walk the checklist with HR in the room.
<task>Prepare termination conversation</task> <context>[describe]</context> <severance>[describe]</severance> <output> 1. Direct opening (no misleading softening) 2. Decision is final 3. Logistics (last day, severance, COBRA) 4. Emotional response handling 5. What NOT to say (legal risk) 6. Post-conversation checklist </output>
Pro tip: Terminations go wrong with softening that misleads. Be direct in sentence 2: "This is a termination conversation." Softening prolongs anxiety.
Boundary-Setting
15/20✨ What it does
Claude writes a boundary script for [person] that names the pattern without blame, states the line, names the consequence, and covers pushback plus follow-up. [describe] the pattern and the desired outcome, then enforce the line the next time it shows up.
<task>Set boundary with [person]</task> <pattern>[describe]</pattern> <desired_outcome>[describe]</desired_outcome> <output> 1. Name the pattern non-accusatorily 2. Specific boundary 3. Consequence if crossed 4. Pushback handling 5. Follow-up enforcement </output>
Pro tip: Boundaries without consequences are requests. "I'll need you to X, and if not, I'll Y." Consequence makes boundary real. Vague boundaries get crossed.
These prompts give you the what. Tutorials give you the why.
Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. The library keeps growing.
Frameworks
5 promptsBATNA Analysis
16/20✨ What it does
Claude maps every alternative if [negotiation] fails, ranks them, names the strongest one, shows how to strengthen it, and when to walk. [describe] the situation, then walk only if that best alternative still beats the deal on the table.
<task>Analyze BATNA for [negotiation]</task> <situation>[describe]</situation> <output> 1. All alternatives if negotiation fails 2. Rank by attractiveness 3. Strongest BATNA 4. How to strengthen before negotiation 5. How to reference during (without bluffing) 6. When to walk </output>
Pro tip: Your BATNA is your real power. Weak BATNA = give in to avoid losing deal. Strengthen BATNA BEFORE negotiation (other offers, vendors, buyers), not during.
ZOPA Mapping
17/20✨ What it does
Claude maps the overlap where a deal can still happen, plus walkaway signals, extra variables, creative trades, an opening at the far edge, and a concession plan. Enter [target + walkaway] and [estimate] their side, then open at that far edge and move only on purpose.
<task>Map ZOPA</task> <my_position>[target + walkaway]</my_position> <their_position>[estimate]</their_position> <output> 1. Overlap zone 2. Signals revealing their walkaway 3. Widen ZOPA — add variables 4. Creative trades 5. Opening anchor at far edge 6. Concession strategy </output>
Pro tip: Narrow ZOPA? Widen by adding variables. If price is fixed, trade timeline, volume, exclusivity. Best negotiators create value, not just divide it.
Anchor Strategy
18/20✨ What it does
Claude designs an opening [number] with a precise, backed ask, how to say it, the justifying story, how to hold versus a counter-anchor, and when to move. [describe] the market, then say the precise number and do not round it down in the room.
<task>Design opening anchor</task> <market>[describe]</market> <target>[number]</target> <output> 1. Specific opening (precise, backed) 2. Delivery method 3. Justifying story 4. How to hold firm vs counter-anchor 5. When/how much to move </output>
Pro tip: Precise anchors ($47,850) beat round numbers ($50,000). Precision signals research. Round numbers get haggled; precise numbers get debated.
Concession Strategy
19/20✨ What it does
Claude plans concessions between your [number] anchor and [number] walk-away, with big-first pacing, something you ask back each time, and stretch language. Mark the gap you can actually give, then trade only when they give something too.
<task>Plan concession strategy</task> <anchor>[number]</anchor> <walkaway>[number]</walkaway> <output> 1. Gap I can concede 2. Pacing (big first, smaller after) 3. Ask for something back per concession 4. Verbal markers ("this is a stretch") </output>
Pro tip: Always ask for something back when conceding. Unilateral concessions train other side to keep pushing. Every concession should cost them something.
Role-Play Simulator
20/20✨ What it does
Claude role-plays the other side of [scenario] for 5 rounds, from your opening through pushback to a close, with realistic pressure and coaching after each round. Set [hard / soft / collaborative] and [describe] their role, then run all five rounds before the real meeting.
<task>Role-play negotiation counterpart for [scenario]</task> <their_role>[describe]</their_role> <style>[hard / soft / collaborative]</style> <output> 5 rounds: you open anchor → I respond → pushback → counter → close. Realistic pressure tactics. Coaching after each round.
Pro tip: Negotiations are muscle memory. Role-play with Claude 3-5 times before high-stakes negotiations. Responses become second nature instead of improvised.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of hands-on tutorials on ChatGPT, Claude, Midjourney, and many other AI tools. New tutorials are added regularly.
7-day free trial. Cancel anytime.