Why this conversation is harder in your second language
Asking for a raise is uncomfortable in any language. In your second language, it’s uncomfortable twice over: you’re negotiating for money or status, and you’re doing it while worrying whether your phrasing sounds confident or just rude, humble or just unsure of yourself.
Here’s the trap. In a lot of languages, softening a request — “I was wondering if maybe, if it’s possible, there might be some room to…” — is what polite sounds like. Translate that instinct directly into English and it doesn’t read as polite. It reads as not sure this request is justified. Your manager can’t tell the difference between “I’m being humble” and “I don’t actually have a strong case.” They just hear hedging, and hedging is what people do when they’re not confident in their own ask.
The fix isn’t to sound more aggressive. It’s to give the conversation a shape, so the words carry the case instead of your tone having to.
The four moves: context, ask, evidence, next step
Every effective raise or promotion conversation — in email or in person — hits four things, in this order:
- Context — why you’re raising this now (review cycle, a year since your last increase, a project that changed your scope).
- Ask — the specific thing you want, stated as a sentence, not a hope.
- Evidence — two or three concrete outcomes that justify it.
- Next step — what you’d like to happen and by when.
The one people skip is the ask itself. They’ll nail the context and the evidence, then land on something like “so I wanted to see if there’s anything that could be done” — and never actually say the number or the title. Your manager now has to reverse-engineer what you want from a paragraph of evidence, and busy managers often just… don’t.
Vague: “I’ve taken on a lot more this year and I wanted to check if there’s any flexibility around my situation.” Specific: “I’d like to talk about moving my salary from $72K to $80K, based on the two projects I’ve led this year.”
The second version takes the same courage to say. It just doesn’t leave your manager guessing.
Set up the conversation — don’t ask it cold
Don’t open this in a hallway or a Slack DM mid-conversation. Request the time separately, so your manager walks in already knowing what the meeting is about:
“Hi Marcus — do you have 20 minutes this week? I’d like to walk you through what I’ve worked on this year and talk about my compensation. Let me know what time works.”
This message does one job: it names the topic (compensation, not “a quick chat”) so nobody is surprised, and it doesn’t try to make the actual case over text.
The full script
Here’s what the conversation itself can sound like, using all four moves:
“Thanks for making time. I wanted to talk about my role and my salary. [Context] It’s been about fourteen months since my last review, and over that time my scope has changed a lot. [Ask] I’d like us to talk about moving my base from $72K to $80K. [Evidence] Since March I’ve owned the onboarding redesign end-to-end — it cut new-user drop-off by 18% — and I’ve been the point person for the two biggest client escalations this quarter, both of which closed without losing the account. I think that work is closer to a senior scope than what I was hired for. [Next step] I know you’ll want to think it through — could we plan to follow up by the end of next week, either way?”
For a promotion instead of a raise, the ask and evidence change shape but the structure holds:
“I’d like to talk about moving into the Senior Analyst role. Over the last two quarters I’ve been running the weekly forecasting model on my own and training two new hires on it — work that’s already at that level, and I want the title and comp to reflect it. Could we talk about what that path would look like, and what timeline is realistic?”
Notice neither script apologizes for asking. Neither buries the number in a subordinate clause. And both end with something the manager can actually act on — a date, not just a feeling.
Two habits that quietly undercut you
Over-apologizing for asking at all. “Sorry to bring this up,” “I know this probably isn’t the best time, but,” “This might be a bad question, but” — these don’t read as humble in a work context. They read as I already suspect the answer is no. Cut the apology and start with the topic: “I wanted to talk about my compensation” is a complete, professional opening sentence on its own.
Staying vague about the actual ask. “I was hoping there might be some room for adjustment” forces your manager to guess a number, a title, and how serious you are, all at once. State it: a number, a range, or a title. If you’re not sure of the exact number, a range is fine — “somewhere in the $78–82K range” is specific; “some adjustment” is not.
What directness actually sounds like
Directness in English business writing is not the same as bluntness. “I’d like to move to $80K” is direct and completely normal — it’s the same register as “I’d like to schedule this for Tuesday.” Nobody reads that as demanding. What reads as off is the opposite: so much hedging that the sentence loses its subject, and the manager has to work to find out what you’re actually requesting.
If you want a gut check before you send the message or walk into the room, run your draft through Copynote’s tone control and set it to direct-but-warm — it’ll flag the phrases still doing the over-apologizing work without you noticing, and show you the fix as a diff so you can see exactly what changed and why.
After the conversation
Send a short follow-up the same day, in writing, restating the ask and the timeline you agreed on. It’s not distrust — it’s a paper trail that makes the next conversation easier, and it gives your manager something concrete to forward to whoever signs off. Two or three sentences is enough: what you asked for, what evidence you shared, and when you’re following up next.
