Most raise conversations fail before they start. Either the number was a guess, the timing was wrong, or the case was about effort instead of impact. None of those are about the manager being unreasonable.
This guide walks through the prep, the script, and the awkward five seconds after you say the number.
What changed in 2026
A few things shape the 2026 conversation.
- Comp transparency laws are wider. More US states require salary ranges in job postings, which gives you internal benchmarks.
- Levels and Pave data is fresher. Quarterly updates make external benchmarks usable instead of stale.
- Budget cycles are tighter at growth-stage companies. Timing your ask to the planning window matters more than it used to.
How to prepare
Five things, before you book the meeting.
- Pull three data points. Levels, Pave, one job posting in your range.
- Write your scope diff. What you owned a year ago vs now.
- List three concrete wins. With numbers.
- Decide your number and your floor. Both, before the meeting.
- Pick the right month. Six to eight weeks before annual planning, ideally.
1. The market case — best for setting the anchor
Open with data. "Looking at Levels and a recent recruiter conversation, the market range for my role and tenure is $175k to $205k. I am at $158k." Two sentences. You are not making an argument yet, you are establishing the gap.
The trade-off is that some managers push back on external data ("we do not benchmark that way"). Have one internal data point ready — a public job posting from your own company is the strongest.
2. The scope case — best for showing the work
One paragraph on what changed. "When I joined, I owned the payments service. Over the last year, I also took on the billing pipeline and onboarded two engineers onto it. Last quarter that pipeline processed $12M without an incident." Specific. Numbers. No adjectives.
The catch: this only works if the scope actually grew. If you are doing the same job, ask for a market adjustment, not a promotion-shaped raise.
3. The number — best for not getting rounded down
Say the number, then stop talking. "Given the market range and the scope change, I am asking for a base of $190k." Then silence. Do not fill it. The first person to talk loses the anchor.
Comparison: ways to ask in April 2026
| Approach |
When it works |
Catch |
| Direct meeting |
Strong manager relationship |
Requires confidence in the number |
| Written proposal first |
Distributed teams, async cultures |
Slower, but easier to share up |
| During performance review |
Companies that bundle comp with reviews |
Limited budget flexibility |
| External offer in hand |
Established performers, hot markets |
Burns trust if you would not actually leave |
Common mistakes to avoid
Asking for a range. "Somewhere between 180 and 200" gets you 180, every time. Pick one number.
Leading with effort. "I have been working really hard" is invisible. Lead with outcomes a non-engineer can repeat.
Threatening to leave when you would not. Managers can tell. The bluff costs more than the raise is worth.
FAQ
What if they say no?
Ask what specific outcomes would change the answer in six months. Get it in writing. Then decide if you believe it.
Should I bring an external offer?
Only if you would actually take it. Otherwise it is a bluff that damages the relationship.
How big a raise is reasonable to ask for?
10–15% for a market adjustment, 20–30% if scope has materially grown. Anything above that needs a promotion conversation, not a raise one.
Where to go next
For related guides see How to negotiate salary using AI, How to quit your job professionally in 2026, and How to write a cover letter in 2026.