How to ask for a raise: the script, and how to actually practice it

It's a ten-minute conversation that can be worth more than a year of good work. Here's what to say, word for word — and how to rehearse it so it survives contact with a deflecting manager.

Your case has exactly three parts

Managers don't grant raises to people who deserve them; they grant raises to people who make the case easy to forward to their own boss. That case needs three components:

• Wins with numbers. Not "I've been working really hard" — three or four concrete outcomes with figures attached: revenue you influenced, hours you saved, projects shipped, people trained. If you don't have numbers, spend a week reconstructing them before you book the meeting.
• Market data. The going range for your role in your market, from two or three sources (levels.fyi, Payscale, actual postings for comparable roles). This reframes your ask from a favor into a correction.
• One specific number. Not "something more competitive," not a wide range. Vague asks get vague answers; a specific number is a thing your manager can say yes to, take upstairs, or counter — all better outcomes than a nod and nothing.

The opener, word for word

Book a meeting titled "compensation discussion" — no ambushes, no tacking it onto a 1:1 about something else. Then open like this:

Then stop talking. The silence after your number will feel enormous. It is not your silence to fill.

The deflections — and your responses

Most managers won't say no. They'll deflect, because deflection ends the conversation without anyone having to decide anything. There are three classics, and you can have an answer ready for each.

Notice the pattern: each response accepts the deflection politely, then converts it into a date, a number, or a commitment. A deflection that produces a scheduled follow-up with an agreed figure is not a loss. A deflection that produces "sure, sometime" is.

Never negotiate against yourself

The most expensive sentences in this conversation are the ones you say to rescue your manager from an awkward pause: "…but I totally understand if that's too much," or "…or even just something closer to it." Each one is a bid against yourself, made before the other side has said anything. State the number once and let it sit. If they ask "is that flexible?", don't produce a lower figure — ask what they can do, and make them name one. You spent a year earning this ask; don't discount it in the first ninety seconds out of pure discomfort.

Why reading your script 20 times won't save you

Here's where most preparation quietly fails. You write the script, you read it over and over, it feels familiar — so you feel ready. But memory research is blunt about this: re-reading builds recognition, not recall. In the classic experiments, learners who kept testing themselves retained about 80% a week later; those who stopped practicing retrieval once the material felt known dropped to roughly 35%. Worse, people in both groups predicted the same performance — the feeling of knowing your script is uncorrelated with your ability to produce it.

And this conversation is a recall task under stress. When your manager says "there's no budget," your response has to come out of your head — the script won't be in front of you, and the pause while you grope for it reads as your case collapsing. So practice the way you'll perform: close the document and produce the lines from memory, out loud. Speaking aloud alone adds a measurable 10–20% to retention over silent reading, and it catches the sentences that look fine on paper but won't come out of your mouth.

Drill your numbers until they're reflexive

Your wins-with-numbers and your market range are the load-bearing facts. "Churn down 18%" delivered instantly is evidence; "churn down… I want to say fifteen? eighteen percent?" is a shrug. Drill them like flashcards: prompt yourself with the win ("onboarding —?") and produce the figure cold, until there's no retrieval delay. These facts are also the first things adrenaline erases, which is exactly why they need to be overlearned rather than merely familiar.

Rehearse against the pushback, not just the speech

The opener is the easy part — you control it. The conversation is won or lost at the seams: the moment after the deflection lands, when you have to pivot from your script to your counter without a beat of panic. Research on choking under pressure shows that practicing under even mild stress — a friend playing the skeptical manager, a recording light on — inoculates you against freezing when it's real. The arousal becomes a familiar cue instead of a novel threat.

So don't just run your speech in the shower. Have someone hit you with "no budget" and "let's revisit at review time," in a random order, and respond out loud. It will feel worse than solo rehearsal. That's the point — you want the first genuinely uncomfortable version of this conversation to be a rehearsal, not the one that decides your salary.

If there's no willing human, that's the gap LobsterClass fills: paste your case and your target figure, and its manager personas push back the way real managers do — then grade whether you actually stated your number, cited your evidence, and held the line after the first no. Spread the sessions across the days before the meeting and sleep between them: spaced rehearsal with a night's sleep in between measurably cuts the effort of keeping material solid.

Then book the meeting. You'll walk in with a case, a number, and — the part that changes how you sound — the experience of having already survived this conversation several times.