You spent three weeks interviewing, survived five rounds, and then the number lands on the table: 18% below what you know the role pays. Or you're the seller, and the buyer's offer reads like a typo. Either way, the temperature in the room changes. Your first instinct is to say something you'll regret, and your second is to say nothing at all.
Neither is good. I've been on both sides of this exchange. I've made bad counteroffers that cost me deals, and I've let a lowball slide once that quietly poisoned a working relationship for months. So let's talk about countering a lowball offer without damaging the relationship — because the two goals are not in conflict, even though they feel like it.
Key takeaways
- Almost always counter. A lowball is an anchor, not a verdict.
- Never negotiate against the number first. Reopen the criteria: scope, seniority, timing, comparables.
- Counteroffers fail relationally when they sound like a verdict on the other person's character.
- Give a specific number and a specific reason. "That's too low" is not a counteroffer.
- Leave the other side something to say yes to — a trade, not a demand.
- If it ends badly, making the exit graceful protects your reputation more than winning would have.
Should you counter a lowball offer?
Yes. Nearly always. The exceptions are narrow and I'll get to them, but the default should be to respond with a number.
Here's the thing most people get wrong: they treat a lowball as information about their worth. It usually isn't. It's information about the other party's position — their budget, their leverage, their fear of overpaying, or simply their habit of opening at the floor because it worked before. When I sold a small consulting package a couple of years ago, the first reply I got was roughly 40% under my quote. My stomach dropped. Then I realized the buyer hadn't rejected my proposal. They'd just started the conversation. We closed 11% below my original number, which was fine — and I would have gotten nothing by staying silent.
When silence actually is the right move
Three situations where I'd think twice. If the offer is so far below market that negotiating feels like repairing a car with no engine, walking is cleaner than haggling — the gap signals a fundamental mismatch in how the other side values the work. If the relationship matters more than the deal and the number is marginal, accepting and noting it can pay off later. And if you've already given your bottom line and they came back lower anyway, a second counter teaches them your numbers are fiction.
Everything else? Push back. Politely, specifically, and with a reason.
What is the best way to respond to a lowball offer?
Separate the number from the person, and do it in the first sentence. That single move does more for the relationship than any script.
Bad opening: "This is well below what I'd expect." True, but it lands as a judgment of the sender.
Better opening: "Thanks for putting a real number on the table — that makes this easier. Let me show you where I land and why."
The second version signals you're negotiating, not litigating. It costs you nothing and buys you room to be firm later.
The four-step response structure I use
- Acknowledge the offer concretely. Name it. "I see 62,000." Vagueness reads as evasion.
- Return to criteria, not feelings. Bring back the scope, the market comparables you can honestly cite, the level of responsibility. "The role includes managing two people and owning the reporting line — that's the part the number seems to be missing."
- Give your number with a reason attached. One sentence of justification, followed by the figure. "Based on that scope and what comparable roles are paying in this market, I'm at 74,000."
- Offer a trade or a path. "If that's outside the band, I can work with 70,000 plus a review at six months." Now they have something to accept.
Notice what's absent: any sentence beginning with "You." Relationship damage almost always comes from making the other person the subject of a criticism.
What not to do
Don't counter with a number you invented to leave negotiating room. I did that once — countered 30% above what I'd have accepted happily — and the buyer read it as me being unserious. The conversation never recovered its tone. Anchor honestly, slightly above your target, and be able to explain every zero.
How to counter a lowball job offer
Job offers are the hardest case because the power imbalance is real and the relationship is long-term by design. You'll be working with these people. Getting this wrong doesn't just cost you a deal, it costs you your first six months.
The good news: hiring managers expect a counter. Most offers are built with a little room precisely because the recruiter assumes you'll ask. What they don't expect is a counter that feels like an ultimatum.
Do your homework before you respond
You need two numbers before you open your mouth: a defensible market figure and your actual walk-away point. Not the number that would make you happy — the number below which you'd decline. Write it down. People who negotiate without a floor tend to accept whatever ends the discomfort.
When you can't verify what the role pays elsewhere, use your own search: what did the last three people at your level in this function get? What did the recruiter's own range say in the first screening call? That first range is often the most honest data point you'll get, and it's worth referring back to. "When we spoke in January, the band was described as 70 to 80. The offer sits outside that." Calm, factual, impossible to argue with.
Script for the call
Have it live, not in an email — email negotiation on salary tends to harden positions. Something like:
"I'm genuinely glad we're at this stage, and I want to say yes. The number is a bit below where I can make it work given the scope we discussed — two direct reports and the migration project. Is there flexibility to get to 72? If the base is fixed, I'd love to talk about the review timeline or a signing component."
"I want to say yes" is doing a lot of work in that paragraph. It tells them you're not shopping, you're solving.
If they can't move on base
Total compensation has more moving parts than most candidates use. Ask about the review cycle and whether it can be pulled forward, signing bonuses, an extra week of leave, a training budget, remote days. None of those damage the relationship because none of them require the manager to admit the base was wrong. I've seen a candidate turn a flat "no" on base into a substantially better first year by asking for a review at five months instead of twelve. The manager was relieved — she had room in one bucket and not the other.
Is a lowball offer disrespectful?
Sometimes. Not usually.
I'll be blunt about this because I think the framing does real damage: treating every low offer as an insult is the fastest way to guarantee you damage the relationship, because you'll respond to the perceived disrespect rather than to the number. In my experience, most lowballs come from one of four places — a rigid budget, a negotiator following a script, an honest but conservative valuation of the role, or a deliberate test of how you handle pressure. Only the last one is a character problem, and you'll only find out which it was by countering calmly.
What is disrespectful: an offer that ignores a scope you already agreed on, a number delivered without explanation after you shared your expectations, or a pattern of moving the goalposts. Those aren't negotiation openings. Those are data about the counterpart.
So the honest answer is: it depends, and the counteroffer is how you find out. Which is a good reason not to burn the bridge while you're still gathering evidence.
Keeping the relationship intact while you push back
Here's what actually protects a relationship through a hard negotiation, ranked by how much difference it makes.
- Speed. Respond within 24 to 48 hours. Long silences get read as games, and games are what people remember.
- Specificity. Vague pushback ("I was hoping for more") is harder to work with than a clear number and reason.
- Acknowledging their constraint. One clause: "I understand the band may be fixed on your side." It costs nothing and signals you're not assuming bad faith.
- Never negotiating through a third party when you can talk directly. Recruiters are useful allies, but positions soften in direct conversation and harden in relayed messages.
- Closing the loop either way. If you decline, say why, briefly, and thank them for the specificity of the offer. Half the people who lowballed me later came back with a better proposal — one came back eight months later with a role at 25% above the original figure, because the first conversation had stayed civil.
The comparison that matters
Two ways to frame the same pushback, with very different relational consequences:
| Approach | What it sounds like | Effect on the relationship |
|---|---|---|
| Verdict | "This offer is insulting given my experience." | Puts them on the defensive; the conversation becomes about their judgment |
| Criteria | "Based on the scope we discussed, I expected closer to X. Here's the reasoning." | Keeps the conversation about the role; disagreement stays professional |
| Ultimatum | "X or I walk." | Fast, occasionally effective, rarely recoverable |
| Trade | "If base is capped, could we look at the review timeline?" | Gives them a way to say yes without losing face |
That third row is worth dwelling on. Ultimatums work — sometimes. But even when they win you the number, they set the tone for everything after. I've never seen a working relationship recover fully from one, and I've seen several start badly because of one.
When it goes badly anyway
You can do everything right and still watch it fall apart. It happened to me on a project bid where I countered ~15% above a lowball with what I thought was an impeccably reasoned email. The client replied in two lines, chose someone else, and I spent a week convinced I'd been too aggressive.
Then I reread my email. I'd opened with "I was surprised by the figure." That phrase — surprised — implied they'd done something strange. I hadn't meant it that way. But intent is not what the other person reads.
What I do differently now: before sending any counteroffer, I read it once imagining I'm the recipient who has already had a long week. If any sentence reads as a comment on my competence, I cut it. Counteroffers should be about the work, the scope, the market, the timing. Never about what the other person must have been thinking.
And if the deal dies? Say thank you, mean it, and leave the door visibly open. The professional world is smaller than it looks. The number you didn't get is temporary. The reputation for being someone who negotiates firmly and without contempt is not.
Which is really the whole point. A counteroffer is a test of whether two parties can disagree about a figure and still want to work together. The ones who can are worth the trouble of finding out.
