Should You Counter a Resignation? A Framework for Retention Offers
A decision framework for when a counteroffer actually fixes the problem, and when it just delays a search you'll end up running anyway.
Counter only when the resignation is driven by something money or title can genuinely fix, not when it's a symptom of manager conflict, stalled growth, or burnout. Even a successful counter usually buys limited time before the employee leaves anyway, so treat it as a bridge, not a solution, and start sourcing a replacement in parallel.
The Counteroffer Reflex
A resignation letter lands on a manager's desk and the first instinct is almost always the same: stop the bleeding. Someone calls HR, HR calls the manager's manager, and within a day or two there's an approved bump in pay, a new title, or a promise of a promotion that was six months out suddenly being pulled forward. The whole exercise happens under time pressure, usually inside 48 hours, because everyone knows the longer it sits, the more real the departure becomes.
The problem is that a counteroffer answers the wrong question. It asks what will keep this person in the chair next Monday. It doesn't ask why they decided, on their own time, to go sit through interviews, negotiate an offer, and hand in a resignation letter in the first place. Those are different questions, and the gap between them is where most counteroffers quietly fail six to eighteen months later.
Diagnose Before You Negotiate
Before any number gets discussed, separate the resignation into what's actually driving it. A straightforward comp gap, where a competitor is simply paying more for the same scope of work, is the one driver a counteroffer can genuinely address. So can a legitimate career-stall issue, where the employee has outgrown their title and the fix is a real scope or title change you'd have made anyway, just accelerated.
Everything else tends to resurface. Manager conflict doesn't go away because the paycheck got bigger. Burnout doesn't resolve with a raise; it just gets more expensive to watch play out. A life event, like a spouse relocating, isn't solved with money at all. And an employee who's been quietly disengaged for a year and finally acted on a recruiter's cold outreach is often telling you, indirectly, that the relationship was already over before the offer letter showed up.
The fastest way to run this diagnosis honestly is to ask the employee directly, before any counter is discussed: if we fixed the comp gap today, would you stay for the next two years, or does this money just buy you time to keep looking? Most people, if asked plainly and without defensiveness, will tell you the truth.
What a Successful Counter Usually Buys
Even when the root cause is fixable, it's worth being realistic about the shelf life of a counteroffer. The employee has now been through the exercise of interviewing elsewhere, has a sense of their market value, and knows that resigning got them a faster raise than asking did. That knowledge doesn't disappear. It changes how they approach the next compensation conversation, and it often changes how leadership quietly views them afterward, flight risk being a hard label to fully remove once it's been attached.
There's also a visibility problem. Compensation conversations don't stay as private as people assume, especially on a team of five or ten where everyone has a rough sense of each other's pay band. Once one person gets an off-cycle raise tied to a resignation, the lesson their peers learn isn't subtle: the fastest way to get a raise here is to threaten to leave. That's the mechanism by which a single counteroffer turns into a pay compression problem across the rest of the team within a year.
The Math That Actually Matters
Run the comparison with real numbers before you approve anything, even hypothetical ones for now. Say a mid-level analyst earning 85,000 dollars gets an outside offer at 98,000, and you counter at 95,000 to close the gap and keep the title intact. That's a 10,000-dollar annual increase, plus whatever it does to the comp band for two or three peers in similar roles who will ask for the same thing at the next review cycle.
Now compare that to the cost of letting the person go: the open seat sits for a stretch while you run a search, there's a fee on the eventual hire, and there's a ramp period before the replacement is fully productive. If the countered employee leaves anyway nine months later because the underlying issue was never comp, you've paid the counter's cost, absorbed the peer pay-compression fallout, and you're running the exact search you were trying to avoid, just later and with less runway to plan it.
Run the Parallel Track
Whatever you decide on the counter, don't let the decision stop you from preparing for the scenario where it doesn't hold. If the role is senior enough that an open search would be visible or disruptive if it leaked, this is exactly the situation a confidential search process is built for: you can quietly start building a slate for the role without announcing that the incumbent might be leaving, so you're not starting a search from zero the day they hand in a second resignation.
For less senior roles, the parallel track can simply be an honest internal conversation with your recruiting partner about the role's market comp and candidate availability, so you have a current read on what a replacement search would actually cost and take, rather than guessing under pressure the second time around.
A Simple Decision Rule
Before approving a counter, answer three questions honestly. First, is the resignation driven by something money or title alone can actually fix, or is it a symptom of something else entirely? Second, would you have made this raise or promotion proactively if the resignation letter had never been written, or is this purely reactive? Third, can you live with the precedent this sets among the employee's peers once they inevitably find out?
If the answer to any of those is no, the counter is probably buying a delay, not a fix. In that case, the better use of the next 48 hours is accepting the resignation on good terms and opening the search immediately, while the job description, comp range, and sourcing plan are still fresh in everyone's mind.
Frequently asked
Good questions.
Does accepting a counteroffer make an employee less trustworthy going forward?
Not automatically, but it does change the dynamic. Managers tend to be more cautious about handing that person a stretch assignment or a long-term project lead, simply because the organization now knows this employee is willing and able to leave. That's not always fair to the employee, but it's a common and predictable side effect worth planning for rather than ignoring.
Should a senior leader's resignation be handled differently than an individual contributor's?
The stakes are higher but the diagnostic is the same: figure out what's actually driving the decision before negotiating. What changes at the senior level is the downstream disruption if they leave anyway, which is why confidential backup sourcing matters more for leadership roles than for individual contributor ones.
What if the employee rescinds their resignation before we've responded at all?
Treat it as useful information, not a resolved issue. An employee who rescinds without a counter being offered was often testing the market or using the offer as leverage rather than planning to leave. It's worth having the same root-cause conversation anyway, since the underlying driver that sent them job hunting hasn't necessarily gone away.
Is it worth matching a competing offer dollar for dollar?
Matching exactly isn't the point; fixing the actual gap is. If the competing offer reflects a legitimate market correction, closing most or all of that gap can make sense. If the offer is inflated or includes components you can't realistically replicate, chasing the exact number usually isn't worth the precedent it sets for the rest of the team.
Ready to make the hire?
Tell us the role, the comp band, and the timeline — we'll tell you exactly how we'd run the search.