Most negotiation scripts AI writes sound like a LinkedIn carousel — “I am very excited about this opportunity and would like to discuss.” Recruiters tune out by the second clause. The job is to use AI for the parts where structure matters (anchor, BATNA framing, the silence) and write the cadence yourself.
The task
You have an offer or are about to. You want a written script for the next call that anchors high, names a real BATNA without bluffing, prepares two pushbacks, and holds composure through the recruiter’s reply.
When this is the right job for AI
- You have an actual offer or a near-certain one, with a number you can quote.
- You have at least one credible alternative — a competing offer, a current comp band, or a strongly-signaled second-round elsewhere.
- You can name your minimum acceptable (the “walk away”) in private. AI cannot find that for you.
- You will rehearse the script aloud at least twice. Reading silently is not rehearsal.
If you do not have a BATNA, do not negotiate over comp — negotiate over scope, start date, or a written growth conversation in 6 months.
What to feed the AI
- The offer in full (base / bonus / equity / sign-on / benefits — name each line)
- Your target number with a written justification (one comp data point + one personal lever)
- Your BATNA, exactly as you would describe it on the call
- The recruiter’s likely first response (most common: “this is at the top of band”)
- Your level on phone composure (do you go silent under push, or do you talk too much?)
Copy-ready prompt
You are drafting my salary negotiation script for a {Senior Software Engineer} role.
Current offer:
- Base: {185k}
- Bonus target: {15%}
- Equity: {120k over 4yrs, 1yr cliff}
- Sign-on: {none}
Target ask: base {210k}, sign-on {25k}, equity refresh discussion in 6 months.
Anchor justification: {Levels.fyi median for L5 at peer co is 210; my current comp is 200 all-in}.
BATNA: {Final round at PeerCo, expected offer 200-215 base based on recruiter signaling}.
Recruiter's likely first pushback: {"This is at the top of the band for the level"}.
My weakness on calls: {I fill silences when nervous}.
Produce a script with:
1. Opening line — NOT "I am very excited about this opportunity". A specific reason the role is a fit, in one sentence.
2. The ask — one sentence, anchor first, three components in priority order.
3. Justification — one comp data point + one personal lever. Under 30 seconds spoken.
4. The silence — explicitly mark a 4-second pause after the ask.
5. Two scripted pushback responses — one for "top of band", one for "we can't move on base, but we can on sign-on".
6. The close — what I say if the answer is "let me check and get back to you".
Then list the 3 things I should NOT do on the call given my weakness about silence.Sample output structure
Opening: A one-line bridge that names something specific about the team (the platform charter, the manager’s reputation for review-velocity, the company’s funding-round shape) so it does not read as boilerplate.
Ask: “Based on what I am seeing in the market and my current comp, I am hoping we can move base to 210, with a 25k sign-on, and a written check-in on equity refresh in six months.” Three components, anchor first.
Justification: One Levels.fyi or peer-company data point as the public anchor, plus one personal lever (current comp, a competing-process status, the cost of the move). Under 30 seconds.
Silence: literally noted in the script — “[pause 4 seconds; do not fill]”.
Pushback 1 reply: “I hear you on band. The way I am thinking about it — base is the load-bearing number for me; sign-on and equity refresh are the levers if base is genuinely capped.”
Pushback 2 reply: For when they offer sign-on instead of base, with the math on what sign-on means after year one.
Close: “Take the time you need. I want to make the right call too — when do you think you will have an answer?”
How to refine
- Sounds like a script: ask AI to rewrite using only words you would say to a friend. Read aloud; cut anything you stumbled on.
- Anchor is too high or too soft: feed AI the actual market data (Levels.fyi, peer offers) and ask for a number 5-8% above your true target so you have room to land.
- Justification cites a number you cannot back up: replace with one specific you can defend in two more questions.
- Pushback feels combative: change to “I hear you on X” framings, not “but” framings.
- You always fill silence: ask AI to insert “[pause 4 sec]” markers explicitly and to write a one-line internal cue (“count to four; breathe”).
Common mistakes
- Anchoring with a range. “180-220” tells the recruiter you will take 180. Anchor with a single number.
- Negotiating against yourself. If you say “210, but I am flexible”, you have already moved.
- Asking for everything at once with no priority. Three components, ranked, so they know which lever to actually pull.
- Negotiating without a BATNA. The negotiation power comes from the alternative, not the tone.
- Sending the ask over email when the relationship is built over phone — phone for the anchor, email for the written follow-up confirmation.
FAQ
- Should I share my current comp? Generally no unless the law requires it; share your target instead. If pressed, share the all-in number with framing (“I am at X all-in, and looking to step up to Y”).
- What if they say it is the absolute final offer? Ask one clarifying question: “is base the part that is capped, or all components?” Their answer tells you where the lever still is.
- Can I negotiate after I have already verbally accepted? Yes, before the written offer is signed. Once signed, the only lever is start date or scope.
- How long should I take to respond? 24-48 hours for the counter; 3-5 business days for the final decision. Both are normal.
- Should I mention a competing offer by name? Only if you have the written offer in hand. Naming without proof is a fast way to lose credibility.
Related
- AI recruiter reply prep
- AI cold outreach for job hunting
- AI cover letter
- AI resume bullet rewrite
- AI behavioral interview prep
Tags: #AI writing #salary-negotiation #Job search #job-search-practice