A salary negotiation script template for owners without a comp team

Search “salary negotiation script” and every result on the first page coaches the same person: the candidate. Open with gratitude, cite your market research, counter with a range, ask for benefits if the base won’t move. It’s good advice. It’s also written for exactly one side of a conversation that has two.

Nobody wrote the other script. The one for the owner who picked a number last night with no comp team, no pay band, and no precedent to point to, who now has to say it out loud to someone who read all those candidate-side guides before the call.

That gap matters more than it used to. Pew Research found that 30% of U.S. workers asked for higher pay the last time they were hired, and of those who asked, 66% walked away with more than the original offer: 28% got exactly what they asked for, 38% got a partial bump. That makes negotiating closer to a coin flip you should plan for than a rare, awkward exception you improvise through.

Why “just sound confident” is bad advice

The advice you’ll actually get, from a friend or a forum, is to just be confident. Say the number, don’t blink, hold the line.

That advice skips the part that makes it work. A corporate recruiter’s calm in that room comes from a pay band they can point to, a compensation team they can say they’ll “check with,” and forty prior hires at the same title that prove the number is real, not from personality. Take that support away, and “just sound confident” is telling someone to fake it.

You don’t have the band or the team. What you do have is a role you understand better than any comp analyst ever will, and the ability to write down, in advance, the three or four reasons your number is what it is. That written reasoning is the thing a big company’s system does for its recruiters automatically. For you, it has to be built on purpose, once, before the call.

What guessing costs you

Without that groundwork, a salary conversation tends to break one of two ways.

You fold at the first pushback and add $8,000 you never planned to spend, because you had no number to hold and no reason to hold it. Or you freeze, repeat your original figure without addressing what the candidate actually raised, and lose them to a competing employer whose own recruiter had a real band to work from. If they’re weighing your offer against a counter offer from their current employer instead, that’s a related but different fight.

On a five-person team, either mistake is expensive in a way it wouldn’t be at a bigger company. And the number you land on doesn’t stay private for long. Pay transparency laws are pushing published ranges into more job posts every year, in states you might not expect to be covered, which means the figure you improvise your way into today is a data point your next three candidates, and possibly your current team, can eventually see.

Build the paper version of a comp team

The fix is homework, not bravado: writing down, before you ever say the number out loud, the three things a real comp function would already have on file.

What you already pay for comparable work. If two people on your team do adjacent jobs, their pay is your first real data point. It’s more relevant than any national survey, because it’s what your business actually spends on similar responsibility.

What the role costs you empty. Add up what an open seat is actually costing: overtime you’re paying to cover it, work that’s slipping, your own hours spent interviewing instead of running the business. That number puts a floor under what a fast, clean hire is worth to you.

One outside reference point. You don’t need a subscription to a compensation database. The Bureau of Labor Statistics’ Occupational Employment and Wage Statistics publishes wage percentiles by role and by state, free, and it’s specific enough to tell you whether your number is in the neighborhood or off the map.

Three points, written down with the number next to each one, is a range you can defend out loud. That page is also where you present total compensation instead of base salary alone, which is usually the fastest way to close a gap without touching the base number at all.

The salary negotiation script, phase by phase

With the range and the reasons written down, the conversation itself gets shorter. Here’s what to actually say at each point it can go.

Stating the number

Say the figure once, plainly, with one reason attached. Don’t apologize for it and don’t over-explain it.

“Based on what this role is worth to us and what we pay people doing similar work here, we’re at $58,000. That number reflects [specific reason: the on-call rotation, the years of experience we need, the pay for the coordinator role next to it].”

One reason is enough. Three reasons in the opening line reads as talking yourself into it.

When they go quiet

Silence after a number feels like rejection. It’s usually just someone doing math. Don’t fill it by raising the offer before they’ve said a word.

“Take a minute with that. What questions do you have about how we got to that number?”

When they name a specific counter

Compare it to your written range before you respond to the vibe of the ask.

If it’s inside what your three reference points support: “That works. Let’s put $62,000 in writing.” If it’s outside: “I can’t get to $70,000 on base, that’s outside what this role and this team support. What I can do is [specific alternative from your total comp page: an extra week of PTO, a 90-day review with a defined increase, a signing bonus].”

When they say they need to think about it

Don’t chase. Set a real date and stop talking.

“Totally fair. Can you get back to me by Thursday? I want to be able to move forward with our other candidates either way.”

Holding the line

If the number is genuinely right and you’ve explained why, repeating it, once, calmly, beats inventing a new number to fill the silence.

“I hear that this is below what you were hoping for. This is our number because [reason]. It’s not moving, but I want this to work, so let’s talk about what else on the offer could.”

Where the range should actually come from

The written range gets stronger the earlier you start building it, and the best version of it doesn’t come from three data points you gathered the night before an offer call. It comes from what you already asked candidates during screening.

If pay range alignment lives in your first screening touchpoint instead of showing up for the first time at the offer, you’re not negotiating off one candidate’s number. You’re negotiating off what your entire applicant pool told you they’d accept, which is a far better third reference point than anything a national database can give you.

That’s the piece Truffle was actually built for. Truffle is a candidate screening platform that combines resume screening, one-way video interviews, and talent assessments, and one of the smaller, less obvious uses of it is qualification questions that ask every candidate their pay expectations before you’ve spent an hour with any of them. By the time you’re negotiating with a finalist, you already know where the other 40 people in the pile landed, which turns “I think this is roughly right” into “this is what this specific labor pool for this specific role actually costs.” Truffle’s plans start at $49 a month and every plan includes qualification questions, so building that range doesn’t require a comp tool on top of your screening tool. It’s the same one.

The range you build once, you use all year

If you’re hiring the same role again in three months, which is the normal pattern for a small business that keeps a recurring seat open, the range and the reasons you wrote for this negotiation are also next quarter’s starting point. Update the three reference points, adjust for whatever’s changed, and you walk into the next offer call with a page instead of a guess.

The confidence a big recruiting team brings to a salary conversation was never a trait. It was infrastructure they built once and reuse on every call. You can build the small-business version of the same thing, on one page, and reuse it the same way.

Ready to build your first range from real applicant data instead of a guess? See Truffle’s plans and start capturing pay expectations at the first screening touchpoint, not the last one.

Frequently asked questions about salary negotiation scripts

How do I know if my salary offer is too low before I even make it?

Check it against your three reference points: what you pay comparable roles on your own team, what the open seat is actually costing you in overtime or lost work, and a wage percentile from the BLS Occupational Employment and Wage Statistics for your role and state. If your number sits well outside all three, expect a counter and have your total compensation components ready before the call, not during it.

What if the candidate negotiates over email instead of a call?

Use the same structure in writing: state the number with one reason, and if they counter, compare it to your written range before responding. Email removes the silence-reading problem, but it also removes tone, so be more explicit than you’d be on a call: “That’s outside what this role supports, here’s what I can offer instead.”

Should I ever negotiate against myself and raise the offer before they’ve countered?

No. If your number came from real reference points, let the candidate respond to it before you move. Raising a number nobody has pushed back on yet just teaches the candidate, and yourself, that your opening number was never the real one.

What’s the difference between this and handling a counter offer from their current employer?

Different moment entirely. This is the conversation before they’ve accepted anything, where you’re setting the number together. A counter offer from their current employer happens after they’ve already said yes to you, when their current boss tries to keep them. The power in the room has shifted by then, so the script has to change with it.

Do I need to give a reason for my number, or can I just state it?

Give one. A number with no reason invites a counter built on nothing but hope. A number with a specific reason, tied to the role or your existing team’s pay, gives the candidate something concrete to negotiate against instead of just pushing on a wall.