How to ask for a raise — by not asking for one

The short version

Don't ask for a raise. Propose a role.

Asking for a raise is a negotiation over a job that already exists, in which you have very little leverage and your manager has every reason to say not right now. Proposing a role is a different conversation: you work out where your organization is losing money or missing opportunities, you work out what your manager is struggling with, you design the job that fixes it, and you name the title and salary that job deserves.

It takes longer than reading a list of negotiation tips. It works considerably better.

This page is the whole method, free, with nothing held back. If you'd rather work through it applied to your own situation, there's a free interactive version that ends with a written proposal you can take into the conversation.

Why the usual advice doesn't work

Read five articles about asking for a raise and you'll get the same four points. Research your market rate. Pick your moment. Practice out loud. Project confidence.

None of it is wrong, exactly. It's just that you can do all four perfectly and change nothing, because all four are about how you ask. They assume the job is fixed, the budget is fixed, and the only variable is your performance in a ten-minute conversation.

That framing puts you in the weakest possible position. You're requesting a larger share of a pot that someone else controls, against colleagues who want the same thing, at a time your manager didn't choose. The most likely honest answer, even from someone who likes you and rates you, is not this cycle.

The advice also quietly assumes something that usually isn't true: that your manager has the authority to just say yes. Most don't. Most have to go and argue for it with their own boss, or finance, or a compensation band. Which means the real question isn't whether you can convince your manager. It's whether you've given your manager something they can win an argument with.

That's what the rest of this is about.

What actually sets your salary

Here's the uncomfortable mechanic underneath all of this.

Your employer forms an estimate of what you're worth to them, keeps some of that, and pays you the rest. It has to work that way — if they paid you the full value you created, employing you would be pointless.

Two things follow.

The first is that your salary tracks your perceived value, not your actual value. Not your effort, not your hours, not your tenure or your loyalty or how reasonable you're being about it. What your employer believes you're worth. Those can diverge enormously, and the gap is invisible to everyone but you.

The second is more useful: if pay tracks perceived value, then there are exactly two levers. Increase the value. Or fix the perception. Most people pull neither and hope.

The two ways to earn more

1. Add more value. Make the number your employer is estimating genuinely bigger.
2. Communicate it better. Make sure the estimate reflects what you actually contribute.

The rest of the method is these two, in order. You do the first so that the second is true rather than a sales job.

Step one: find where you can add value

Picture your employer's bottom line as a pie.

You can ask for a bigger slice. That's the conversation above — adversarial, zero-sum, and it makes your manager the person standing between you and the money.

Or you can make the pie bigger. Now you're both on the same side, and your slice grows as a consequence rather than at someone's expense.

This sounds harder than it is, because as the person actually doing the work you already know where the opportunities are. They're the things you complain about. Three places to look:

Generate new revenue. Customers nobody is calling. A service people keep asking for that you don't sell. A product line that would obviously work. Revenue sitting on the table because nobody owns going to get it.

Improve efficiency. The process that eats a day a week. The report three people build by hand every month. The spend that stopped earning its keep two years ago and renews automatically.

Take on responsibility. The thing your manager keeps apologizing for not getting to. The decision that always waits on one person. The skill nobody on the team has and everybody needs.

That third one is the most underrated, because it's the one that most directly makes your manager's life better — and your manager is the person who has to go and argue for your raise.

Write down two or three, specific to your team. Vague doesn't survive contact with a budget conversation; "we lose about six hours a week rebuilding this report by hand" does.

Step two: start from your manager's problem

This is the step almost everyone skips, and it is the one that makes the difference.

Before you think about what you want, work out what your manager needs. Genuinely work it out, on paper:

• What are they accountable for? What does their boss judge them on?
• What are they anxious about right now?
• What do they never get around to?
• What keeps landing back on their desk because there's nobody else to take it?

Most people preparing for this conversation spend all their time on their own case — their achievements, their hours, their market rate. It feels diligent. It's also why so many of these conversations go nowhere: you've built an argument about yourself and handed it to someone whose actual problem is something else entirely.

Answer those four questions properly and your proposal stops being about your salary. It becomes a solution to a problem your manager already has, which happens to involve paying you more. That's an easier thing to say yes to — and much more importantly, it's an easier thing for them to defend upward, which is usually where the real decision gets made.

Show why fair pay for you is best for your employer.

Step three: design the role

Now put the two together. You know where value is being left on the table. You know what your manager is struggling with. The proposal is the job that sits at the intersection.

Four things to settle:

What you'll own. Three or four specific responsibilities you don't have today. Not "more strategic work" — the actual things.

Why you. Track record, position, what you've already demonstrated. Evidence rather than assertion.

The title. What would this job be called anywhere else? Look at comparable roles, and at how your own organization names equivalent scope. A title is not vanity; it's the thing that makes the salary defensible to finance and portable to your next employer.

The number. One number, not a range — a range is an invitation to the bottom of it. Back it with published data, advertised roles, or what your organization already pays for equivalent scope.

Step four: plan your own backfill

Here's the move that separates a proposal from a request, and almost nobody makes it.

If you take on new responsibilities, someone has to absorb the ones you're putting down. Work out who, before the conversation. Some of it moves sideways to a colleague who'd benefit from the stretch. Some of it justifies a hire. Some of it, honestly, turns out not to need doing at all.

Then bring that with you.

It does two things. It removes the most natural objection your manager has — but then who does what you do now? — before they have to raise it, which matters because an objection you answer preemptively costs nothing and an objection they voice costs you the momentum of the conversation.

And it signals that you are already thinking like the person in the larger job. That is the single most persuasive piece of evidence available that you should have it. Anyone can claim they're ready for more scope. Arriving with the org chart worked out demonstrates it.

Twenty minutes of thinking. It changes how the entire conversation lands.

How to run the conversation

Order matters more than wording.

1. The opportunity for the business. Start where their interests are, not yours.
2. The challenge facing the team and your manager. Show you've understood it properly.
3. The responsibility you want to take on. Now the solution arrives, and it involves you.
4. Why you'll succeed at it. Evidence.
5. The title and compensation that fit. Only now. Plainly, without apologizing.
6. Timeline and next steps. Make it easy to agree to a process rather than a number.

Your salary comes fifth. By the time you name it you've spent most of the conversation talking about your employer, and the number arrives as the conclusion of an argument rather than as an ask.

On timing: don't hunt for your manager's good mood. Align with the cycles your organization already runs on — budget setting, headcount planning, the review round, the point in the year when next year's priorities are decided. A proposal that lands while those decisions are being made is a contribution. The same proposal a month later is an inconvenience.

You also usually don't need a special meeting. Asking for one raises the stakes and puts your manager on guard before you've said anything. Taking time on an agenda you already share is calmer and works better.

Then follow up in writing, the same day. A short note: thanks for hearing me out, here's what I proposed, can we pick this up next week? That puts your case somewhere it can be forwarded to whoever actually approves it, names a next step so the conversation can't quietly die, and makes clear you expect an answer.

What to do if the answer is no

Decide this in advance, while you're calm — not in the room, and not that evening.

A flat no is rare for a well-made case. Far more common is not this cycle or not at that number. Those are different answers and they deserve different responses. Work out now: which could you live with? What would you need to hear to stay? What do you want to revisit in three months, and what would have to be true by then?

Deciding in advance stops you either capitulating in the room or overreacting afterward.

A first answer is not the last word. The proposal you leave behind keeps working after you've left the room — which is exactly why you put it in writing.

What one raise is actually worth

One more thing, because it's the part people underestimate and it's why this is worth the effort.

A raise is not a one-off payment. It lifts the base that every future percentage increase is calculated from, it raises what goes into your retirement accounts, and it resets what your next employer offers. A modest increase, compounded over a career, becomes a number most people find genuinely startling.

Work out what your next raise is worth → — about thirty seconds, no signup.

How this compares to the alternatives

A good career coach gives you something this can't: someone who knows your industry, who pushes back in real time, and who will rehearse the conversation with you. If you can afford one and the stakes are high, hire one.

But most people never will, and the space underneath that price point is basically empty — a wall of interchangeable articles, and then a thousand-dollar invoice. This is an attempt at the middle: the coach's process without the coach's time, which is why it's free and why it asks more of you than reading does.

This isn't only about raises

The framing here is a raise because that's the sharp, urgent version. But the underlying work — define the value you add, find ways to add more, design the role that reflects it, make the case to the person who decides — is what career advancement is.

It's the same method for a promotion case, an internal move, a request for a bigger remit, or a pitch for a role that doesn't exist yet. Once you've done it properly once, you have it for the rest of your working life. That, more than any single increase, is the thing worth having.

Ready to do it properly?

The free course walks you through this applied to your own job, one question at a time, and produces a written proposal you can take into the conversation. Fifteen minutes, no payment, and nothing you write ever leaves your browser.

Start the free course →