How to Ask for a Raise (With Scripts)

Asking for a raise is one of the highest-leverage conversations you'll have at work, and it's the one most people fumble. They wait too long, lead with feelings instead of facts, or freeze when their manager pushes back. The good news: a raise conversation is a skill, not a personality trait. Get the timing, the evidence, and the words right, and you put yourself in a strong position no matter how the company responds.

Here's how to do all three, with scripts you can adapt.

Get the Timing Right

Timing is half the battle. The same request lands very differently depending on when you make it.

Good windows:

• After a clear win. You just shipped a project, closed a big account, or fixed something that was costing the team. The impact is fresh and undeniable.
• During your annual or mid-year review cycle. Budgets for merit increases are often locked in 1-2 months before reviews happen, so raise the topic early in the cycle, not the week of your review.
• After you've taken on more scope. You've been doing your old job plus a chunk of someone else's for two quarters. Your title and pay haven't caught up.

Bad windows: right after layoffs, during a hiring freeze, immediately after a personal mistake, or on a Monday morning when your manager is buried.

A simple opener to lock in the meeting (don't ambush them):

"Hi [Manager], I'd like to set up 30 minutes this week or next to talk about my role and compensation. Nothing urgent, but I want to give it the time it deserves. Does Thursday work?"

This signals seriousness, gives them time to prepare (and to check the budget), and avoids a defensive on-the-spot reaction.

Build the Case With Evidence

This is where the honesty matters most. A strong raise case is built on things that actually happened, with numbers you can defend if your manager asks "how did you get that figure?" Inflated or invented metrics fall apart the moment they're scrutinized, and they cost you credibility you can't easily get back.

Pull together a one-page "brag document" before the meeting. For each accomplishment, capture the before, the action, and the after.

Before → after examples by function:

• Sales: "Came in at 87% of quota in Q1; restructured my outreach cadence and closed 118% in Q2 ($340K in new ARR)."
• Engineering: "Reduced API p95 latency from 1,200ms to 340ms, which cut our cloud bill by roughly $2,100/month."
• Marketing: "Grew organic blog traffic from 8K to 21K monthly sessions over six months and sourced 40 marketing-qualified leads."
• Operations/Support: "Cut average ticket resolution time from 14 hours to 6, and CSAT rose from 4.2 to 4.6."

Notice these are specific and verifiable. If you don't have a clean dollar figure, use the metric you do own (time saved, error rate, throughput) rather than guessing at revenue you can't trace to yourself.

Then do your market research. Pull comp data from Levels.fyi, Glassdoor, LinkedIn Salary, Payscale, and any role-specific surveys. Look at your title, location, and years of experience. Bring a range, not a single number, and aim your ask near the top of the realistic band.

A clean way to frame the number:

"Based on the scope I'm now covering and market data for this role in [city], comparable positions are paying $X to $Y. I'd like to move toward the upper part of that range."

The Conversation

Keep it calm, specific, and forward-looking. You're presenting a business case, not pleading.

Opening:

"Thanks for making time. Over the past year I've taken on [specific scope] and delivered [1-2 headline results]. I've enjoyed the work and I want to keep growing here. I'd like to talk about adjusting my compensation to reflect that."

Make the ask, then stop talking:

"Given my impact and where the market is for this role, I'm asking for an increase to $X. I've put together a short summary of the work behind that — happy to walk you through it."

Then go quiet. Silence feels uncomfortable, but resist the urge to soften your number or fill the gap. Let your manager respond.

If they ask for justification, walk through your brag document calmly:

"Sure. Three things stand out. First, [win with metric]. Second, [scope you absorbed]. Third, [market data]. Together that's why I landed on this number."

Avoid the traps: don't compare yourself to a specific coworker ("Jordan makes more than me"), don't threaten to quit unless you're genuinely prepared to, and don't anchor on personal expenses ("rent went up"). Tie everything to value delivered.

Handling a No

A "no" is rarely the end. Often it's "not right now" or "not at that number." Your job is to turn a vague no into a concrete plan.

If it's a budget timing issue:

"I understand the budget is tight this quarter. Can we agree on a specific number and revisit it in [month]? I'd like to put that in writing so we're aligned."

If they want to see more first:

"That's fair. Can we define exactly what 'ready' looks like? If I hit [specific, measurable goals] by [date], can we commit to revisiting the increase to $X?"

Pin down the criteria and the date in an email afterward — that turns a soft promise into an accountable commitment.

If the answer is a hard no with no path forward, stay gracious and gather information:

"I appreciate the honesty. So I understand the bigger picture — what would it take to reach $X here, realistically?"

The answer tells you whether to keep investing in this role or quietly start looking. Either way, you leave the conversation with dignity and useful information, not burned bridges.

Before You Walk In

Most raise conversations are won in the preparation. Update your accomplishments list while wins are fresh, keep your resume current with real, quantified results, and rehearse your script out loud once or twice.

If you're refreshing your resume as part of this — or because the conversation pushed you to explore options — PrismResume can help you sharpen the language around your actual achievements. It polishes what you genuinely did; it won't invent titles or numbers for you. The same honest, evidence-based wins that earn a raise are the ones that survive scrutiny in an interview.

Ask early, ask with evidence, and ask for a specific number. Then let the work speak.