You've been in the role 18 months. Your scope has quietly doubled. You know you're underpaid. And the thought of "shopping around just to get a counter" makes you want to lie down.
Good news: you don't need a competing offer to get a raise. You need a different kind of leverage — one built from inside the job you already have. Done well, this path is often cleaner than waving an outside offer around, because nobody feels blackmailed and nobody writes you off as a flight risk the moment the raise clears.
Here's how to run it.
Why "no competing offer" is not the weakness you think it is
Managers approve raises for three reasons: the person is underpaid for their current scope, the person is about to leave, or the person is about to be promoted. A competing offer only addresses the middle one — and it addresses it with a threat.
If you can make a clear case for the first or third reason, you don't need the threat. You need evidence. Most people skip the evidence step and go straight to "I feel I deserve more," which puts the manager in the awkward position of having to argue with your feelings.
Don't do that. Argue with data instead.
Step 1: Separate "raise" from "market correction"
There are two different asks hiding inside "I want a raise," and they're negotiated differently.
- Market correction: your pay is below the market rate for the work you're already doing. The ask is "pay me what this role pays."
- Scope-based raise: your responsibilities have grown past your original job description. The ask is "pay me for the job I'm actually doing now."
Figure out which one you're making before you walk in. A lot of raise conversations go sideways because the employee is making a scope argument and the manager is responding to a market argument, or vice versa. If both apply — great, stack them. But name them separately.
Step 2: Build a defensible number
Without a competing offer, your number has to come from somewhere credible. Three sources, in rough order of weight:
- Published pay bands. If your company publishes them (increasingly common post-2023 pay-transparency laws in states like Colorado, California, New York, and Washington), use them. Point to the band for your level and where you sit in it.
- Market data for your title, level, and metro. Levels.fyi for tech, Payscale and the BLS Occupational Employment Statistics for most other roles. Pull a range, not a single number, and know how it was collected. (We compared the main sources in Glassdoor vs Levels.fyi: which is more accurate?.)
- Internal comparables you legally know about. In the US, the National Labor Relations Act protects most non-supervisory employees' right to discuss pay with coworkers. If a peer told you their number, you can use that information to inform your ask — you just can't quote them by name in the meeting.
Land on a specific target and a floor you'd accept. "Somewhere in the mid-nineties" is not a number. "$96,000" is.
Step 3: Document the scope change
This is the part nobody wants to do and it's the part that wins the meeting.
Open a doc. List, in bullets:
- Projects you've shipped in the last 12 months, each with a measurable outcome (revenue, cost saved, users, latency, headcount managed, customers retained — whatever your function measures).
- Responsibilities you own now that weren't in your original job description or last review.
- People you've onboarded, mentored, or unblocked.
- Any explicit "can you also take this on" moments where you absorbed work from a departure, reorg, or hiring freeze.
Three to seven strong bullets beat twenty weak ones. If a bullet doesn't contain a verb and a number, rewrite it or cut it.
This document does double duty: it's your argument in the meeting and the artifact your manager forwards to their boss when they go to bat for you.
Step 4: Pick the right moment
Timing is leverage you can create for free.
- Good moments: right after a visible win, during the budget-planning window (ask your manager when that is — most companies set compensation budgets 2–3 months before the fiscal year starts), at your formal review if the review process allows mid-cycle adjustments.
- Bad moments: right after a layoff announcement, during an active hiring freeze (though not impossible — see our guide on negotiating during a hiring freeze), the week before your manager's own review, Monday morning.
You don't need the perfect moment. You need a moment that isn't actively working against you.
Step 5: Have the conversation in two meetings, not one
This is the move most people miss.
Meeting one is a 15-minute "I want to talk about my growth and compensation" conversation. You lay out the scope change, share your doc, say you've been looking at market data, and ask your manager to think about where your comp should land. You do not demand a number in meeting one.
Why: your manager almost certainly cannot approve a raise alone. They have to talk to their manager, HR, or finance. Forcing an answer on the spot gets you a reflexive "let me look into it" at best and a reflexive "no" at worst. Giving them a week to go advocate for you — armed with your doc — gets you a real answer.
Meeting two, a week or two later, is where numbers get said out loud.
What to actually say
A script you can adapt. Keep it short — the doc does the heavy lifting.
"Thanks for making time. I want to talk about my compensation. Over the last year my scope has grown meaningfully — I'm now [owning X, leading Y, responsible for Z] — and when I look at market data for this level in [metro], the range is [$A–$B]. I'm currently at [$C], which is below that. I've put together a short doc with the specifics. I'd like you to take a look and come back with where you think my comp should land. I'm not asking you to decide today."
Then stop talking. Do not fill the silence. Do not pre-negotiate against yourself with "I know budgets are tight" or "I understand if that's not possible."
In meeting two, if the number comes back lower than your target:
"Thanks for pushing on this. That's closer, but it's still below the market range I shared. What would it take to get to [$target]? Is that a scope conversation, a timing conversation, or a title conversation?"
That last question is the important one. It forces a specific answer instead of a vague "budgets."
When the answer is no
Sometimes it will be, and not always for bad reasons. Freezes happen. Bands are real. Your manager may genuinely have fought and lost.
Don't walk out empty-handed. Negotiate for the next-best things:
- A written commitment to revisit in 90 or 180 days, with specific criteria.
- A promotion track with a timeline.
- A one-time bonus if the base is capped.
- Non-cash items you actually value: additional PTO, remote flexibility, a conference budget, a title change that will help you on the market later.
And then make a quiet decision about whether to start looking. A "no" that comes with no path forward is useful information. (If you're already there, we wrote about what to do when you're underpaid.)
The one mistake to avoid
Don't bluff a competing offer you don't have. Managers talk to recruiters. HR runs reference checks in both directions. The downside of being caught inventing leverage is permanent; the upside of a successful bluff is a one-time raise. Bad trade.
You don't need the bluff. A clean scope argument, a defensible number, and the willingness to ask twice will get you most of what an outside offer would have — without burning the relationship or starting a job search you didn't want.
If you want help turning your scope-and-market evidence into the exact language to use in the meeting, that's what SalaryAsk does. Paste in your current comp, your target, and the facts above, and get a script tailored to your situation.