Skip to content

Generator

Raise Negotiation Script Generator — 10-Year Compounding + Script

Enter your current salary, target raise, and tenure plan. See the compounded 10-year impact and get a two-paragraph raise request script written to your manager's style.

10-year compounding
Every % today compounds through every future raise. The tool shows the real stakes.
Script to your manager
Editable two-paragraph ask with your numbers, your evidence, and a specific close.
Run it monthly
Market rates drift. Re-run quarterly to stay within 10-15% of market at all times.

15% → new base $161,000

10-year compounded value of the ask

Assuming 3% annual raises in both scenarios. The gap widens every year because future raises compound on a bigger base. This is why people who negotiate early out-earn equally talented peers by hundreds of thousands of dollars over a career.

Extra lifetime earnings from this raise: $240,741 over 10 years.

Email script

Subject: 15-minute check-in on compensation

Hi [manager first name],

I'd like 15 minutes this week to talk through compensation. I've been in the Senior Engineer role for 22 months, and the scope has grown meaningfully. I'm not asking for a conversation about the full promotion packet yet — I'm asking for a compensation review against the Staff Engineer band.

Three pieces of evidence on the ask:
1. Led the migration from REST to gRPC across 9 services; cut p99 latency from 480ms to 140ms.
2. Onboarded and mentored 3 engineers; all three shipped to prod within 45 days.
3. Caught and rewrote the billing double-charge bug in Q2 — recovered $180k in refund risk.

Market reference: levels.fyi median for Staff Engineer at similar-stage SaaS is $225-270k.. My current base is $140,000. I'd like to bring the base up to $161,000 (15%).

I'm committed to the team and the roadmap. I'd rather have this conversation directly and early than wait for the review cycle, where by default it gets diluted. Can we find 15 minutes this week?

Best,
[Your name]

Call script

[Open — first 20 seconds]
"Thanks for making time. I want to keep this short. I've been in the Senior Engineer role for 22 months, and I'd like to talk about moving the base to $161,000 — a 15% raise."

[Evidence — say the number, then the proof]
"Three reasons this is the right number:
 - Led the migration from REST to gRPC across 9 services; cut p99 latency from 480ms to 140ms.
 - Onboarded and mentored 3 engineers; all three shipped to prod within 45 days.
 - Caught and rewrote the billing double-charge bug in Q2 — recovered $180k in refund risk.
Market reference: levels.fyi median for Staff Engineer at similar-stage SaaS is $225-270k."

[Silence]
(After you make the ask, stop talking. Do not fill the silence. Your manager will respond. The first person to break the silence loses leverage.)

[If they say "I need to talk to HR/finance"]
"That makes sense. What's the best way to follow up — should I send a short written version so you have it on paper for the conversation? I can get that to you today."

[If they say "reviews are in Q4"]
"I understand that's the default cycle. Given the scope change, I'd like to do an off-cycle adjustment. If off-cycle isn't possible, can we put the $161,000 number on paper now, tied to Q4, so I know we're aligned?"

[If they say "that's above band"]
"I hear you. Two questions: what's the top of the current band, and what would it take to move me into the next band? I'd rather know the gap now than guess for another 6 months."

[Close]
"Thank you. I'll follow up in writing tonight. I appreciate you hearing this directly."
Manager POV: a well-run raise ask is easier to say yes to than a bad retention fight. Send the email on a Monday morning. Ask for the meeting before Friday. Come with three wins and a number. Do not include five wins or three numbers.

A 5% raise today is worth $60k over the next decade. Do the math before you walk in.

The framing most candidates use is wrong. "I want a 5% raise" sounds small; 5% on $100k is $5,000. But that raise isn't a one-time event — it becomes the new baseline for every future increase. If your employer gives 3% annual raises and you stay 10 years, a 5% raise today is worth roughly $60,000 in cumulative extra earnings over those ten years, compared to taking the standard 3%. A 10% raise instead of 3% is worth $120,000+.

The compounding cuts both ways. A raise you didn't get is a raise you will never recover, because every future raise is a percentage of a permanently lower base. This is why candidates who "wait for next year" almost always lose — the lost compounding stacks year over year. The tool shows the full curve so you see exactly what you're fighting for.

When to ask (and when not to)

Raise conversations are 70% timing, 30% content. The good windows:

  • 8-10 weeks before annual review cycle. Manager is building their comp case for you; your data goes into their packet. Asking during the review itself is usually too late — the budget is allocated.
  • Right after a visible win. Shipped a project, closed a big deal, saved the company money. Recency bias works in your favor; a conversation within 30 days of a win lands differently than one 6 months later.
  • After an internal promotion to new scope with no pay adjustment. This is the clearest case — the company has already decided you operate at a higher level and owes you the pay to match.
  • When market has moved and you haven't. If similar roles at similar companies are paying 15%+ more than you, that's data, not feeling.

The bad windows:

  • During a layoff round or hiring freeze. Budget is frozen; asking looks tone-deaf. Wait for the thaw.
  • During or right after a team failure. Even if you weren't responsible, the vibe is wrong.
  • In your first 6 months at a new company. The market rate you negotiated at hire is still the best data you'll have; re-negotiating that number this early is a hard conversation.

What counts as evidence

A raise conversation runs on three kinds of evidence:

Scope evidence. How much have you taken on since the last comp adjustment? Number of reports, number of projects, number of stakeholders. Use concrete comparisons: "12 months ago I was IC on 2 projects; today I'm tech lead on 4 with 3 direct reports."

Impact evidence. What did you ship? Numbers only. "Shipped the enterprise tier; ARR moved from $4M to $22M" beats "contributed to enterprise tier growth." At least two impact artifacts.

Market evidence. What does the market pay for your current scope? Pull from levels.fyi, a recruiter conversation, recent peer offers. Your evidence statement: "Market rate for a Senior Engineer with 7 YOE at B2B SaaS companies in my market is $X, median. I'm currently at $Y, which is 18% under market."

Three artifacts beat seven adjectives. A manager who's been handed "I've been working hard and think I deserve more" has nothing to escalate with. A manager who's been handed three artifacts, a market rate, and a specific number has a one-pager they can take to their skip-level.

The two-paragraph script, explained

The tool generates a short script because the conversation is short. A raise ask is two paragraphs, not a speech:

Paragraph 1 — the ask. "I'd like to talk about comp. Over the last 12 months I've [scope change] and [impact artifact]. Market rate for this scope is $X per [source]; my current comp is $Y, which is [difference]%. I'd like to move to $Z, a [delta]% adjustment." One breath. No throat-clearing. No apologies. The clearer the ask, the easier the manager can escalate it.

Paragraph 2 — the close. "I know this takes time to work through. What's the right process from here — should I send this in writing, or do you want to take it to [skip-level]?" Give the manager a specific next step. Open-ended "what do you think?" closes often result in "let me think about it" and nothing happens.

The whole conversation should take 8-12 minutes. Longer than that and you're either over-justifying or the manager is trying to renegotiate the ask in real-time. Don't negotiate against yourself on the spot — if the manager pushes back, respond with "I hear you. Would it help if I put this in writing so you can take it to the skip-level with specifics?" and wait.

Handling the common manager responses

"Budget is tight this year." Response: "I understand. I'd like to put the ask in writing so if budget opens up, I'm in the queue. Can we set a specific follow-up date?" Written asks get processed during budget cycles; verbal asks evaporate.

"Let's talk about this at your review." Response: "Happy to. My review is [X months out]. Can I put the ask in writing now so it's in the comp-planning cycle, rather than waiting until review?" Manager who pushes the conversation out 6 months is hoping you'll forget. You won't — and the written record keeps you in the cycle.

"You're already above band." Response: "Can you share the band? I've been calibrating to external market data." Sometimes true (common at highly structured companies); often the band cited is last year's and hasn't been refreshed.

"Your peers make the same — I can't give you more without giving them more." Response: "Are my peers operating at the same scope and shipping the same impact? If yes, then the data says all of us are underpaid for the scope, which is a bigger conversation. If no, the compression problem is your team lead's to solve, not a reason to freeze my comp."

"Wait until next quarter." Get it in writing. Specific date. Specific criteria. Otherwise "next quarter" becomes "next year."

If the answer is a hard no

Sometimes the answer is no and stays no. At that point, you have three options:

  1. Accept and plan to search. Start a discreet job search. A competing offer almost always moves a "no" to a "yes, immediately" but the cost of getting there is real. Plan the search if you're going to use this lever.
  2. Accept and plan to ask again. Pick a specific 90-120 day window. In that window, land one unmistakable artifact that the manager can't ignore. Re-run the raise conversation with the new evidence.
  3. Accept and disengage. This is what happens when candidates don't plan either (1) or (2). Work quality drops, tenure extends, options narrow. Don't let this be the default. Pick (1) or (2) deliberately.

The worst outcome is accepting a "no" and then sitting in place for 18 months without acting. Either the company will pay you fairly or someone else will. Getting clear about which requires a deliberate next step, not passivity.

The 11-month recurring reminder

Comp drifts. Market rates move 3-6% per year; company raises typically don't keep pace. Most long-tenured employees are 10-20% under market because they never re-anchor. Set a recurring calendar reminder 11 months from your last comp adjustment. When it fires, re-run this tool with current market data. If you're more than 10% under market, you have a conversation to have. If you're not, relax — but check again next year.

Candidates who run this loop stay within 5% of market for their entire career. Candidates who don't often wake up at year 4-5 realizing they're 25% under. At that point, catching up without switching jobs is nearly impossible because no company gives a 25% raise in one cycle.

Pair this with

Frequently Asked Questions

Depends on the gap. If you're 15-20% under market with clear scope growth and strong artifacts, yes — that's the standard case for a correction. If you're at market already, expect 3-7% merit raises. Raises much above 20% in one cycle are rare outside of promotions or competing offers.

Digital Dashboard Hub

Track salary negotiations, career earnings, and financial goals

DDH helps you see the financial impact of your career moves — track take-home pay, savings rate, and net worth as your income grows. Free 14-day trial.

Track your career finances free →