How to Ask for a Raise Without Sounding Entitled or Apologetic
The raise ask is one of the few sentences at work where being liked and being paid pull in opposite directions. Ask too softly and you signal you don't quite believe it yourself; ask too hard and you brace for a fight that was never coming. Almost everyone lands on the soft side, and the softness costs real money. This guide is about writing the ask as what it actually is — a business case — instead of what it feels like: a favor you're afraid to request.
Here's the trap. When you ask for more money, two things are true at once: you've earned it, and you don't want to seem greedy. The first belongs in the message; the second is the one that quietly writes it. So the ask fills up with hedges — "if it's possible," "no pressure at all" — each a small apology for having spoken, until you've made your own case sound optional. And an optional case gets treated as optional. You can fix that without becoming someone you're not. You just have to spot the three places where an ask stops being a case and turns into a plea.
The single mechanism: what your ask is quietly about
Every raise request has an unspoken subject — the reason it's built on. And there are really only two things you can put there.
You can build it on your need. "Rent went up, the car died, everything's more expensive this year." All true, all human, and all beside the point, because your manager cannot approve a raise on the grounds that your life got pricier. Need is a reason you want money. It is not a reason the company will move it.
You can build it on your contribution. "I've taken on the reporting the whole team runs on, and my pay was set before any of that existed." Now the subject is value the company can see and weigh. This is the only version that travels, because a raise is almost never granted by the person you're talking to — it's granted by their boss, and your manager needs a case they can carry up the chain without looking soft.
That's the mechanism, and it's nearly mechanical: read your draft and ask what is this argument resting on? If it rests on what's happening to you, you've written a sympathy request in a professional voice. If it rests on what you've delivered, you've written something a manager can fight for.
Not sure whether your draft reads as confident or apologetic? Paste it into the tool, try it in a firmer tone, and see which words are doing the flinching.
Habit 1: Name a number, not a feeling
"I'd like to talk about my compensation" is a fine way to open the meeting and a terrible way to end it. Somewhere you have to say an actual figure, and the person who says the number first sets the anchor everyone negotiates around. Leave it to your manager and you've handed them the pen — they'll fill in the lowest figure they can justify, because that's their job. Pick a specific target and be able to say why it's that one: grounded in what the role pays elsewhere for your level, adjusted for how far below that your current pay sits. "A bit more" is just an invitation to define "a bit" down to almost nothing.
Habit 2: Attach the number to delivered value, not promises
The most common weak ask is future-tense: "I'll really step up if you can bump my pay." It sounds motivated and quietly concedes the whole point, because it admits you haven't earned the raise yet — you're proposing to. Flip it to the past tense and it gets its spine back. Point at what you've already done and the gap between that and what you're paid for it: "When I started, my job was A. Since then I've taken on B and C, and I'm effectively doing the role one level up from my title." Now you're not asking them to bet on you; you're asking them to true up a bill that's already run. Two or three concrete, checkable examples beat a paragraph of adjectives about your work ethic.
Habit 3: Make the ask, then stop talking
This one is mostly nerve. You say your number and your reason, and then silence arrives, and it feels unbearable, so you fill it — "but I totally understand if that's not doable, whatever works, honestly it's fine." In one breath you've negotiated against yourself before the other person has said a word. Let the silence sit. It's supposed to be a little uncomfortable; that's the sound of someone actually considering it. Say the ask completely, put a full stop on it, and wait for a real response before you concede anything. If you can't manage silence in a live conversation, that's an argument for making the ask in writing first, where the pause is invisible and you can't talk yourself out of it in real time.
Habit 4: Time it to their calendar, not your panic
A good ask at a bad moment still loses. The instinct is to ask the second you feel underpaid, which is usually the second you're most frustrated — and frustration leaks in as an edge the manager feels before they read a word. Hook the ask to a moment the business already recognizes: a review cycle, the close of a big project, the start of budget planning. You want them to hear "this is the natural time to look at it," not "you cornered me on a Tuesday." Timing also means giving them a path to yes — ask who else is involved and what their constraints are, so the request lands as "help me understand how this gets done here" rather than a demand they grant or refuse on the spot.
A worked example
Here's a real-shaped situation. You've quietly absorbed a chunk of a departed colleague's work over six months, your pay hasn't moved since before that, and you want to open the conversation by email. Most first drafts look like this:
Hi Priya — hope you're well! Sorry to bug you about this. I was wondering if there's any chance we could maybe chat about my salary at some point? I know budgets are super tight right now and I totally understand if it's not possible, but things have been really expensive lately and I've been working so hard. No pressure at all!! Thanks so much for considering it 🙏
Read it against the mechanism. The subject is need — "expensive lately" — plus effort, "working so hard," neither of which Priya can take upstairs. "Sorry to bug you," "any chance," "maybe," "no pressure at all" are four separate apologies for asking. It's warm, and it has pre-approved its own rejection.
Now rebuild it: anchor on contribution, point at delivered value, name why it's the right time, and ask for a concrete next step without apologizing for existing.
Hi Priya — I'd like to set up 30 minutes to talk about my compensation. Since Marcus left in February I've taken on the client reporting and the weekly forecast, on top of my own role, and my pay was last set before either of those landed on me. With review season starting, it feels like the right moment to bring my salary in line with the work. Could we find time this week or next? Happy to send a short summary beforehand so you have what you need to take it forward.
Roughly the same length. But the subject of every key sentence is now something Priya can defend to her boss, the value is specific and checkable, the timing is framed as natural rather than desperate, and there's exactly one apology in it: none. It even hands her the ammunition to make her own job easier. Nobody has to be reassured that a no would be okay — because you haven't offered them one.
What to avoid
A few reliable ways to sink a decent ask. The ultimatum you can't back: "give me a raise or I'm gone" only works if you're genuinely ready to leave; if you're not, it's a bluff your manager will remember. The comparison to a coworker: "Jordan makes more than me" turns the conversation toward Jordan instead of you, and can out someone's private pay. The buried lede: three paragraphs of throat-clearing before the actual request, so the ask arrives exhausted. The apology stack: "sorry," "I know it's a lot," "no pressure," each one shaving points off your case. And the moving target — refusing to name a number so you can't be pinned down, which feels safe and reliably costs you the difference between what you'd have accepted and what they'd have paid.
When this is the wrong tool
A raise ask is for when you've delivered value your pay hasn't caught up to, and there's a real budget it could come from. Don't ask right after a genuine miss — repair that first, and let some clean results land. Don't use a raise conversation to fix a problem that isn't about money; if you're burnt out, sidelined, or badly managed, a bigger number won't touch it, and you'll have spent your ask on the wrong thing. Don't ask during a visible freeze or layoffs, unless your plan is to use the answer as information about whether to stay. And if you already know your role simply isn't valued where you are, no wording fixes that — the real move is a conversation about your path, or a look at the market, not a cleverly phrased email. The words matter, but they can't argue a case the facts won't support.
The short version
Build the ask on what you've delivered, not what you need. Name a specific number and say why it's that one. Point at value you've already earned, not effort you're promising. Make the ask, then stop talking. Time it to a moment the business already respects. Do that and your request stops sounding like a favor and starts sounding like what it is — a reasonable person asking to be paid for work they've already done. Say what you feel; just make sure the sentence is about your contribution, not your rent.
Want to hear whether your ask sounds confident or apologetic before you send it? Try it in the tool →