How to Ask for a Raise (When You're Already Employed)

Asking for a raise feels similar to negotiating a job offer — same word, "salary," same basic goal of ending up with a bigger number. But it's a fundamentally different conversation, played with different leverage, against a different set of constraints, and treating it like a smaller version of offer negotiation is the most common way people undersell their case or, worse, get a manager defensive when they didn't need to.

Here's the actual difference, and how to work with it instead of against it.

Your leverage is results, not the market

When you're negotiating a new offer, your leverage is comparative — this is what the market pays for this role, this is what another company is offering, take it or lose me. That leverage doesn't really exist in a raise conversation, and leaning on it is a mistake many people make by accident.

Telling your manager "Glassdoor says people in this role make more" or "my coworker on the same level makes more than me" rarely lands the way it's intended. It puts your manager in a position where agreeing means admitting a mistake or a fairness gap, which triggers defensiveness rather than problem-solving — and peer comparisons specifically tend to backfire, because now you've made it about someone else's number instead of your own case, and your manager likely can't discuss that other person's comp with you anyway.

Your leverage inside a company you already work for is different: it's the value you've already demonstrably delivered. Revenue you drove, costs you cut, a project you shipped that unblocked other teams, a process you fixed that was quietly costing hours every week. That's not comparative, it's not abstract, and it's much harder to argue with because it's your own track record, not someone else's.

Build the case before the conversation, not during it

Walking in with "I feel like I deserve more" is not a case, it's a feeling, and feelings are easy for even a sympathetic manager to defer indefinitely. Walking in with a short, concrete list of what you've delivered since your last comp conversation is a case a manager can actually take somewhere.

Concretely, that means writing down, ahead of time:

• Specific outcomes with numbers where you have them. Not "I worked hard on the migration" but "I led the database migration that cut page load time by X and let us retire the old hosting contract." Numbers don't have to be dramatic to be persuasive — concrete beats impressive.
• Scope changes since your last raise or review. If you're doing work that wasn't in your original job description — mentoring, owning a system nobody else touches, covering for a role that got cut — that's a legitimate basis for a raise even without a title change.
• What "good" looks like for your specific role, if your company has any kind of leveling framework, so you can frame your case in language that matches how they already evaluate performance, not just your own sense of effort.

This is the same instinct as building a market range before negotiating an offer — data over feeling — just pointed at a different data source. Here the data is your own delivered work, not comparable salaries.

Understand what your manager actually controls

This is the part people miss most often: your manager, even a manager who thinks you're great and wants to pay you more, frequently does not have unilateral authority to just give you a raise. Most companies run comp through a budget cycle — a pool of raise money gets approved at a level above your manager, sometimes months before your conversation even happens, and your manager is often working within a fixed allocation they have to divide across their whole team.

That changes how you should read a "no," or a "let me see what I can do." It's frequently not your manager saying you don't deserve it — it's your manager telling you the honest state of a constraint they don't control either. Two things follow from that:

1. A manager who's genuinely on your side needs ammunition to make the case upward, not just to be convinced themselves. Give them a clean, written case they can forward or paraphrase to their own boss or to HR, not just a strong verbal moment in a one-on-one they have to reconstruct from memory later.
2. If the honest answer is "there's no budget right now," the useful follow-up isn't to push harder in that moment — it's to ask what it would take and when the next real opportunity is, so you're not just quietly waiting and hoping it comes up again on its own.

Timing: use the natural moment, but don't be stuck waiting for it

Annual or semi-annual review cycles exist because that's when comp conversations are already expected and budget is already being allocated — so it's the easiest moment to ask, because you're not introducing a surprise topic into an otherwise unrelated meeting. If your company has a review cycle, that's your default timing, and it's worth showing up to it with the concrete case above already prepared rather than waiting to see what your manager opens with.

But don't treat the annual review as the only legal moment to raise this. If you've taken on a major scope change, shipped something with a clearly measurable business impact, or your role has quietly turned into a different, bigger job than the one you were hired for, that's a legitimate reason to ask outside the normal cycle. The case matters more than the calendar slot — a strong case slightly off-cycle beats a weak one perfectly on-cycle.

What's a reasonable ask

A raise in the 3-5% range is generally considered a solid, unremarkable outcome for a normal performance-based cycle — not exciting, but not an insult either. That's a useful baseline to know so you can calibrate your own expectations and recognize when an offer is actually fair.

But don't treat that range as a ceiling if it doesn't fit your situation. If you're genuinely underpaid relative to your scope — not relative to a Glassdoor number, but relative to what you're actually doing day to day — or if your responsibilities have grown substantially since your last comp adjustment, asking for more than the standard cycle bump is reasonable, and framing it around scope and delivered results (not market comparisons) is exactly the case that holds up under that kind of ask.

Rehearsing the actual conversation

Knowing the case you want to make and delivering it calmly, in the room, when your manager says something you didn't fully anticipate, are two different skills — and the second one is where most people actually stumble, not the research part.

Prepair's salary negotiation practice covers this specific scenario as the "annual review" context: Cam plays your manager instead of a recruiter, you pick how firm or reasonable you want that manager to be, and you run the conversation as a turn-based back-and-forth of roughly eight exchanges — you make your case, Cam responds the way a real manager might (including realistically citing budget constraints or asking you to justify scope), and you adjust in real time. You get a scored evaluation afterward: what you asked for, what you got, and where your case held up or didn't. Same product, same push-to-talk voice option as Prepair's regular interview practice if you'd rather talk it through than type — voice is never required.

It's part of the Pro plan, and it's not a substitute for actually doing the work of writing down your case beforehand. What it's good for is the part that's hard to prepare for on paper: staying steady and specific when your manager pushes back, instead of finding out in the real conversation that you hadn't thought through your answer to "there's just no budget right now."