Back to insights

How to Respond When an Employee Asks for a Raise

Abstract dotted curve rising on a dark blue background, representing a raise request as a compensation signal.

When an employee asks for a raise, most managers get stuck on the number. That is often the least useful part of the conversation. The better question is what the request is telling you about market value, retention risk, and whether your system only reacts when someone is halfway out the door.

Author

Ed Khristus

Category

HR & People Ops

Published

25 May 2026

When an employee asks for a raise, do not start with the spreadsheet.

Start with the signal.

A raise request is rarely just about money. Sometimes it is a market correction. Sometimes it is a retention warning. Sometimes it is the first sign that your compensation system only moves when someone threatens to leave.

That is the part managers miss.

A raise request is often a market signal

If a strong employee shows up with an offer that is roughly 30% higher, that is usually not greed. It is often the market telling you that this person has quietly outgrown what you are paying.

You hired them a while ago. Their skills improved. The market moved. You did not update.

In that case, matching the offer may not be generosity. It may just be catching up.

But there is a bigger problem hiding underneath. If the only time someone gets corrected to market value is when they bring an external offer, they learn a simple lesson: leaving is the fastest salary strategy.

That is bad compensation design.

A 100% jump is a different conversation

If someone brings an offer that is double their current pay, slow down.

This is no longer just "should we match?" It becomes a sharper question: what does that market see that we do not?

Maybe the role has become much more valuable somewhere else. Maybe the person is under-scoped with you. Maybe another company is playing a very different game. Or maybe the offer is simply outside your model and not one you should try to chase.

That is why not every raise request should end in a panic counter-offer.

Sometimes the right move is to redesign the role if it is strategically important. Sometimes it is to accept that you are not competing in the same market. And sometimes it is to handle the exit quickly and respectfully.

Do not let exceptions destroy the system

In a small company, you can bend the rules for a truly critical person. Sometimes that is rational.

In a bigger company, random 50% or 100% jumps are how you quietly wreck trust in the compensation system.

Big exceptions should stay rare. They should be tied to role logic, not to who negotiates hardest or who brings the most dramatic offer. Otherwise your salary structure turns into theatre.

And once that happens, everyone notices.

Retention should happen before the offer appears

This is the real point.

Replacing strong people is usually more expensive than keeping them. But what really costs you is not the raise itself. It is the delay.

The delay creates panic counter-offers, rushed decisions, awkward exits, and the feeling that nobody's value is discussed until it becomes urgent.

If the first serious compensation conversation happens when someone already has another offer, you are late.

A better system is boring. That is why it works.

  • Review market fit earlier.
  • Notice role growth earlier.
  • Talk about value before resentment turns into job search.
  • Treat retention as a process, not a crisis.

That is a much better answer to a raise request than pretending every case is a special surprise.

Final thought

When someone asks for a raise, the number matters.

But the signal matters more.

Because the real question is not just, "Can we pay this?"

It is, "Why are we only learning this now?"