You build the case entirely on documented internal value: market-rate data for your role and location, a written record of how your scope has grown since your last comp review, and a request timed to a review cycle or right after a major shipped win, not dropped into a random Tuesday. No external offer, no ultimatum, just evidence a manager can take to their own boss and defend.
Negotiating with a competing offer in hand is a different, easier problem. If you have one, salary negotiation for tech professionals covers how to use it. This article is for the harder, more common situation: you like your job, you are not interviewing anywhere, and you still think you are underpaid for what you are now doing.
Why does asking without an offer feel so much harder?
Because an external offer does the persuasion work for you. It is a number a market has already agreed to pay, verified by someone else's hiring process. Without it, you are asking your manager to trust your own account of your value, which is a weaker starting position by default, unless you replace the missing offer with something almost as concrete.
That replacement is evidence. Glassdoor's guide to asking for a raise notes that a well-prepared case built on market data, documented contributions, and a clear ask can work about as well as a competing offer, because it gives the manager the same thing a competing offer gives them: a number they did not have to invent, and a paper trail they can forward upward. Framing the request around market research and unique contributions, rather than a vague sense of being undervalued, is what makes that case land, according to the same guide.
What evidence actually makes the case?
Three things, and none of them are "I feel underpaid."
Market-rate data for your specific role, level, and location. General salary averages are weak evidence because they do not isolate your title, seniority, or geography. Pull actual ranges from Levels.fyi for tech-specific total comp, Glassdoor or LinkedIn Salary for roles it does not cover, and, if you can get it, a current internal posting for your own title. A number pinned to a named source is much harder to wave off than "I looked around and I think I'm underpaid."
A written record of what changed since your last raise. Scope creep is invisible to most managers until someone writes it down. List what you owned a year ago against what you own now: new systems you run solo, people you now mentor or informally lead, projects that used to need a senior engineer's sign-off and no longer do. Robert Half's guide to asking for a raise recommends compiling this into a short written summary with salary benchmarks and measurable results, so your manager has something to forward if the decision needs approval above their level. A one-page document beats a verbal list every time; managers negotiating on your behalf need something to hand to finance, not a memory of what you said in a meeting.
Quantified outcomes, not just activity. "I shipped the migration" is weaker than "I led the database migration that cut query latency by 40% and removed the need for a contractor we'd budgeted for." Tie each accomplishment to a business outcome, revenue, cost saved, risk reduced, time saved, wherever you can attach a real number.
Industry perspective
"Don't get fixated on money. Focus on the value of the entire deal."
— Deepak Malhotra, Harvard Business School, via Harvard Law School Program on Negotiation
When should you actually have this conversation?
Two windows work far better than the rest of the calendar.
Right before your formal review cycle, not during it. Raise the topic a few weeks ahead so your manager has time to pull budget data and, if needed, get sign-off from their own manager or finance before the review conversation happens. Walking in cold on review day with a number for the first time gives them no room to prepare a real answer.
Right after you ship something that mattered. The evidence is freshest and hardest to dispute immediately after a launch, a resolved incident, a closed deal, or a project that visibly exceeded expectations. Waiting six months to raise it means your manager is now reconstructing the impact from memory instead of watching it happen.
Avoid asking during a hiring freeze, right after a layoff round, or in the same week as a bad earnings report. Timing that ignores what your manager is dealing with signals that you have not done the "assess organizational financial health" step of your research, and it makes a genuinely deserved raise look tone-deaf.
What do you actually say?
Frame the ask as aligning pay to scope that has already expanded, not as a demand. The distinction matters: one is a factual correction your manager can agree with, the other is pressure they have to push back against.
A workable structure for the actual conversation:
- State that you want to discuss your compensation, and ask for dedicated time rather than folding it into another meeting.
- Walk through what has changed in your role since the last comp review, using your written list.
- Name your market-rate research and where it came from.
- State a specific number. Not "market rate," a number: "Based on this, I'm asking for [X]."
- Stop talking. Let the silence sit. Do not immediately soften the number or offer a discount before they respond.
A short version of that framing: "Since my last review, I've taken on [specific scope]. Based on [source]'s data for this role and level, that puts market rate at [X]. I'd like to align my compensation with what I'm actually doing now." That is a statement of fact with a number attached, not a negotiation opener that invites haggling down from an inflated ask.
What if they say there's no budget right now?
Treat it as the start of a second conversation, not the end of the first one.
Ask directly what would change the answer: is it a timing problem (budget resets next quarter, next fiscal year) or a scope problem (they do not yet see your case the way you do)? Robert Half's guidance for this exact scenario is to ask what milestones would justify an increase and agree on a timeline to revisit it, so "no" converts into a dated follow-up instead of a dead end. Get that follow-up date in writing, in an email recap if nowhere else, so it does not quietly disappear into next year.
If base pay is genuinely frozen, ask about the levers that are not tied to the same budget line: a one-time bonus, funding for a certification or course, extra PTO, or a title change that sets up the next comp cycle. None of these fully substitute for base, but a real concession beats a vague promise, and a documented "we'll revisit this in Q2" is worth much more than an unscheduled "sometime soon."
Should you threaten to leave if there's no real offer behind it?
No. An unbacked threat to quit is close to the riskiest move available in this conversation, and it is a common failure mode precisely because it feels like the fastest way to get negotiating power you do not otherwise have.
The mechanics of why it backfires are straightforward. A real competing offer works because it is externally verified: someone else already agreed to pay that number. A bluff has no such backing, and managers who have been in the role for a while have usually seen the move before. If they do not call it, you get an awkward raise granted under duress, with a manager who now privately treats you as a flight risk on the next round of promotion or project decisions. If they do call it, either by asking to see the offer or simply declining to match a threat with nothing behind it, you have burned trust with no compensation to show for it and no real option to fall back on. Either outcome costs more than it buys.
This is the same dynamic covered in how to handle a counter offer from your current employer: a raise that only exists because of a resignation threat, real or bluffed, is not a fixed comp problem, it is a stall tactic that tends to resurface. If you are going to use a competing offer as a negotiating tool, it needs to be real. If it is not real yet, this article's evidence-based approach is the actual path, not a substitute conversation dressed up as one.
How does Hire.monster help you build this case?
Hire.monster's job board surfaces structured salary data straight from the ATS source on live postings, which is useful even when you are not actively applying. Pulling current ranges for your title and level from real, currently open postings gives you a second, independent data point alongside Levels.fyi or Glassdoor, strengthening the market-rate half of your case before you ever sit down with your manager.
If the raise conversation stalls or the timeline your manager gives you keeps slipping, that is also the point to start a quiet parallel search rather than wait indefinitely. Browse current roles at hire.monster/jobs.
Key takeaways
A documented case replaces the negotiating power a competing offer would provide
Market-rate data tied to your specific role and location, a written record of expanded scope, and quantified outcomes give a manager the same thing an external offer gives them: a number they did not have to invent and a paper trail they can defend upward.
Timing the ask to a review cycle or a recent win beats asking cold
Raise the topic a few weeks before your formal review so there is time to get budget approval, or ask right after a major shipped win while the impact is fresh. Avoid asking during a freeze, layoff, or a bad earnings quarter.
Frame the request as aligning pay to scope, not as a demand
State what has changed since your last comp review, cite your market research, then name a specific number and stop talking. This reads as a factual correction, not pressure your manager has to resist.
A "no budget" answer should convert into a dated follow-up, not a dead end
Ask what would need to change for the answer to be yes, and get a specific timeline in writing. If base pay is frozen, ask about bonuses, professional development funding, or a title change that sets up the next cycle.
An unbacked threat to quit usually costs more than it gains
A real competing offer is externally verified; a bluff is not, and experienced managers can tell the difference. Getting caught bluffing damages trust permanently, while a granted raise under a threat you did not mean often leaves you marked as a flight risk anyway.
Frequently asked questions
Can I ask for a raise without any competing offer at all?
Yes, and it is the more common scenario in practice. A well-documented case built on market-rate data, a record of expanded scope, and quantified outcomes since your last comp review can work about as well as a competing offer, because it gives your manager a verifiable number and a paper trail rather than an ultimatum to react to.
How much of a raise is reasonable to ask for without an offer in hand?
There is no fixed number since it depends entirely on the gap between your current pay and documented market rate for your role, level, and location. Base your ask on that gap, not a round percentage picked in advance, and be ready to explain the sources behind it if your manager asks.
What if my manager agrees the raise is fair but says HR won't approve it?
Ask your manager what evidence HR or finance would need to approve it, and offer to provide a written one-pager with your market data and accomplishments they can forward. This shifts you from being blocked to actively supporting the internal approval process, which is often the actual bottleneck, not disagreement about whether you deserve it.
Is it better to ask verbally or send a written request first?
Request a dedicated conversation rather than raising it in passing, but come with a short written summary of your case, market data and accomplishments, that your manager can keep and forward. The conversation should happen live; the documentation should exist on paper either way.
What if I get a vague "we'll revisit it later" instead of a real answer?
Treat vague, undated promises as effectively a no. Ask for a specific milestone and date to revisit the conversation, and get that date confirmed in writing, even just a follow-up email recapping what was discussed. Without a date attached, "later" tends to quietly become never.
Whatever you decide to do next, track the conversation and any follow-up dates somewhere durable instead of trusting memory. And if the raise conversation stalls out longer than it should, hire.monster/jobs is a reasonable place to start looking quietly at what else is out there.