The Counteroffer Exposure Read: Close Now, Pre-Empt, or Keep a Backup Warm

This is the check I run on a finalist before the offer goes out. It answers two questions: how likely their current employer is to counter, and how likely they are to accept. It is for in-house recruiters, sourcers, talent leaders, and founders who close their own hires. You score five person-side and five employer-side dimensions from your interview notes and public company signals. The result is one of three verdicts: Close Now, Pre-Empt, or Keep a Backup Warm. Each verdict comes with specific moves to make before the offer goes out.

What does a counteroffer exposure read decide?

The read decides three things: how fast to close, whether to change the offer before it goes out, and how firmly to hold your runner-up. It is a forecast, because the counteroffer usually only arrives after the candidate has accepted your offer and resigned.

Two terms first:

• A counteroffer is what the current employer offers to keep someone who has resigned or said they are leaving. It is usually more pay, sometimes a title or a grant.
• A renege is when a candidate accepts your offer and then backs out before or around the start date.

When the counter arrives matters more than most counteroffer advice admits. In a Robert Half survey, as many as 28% of candidates said they had accepted a job offer and then backed out. The table below compares their reasons with those from a CareerBuilder survey of 400 staffing professionals about offers declined before acceptance.

Counteroffers make up a share 2.7 times larger after acceptance than before it. Candidates have not changed character. The current employer only finds out at the resignation, and the resignation comes after the yes. A clean read at offer stage tells you the candidate is not using you as leverage today. It does not tell you what happens when their manager sits them down next week.

The pre-offer read is a forecast of something that happens after the candidate says yes.

So the read has two jobs. Before the offer, it sets the verdict and the moves you make first. After the resignation, you score it again, because that is when the risk actually lands.

What do the public counteroffer numbers actually support?

Only one "leave anyway" figure has a named institution behind it. CEB (now Gartner) data, cited on the Dear HBR podcast, says "50% of employees who accept a counteroffer leave within 12 months." Its method was never published, so treat it as a rough direction. The 80% figure most recruiters quote has never been traced to a published study.

The 80% claim is usually credited to the National Employment Association or the Wall Street Journal. Recruiter Ken Davies, who went looking, put it bluntly: "go and try and find the original article in the Wall Street Journal". The number also changes as it gets copied. One write-up lists versions of 48%, 66%, 80%, 89%, 90%, and 93%. Another popular pair says 50% of people get a counteroffer and 57% accept it. Nobody has found the original survey behind that one either.

Some evidence points the other way, and it deserves the same scepticism. In a staffing firm's survey, 38% of employees had received a counteroffer, and 94% said the relationship afterwards was the same or better. No study with a published method tracks how many people who accept a counteroffer actually stay. That number is not established.

The size of the counter is better grounded. A ZipRecruiter survey found this:

This is the most useful fact in the research for your read. A money-only counter usually comes in well below what people say would keep them. So the real question is how your offer's uplift (the increase over their current pay) compares with a routine 10% move. If you offer 30% over current pay, the employer has to go well beyond its usual move to match. If you offer 8%, a routine counter beats you without anyone needing special approval. The same survey found that only 18% of more than 3,000 job seekers had ever used an offer as leverage. A candidate who has done it before is unusual, and that is worth writing down.

Person-side dimensions: will this candidate take a counteroffer?

The person side estimates whether this candidate would say yes to a counter. You score five dimensions from 0 (low risk) to 2 (high risk), for a total out of 10. Most of what you need comes from two conversations you already have: why they are moving, and the counteroffer question at the final round.

For each dimension, here is what it proves and how it can mislead you.

• P1. Reasons for moving. Ask at every stage, not just once. Proves: there is something the current employer cannot fix by changing a number. Misleads when: the reasons are ones you supplied earlier in the process, which fall apart when the boss pushes back. It also misleads when the reason is something the employer can grant, such as a title or a lead role. Score a fixable reason as 1, however sincerely the candidate states it.
• P2. The counteroffer answer. At the final round, ask what their current employer would need to offer for them to change their mind. Keep going until you get a specific answer. Proves: the candidate has already pictured that conversation. Misleads when: "nothing" comes out instantly. A reflex "nothing" scores 1 until they tell you why.
• P3. Offer uplift. Work out your offer's increase over their current pay. I set the bands around the 10% average counter and the 33% employees say they need; they are my own judgement, not published cut-offs. Proves: how much room a routine counter has to beat you. Misleads when: you compare base pay to base pay and miss a bonus or unvested equity. It also misleads when you don't actually know their current pay. If you cannot or should not ask about current pay where you hire, check with counsel and score from what the candidate tells you unprompted. With nothing to go on, score 1.
• P4. Leverage history. Ask how they handled their last departure, and whether their manager knows they are interviewing. Proves: whether the candidate treats offers as bargaining chips. Misleads when: the candidate hides it. The indirect question about their last exit gets a more honest answer than "would you use this as leverage?"
• P5. Resignation plan. Ask them to walk you through how they would resign: who they tell, when, and what they would say. Proves: the decision is already made. Misleads when: the plan is a script you wrote for them. The rehearsal later in the procedure tests this properly.

Employer-side dimensions: can and will the current employer counter?

The employer side estimates whether the current employer has the room and the reason to make a serious counter. You score five dimensions from 0 (unlikely to counter) to 2 (likely and able), for a total out of 10. Most counteroffer advice skips this side entirely, and most of it can be checked from public signals in about fifteen minutes.

E1: Where their pay sits in the employer's posted range

In pay-transparency jurisdictions, the employer's own job postings show its pay band for the role. In the state tracker I checked, 18 of the 51 US jurisdictions (50 states and DC) had a statewide pay-transparency law, and 15 of those required the range in the posting itself. That count keeps growing, so check a current tracker before you rely on it. Posting rules also apply above different employer sizes, and these thresholds change too:

• New York: 4 or more employees
• Colorado: all employers
• California, Washington, Illinois: 15 or more
• Massachusetts: 25 or more
• Minnesota: 30 or more
• Hawaii: 50 or more

To read it, find a current posting at the candidate's employer with the same title, level, and location, and place the candidate's pay in that band. A candidate near the top can't be matched on base pay without a promotion or a one-off grant, and those take longer and need more sign-off. A candidate low in the band can be moved with a routine adjustment. No published study confirms this effect. It is reasoning from how pay bands work.

Misleads when: the posting is for a different level or city, or is a placeholder. California defines the posted pay scale as a good-faith estimate of the expected range, so treat a very wide band as a weak signal and score it 1.

E2: Unvested value and the next vest or refresh date

At the final round, ask what they would leave unvested and when the next vest or refresh grant lands. A large unvested amount gives the employer an easy lever and gives the candidate a reason to wait. Proves: what leaving now costs them. Misleads when: the candidate doesn't know their own schedule, or quotes a paper value. Score unknown as 1. This is practitioner logic; no published source links grant timing to how often employers counter.

E3: Layoffs versus fresh money

The federal WARN Act requires employers with 100 or more employees to give at least 60 days' written notice of a plant closing or a mass layoff affecting 50 or more employees. California's version reaches employers with 75 or more. Search the public WARN databases that collect state filings, and the state's own listing. A filing that covers the candidate's site or function suggests a tight retention budget. Fresh funding, an acquisition, or a just-finished raise cycle suggests money is available.

Misleads when: the filing covers a different site. Filings are triggered by site and headcount thresholds, so they don't tell you which teams were hit, and not every state has a WARN act that requires full disclosure. Finding no filing proves nothing, so score that 1. Also, a company that has just cut deep may fight harder for the few people it cannot replace. That is why E4 sits next to this signal.

E4: Replaceability

Check whether the candidate is visibly the single owner of something the employer cannot run without. The public GitHub graph shows who maintains an employer's repositories, including anyone who is the sole or main contributor. Public profiles show whether the candidate is the only person with their title, and whether teammates have recently left. Proves: the employer has a reason to pay above its usual move. Misleads when: the public repository is not the system that matters, or the footprint is personal projects.

Checking the rest of the team by hand across public records is slow. Refolk lets me ask for that team in plain English, for example engineers at that company working on the candidate's system. It returns the people with their public profiles, which makes recent departures and a thin bench easy to spot.

E5: Counter habit

Ask the candidate: "Has anyone on your team resigned and been kept?" Proves: the employer has a routine for counters and the approvals to run it. Misleads when: one counter for a single star gets treated as company policy. Score unknown as 1.

How do ten scores become a verdict?

Add the person scores (0 to 10) and the employer scores (0 to 10), then read the verdict from the grid below. Low risk on both sides means Close Now. A person score of 6 or more means Keep a Backup Warm whatever the employer looks like. Most of the middle means Pre-Empt. The person side counts for more, because an employer with every reason to counter still cannot keep someone who won't take it.

Overrides

• Uplift under 10% (P3 = 2): the verdict cannot be Close Now. Either raise the offer or treat it as Pre-Empt at minimum.
• A counter they would take is within reach (P2 = 2 and E1 = 2): Keep a Backup Warm. The candidate has told you their price, and the employer's band can pay it.
• Unknown scores 1, never 0: missing information is a risk, not a comfort.
• Score again after the resignation: a Close Now at offer stage can become Keep a Backup Warm during the notice period.

What each verdict sets in motion

Pre-Empt changes the offer, not just the pitch. If P3 is the problem, the answer is money: get the uplift well clear of a routine 10% counter. If P1 is the problem, sell the thing the current employer cannot match, and have the hiring manager say it. If E4 is the problem, expect a bigger counter than usual and agree your own ceiling before the offer goes out, not during the notice period. No source I trust documents equity buyouts or make-whole grants as a defence against counters, so I would not build a policy on them.

Keep a Backup Warm is where a thin runner-up becomes your problem. If your second choice is weak, start a small backup slate now, while the finalist works their notice. Favour people at employers whose bands you can read, so the next read is faster. Refolk handles that kind of search in one plain-English request:

The scoring and pre-close procedure, step by step

The procedure runs from the first interview to one week after the start date. The scoring itself takes about 25 minutes: ten inside the final round and fifteen of sourcer time on employer signals. Adding up and reading the grid takes a couple of minutes on top.

Sources disagree on when to rehearse. Ambassador Group says to rehearse the resignation before the offer goes out, not after. Another practitioner puts it after the verbal yes. My rule: for Pre-Empt and Keep a Backup Warm, rehearse before the offer, because the rehearsal is a test that can change the verdict. For Close Now, after the verbal yes is fine. Either way, the person delivering the offer "should be the direct hiring manager, not an agency recruiter or internal HR".

Candidate:
Role / level / location:
Current employer:
Date scored:                Scored again after resignation:

PERSON SIDE (0 = low risk, 2 = high risk)
P1 Reasons for moving (their words, unprompted):          Score: __
   Quote:
P2 "What would your current employer need to offer
    for you to change your mind?"                         Score: __
   Answer:
P3 Offer uplift over current pay: ___%
   (over 20% = 0, 10 to 20% = 1, under 10% = 2)           Score: __
P4 "How did you handle leaving your last job?
    Does your manager know you're looking?"               Score: __
P5 "Walk me through how you'd resign."                    Score: __
PERSON TOTAL: __ / 10

EMPLOYER SIDE (0 = unlikely to counter, 2 = likely and able)
E1 Place in posted band (title, level, location matched): Score: __  Source:
E2 Unvested value and next vest or refresh date:          Score: __  Source:
E3 WARN filing for their site / fresh money or raises:    Score: __  Source:
E4 Sole owner of a critical system, or thinned team:      Score: __  Source:
E5 Known counters on their team:                          Score: __  Source:
EMPLOYER TOTAL: __ / 10

OVERRIDES
[ ] P3 = 2  ->  not Close Now
[ ] P2 = 2 and E1 = 2  ->  Keep a Backup Warm

VERDICT:  Close Now  /  Pre-Empt  /  Keep a Backup Warm
Pre-offer moves agreed with hiring manager:
Runner-up status and next check-in date:

How the read goes wrong: failure modes and false positives

The read fails in eight predictable ways. Most of them give you false comfort: a Close Now that should have been a Pre-Empt, or a runner-up released a week too early. Each one below comes with the check that catches it.

1. Quoting 80% as the base rate. It makes an accepted counter look self-correcting ("they'll be back on the market within a year anyway"), and that leads to careless runner-up decisions. Check: use CEB's 50% and say that its method is unpublished.
2. Treating the offer-stage score as the full picture. Counteroffers cause 10% of declines but 27% of reneges, because the counter only arrives after the resignation. A clean read at offer stage is a common false negative (a read that says safe when it isn't). Check: score again the day after the resignation, and call the candidate to ask what their manager said.
3. Misreading the posted range. The posting may be for a different level or location, or it may be a placeholder or a very wide good-faith estimate. Check: match title, level, and location before scoring E1. Score a wide California-style band as 1.
4. Reading a WARN filing as "no budget to counter". Filings are triggered by site and headcount thresholds, so they don't tell you which teams were hit, and some states don't require full disclosure. A company that has just cut deep may still pay up for someone it cannot lose. Check: confirm the filing covers the candidate's site or function, and read it alongside E4.
5. Treating a verbal yes as commitment, or skipping it. If the written offer goes out before a verbal yes, the candidate is holding a bargaining document. Even a firm verbal yes is a step, not the finish line. Check: no written offer without a verbal yes, and the runner-up stays on hold either way.
6. A rehearsal the recruiter scripted. Reasons you handed the candidate fall apart when their boss pushes back. Check: the candidate states their reasons unprompted. In the rehearsal, play the manager and push hard on the main reason to see whether it holds.
7. Letting the runner-up go too early. If you only check in until the offer is signed, you miss counters during the notice period and no-shows. Check: keep them warm through the start date plus one week.
8. Assuming money motivation means low risk. "They just want more money, and we're paying more" sounds safe. But employees say they need 33% and counters average 10%. If your increase is under about 10%, a routine counter can match it. Check: work out your offer's uplift over current total pay, not just base.

There is one false positive worth naming too. A high employer score paired with a low person score is not a reason to raise the offer. It means the employer will try and the candidate will probably hold. The right move is to rehearse the resignation and shorten the timeline, not to bid against a counter that hasn't happened yet.

Holding the runner-up and keeping the read current

Keep the runner-up warm until your hire has physically started and cleared their first week, whatever the verdict. The verdict only changes how often you talk to them. As many as 28% of candidates say they have backed out of an accepted offer, and those losses land in the notice period, long after the read was taken.

Say it by phone first. Then put it in writing the same day, so the runner-up never finds out from someone else.

CALL
"[Name], I want to be straight with you. I've extended an offer to another
finalist for the [role] position. You were a very close second, and if it
doesn't go ahead, you're the first person I'll call. I'd like to stay in
touch until their start date, which is around [date]. Is that alright with
you, and is there anything on your side, like another process, that I
should know about?"

FOLLOW-UP NOTE
Subject: Where things stand on the [role] search

Hi [Name],

Thanks for your time today. To put it in writing: an offer is out to
another finalist, and you are my next choice. I'll check in on [date] and
again around their start date on [date]. If anything changes on your side
before then, tell me, and I'll tell you where things stand on mine.

[Your name]

Three things go stale and need re-checking:

• The pay-transparency map. Jurisdictions get added and posting thresholds change. Re-check a current state tracker before relying on E1 in a new state.
• WARN coverage. Public WARN databases depend on state filings, and states differ in what they require. When a filing matters to a verdict, confirm it against the state's own listing.
• Your own calibration. No study with a published method tracks counteroffer outcomes, so your log is the best evidence you will have. For every finalist, record the verdict, both scores, and what happened: accepted, resigned, countered, took the counter, started. After enough hires to show a pattern, move the cut-offs to fit.

Run this before every offer goes out: