Most advice on asking for a raise falls into two useless categories. The first is vague encouragement: know your worth, be confident, just ask. The second is a script so stiff that saying it out loud would feel like reading from an index card. Neither helps you in the actual room, five minutes before the conversation, when your heart rate is up and you can’t remember why you thought this was a good idea.

This is the version that skips both. It’s built around one idea: asking for a raise is not a personality trait, it’s a process, and processes can be prepared for. Below is how to tell if you’re actually ready, how to land on a number that’s ambitious without being laughable, how to run the conversation itself, what to send if you’d rather do it in writing, and what to do if the answer is no.

How to know you’re actually ready to ask

People usually ask for a raise for one of two reasons: something changed, or enough time passed. Only the first one is a strong case. “It’s been a year” is a reason to have a conversation about your growth. It is not, by itself, a reason your employer should pay you more. Time in a seat is not the same as increased value.

You’re on solid ground if any of these are true:

  • Your responsibilities have grown since your salary was last set — you’re managing people, owning a bigger budget, or doing work that used to belong to a more senior title.
  • You can point to a specific, measurable result: revenue you brought in, costs you cut, a project you shipped that the business depended on.
  • You checked what the market actually pays for your role and level, and you’re meaningfully below it — not by a hunch, but by real data.
  • You took on work that was never in your job description because someone left and nobody backfilled it.
  • Your manager has said, directly or in a review, that you’re performing above your level.

You’re on weaker ground if your case is mostly “I’ve been here a while” or “a friend at another company makes more.” Both might be true and neither moves the needle on its own. If you’re short on hard evidence right now, that’s useful information too — it tells you to spend the next month building the case rather than walking in empty-handed.

Timing matters more than most advice admits

The same request lands differently depending on when you make it. A few things worth checking before you put it on the calendar:

Right after a strong result, not months later. If you just closed the deal, shipped the launch, or fixed the thing that was on fire, that’s the moment your value is most visible. Waiting three months to bring it up means your manager has to remember it instead of feeling it.

Before the budget is set, not after. Most companies decide compensation budgets on an annual or semi-annual cycle, often a month or two before performance reviews actually happen. If you wait until the review itself, the number may already be locked. Ask your manager, generally, when comp decisions get made — it’s a normal question, not a suspicious one.

Not during a hiring freeze or a bad quarter. This doesn’t mean never ask, but read the room. If the company just announced layoffs or missed a target publicly, that’s a harder month to get a yes, whatever your individual case looks like. You can still start the conversation — just adjust what you’re asking for.

Not in the same breath as a mistake. If you’re a week removed from a visible miss, let that settle first. This isn’t about hiding it; it’s that the conversation goes better when your manager’s most recent memory of you is strong, not shaky.

Know your number before you ask for one

“How much should I ask for” is the question people get stuck on longest, and it’s usually because they’re guessing instead of researching. A defensible number comes from three places, not one:

Market data for your specific role, level and location. Sites like Levels.fyi (strong for tech), the Acas guidance on pay and wages, and Glassdoor’s salary reports each give you a range. Use more than one source, because any single site can skew. You’re looking for the range, not a single figure — then deciding where in that range your case puts you.

Here’s what that looks like worked through. Say the BLS data and two salary sites put your role, in your metro area, between $68,000 and $82,000. You’re currently at $71,000. That alone tells you $71,000 is defensible but low in the range — not a crisis, but not competitive either. If you also have a genuine case for above-average performance, the top third of that range, around $78,000–$80,000, is a realistic ask. Asking for $95,000 because a friend at a different company makes that isn’t supported by the data you just gathered, and bringing an unsupported number in tends to undercut the credibility of the whole case, including the parts that were solid.

What a promotion or backfill would cost. If your company had to hire externally for the work you’re already doing, what would that role pay? This is often a higher number than your current salary, because internal raises are frequently smaller than what a new hire in the same seat would command.

A specific percentage, not a round number pulled from nowhere. A standard “good performance” raise typically lands somewhere in the 3–6% range. A raise tied to expanded scope or a market correction is usually higher — 10–20% isn’t unusual when the case is strong. Asking for “more money” invites a lowball counter. Asking for a specific number, backed by a reason, is much harder to negotiate down casually.

A useful trick: decide on three numbers before you go in — your target, your walk-away-happy number, and your floor. If you only have one number in your head, you’ll either freeze or over-negotiate against yourself the second there’s any pushback.

Build the case before you build the courage

The conversation goes better when you’re not trying to remember your accomplishments in real time. A week before, put together a short document — not a formal proposal, just notes for yourself — with three things:

  1. Three to five concrete wins, each with a number attached where possible. Not “improved the onboarding process” but “cut onboarding time from six weeks to nine days, which let us backfill two open roles a month faster.”
  2. Anything that expanded your scope. New responsibilities, people you now manage, systems only you understand, decisions that used to require your manager’s sign-off and no longer do.
  3. Your market number and where it came from. Not to wave the data at your manager like a weapon — to have it ready if they ask, or if the number they offer is well under it.

You don’t need slides. You need to not be nervously trying to recall your own year while also trying to read your manager’s face.

Raise or promotion — know which one you’re asking for

These get conflated constantly, and asking for the wrong one weakens both. A raise is more money for the job you’re already doing, made stronger. A promotion is a different job, usually with a title change, and the compensation conversation happens alongside a scope conversation, not instead of one.

The mistake shows up like this: someone puts together a strong case for why they deserve more money, but frames it as “I think I’m ready to be a Senior [Title].” Now the conversation isn’t about pay anymore — it’s about whether the role exists, whether there’s headcount for it, whether other people need to weigh in. All of that takes longer than a raise decision, and a lot of it is entirely outside your manager’s control even if they agree with you completely.

If what you actually want is more money for your current scope, ask for that directly. If you want the new title and the responsibilities that come with it, say that instead, and expect a longer process with more people involved. Asking for both in the same breath is fine, but be clear with yourself about which one is the priority, because you may get offered one without the other.

Mistakes that sink an otherwise solid case

Most rejected raise requests aren’t rejected because the person didn’t deserve more money. They’re rejected because of how the ask was made. The recurring patterns:

  • Comparing yourself to a specific coworker by name. “I know [colleague] makes more than me” turns the conversation into a dispute about someone else’s pay, which your manager likely can’t discuss with you anyway, instead of a conversation about your own case.
  • Leading with personal financial need. Rent going up or a new baby is real and understandable, but it isn’t something the business is obligated to solve, and leading with it shifts the conversation away from the value you bring, which is the part actually within your manager’s power to act on.
  • An ultimatum you won’t follow through on. “Give me a raise or I’ll leave” only works if you’re genuinely prepared to leave. Said without meaning it, and not backed up, it damages trust permanently the first time it doesn’t happen.
  • Asking with no notice, in the middle of something else. Bringing it up in the last two minutes of an unrelated meeting reads as an afterthought and gets an afterthought-quality answer. Book the time.
  • Going in with a number but no reasoning behind it. A number alone invites a counter. A number attached to a specific, sourced reason is far harder to talk down.

The conversation: what to actually say

Ask for a dedicated meeting rather than raising it at the end of an unrelated one-on-one. “Can we grab 20 minutes this week — I’d like to talk through my compensation” gives your manager time to prepare instead of being caught flat-footed, which usually gets you a better answer than an ambush would.

In the room, a simple structure works better than a speech:

“I wanted to talk about my compensation. Over the past [period], I’ve [one or two concrete results]. My responsibilities have also grown — I’m now [specific new scope]. Based on that, and on what similar roles are paying in the market, I’d like to move my salary to [your number]. Can we talk about what that would take?”

Then stop talking. This is the part almost everyone gets wrong — filling the silence that follows with justifications, caveats, or a lower number nobody asked for. Silence after you’ve made a clear ask is not a problem to solve. Let your manager respond first.

A few things that consistently help:

  • Say the number out loud. Vague requests get vague answers. Harvard’s Program on Negotiation makes the same point from the research side: an anchored, specific first number shapes the entire rest of the negotiation far more than a vague one does.
  • Frame it as a conversation, not an ultimatum, unless you genuinely have another offer and are prepared to use it.
  • If they need to check with someone else — which is common — ask for a specific date you’ll hear back, not “soon.”
  • Write down what was said immediately after. Memories of verbal commitments fade fast, on both sides.

If you’d rather put it in writing first

Some workplaces, especially remote ones, run compensation conversations by email before or instead of a meeting. A written request needs to do in a few sentences what the verbal version does in a conversation: state the ask, back it with evidence, and make it easy to say yes.

Subject: Compensation conversation

Hi [Manager],

I’d like to set up time to talk about my compensation. Over the past [period], I [one or two specific, measurable results]. My role has also grown to include [expanded scope], which wasn’t part of my original responsibilities.

Based on that and on current market rates for this role, I’d like to discuss moving my salary to [number]. I’ve attached a short summary of the details behind that. Could we find 20–30 minutes this week or next to talk it through?

Thanks,
[Name]

Keep the attachment to one page: the wins, the scope change, the number, the source of the number. Don’t pad it — a dense one-pager reads as more credible than three pages of context nobody asked for.

If the number comes back lower than you asked for

A counter-offer isn’t a no, and it isn’t automatically the final answer either. Two questions are worth asking before you accept or push back:

“Can you walk me through how that number was reached?” Sometimes it’s a hard budget ceiling with no flexibility this cycle. Sometimes it’s a starting offer that assumes you’ll negotiate. You genuinely can’t tell which without asking, and the answer changes what you do next.

“Is there room to close the gap with anything other than base salary?” If cash is genuinely capped, a bonus, extra equity, an extra week of vacation, a professional development budget, or a firm date for revisiting the number can close some of the distance. This isn’t a consolation prize to settle for reflexively — it’s a legitimate option when the constraint is real and the alternative is walking away with nothing.

If the gap between what was offered and your researched number is large, and there’s no flexibility anywhere, that itself is useful information about where you sit at that company relative to the market — even if it’s not the answer you wanted.

What if you don’t have another offer

You do not need a competing offer to ask for a raise, and most people who successfully negotiate one don’t have one in hand. What a competing offer does is remove uncertainty for your employer — it proves the market number is real. Without one, you replace that proof with data and results instead.

This means your case needs to work harder in two places: the market research has to be specific and sourced, and the results have to be concrete rather than general. “I work hard” doesn’t substitute for an external offer. “I generated $340,000 in new business this quarter, and the market rate for this role at my level is $X, sourced from Y” does the same job without needing a second employer involved.

If you genuinely have no leverage — new to the role, no measurable wins yet, market data that doesn’t support a jump — that’s not a reason to stay quiet forever. It’s a reason to ask what it would take to get there, and put a timeline on it. “What would need to be true in six months for us to have this conversation with a yes” is a legitimate, useful question on its own.

Asking for a raise when you work remotely

Remote work removes the informal visibility that used to build a raise case without you trying — the manager who happens to see you handling a crisis, the hallway comment that gets remembered at review time. If nobody’s watching you work, the case has to be made explicitly, in writing, more often than once a year.

A few adjustments that matter for distributed teams specifically:

  • Document wins as they happen, not from memory eight months later. A running note with dates and outcomes is worth more than a strong memory in a remote setting, because there’s no shared physical context to jog anyone’s recollection.
  • Ask for video, not a phone call or a chat message, for a conversation this important. Tone is easy to misread in text, and a compensation ask deserves the same weight in person that it would get in an office.
  • Check whether pay is location-adjusted. Some companies set remote salaries by where you live. If that’s the case, your market comparison needs to reflect the right geography, not a national average that doesn’t apply to your contract.
  • Over-communicate scope changes as they happen, not just at review time. If you’ve absorbed new responsibility, say so in the moment — “just flagging that I’ve taken over X since Y left” — so it’s on the record before the raise conversation, not introduced for the first time inside it.

If the answer is no

A no is common, and it is not automatically the end of the conversation. What matters is what you ask next: “What would it take to get there, and by when?” A manager who says no with no path forward is telling you something different from one who says no but names a concrete milestone and a date to revisit.

Get the answer to that question in writing if you can — a follow-up email summarizing “we agreed to revisit this in Q3 if X happens” costs nothing and prevents the conversation from quietly disappearing. Set a calendar reminder for that date yourself. Don’t rely on your manager to bring it back up; in practice, the employee almost always has to.

On the fear that asking puts your job at risk: at a functioning company, a respectful, well-prepared request for fair compensation is not grounds for anything close to termination, and in a number of places doing so is specifically protected. What can go badly is how it’s asked — an ultimatum you’re not prepared to follow through on, or repeated asks with no new case behind them. The request itself, made professionally and once, is a completely normal part of having a job.

If a no comes with no path forward, no acknowledgment of your case, and no willingness to say what would change that — more than once — that’s information too. It’s just information about the company, not about whether you were right to ask.

If you are weighing a move rather than a raise, the same principles apply with different leverage in negotiating a job offer. And before either conversation, it is worth knowing exactly what your current package already pays you.

A rise is also the single best moment to change what happens to your money, before the increase quietly becomes normal spending — lifestyle creep is the reason most pay rises disappear.

Acas sets out the ground rules on pay and wages, which is worth knowing before you sit down to argue about yours.

Frequently asked questions

How often should you ask for a raise?

Once a year is standard if nothing unusual has changed. If your scope expands significantly mid-year, or you land a result that clearly moves the business, you don’t need to wait for an anniversary — ask when the case is strongest, not when the calendar says it’s time.

Can you get fired for asking for a raise?

Asking for fair pay, done professionally, is not grounds for termination at a reasonable employer, and is specifically protected from retaliation in many places. The risk sits in how it’s done — threats you won’t follow through on — not in the act of asking itself.

Should you ask for a raise by email or in person?

In person or on video for the initial conversation, ideally, because it’s easier to read the response and negotiate in real time. Email works well as a follow-up to confirm what was discussed, or as the first step at companies that default to written requests.

What if I don’t get a raise this year?

Ask specifically what would need to change for a yes next time, and get a date to revisit attached to it. A no without a path forward is a different signal than a no with one.

If you are weighing a new job rather than a raise where you are, the same principles apply with different leverage — negotiating a job offer before you accept it covers that conversation.

Is it okay to name a specific number?

Yes — it’s usually better than not. A specific, researched number is easier to say yes to than a vague request for “more,” and it’s harder for the conversation to drift somewhere unhelpful.