Salary negotiation scripts: how to get 20-40% more without sounding greedy

You've probably already given away money in a negotiation without noticing it: you answered the recruiter's comp question on the first call, or you took the offer as written because countering felt greedy.

This article has a script for each stage of a negotiation, from the recruiter screen to the final paperwork, plus the delivery techniques that make them land. Read it before your next offer and practice the lines out loud, because they need to sound like you by the time the recruiter calls.

The scripts below run in order, from recruiter screen to signed paperwork. They come from Jacob Warwick, an executive negotiator who has closed more than a billion dollars in comp for his clients, and Chris Voss, who spent 24 years negotiating hostages for the FBI. Every script plays at the exact moment it gets explained.

Why asking does not backfire

Start with the fear itself, because it is the actual obstacle. Phyl Terry runs job search councils and has tracked negotiation outcomes across many years:

Austin Belcak, who coaches job seekers at Cultivated Culture, sees the same result in his own LinkedIn polls, with samples of 15,000-plus:

He also modeled what staying silent costs over a career: two people who start at $50,000 and change jobs five times over 30 years end up more than $560,000 apart, purely on whether one of them negotiated each move. Companies expect the ask. The offer has room built into it. What follows is how to use that room without damaging the relationship you are about to start.

Stage 1: The recruiter asks for your number

Jacob Warwick's rule is to never anchor first, because the role is still being scoped and an early number becomes your ceiling:

His reasoning (27:55): you should never be so sure of what you are worth that you would not accept more. Interviews expand the role as the company gets to know you. Give a number on day one and it gets anchored to the smallest version of the role.

Some recruiter screens won't move forward without a number. Austin Belcak's fallback is to flip the question once before conceding: "I completely understand, and I don't want to waste anyone's time either. Since you seem to have a range in mind, would you be open to sharing the range you've budgeted for this role?" Recruiters share it more often than you'd expect, and then you never have to name a number at all; "that's in line with the other roles I'm being considered for" does the rest.

Stage 2: The offer lands

This is the hero script, and it is one sentence:

Warwick says this works from $100K offers to seven-figure packages, and that well-run negotiations average around 40 percent total movement. The sentence carries no number and no demand, so there is nothing in it to sound greedy about.

Stage 3: Countering without naming a number

If the offer is genuinely light, Warwick's counter is a statement followed by silence:

The silence is the technique. They respond by revealing the range, and now they are negotiating against themselves. If you are forced to name a number anyway, Warwick cites the data on anchoring (1:38:31): people who anchored aggressively high ended up 175 percent better off than people who tried to be reasonable, because recruiters instinctively split the difference with whatever you say.

Stage 4: Breaking out of the band entirely

The biggest moves in Warwick's client history came from getting the role re-leveled rather than haggling within the band:

He describes clients who entered processes scoped at $185K to $285K and closed at $1.1M, not by pushing the band but by resetting which band the conversation was in.

There's a smaller version of the same move for anyone who already gave a number early and regrets it. You can't just ask for more; you need something to have changed, and something almost always has: the role you priced on the first call is not the role you understand after four rounds of interviews. Belcak's recovery script names the change directly: "When I shared that number, it was based on what I knew from our first conversation. Through this process I've learned a lot about the goals and expectations for this role, and given the scope, I believe this number better aligns with the value I'd bring to the team." If nothing obvious changed, ask a question whose answer might change it: career coach Adam Broda suggests asking how many hours a week the role really expects. Any answer above forty legitimately reprices the number you gave for a forty-hour week.

Worth knowing from the employer's side: salary bands come out of formulas someone chose. Matt Mochary's curriculum, used by CEOs at OpenAI and Coinbase, shows founders an explicit formula for offers: market comp minus your cash salary, multiplied over four years, divided by an optimism factor, paid as equity. It also advises setting cash at "what you need to live comfortably," which means volunteering a low cash need lowers your cash offer. And when a company offers you a menu of cash/equity trade-offs, the menu itself is part of the negotiation; some CEOs are hoping you take the equity-heavy option. For the equity mechanics behind all this, The Skip's episode with Goodwin Procter's compensation lawyers is a solid deep dive, and Nikhyl Singhal's insider's guide to tech compensation covers how bands and levels really work inside big companies.

Delivery: the Voss mechanics

Chris Voss spent 24 years negotiating for the FBI, and his techniques cover how the scripts above should sound. Three that map directly to salary conversations:

Label, don't interrogate

Instead of "what's the budget for this role?", try "it seems like there's a range you're working within." Labels pull out the same information without the cornering.

Go for no

Voss phrases asks so the other side can safely decline (29:45): going for yes creates friction, going for no creates safety. Warwick's deflection script ends with exactly this shape: "Is that going to be a problem?" invites a no that moves you forward.

Make them feel heard first

Before you counter, restate their constraints back to them better than they said them. It costs nothing and it is the opposite of sounding greedy.

The collaborative close: negotiate the job, then the money

Phyl Terry's sequence prevents the entire conversation from feeling adversarial. Before talking money, negotiate what you need to succeed:

Budget, headcount, training, scope: tie the asks to the job mission you and the hiring manager already agreed on. He tells the story of a CPO who asked for $20M for tech debt in the negotiation, got it on day one, and got promoted within a year partly because she started with the resources to win. Then, for the money itself, his phrasing is deliberately plain (1:01:01): "Are you open to 450? That was really what I was hoping for. Is that something we can talk about?" Most of the time, they say yes.

Two habits keep the close collaborative when the base truly won't move. First, Belcak's trading rule: never accept a concession without asking for something back. "I understand the base is fixed. Would we be able to make up the difference in the bonus? That way you only pay me if I meet or exceed expectations." A performance bonus takes risk off the company, which is why it's the easiest yes in the room, and the same shape works for a continuing-education budget, extra PTO, a later start date, or a standing quarterly 1:1 with your skip-level. Second, walk in with three versions of the deal already gamed out: Plan A leads with the item you value most, Plan B makes up for losing that item with the others, and Plan C hits the same total through a different mix. When the recruiter says no to A, you're not improvising; you're presenting B.

Stage 5: Protect the close

Deals lose money at the paperwork stage. Warwick tells the story of a CRO whose written severance came back at half the discussed number. The recovery script was four words:

That one question recovered $90K on the spot and eventually $350K. Read every document against what was said, and when they differ, assume a mistake before assuming bad faith: "was that a mistake?" lets everyone fix it without a fight.

The scripts on one page