What to do if you get a lowball offer

A lowball offer is a specific kind of disappointment. Five rounds of interviews, three weeks of waiting, the email finally arrives, and the number is fifteen to twenty thousand dollars below what the role should pay. The instinct is to feel insulted. The next instinct is to feel grateful, because at least the offer exists. Neither instinct produces a good decision.

A lowball is a starting point, not a verdict. About half of lowball offers in 2026 are first numbers that the company expects to move. About a quarter are sincere — the company genuinely does not pay more for the role, often because they have a tight internal band. The last quarter are signals that the company does not value the role highly enough to keep someone in it for long. Telling the three apart, and acting accordingly, is the work.

How to know if it is actually a lowball

The first move is not to react. The first move is to check.

Most candidates do not have a reliable picture of what the role should pay. The number that “feels low” is often anchored on the candidate’s last salary, which may have been above or below market, especially after a layoff. The honest check is against external sources.

Three sources to triangulate:

• Levels.fyi or a published band for the role at this level. For tech roles, Levels.fyi is the strongest single source. For other industries, look for the company’s posted ranges on its careers page, required by law in several states
• Glassdoor or Payscale for the company at your level. Often noisier than Levels.fyi, but a useful second data point
• A back-channel conversation with one or two people who work in similar roles at similar companies. This is the most useful source if you have it, and the hardest to come by. A direct ask to a former colleague — “what is your team paying for senior product managers right now?” — usually gets a real answer

Take the middle of the three. Compare to the offer.

• More than 15% below the middle — a lowball. Counter with conviction
• 5–15% below — a normal starting position. Counter once and accept what lands
• Within 5% of the middle — a fair offer. Counter for the principle and accept

If the three sources do not roughly agree, the role is in a band the market has not settled on yet. In that case, use the highest credible source as the anchor and counter to that number with a reason.

The three honest options

A lowball offer has three responses, and the right one depends on the size of the gap, the runway, and the rest of the package.

Counter

The default response. A specific number, a specific reason, in writing.

A worked example, after an offer that came in fifteen thousand dollars below market:

“Hi Jamie — thank you for the offer. I am very interested in the role and the team. Looking at the market range for this level — Levels.fyi shows the middle of the band for senior PM at companies your size at around one-eighty, and that matches what I have seen from a couple of recent conversations — I was hoping we could land base at one-eighty. Is there room there, or could we get there through a combination of base and sign-on?

Either way, please know I am genuinely interested. Happy to talk it through on a call if useful.

Best, Pat”

That counter does five things at once. It names a specific number. It names a specific source. It opens the door to a creative answer involving multiple components. It confirms interest without sounding desperate. And it offers a call, which makes the negotiation feel like a conversation rather than an ultimatum.

The recruiter almost always responds with something. Sometimes the full ask. Sometimes a partial. Sometimes “the base is firm, but we can do a sign-on of ten.” The response tells you what kind of company you are dealing with.

Decline

The right move when the gap is too large to close in one counter, or when the lowball is paired with other signals — a defensive recruiter, a manager who does not push back internally, a sense that the company is undervaluing the role on purpose.

A clean decline is short and professional. No long explanation. No critique of the offer. No suggestion that the company “come back when they are ready” — that closes the door without elegance.

A worked example:

“Hi Jamie — thank you for the offer and for the time the team put into the process. After reviewing the package against where the market is for this role, the gap is larger than I am able to close on my side. I want to be straightforward rather than draw the conversation out. Wishing the team well, and I hope our paths cross again.

Best, Pat”

Two short paragraphs. Calm. Not bitter. Not lecturing. The recruiter knows what happened and the team can move to the next candidate. The relationship is preserved for a future conversation that might come back around in a year or two.

Decline when the math is honestly impossible — when the offer is so far below the role’s value that a counter would only embarrass both sides, or when accepting would actively damage your earning trajectory for the next decade.

Accept

The right move in three narrow cases.

Runway is short. If the math says you have under sixty days of liquid runway, the lowball offer is bridge income, not your forever role. Take it, do the role well for a year, and search again from a position of stability. The cost of staying unemployed for another two months is usually larger than the cost of a year at below-market pay.

The role is a real pivot. If you are deliberately changing industries or functions, the first role often comes in below your prior compensation. A reasonable pay cut to break into a new field is a real investment. The way to know if the cut is reasonable is to compare against entry points into the new field, not against your previous role.

The rest of the package is strong. Sometimes the base is low but the equity is significant, the growth path is clear, the manager is excellent, and the company is on a real trajectory. In that case, the base is not the whole story. Total compensation, plus the value of being in the right room for two years, can outweigh a soft starting number.

Accepting a lowball offer is the right move sometimes. It is wrong when it is taken from panic. The way to tell the difference is whether you can name, in one specific sentence, the reason the offer is worth accepting. “Because I need a job” is not that sentence. “Because the equity grant is twice what comparable companies are offering, and the manager is the strongest I have interviewed with in two years” is.

The components beyond base

Most lowball offers have more flex outside of base than inside it.

The five places to look:

• Sign-on bonus — often the cleanest concession. A company that cannot move on base can frequently add a one-time sign-on of ten to thirty thousand
• Equity grant — at private companies, often the largest dollar number on the offer and frequently negotiable by 20–30%
• Bonus target — sometimes flexible on the target percentage, especially at companies where the base is constrained by internal banding
• Vesting — sign-on cliff, equity cliff, acceleration on involuntary termination. The last one is worth asking for in senior roles and almost never raised by the company on its own
• Other — additional PTO, signing-year bonus protection, relocation, learning budget, remote allowance. Smaller dollar amounts individually, sometimes meaningful together

If the recruiter says base is firm, the next sentence is, “Got it — can we look at the rest of the package? I would be glad to talk through what would close the gap.” That sentence keeps the negotiation alive without arguing the same point twice.

CareerCanopy is built for exactly the moment where the offer is in front of you and the math says counter, and the runway says accept, and you are not sure how to weigh them. The frame above does not eliminate the tension. It makes the trade-off explicit so the decision can be made once, deliberately, instead of relitigated for the next six months.

What to say to buy yourself time

A common pressure tactic on lowball offers is to ask for a quick decision. “We need to know by Friday.” Push back politely.

The phrase: “I want to give this the consideration it deserves, and I would like a week to review the full package. Can we land on next Wednesday?”

That sentence is rarely refused. If it is refused, the refusal is itself information about the company. A team that cannot give a candidate a week to consider an offer is a team that will pressure decisions in the same way once you are on the inside.

In the week you have, do three things. Run the market check above. Talk to one person who knows you well, not who knows the company well. Sit with the decision overnight before responding. The instinct to respond fast — to show eagerness, to lock in the offer before it disappears — is almost always wrong. Offers very rarely disappear in a week.

A short worked example, end to end

A senior marketing leader was laid off in February. By May, she had her first offer — base of one-thirty for a role where the market middle was one-fifty-five. Her runway was four months.

The check: Levels.fyi did not cover marketing roles cleanly. Glassdoor for the company showed a range of one-thirty-five to one-seventy for senior marketing at her level. A back-channel call with a peer at a comparable company confirmed one-fifty-five was middle of band.

The counter: “Looking at the market range for the role, I was hoping we could land base at one-fifty-five. If there is not room there on base alone, would a combination of one-forty-five base and a fifteen-thousand sign-on work for the team?”

The response: the company came back with one-forty-five base and a ten-thousand sign-on.

The decision: she accepted. The total comp was close enough to market that the residual gap was within the noise, the manager had been strong throughout the process, and her runway was tight enough that further negotiation was not worth two more weeks.

That is what most lowball negotiations look like when they go well. A specific counter, a partial response, an accept at a number that is close enough. Not the full ask. Not a victory. A reasonable offer arrived at honestly.

What not to do

A short list of moves that hurt the candidate.

• Accept the lowball without countering — almost always the wrong call, even when the runway is tight
• Counter with a wide range instead of a specific number — gives the company permission to land at the bottom of it
• Reveal your last salary — anchors the conversation on history, especially damaging after a layoff
• Pretend to have a competing offer — falls apart the moment the recruiter asks for details
• Make the counter feel adversarial — “I expected better” or “this is disappointing” closes doors that did not need to close
• Slow-walk the response — wait the week you asked for, then answer cleanly

The good counter is short, specific, anchored on market, and paired with continued interest. The bad counter is long, vague, anchored on history, and laced with emotion. The difference between the two is often the difference between a closed offer and a missed one.

The simple summary

A lowball offer is a starting position. The default response is to counter with a specific number and a specific source. The right number is the middle of the market band, not your last salary. The right tone is professional and forward-looking, not defensive. Accept when the runway is short, the role is a real pivot, or the rest of the package is strong. Decline cleanly when the gap is too large to close.

The candidate who handles a lowball well is the candidate who treats it as a conversation, not as an insult. Most of the time, the conversation ends with a reasonable offer. The hour it takes to do it well is one of the highest-return hours of the entire search.