Counter Offer

When somebody resigns, a company does one of two things: let them go, or try to keep them. Before the second one had a name, it mostly happened on impulse. A manager, caught off guard, asks what the other place is paying. The words "let me talk to someone upstairs" come out on the spot. Three days later a 15 percent raise lands. No process meant no standard, and the result depended entirely on who was in the room.

The damage showed up first among the people who stayed. At Pagedeck an engineer brought in an offer — a written proposal of joining terms — from another company, and Grace agreed on the spot to match the salary. A colleague one desk over had delivered comparable work that year and nothing happened. It took two weeks for the difference to travel through the team, and by the next quarter people were describing Pagedeck as the place where you have to threaten to quit before anything moves.

The term exists to turn that improvised save into something a company can actually review before doing it. The name gives away the direction. In hiring, a company proposes terms to someone who hasn't joined yet. In a counter offer it is proposing terms to someone already inside, against conditions a rival company put on the table first.

A counter offer moves through five steps, and the improvised version almost always skips the first two.

1. Resignation received — the person tells their direct manager they are leaving. Money doesn't come up in this conversation. Numbers said reflexively in the first ten minutes tend to get walked back, and a walked-back number costs whatever trust is left.
2. Fact-finding — is there a real offer, from which company, for which role, on what terms? A move that only raises pay and a move that changes the work entirely leave a company with completely different things to match. If the reason for leaving is a person rather than a package, money never reaches it.
3. Internal review — decide whether to make the attempt at all. Weigh the cost and elapsed time of refilling the role, the work the person is currently holding, and the compensation of everyone else at that level. An exception carved out for one person comes back as ten people's questions at the next performance review.
4. The counter — if the answer is yes, bundle the raise, the title change, the shift in scope, and any extra stock options into a single proposal. Raising the number in stages tells the other side there is more above it, and the negotiation never closes.
5. A deadline — three days to a week to respond. Leaving it open gives the person time to go back and renegotiate elsewhere, and costs the company the window it had to start looking for a replacement.

Three people are involved, and they enter at different points.

The direct manager hears it first. Steps 1 and 2 belong almost entirely to this person, and the job there is not persuasion but getting the real reason stated accurately. The people team enters at step 3, checking the salary band for that level and calculating how far the proposal bends it — left to the manager alone, the company-wide view simply drops out. A founder or executive approves at step 4. Anything beyond budget, or any change in level, cannot go out without that approval.

On timing, the dividing line is whether the person has already signed with the new company. Before signing, it's a comparison of terms. After signing, the person has to break a commitment to accept, which is a different kind of decision. Companies sit on the receiving end of this too: a candidate accepts your offer and then loses to their current employer's counter. This is usually the moment Pagedeck recalculates time to hire from 60 days to 90.

"Theo said he's leaving. Do we want to put a counter offer together?"

A request to make the keep-or-release decision at the company level instead of the manager deciding alone.

"We have a policy of not making counter offers."

A decision made in advance, on the view that matching terms for anyone who threatens to leave dismantles the pay structure.

"She'd already accepted, but her current company came back with a counter offer."

A candidate who had confirmed a start date is now wavering because of a counter, so prepare for it to fall through.

At Pagedeck the phrase travels in both directions. Inward, it surfaces the week Theo says he's leaving, when Grace and the people team sit down together. If Theo's reason turns out to be the scope of his work rather than his salary, Grace's move is to redraw next quarter's assignments rather than raise the number. Outward, it surfaces while Sofia is filling a sales role: when a candidate stops answering two weeks before the start date, the current employer is usually the reason.

Both directions point at the same thing. By the time a counter offer is on the table, it's already late. The work worth doing is the retention conversation that happens long before anyone resigns.

The most common mistake is assuming that accepting a counter offer resolves the problem. The person named salary as the reason, salary went up, so the logic holds on the surface. But deciding to leave usually takes months, and what accumulates over those months tends to be the absence of a next step or a manager relationship that stopped working. Salary is simply the easiest version of that to say out loud. Left alone, the same conversation returns about six months later, except the company has now spent every card it had. This is why teams often tag counter-offer saves separately when reading turnover rate.

There is a matching mistake on the company side: the belief that keeping someone is cheaper than replacing them. On immediate cash, that's true — a 10 percent raise costs less than running the entire hiring process again. What that 10 percent does not do is stay with one person. The moment others at the same level learn about it, it becomes the reference point, and the cost of meeting that reference at the next review attaches itself to the original decision. The arithmetic belongs at the level, not at the individual.