How to Ask for a Raise: A Calm, Step-by-Step Approach

Asking for a raise makes a lot of people feel slightly sick, and it makes remote workers feel worse. When you're not in the building, there's a nagging worry that your work is less visible, that your manager doesn't quite see what you do, that bringing up money will come across as ungrateful from someone who already gets to work in their slippers. I've felt all of that, and I've also gotten the raises. The two facts are not in tension.

The thing that turns the conversation from terrifying to merely uncomfortable is preparation. A raise request is not a performance of confidence you either have or don't. It is a case you build, quietly, over weeks, until asking feels less like a leap and more like presenting an obvious conclusion. Here is how I'd walk through it. None of this is financial or legal advice — it's the practical playbook I wish someone had handed me earlier.

Build the case before you build up the nerve#

The mistake almost everyone makes is leading with how they feel. "I feel underpaid" or "I've been here two years" are not arguments — they're the reason you're having the conversation, not the case for it. The case is evidence of the value you've added, in terms your manager can repeat to their manager.

Start a running document, today, before you need it. Every time you ship something, solve a problem, take on scope, or get praise, write it down with enough detail to reconstruct later. By the time you're ready to ask, you want a page that answers one question: what is this person worth keeping?

Frame each entry around impact, not activity:

• Not "I managed the migration project," but "I led the migration that cut our support tickets by a noticeable margin and freed two engineers for other work."
• Not "I help new hires," but "I onboarded the last three people on the team, who all ramped to independent work faster than usual."
• Not "I'm reliable," but "I've owned the on-call rotation for eight months with no missed escalations."

This habit does double duty. It's the foundation of your raise case, and it's the same log that keeps you visible the rest of the year — something we dig into in staying visible when you work remotely.

A raise is rarely granted because someone deserves it. It's granted because a manager can build a defensible case for it to the people who control the budget. Your job is to hand them that case, fully assembled.

Research the range so your number isn't a guess#

Once you know your value, you need to know its market price. Walking in with a number you pulled from hope is how you end up either lowballing yourself or naming something so far off it undermines the whole conversation.

Look at salary data for your role, your level, and — this matters for remote workers — the geography your company benchmarks against. Some companies pay for the location of the role; some pay for the location of the person. Know which one applies to you, because it changes the range entirely. Cross-reference a few sources: public salary databases, what recruiters quote you for similar roles, and, where you can have the conversation safely and appropriately, trusted peers.

Land on three numbers before the meeting: your ideal figure, a number you'd be genuinely happy with, and your walk-away floor. Ask for somewhere near the top of the defensible range, because the negotiation usually settles below your opening number, and you want room to land somewhere good.

Time it well#

Timing is leverage you can control, and most people waste it. The worst moment to ask is when you're personally stressed about money, because that's about your need, and need is not a business case. The best moment is when your value is freshly visible.

Good moments tend to cluster around evidence:

• Just after you've delivered something significant, while it's still top of mind.
• During a scheduled review cycle, when compensation is already on the table.
• When you've taken on responsibilities clearly beyond your original role.
• After positive feedback from someone senior, which you can reference directly.

Also read the wider weather. Asking the week after a hiring freeze or a rough quarter is a harder sell through no fault of yours. You can't always control the climate, but you can avoid walking into an obvious storm. And give your manager a heads-up rather than ambushing them — a short note saying you'd like to discuss your compensation in your next one-on-one lets them prepare, which usually works in your favour.

The conversation itself#

Keep it calm, short, and specific. You are not pleading; you are presenting. A structure that has served me well:

1. Name the topic plainly. "I'd like to talk about my compensation. I've taken on a lot this year and I think it's worth revisiting." No long wind-up.
2. Make the case. Walk through two or three of your strongest, most concrete contributions from the log. Tie them to impact the business cares about.
3. State your number and your reasoning. "Based on that and on what I'm seeing for this role in the market, I'm asking for X." Then stop talking. The silence after the ask is uncomfortable, and the temptation is to fill it by negotiating against yourself. Don't. Let them respond.

A sample of how that sounds in one breath: "Over the last year I've led the migration, taken on the on-call rotation, and onboarded most of the new team. Looking at the market for this role, I'd like to bring my salary to X. I wanted to raise it with you directly because I'm hoping to keep growing here."

That last line matters. You're signalling that this is about staying and investing, not a threat on your way out. Stay warm. The person across the table is, ideally, your advocate in the rooms where the real decision gets made.

When the answer is "not right now"#

Often you won't get a yes in the room, even when the case is strong — budgets work on cycles and managers rarely control them alone. "Not right now" feels like rejection, but treated correctly, it's the start of a plan. The worst thing you can do is nod, deflate, and let it evaporate.

Instead, get specific while you're still in the conversation. Ask the question that turns a vague no into a concrete path: "I understand. What would need to be true for this to be a yes? And when can we revisit it?" You're looking for two things — the conditions and a date.

Then pin it down in writing afterward. A short, friendly follow-up note summarising what you discussed and agreed creates a record and a commitment. "Thanks for the conversation — as I understood it, we'll revisit this in the next cycle, and in the meantime I'll focus on X and Y. Let me know if I've got that right." Now it's documented, it's specific, and you have a scheduled second conversation where the answer is much harder to defer again.

If you keep hitting a wall despite a strong case, clear conditions, and good timing, that's information too. Sometimes the honest conclusion is that the ceiling here is real, and the raise lives at a different company. But don't jump there first. Run the calm version — the case, the range, the timing, the conversation, the written follow-up — and you'll be surprised how often the answer that felt impossible turns out to be yes.