Whoever Says the Number First Doesn't Lose. That's Outdated Advice.

Whoever names the number first doesn't automatically lose. In negotiation experiments, the party that anchors first with a credible figure tends to land closer to their target, and that first offer can explain 50 to 85 percent of the variation in final outcomes. The catch: you need a researched number to anchor with. The real question isn't "should I go first." It's "do I know enough to go first well."

"Never say a number first" was never a strategy. It was a hedge against being uninformed. It made sense in a world where the candidate was blind and the employer held every card. That world is closing. So before you parrot the rule one more time, ask what it was actually protecting you from.

Where did "never go first" come from, and when was it good advice?

The rule exists for one reason: information asymmetry. The employer knew the band, the budget, the urgency to fill, and what the last three hires signed for. You knew none of it. In that setup, naming a number first is genuinely dangerous. You might lowball yourself against a ceiling you can't see.

The fear was rational. There's even data on it. In one study of low-power, anxious negotiators, buyers who made the first offer produced offers indistinguishable from what the other side would have demanded anyway: they anchored around $1,415 when the neutral seller's demand averaged $1,711. No advantage. They anchored themselves down out of fear. So if you're anxious and uninformed, deflecting protects you.

But here's what got lost. The advice was a workaround for a missing input, not a rule about how negotiation works. Most of the outcome is decided before you open your mouth, and the input you're missing is the band. Fix the input and the rule inverts.

What does anchoring research actually show?

It shows the first credible number sets the gravity for everything after. The classic Galinsky and Mussweiler experiments found that whichever party made the first offer consistently got the better outcome, and that first offers were a strong predictor of final settlement prices. When you pool the research, Guthrie and Orr's meta-analysis still lands at a correlation of about 0.497 between the first offer and the final agreement. Same direction every time.

There's a second, sharper finding. Precision matters. Loschelder and colleagues found that a precise opening figure, say $93,450 instead of $93,000, makes the counterpart perceive you as more expert, counter less aggressively, and concede in smaller steps. The round number reads as a guess. The precise one reads as a calculation. The counterpart adjusts down from a precise anchor far less than from a vague one.

So the math favors going first. The condition is that your number has to be real.

What changed that makes the old rule obsolete?

The information asymmetry collapsed. That's the whole story. You can now look up the band on Levels.fyi, Glassdoor, Blind, or a live salary-band check for your role and city before you ever pick up the phone. What you find isn't one figure either, it's a spread, because there is no single market rate, just a 2x range and a question of where you land in it. And the law caught up: salary range posting is now required in 16 US states as of 2026, with Colorado's transparency rule associated with wages rising as much as 3.6 percent. In a disclosed-range market, you often already know the band before the recruiter asks.

Salary history bans pushed it further. In jurisdictions with bans, newly hired women saw salaries about 7.8 percent higher than peers in places without them. Your past pay is off the table. Your expectations are fair game. When a recruiter in California or New York asks what you're targeting, deflecting just stalls a question you'll have to answer anyway, and now you have the data to answer it well.

There's a relationship cost to over-deflecting, too. Most recruiters are screening for one thing on that call: does your number fit the budget. Dodge it three times and you read as either naive or playing games. One graceful deflect is calibration. A prolonged dance is friction.

When you know the band, what does going first sound like?

It sounds like a sentence with a source in it. Watch the difference.

Weak: "I'm flexible on compensation."

That anchors nothing. You've handed the entire range back to the employer and asked them to be generous. They won't be. "Flexible" is what people say when they haven't done the work, and the recruiter hears exactly that.

Strong: "Based on Levels.fyi data for Senior PM roles in Bangalore with 6 to 8 years of experience, the band runs 42 to 55 lakh. I'm targeting 52 given my specific work on zero-to-one product launches."

This anchors at the top of a documented range. It cites the source, so it doesn't read as greed, it reads as research. And it ties the high end to a specific reason. The recruiter now negotiates down from 52, not up from whatever number they were going to float. That's the 50-to-85-percent effect working for you instead of against you.

Notice the precision, too. "52 lakh" with a reason beats "somewhere around 50." Be specific enough to look like you calculated it.

When is deflecting still the right move?

When you genuinely don't have the data yet. The rule isn't dead everywhere. It's just narrowed to the cases it was always meant for.

The early phone screen with no role clarity is the clearest one. A recruiter calls about a "Director-level opportunity," no JD, no org context, no scope. Naming a number here is guessing. The move is to calibrate, not avoid:

"Happy to dig into compensation once I understand the scope. Can you share the band you're working with for this role?"

That's not dodging. You're asking them to reveal the band so your eventual number is anchored to reality. If they post or share it, you've just converted yourself from uninformed to informed in one sentence.

The second case is the expert counterpart. Loschelder's work also found that hyper-precise anchors can backfire with experts who do this all day: a recruiter may meet "$93,218" with skepticism rather than compliance if you can't justify the precision. Precise, yes. Absurdly precise without a reason, no.

And the third case is the one the data won't let us pretend away.

Is the "go first confidently" advice the same for everyone?

No. And ignoring that would be the dishonest version of this post. Bowles, Babcock, and Lai found that women who initiated salary negotiation were penalized more than twice as much as men in willingness-to-hire, and the penalty on perceived collaboration was 5.5 times greater. The act of asking carried a social tax that men simply didn't pay, which is why women negotiate as much as men and get penalized for it anyway.

That's not a reason to stay quiet. The same body of research points to what mitigates the backlash: framing the number as market rate rather than personal want. "The band for this role is X" lands cleaner than "I want X." Both name a number. One reads as informed, the other as demanding. The market-rate framing is also exactly what salary transparency now makes available to everyone, which is part of why range-posting laws are narrowing pay gaps in the first place.

This is the agency-over-fatalism line. The tax is real. It's also navigable with the right framing and the right data behind you.

What's the trade-off in going first?

Going first means you can undershoot. That's the honest cost.

Even with transparency, the employer often knows things you don't: the true ceiling, how badly they need to fill the seat, what competing offers are on the table. If your anchor lands below what they'd have paid, that gap is real money you'll never see, and you'll never know you left it there. The high anchor protects against this, which is why "top of the documented range" beats "middle." (The same logic applies past base pay, which is why it's worth learning how to negotiate equity and ESOPs before you sign.) But there's no version where going first is risk-free. You're trading the comfort of letting them reveal first for the leverage of setting the frame. When your data is good, that trade pays. When it's thin, it doesn't.

There's also a relationship cost to anchoring hard purely for dollars. Curhan and colleagues' longitudinal study of job-offer negotiations found that how people subjectively felt about the negotiation predicted their job satisfaction a year later, while the economic outcome alone did not. Winning the number while souring the room has a downstream price. So anchor high, anchor with a source, and stay warm while you do it.

The decision rule: should you name salary first?

Two questions. That's the whole thing. The old blanket rule dies here, replaced by a fork.

Do you know the band?	Do you know where you rank in it?	What to do
Yes	Yes	Anchor high, precise, with the source named. Tie the figure to a specific reason.
Yes	No	Anchor near the top of the band, framed as market rate, and let your fit make the case.
No	No	Deflect gracefully with a calibrating question: ask them to share the band first.

The reason most untrained negotiators prefer not to make the first offer at all is a knowledge gap, not a courage gap. Close the gap and the avoidance disappears. The question was never "should I go first." It's "do I know the band." Answer that, and the rest decides itself.

What to do now

Before your next salary conversation, do the homework that converts you from the "deflect" row to the "anchor" row:

Pull the band for your exact role, level, and city from at least two sources. One aggregator and one peer signal.
Decide where you rank in that band and write the one-sentence reason, the specific work that justifies the top end.
Draft your opening line with the source named and a precise number, then say it out loud until it sounds like a fact, not a request.
Check the law where you're interviewing. If you're in a salary-history-ban or range-posting state, expect to give a number, and walk in ready with yours.

Do that and "who should name salary first" stops being a gamble. It becomes a calculation you've already run.

Want to know the real band for your role, level, and city before you walk into that conversation, not a Glassdoor guess? Message Praxy on WhatsApp and we'll pull the number and draft your opening line with you.