Raise Request Builder
Most raise requests fail because they're framed as a need. This builds it as an investment case — the version your manager can actually carry into the room where the decision gets made.
Why most raise requests fail
They're framed as a need. "I've been here two years." "The cost of living has gone up." "I'm the only one who knows how this works." All of these may be true, and none of them give your manager anything to work with.
Here's the thing almost nobody realises: your manager doesn't grant the raise. They argue for it — to their boss, to finance, in a room you're not in, against other managers arguing for their people. So the question isn't "how do I convince my manager?" It's "how do I arm my manager?"
That single reframe changes everything about how you prepare. You're not building a case for your manager to evaluate. You're building a case for them to carry. And the strongest version has three parts:
1. Value delivered, in their language
Not effort. Not hours. Outcomes — revenue, cost, time saved, risk reduced, quality improved. With a number attached wherever you can honestly attach one. This is why keeping a running log of your wins matters far more than people think: the case you make in month eleven is only as good as what you captured in month three.
2. Market context
A defensible range for someone with your industry, experience and outcomes — held as a range with reasoning, not a number you found online and are now repeating. If they push on it, you need to be able to explain why that range, not just cite it.
3. The replacement frame
The honest economics: replacing you costs a great deal more than the raise, takes months, and carries real risk. This is not a threat and must never sound like one — the moment it does, you've lost. It's simply the arithmetic your manager is already doing in their head. You're just making it explicit and easy to repeat.
Timing is the thing people get wrong
Compensation decisions are made in a budget cycle, usually weeks before anyone hears a word about it. If you ask after the numbers are locked, the answer is no — not because of your case, but because there's nothing left to say yes with. Ask six to eight weeks before your cycle. If you don't know when your cycle is, that's the first question to ask.
When the answer is no
Get the criteria. "What specifically would need to be true for this to be a yes?" A no without criteria is the thing that actually breaks people — and it's alarmingly common. A no with a written path and a date is survivable, and often turns into a yes six months later.
Also worth asking: if cash is genuinely frozen, what isn't? Title, scope, a development budget, a promotion timeline in writing. A no on base pay is not a no on the whole deal.
One thing this tool won't do: tell you what you're worth. Nobody honestly can from the outside, and any tool that claims to is guessing. What it will do is build a range you can defend and the argument behind it — which is the part that actually wins.