The single highest-ROI meeting of your year is the one where you ask for a raise — and almost nobody prepares for it the way they'd prepare for a job interview. That's backwards. A 10% raise on a $150k salary is $15k/year. Over five years, compounded into future raise baselines and equity grants, that one meeting is worth six figures.
Here's the playbook I'd run if I were asking tomorrow.
Step 1: Pick the right moment
There are four windows that dramatically increase your odds:
- Right after a visible win — a launch, a closed deal, a successful incident response, a promotion-level project shipped.
- Budget season — usually 2–3 months before the company's fiscal year flips. This is when managers have room to advocate.
- After a positive performance review — while the evidence is fresh and on paper.
- When you have a competing offer — only use this if you'd actually take it. (More on this in our counter-offer playbook.)
The worst times: right after a bad quarter for the company, during layoffs, or in the first three months of a new manager relationship.
Step 2: Do the documentation work
You can't wing this. Before the meeting, build a one-page "case" document with three sections:
What I've done — 5–8 bullets, each with a metric. Latency cut by 40%. Migrated 12 services. Hired and onboarded 3 engineers. Shipped the billing revamp that unlocked $2M ARR.
How my scope has grown — what you're doing now that wasn't in your job description 12 months ago. "I own the on-call rotation for two services." "I mentor two juniors." "I run cross-team design reviews."
What the market pays — pull real ranges. Our software engineer salary guide, the product manager salary guide, and levels.fyi are the three sources I'd triangulate. Write down the 50th and 75th percentile for your role and level.
If you need help framing impact with metrics, see the software engineer resume example for the bullet pattern.
Step 3: Send a calendar invite, not a "quick chat"
Don't ambush your manager. Send a 30-minute invite titled "Comp conversation" at least a week out. Managers who are surprised by a comp ask give worse answers than managers who had a week to think about it and maybe pre-align with their own manager.
Step 4: The meeting itself
Open with confidence, not apology. Never start with "I'm sorry to bring this up" or "I know it's a tough year."
"Thanks for making the time. I want to talk about my compensation. Over the last year, I've [big win 1], [big win 2], and [big win 3]. My scope has grown to include [new responsibility 1] and [new responsibility 2]. Based on market data for this role and level, I'm seeing ranges of [X–Y], and I'd like to discuss moving my comp to [specific number]. What does the path to that look like?"
Then stop talking. Let your manager respond. This is the most important silence of the meeting.
Step 5: Handle the three common responses
"Let me think about it / check with HR." Good. Ask when you'll hear back. Nail down a specific date.
"That works. Can we put a follow-up on the calendar for [date]? I'd love to have a concrete answer by then."
"We can do [smaller number]." Don't accept the first counter.
"I appreciate that. Can we look at the full package — base, bonus, equity refresh? If base is capped, what other levers are available?"
"This isn't the right time." The critical response. Ask:
"I hear you. What would need to be true for this to happen? What are the specific outcomes and timeline I should be working toward?"
Get this in writing after the meeting. "Just summarizing — to qualify for [raise] by [date], I need to deliver [A], [B], [C]." If they agree in writing, you have a roadmap. If they dodge, that's data about whether to stay.
Step 6: If the answer is no
A hard no on a well-prepared ask is a significant career signal. You have three options:
- Accept the roadmap — if they gave you specific, achievable criteria and a date, work toward it. Re-raise at the checkpoint.
- Start interviewing — see the software engineer interview questions guide and the product manager cover letter example to tee up the process.
- Both — interview externally while delivering on the internal roadmap. The best leverage for a counter-offer is a real offer.
Don't make threats you won't follow through on. "If I don't get this raise I'll leave" is the worst thing to say unless you are genuinely ready to resign the next morning.
Step 7: After you get the yes
Three things:
- Get it in writing. "Confirming — new base of $X effective [date], plus [equity refresh / sign-on]."
- Don't tell coworkers. Comp conversations among peers get messy. If asked, deflect.
- Mark your calendar for 12 months out. That's when you review again.
The common mistakes
- Asking based on need, not performance. "I have to pay for daycare" is not a case. "I delivered $2M of impact" is.
- Apologizing for asking. You are not being rude. This is a normal business conversation.
- Accepting the first counter. Managers almost always have a second number.
- Not rehearsing. Say the opening line out loud, to a friend or a camera, at least three times before the meeting.
The bottom line
A raise ask is a structured business case, not a favor. Prepare the document. Send the calendar invite. Open with achievements and a specific number. Stop talking. Get the response in writing. The people who do this consistently out-earn equally talented peers by 20–40% over a decade — because raise decisions compound, and each missed raise delays every future one.
This is a meeting worth doing well.
