Three Checks Before You Accept a Counteroffer From Your Employer

A counteroffer is not a raise, even though it arrives wearing one. A raise is what a company pays for work you are already doing, decided in a planning cycle, benchmarked against a band. A counteroffer is what a company pays to not have to solve your absence this quarter, decided in about a day, benchmarked against whatever number you just handed them.

Ilona had spent four years building the refill adherence reporting at Brimmond Specialty Pharmacy. She resigned on a Tuesday for a role at Ardveigh at 142,000, up from the 118,000 she was on. By Thursday her director Fintan had come back with 136,000, the title Principal Data Engineer, and a sentence she would replay for a week: "You do not have to leave to get this."

Here is the honest answer to whether you should accept a counteroffer from your employer. Accept it only when money was genuinely why you started looking, and when the new number puts you where the market already said you belonged rather than close enough to make leaving awkward. If you left for anything else, scope, a manager, a promise that kept sliding, a counteroffer pays you to keep the problem. Three checks tell you which case you are in, and none of them is "does the number feel good."

Nothing about a counteroffer is an insult, and nothing about it is affection either. It is a purchase with a clear price.

When you resign, your manager inherits a dated cost: a role to backfill, a hiring loop that takes weeks, a ramp that takes months, and meanwhile your work spread across people who already have their own. If you hold knowledge that is written down nowhere, and most senior individual contributors do, that cost climbs and lands on the manager who has to explain the slipped roadmap.

Against that, another 18,000 a year is cheap, and it is available immediately. Retention money often sits outside the normal merit cycle precisely so it can be spent fast. That is why a counteroffer can appear in two days when a raise you asked for in March took two quarters to get a no.

So the number going up tells you almost nothing about how you are valued. It tells you the replacement was expensive and the retention budget was liquid. Both were true last month too.

Yes, in a narrower set of cases than the internet suggests. The common advice that you should never accept one is too blunt to be useful.

A counteroffer is worth taking when three things line up: money was the actual reason you opened the other conversation, the new figure moves you to a defensible position in the band for your role rather than a few thousand above where you were, and whatever you would be walking toward elsewhere is something you can get where you are. Someone underpaid for years by a slow merit process, who likes the work and the people, has just found the one lever their employer responds to. Taking the correction and staying is a real answer.

It is not worth taking when the number is the only thing that changed. If the reason you interviewed was the work, the reporting line, the ceiling above you, or a promise that has been rescheduled twice, the counteroffer is a payment for continuity. Continuity of exactly what you were trying to leave.

Run all three before you answer. Together they take an evening, and they are the difference between a decision and a reaction.

The check	The question it asks	What a yes looks like	What a no looks like
The band, not the bump	Where does the new number sit in the published or inferred range for this role, at this level, in this city?	The counteroffer lands at or above the midpoint of the band, which means they corrected an underpayment.	The counteroffer is calculated from your old salary, or from the outside offer minus a little, and still sits under the midpoint.
The reason you looked	Write the sentence you told a friend in week one of interviewing. Does more money change it?	The sentence was about pay, and nothing in it survives the new number.	The sentence was about the work, the manager, the ceiling, or a promise. The number does not touch any of it.
What changes on Monday	Besides payroll, what is different next week, and who has written it down?	A named scope change, a named reporting line, or a dated review, in an email you already have.	A title with no new authority, and reassurance delivered verbally by the person who benefits most from you staying.

Ilona's first check took ten minutes. The band for a principal engineer at Brimmond ran from 124,000 to 158,000, and her 118,000 had been sitting below the floor of the band for the job she was already doing. The counteroffer of 136,000 was a real correction of that, and it was still 5,000 under the midpoint of a range she had been under the floor of for two years. The 18,000 felt like a windfall because it was measured against her own underpayment.

Her second check decided it. The sentence she had told a friend in February was "I have asked to rebuild the reporting stack three times and it keeps getting pushed to next quarter." No salary figure changes that sentence.

How bands, ranges and evidence work across a full comp conversation is in the salary negotiation guide. This page is the version where the offer comes from the employer you are already leaving, which makes the conversation warmer, faster, and much easier to lose.

Thursday afternoon, Fintan's office. He is not manipulating anyone. He is a competent manager doing the reasonable thing, which is precisely why this conversation is so easy to slide through.

The version where the meeting decides for her:

Fintan: I talked to finance last night. We can do 136 and Principal, effective the first. I do not want to lose you over a number.

Ilona: That is really generous. Thank you. I honestly did not expect it.

Fintan: You should have had it sooner. That is on me. So, can I tell them you are staying?

Ilona: I mean, yes. Yes, I think so. Let me just tell Ardveigh today.

Three things went wrong and none of them sounded like a mistake. "That is really generous" priced the offer against her old salary instead of the band, out loud, in front of the person who set both. "I honestly did not expect it" handed over the fact that she has no idea what the role is worth. And "yes, I think so" answered a question about the number, while the thing that made her leave went unmentioned by either of them. The reporting stack is not in this conversation, and it will not be in the next one either.

The version where she keeps the decision:

Fintan: I talked to finance last night. We can do 136 and Principal, effective the first. I do not want to lose you over a number.

Ilona: Thank you for going to get that, genuinely. I want to be straight with you about something, because I would rather say it now than in six months. The number was not why I interviewed.

Fintan: Okay. Then what was?

Ilona: The reporting rebuild. I have raised it in three planning cycles and it has moved each time. That is the piece Ardveigh is hiring me to own from day one.

Fintan: That is fair. I think we could scope that for you.

Ilona: Then here is what would make this a real decision for me. Can you put in writing what I would own, who signs off on it, and the quarter it starts? And separately, 136 is under the midpoint of the principal band. If the title is changing, I would want the number to sit at the midpoint. I can give you an answer Monday.

The second version is not tougher, it is slower. She thanked him for the effort and declined to price it. She named the actual reason out loud, which is the only way it ever gets addressed and the thing almost nobody says. She asked for the promise in writing, which costs him nothing if he means it and everything if he does not. She corrected the number against the band rather than her old salary. And she took the weekend, because a decision made inside the meeting is made by the person who called it.

There is a Monday where Fintan returns with a written scope and 141,000, and staying is clearly right. There is a Monday where the writing never arrives. Both are answers, and she gets either one only by not saying yes on Thursday.

Money is the easiest part of a counteroffer to verify and the least likely part to be the problem. Everything else in it is spoken.

Titles are the usual sleight of hand. Principal Data Engineer with the same scope, reporting line and say over the roadmap is a word, and words do not survive a reorg. Ask what the title changes about what you decide. If the answer is a pause, you have learned something.

Retention promises expire quietly. "We will get to the rebuild next quarter" is the sentence that was said last quarter, now said by someone under pressure. Ask for the quarter, the owner and the sign-off in an email. A manager who means it will send it that week.

Then there is the thing nobody says out loud. In some organizations a withdrawn resignation becomes a known fact about you, and it shapes what you get handed for a while. Not universal, not always fatal, but real often enough to watch for. The tell is not what people say in the first month. It is what you are quietly not asked to lead in the third.

And if the counteroffer arrives before you hold a signed contract from the other company, you are being asked to trade a live option for a verbal one. Do not accept one that requires that.

Most of the damage in a counteroffer conversation happens in about nine seconds, between the number landing and your face reacting to it. You do not need a script for the whole meeting. You need two lines that buy you the weekend.

The first thanks them without pricing the offer: "Thank you for going and getting that. I want to give it a proper answer rather than a fast one."

The second names the real reason, the only sentence in the meeting that can change anything: "The number was not why I interviewed. It was X, and that is what I would need to see move."

Write both down before you hand in your notice, not after the counteroffer arrives, because after is when you are flattered and tired and want the discomfort to end. Then say them out loud once. The gap between a written sentence and a spoken one is wider than it looks, and the save meeting is a poor place to find that out.

Before the next one of these lands on you, run the two lines at someone who pushes back. The asking for a raise scenario puts you across from a manager with reasons of their own, and practicing the raise conversation covers rehearsing the ask itself. Neither is the counteroffer meeting exactly, and both train the nine seconds that decide it.