How to Ask for a Raise: The Complete Script and Salary Negotiation Guide

Most people rehearse the raise conversation a dozen times in their head and then, in the actual room, say something like "I was hoping we could maybe talk about a raise?" — a sentence built entirely out of hedges. It isn't a confidence problem. It's that almost nobody is ever taught how to ask for a raise as a structured skill, so the moment gets improvised under pressure, and improvised asks are the ones that get deferred, discounted, or quietly forgotten. This is the complete playbook: how to build the case, the exact script to use, how to handle "budget's frozen" and "let's revisit next quarter," the mistakes that sink an otherwise solid ask, and the questions people have most.

The good news is that salary negotiation is one of the most learnable conversations in a career — it rewards preparation far more than it rewards charisma. A well-built case delivered plainly beats a nervous, well-meaning ramble every time, and the skills below are the same ones that work whether you're asking for a first raise or negotiating a counteroffer.

Why "asking for a raise" is really a case-building skill

The instinct most people have is to treat a raise request as a personal appeal — explaining why they need more money, why it's been a while since their last increase, why it would help right now. All of that is understandable, and none of it is what actually moves a manager to act. A manager can't approve "need." What they can approve is a case: a specific number, tied to specific, demonstrable value, that they can defend when someone above them asks why. Reframing the ask from a personal appeal into a business case is the single biggest lever in the entire conversation, and it changes everything downstream — what you say, what number you pick, and how you respond when you hear "let me see what I can do."

This isn't about being unemotional or robotic. It's about recognizing that your manager is, in this moment, doing a job on your behalf — carrying your case to finance, to their own boss, to whoever actually signs off. The clearer and more specific you make that case, the easier their job is, and the more likely they are to actually fight for it instead of quietly letting it slide because it never had sharp enough edges to hold onto.

When to ask: timing matters as much as the pitch

The best moment to ask is right after you've delivered something concrete and visible — shipped a project, closed a deal, absorbed a departed colleague's workload, hit a number that mattered. Visible wins are fresh in memory and easy to point to; asking six months after the fact means reconstructing the case from scratch. The worst moments are immediately after a layoff round, during a hiring freeze announcement, or in the same week your manager is clearly underwater with something unrelated — not because the case is weaker, but because attention is the scarcest resource in those windows and yours needs it. Book a dedicated 1:1 for this rather than tacking it onto the end of a status meeting; a raise conversation deserves its own agenda item, not the last three minutes before the next call starts.

1. Anchor the ask in value delivered, not personal need

"My rent went up" and "I've taken on Priya's three accounts since March" are both true statements, but they land completely differently. The first is a circumstance your manager can sympathize with and still decline, because it says nothing about your work. The second is evidence — it tells them exactly what they'd be paying for and why it's a fair trade. Before the conversation, write down the actual scope change: new responsibilities absorbed, projects delivered, metrics moved, decisions you now own that you didn't a year ago. This becomes the spine of your case, and it's the part that survives being repeated to someone who's never met you.

2. Pick a specific number, backed by a specific rationale

"Can we talk about a raise?" invites a vague, easy-to-defer answer. "I'm asking for 82K, based on the scope I've taken on since March" invites a real decision. The number should come from somewhere concrete — market-rate research for your role and region, the pay band for the level your added scope actually matches, or a documented gap versus peers doing comparable work. You don't need to disclose your sources in the room, but you should be able to explain, in one sentence, why that number and not a different one. A specific number with a visible rationale behind it is dramatically harder to wave away than a round number that sounds like a guess.

3. State the number, then hold still

This is the skill almost nobody practices, and it's the one that matters most in the room. Say the number plainly — "I'm asking for 82K" — and then stop talking. The silence that follows feels enormous, and the urge to fill it by immediately softening ("but obviously I'm flexible," "whatever makes sense," "no pressure though") is close to universal. Resist it. Every word you add after the number, before the other person has responded, is a discount you're offering for free. Let your manager be the one who speaks next, even if it takes an uncomfortable few seconds. Silence isn't a negotiating trick — it's simply giving the number room to be heard as serious.

4. Handle "the budget's frozen" without abandoning the number

A frozen budget is one of the most common deflections, and it's usually true, not a lie — but it's a timing problem, not a verdict on whether your case is valid. The mistake is treating it as a no and retreating. Instead, acknowledge the constraint and ask what would actually need to be true for an exception: is there an off-cycle process, a different budget line, a review that happens at a specific point in the quarter? Keep the number exactly where it is while you find out. A frozen budget explains why the timing is hard; it says nothing about whether the case is fair.

5. Turn "let's revisit it later" into an actual date

"Let's circle back next quarter" is one of the friendliest-sounding non-answers in the workplace, and it's also one of the easiest promises to quietly let evaporate — for both sides, honestly, because neither of you put anything on a calendar. The fix is simple and almost always works: propose a specific date, a specific deliverable ("I'll send the scope breakdown by Thursday"), and a specific checkpoint meeting. "Can we put a date on that — say, the 15th?" converts a vague good intention into a real commitment that both of you can be held to, and it costs your manager nothing to agree to, which is exactly why it usually works.

6. If the answer is no, ask what would make it a yes

A flat no is rare; a soft no with room to grow is common. Rather than accepting silence or a vague "maybe next year," ask directly: "What would need to be true for this to be a yes — a specific project, a certain scope, a particular timeframe?" This does two things. It turns an ambiguous rejection into a concrete roadmap you can actually work toward, and it signals that you're serious and persistent without being combative. Write down the answer, and refer back to it explicitly the next time you raise the topic — that follow-through is itself part of the case.

7. Close the loop with a real system, not a good feeling

However the conversation lands — a yes, a date, a roadmap — leave it with something concrete attached: a document you'll send by a specific day, a calendar invite for the follow-up, a written summary of what was agreed. A warm conversation that ends with nothing written down is the easiest thing in the world for both people to remember slightly differently a month later. Sending a short recap email the same day — "just confirming what we discussed: I'll send the scope breakdown Thursday, we're revisiting the number on the 15th" — costs two minutes and removes almost all of the ambiguity that lets a promising conversation quietly go nowhere.

A full script you can adapt

Putting it all together, a raise conversation can follow a shape as simple as this:

• Open with the topic, not a preamble. "I wanted to use this time to talk about my compensation."
• State the case in one or two sentences. "Since [date], I've taken on [specific scope] — that's roughly [comparison, e.g. 'a role and a half'] at my current level."
• State the number and stop. "I'm asking for [specific number]." Then silence.
• Respond to a deflection by holding the number. "That's useful to know — the number the scope supports is still [number]. What would need to be true for an exception?"
• Convert any deferral into a date. "Can we put a specific date on that, so it's a real checkpoint?"
• Close with a written follow-up the same day, confirming whatever was agreed.

Common mistakes when asking for a raise

• Leading with personal circumstances instead of value delivered. It's sympathetic, but it isn't a business case, and only a business case gets approved.
• Asking a vague question instead of stating a number. "Could we maybe talk about my salary?" invites an equally vague, easy-to-defer answer.
• Filling the silence after the number. Softening the ask before anyone has even responded is negotiating against yourself for free.
• Accepting "let's revisit it" with no date attached. Without a specific checkpoint, a friendly deferral is functionally identical to a no.
• Treating a frozen budget as a final answer. It's a timing constraint, not a verdict on whether the case is fair — ask what has to change.
• Leaving the conversation with nothing written down. A warm conversation and a real commitment are not the same thing until one of you puts it in writing.

Frequently asked questions

How do I ask for a raise without sounding entitled?

Anchor the ask in the value you've delivered — added scope, results, responsibilities you've absorbed — rather than personal circumstances like rent or bills. A raise tied to impact reads as a business case your manager can evaluate; a raise tied to need reads as a favor they can grant or decline.

What's the best salary negotiation script to use?

State a specific number with a specific reason in one or two sentences — for example, "I'm asking for X, based on the scope I've taken on since [date]" — then stop talking. Resist the urge to soften, discount, or justify further before your manager has even responded; let the silence sit.

What if my manager says the budget is frozen?

Acknowledge the constraint without abandoning the number: ask what specifically would need to be true for an off-cycle exception, and keep the conversation on that path instead of quietly shrinking the ask to fit the excuse. A frozen budget is a timing problem, not a verdict on the case.

How do I respond if my manager says "let's revisit next quarter"?

Convert it into a specific date on both calendars, with a concrete next step attached — a document you'll send, a checkpoint meeting, a deadline for a decision. A vague "later" with no owner and no date is the easiest way for a raise request to quietly die.

Should I bring up other job offers?

Only if it's true and you're prepared to follow through — a bluffed offer that gets questioned destroys the whole case. A real competing offer is powerful leverage, but the scope-and-value case above should stand on its own regardless; don't build the entire ask around a threat.

What if I get a smaller raise than I asked for?

Accept it as a data point, not a final answer — ask directly what the gap represents and what timeframe would close it, then put that answer in writing. A partial yes with a documented path forward is a far better outcome than a full ask that gets forgotten.

Not sure whether presence, clarity, listening or handling conflict is the thing quietly holding your career back? Take our free communication skills test. It scores six dimensions of real conversation and tells you, bluntly, where to build first.