Asking for a raise is scarier than negotiating a job offer. At the offer stage, you are selling potential. When you ask for a raise, you are selling what you already delivered -- and if you get the tone wrong, you burn credibility you spent months or years earning.
The good news: no manager falls out of their chair when someone asks for a raise. It is part of the job. The bad news: asking the wrong way -- without numbers, without timing, without prep -- turns a professional conversation into an awkward one you cannot undo.
This post is not about what you deserve. It is about building a case with the same logic your boss uses to defend budget to their director.
Why "I need more money" is not an argument
Companies do not pay based on your personal expense spreadsheet. They pay for the value you generate -- or for the cost of replacing you on the open market.
Survey data from compensation consultancies in 2026 consistently shows that roughly two-thirds of managers approve raises when the employee presents a documented case with measurable results and market benchmarks. When the argument is purely personal ("my rent went up," "my kid started college"), the approval rate drops sharply.
This does not mean your cost of living does not matter. It means that argument alone will not convince the person who needs to sign off on the budget. Your manager needs something they can carry to the finance director. Your electricity bill does not close a budget spreadsheet. Your measured impact does.
Three things your manager needs to hear to defend your raise internally:
- What you delivered since your last review -- with numbers.
- What the market pays for someone doing what you do.
- What you do today that you were not hired to do.
Without all three, your request depends on your manager's goodwill. Goodwill does not scale.
Build your case with 3 pillars
Pillar 1: Measurable impact since your last review
You need a short list -- three to five items -- with concrete outcomes. Not "participated in project X." That is a job description. What works:
- "Reduced month-end close time from 5 days to 2 days by automating reconciliation across 12 GL accounts."
- "Led the CRM migration that impacted 80 sales reps, with zero data loss and 94% adoption within 60 days."
- "Shipped project Y three weeks ahead of schedule, freeing up $200K in opportunity cost for Q3."
Format: action verb + what changed + number + scale context.
If you do not have exact numbers, reconstruct them. Take the project, estimate before and after, ask colleagues, dig through old emails. A reasonable approximation with logic beats no data at all. "Reduced by approximately 30%" is better than "improved the process."
And do not wait for your annual review to start documenting. Start today. Every meaningful delivery goes into a separate doc -- a note, a Notion page, an email to yourself. Walking into the conversation with a 12-month memory of your achievements is not a strategy.
Pillar 2: Market -- what your role, region, and seniority actually pay
This pillar is about research, not opinion. Sources that hold up:
- Glassdoor: employee-reported salary data, filterable by company, title, and city. Best for corporate roles in major US metros and UK cities. Expect some self-reporting bias -- cross-reference.
- Levels.fyi: granular data on base, bonus, and equity for tech roles (engineering, product, design, data). Covers big tech, startups, and a growing set of international companies. If you work in tech, this is the single best source for comp bands by level (L3, L4, L5, etc.).
- Bureau of Labor Statistics (BLS): Occupational Employment and Wage Statistics (OEWS) program. Published annually, covers 800+ occupations with median wages by state and metro area. No self-reporting bias -- this is employer-reported survey data. Use it as a floor whenever possible.
- Payscale and Salary.com: aggregate data from employer surveys and user submissions. Good for roles outside tech. Both offer free salary reports with filters for experience, location, and company size.
- Peer conversations: three or four people in the same function, similar seniority, comparable company size. Ask about bands, not exact numbers. "What range would you consider fair for someone with my experience in this market?" is a better question than "how much do you make?"
For a deeper dive into each source and how to filter by industry, company stage, and work model, read the full guide: salary research: how much your role actually earns.
With your research done, you do not walk in with a single number. You walk in with a band -- floor, target, and ceiling. Example: "For a senior data analyst with 5 years of experience in Austin, the market range is $105K to $135K, depending on the total package."
If your current comp sits below that band and you are delivering on pillar 1, the argument is nearly built. If you fall within the band, the weight shifts more toward impact and scope.
Pillar 3: Scope -- what you do today that you were not hired to do
This is the pillar most people forget. Your starting salary was negotiated for scope X. If you are now doing X + Y + Z, the price changed.
Examples that count as scope expansion:
- You formally took over team leadership (tech lead, manager, team lead).
- You covered for your boss during a 4-month leave and the team did not skip a beat.
- You onboarded and trained three new hires.
- You started reporting to a VP instead of a director.
- You took over a strategic client relationship that used to belong to your manager.
- You became the point person for compliance, accessibility, SOC 2 -- something not in your original job description.
One note: "I started working longer hours" is not scope expansion. That is overtime. "I started managing the entire team's sales pipeline" is scope.
Combine the three pillars into a single summary sentence before the meeting:
"Over the past 12 months, I reduced month-end close time by 60%, onboarded three new analysts, and my market research puts the range for this role at $105K to $135K. My current comp is $88K. I would like to discuss an adjustment toward the $115K range."
Three pillars. Ten seconds. Your manager already understands the game.
Timing -- when NOT to ask for a raise
As important as what you say is when you say it. Bad timing burns credibility even with a strong case.
Right after mass layoffs or a bad quarter. If the company just laid off 15% of staff or the CFO reported below-guidance earnings, your raise request looks disconnected from reality. Wait for the next cycle or a strong delivery trigger.
One week before your annual review. The merit budget was locked weeks ago. Your manager cannot change anything at this point. The ideal conversation happens 3 to 4 months before the budget cycle -- when spreadsheets are still being built.
With nothing specific to show. If your last meaningful delivery was 8 months ago and you have been in maintenance mode since, you have no leverage. Build a significant delivery first, then ask.
New manager with less than 3 months in the role. They are still learning the team, the budget, and the dynamics. They do not have the context to evaluate your case or the influence to approve it. Wait for them to complete their first cycle.
You got a raise less than 6 months ago. Unless you had a radical scope change in that period (promotion, new team, new responsibility), asking again so soon weakens both your current and future cases.
Timing -- when TO ask for a raise
After delivering a major project with measurable results. You shipped, you measured, you documented. The momentum is on your side. The memory of the impact is fresh. Ask the week after results land, not three months later.
When you formally took on new scope. Got the email from your manager saying "you will also own X now"? Wait 60 days, deliver something within that new scope, and then ask. The argument is on the table: you are doing more than you were hired to do.
Before the annual budget cycle (3 to 4 months ahead). Most companies lock people budgets between September and November for the following year. If your review cycle is in March, have the conversation in November or December. Your manager needs lead time to include your number in the spreadsheet going up to leadership.
When you received an external offer -- but without using it as a threat. Having an offer from another company is a strong market signal. But walking up to your manager and saying "pay me X or I leave" is the fastest way to destroy the trust relationship. If you use the offer as a reference point, the tone is: "I received an offer at $130K for a similar role. I would rather stay here. Is there room to discuss an adjustment?" You are not threatening. You are asking to stay.
After the company announces strong results. Record profit, Series B raise, expansion into a new market. The money exists. Your timing aligns with the company's momentum.
Conversation script: what to say from start to finish
A raise conversation does not start with "I need more money." It starts with a meeting request. Here is the playbook.
Step 1: schedule the conversation with neutral framing
Message to your manager (Slack, Teams, email -- depends on culture):
"Hi [Name], I have been here [X] months now and would love to set up some time to talk about my compensation and growth. Do you have 30 minutes next week?"
Why this works:
- "I have been here X months" anchors on tenure, not dissatisfaction.
- "Compensation and growth" is broad enough to not sound like an ultimatum.
- "30 minutes next week" gives your manager time to prepare and signals this is a conversation, not a vent session.
Do not say "I need to talk urgently" if it is not urgent. Do not send it on a Sunday night. Do not write a ten-paragraph Slack message. Three lines is enough.
Step 2: the first two minutes of the meeting
You walk in (or join the video call). Do not open with "so, about my salary." Open with positive context:
"Thanks for making time. I have really enjoyed the work over the past [X] months and feel good about what the team has accomplished. I put together a quick summary so we can talk about where I am at."
Three sentences. You are not apologizing. You are framing the conversation as professional, not adversarial.
Step 3: present the case using the 3 pillars
Now you go into substance. Do it like this:
- Impact: "Over the past 12 months, I delivered three main results: [project A with number], [project B with number], [project C with number]."
- Market: "I did some market research. For [your role and level] in [your city], the current range is $[X] to $[Y]. My current comp is $[Z]."
- Scope: "Since I started here, I have taken on [new responsibility 1], [new responsibility 2]. This goes beyond the original scope of the role."
Do not read from a piece of paper like a PowerPoint deck. Have the numbers in your head -- or in a discreet notepad. Your manager needs to feel that you know what you are talking about, not that you memorized a script.
Step 4: make the specific ask
The most common mistake is leaving the ask vague: "I would like a raise." A raise of how much? 5%? 30%? Double?
Be specific:
"My suggestion is an adjustment to $115K, which is within the market range for the role and reflects the current scope. I want to understand from your side: is this feasible in this cycle? If not now, what would the path and timeline look like?"
Why "my suggestion" instead of "I want" or "I need": because you are opening a negotiation, not giving an order. Your manager may have budget constraints you do not know about. But if they say "not right now," you already have the second question ready: "what is the path and timeline?"
Step 5: how to respond in each scenario
Manager says "let me check with HR and get back to you": Note the date. Ask: "Can you get back to me by [date -- suggest 15 days]?" If it slips, send a follow-up (next section).
Manager says "budget is locked for this year": Ask: "When does the next cycle open? Is there room to discuss an off-cycle adjustment based on the results I shared?" Sometimes retention budget exists. Sometimes it does not. Either way, you now know whether to wait or start looking.
Manager says "you are delivering well, but I need to see more consistency": This is the most common response and the most dangerous because it is vague. Ask: "What specifically would you want to see over the next [3 or 6] months to justify that adjustment?" Ask for objective criteria. If they cannot answer, the problem is unclear expectations -- and you need to solve that with or without a raise.
Manager says "the market is not paying that": You have the research. Show the data. Education, not confrontation. "The data I pulled from Glassdoor, Levels.fyi, and peer conversations points to a band between $X and $Y. If you have a different reference, I am happy to compare." If they have no data and you do, the weight is on your side.
Manager says "yes, I will move this forward": Do not celebrate in the room. Thank them with restraint: "Thank you. I will wait for the next step. If you need any additional information to defend this internally, I am available." And document what was agreed via email.
Follow-up email template (after the meeting)
Walked out of the meeting with a "let me check"? Send an email the same day or the following day. This creates a paper trail and applies polite pressure for a response.
Template:
Subject: Follow-up -- compensation conversation
Hi [Name],
Thanks for your time today. I appreciate us having the conversation about my role and compensation.
Just to recap what we discussed:
- I shared my key deliveries over the past 12 months: [project A], [project B], [project C].
- My market research points to a range of $[X] to $[Y] for [role] in [city].
- My suggested adjustment: $[specific number].
You mentioned you will check with [HR / leadership / finance]. I will wait for your response. If you need any additional information to support the case internally, let me know.
Can we pick this back up by [date -- 15 days out]?
Best, [Your name]
Do not write "anxiously awaiting" or "no pressure." Professional, direct, with the information your manager needs to argue the case. You are making their job easier.
Mistakes that sabotage your raise request
Things I see over and over that kill any case:
Threatening to leave without a real offer. "If I do not get a raise, I will start looking." The moment you say that at the table, your manager begins planning your replacement -- even if the raise gets approved. Your loyalty was questioned and that does not recover fast.
Comparing yourself to a coworker. "Alex makes more than me and we do the same thing." First: you do not know Alex's full package (bonus, equity, sign-on, negotiation context). Second: you are outsourcing your argument. The manager hears "Alex" and ignores your numbers.
Making it personal. "My kid started private school and tuition is $3K a month." Your personal life matters to you. To the company, what matters is the value you generate. Personal and professional are separate spheres at the negotiation table.
Asking over text, WhatsApp, or chat. A raise gets asked in a voice conversation -- in person or over video. Text loses tone, loses context, loses your ability to read the manager's reaction and adjust in real time.
Not having a number in mind. Walking into the meeting and saying "I would like a raise, I do not know how much, whatever you think is fair" is handing over the negotiation on a platter. You did the research. You have the number. If you do not, do not schedule the meeting.
Asking during a feedback session or one-on-one with no heads-up. Your manager walked in to talk about projects and goals. You change the subject to compensation. They are caught off guard, they do not have budget numbers top of mind, and the default response is "I will look into it." Schedule a dedicated conversation -- like in step 1 of the script.
Talking only about the future, never the past. "If I keep delivering, I deserve a raise." A raise is for what you already did, not what you promise to do. Promises do not pay bills. Deliver first. Ask second.
Using an emotional or aggressive tone. Crying, anger, ultimatums. If you have reached that point, your relationship with the job is already broken. A raise conversation is transactional, not therapeutic. Go in with data, not emotion.
What to do if the raise is denied
A "no" is not the end of the road. It is new information. With that information, you decide:
Scenario 1: denial with clear timeline and criteria. "Not now, but I can revisit in April. What I need to see is X and Y." This is a signal from a manager who wants to retain you. Accept the timeline, deliver X and Y, document it, pick it back up in April.
Scenario 2: vague denial with no criteria. "Not right now, let us see down the road." This is a stall. Insist on criteria and timeline. If neither comes, understand that the company does not have a structured compensation review process -- and may never have one. Recalibrate your expectations and assess whether staying makes sense.
Scenario 3: denial with a non-monetary counter-offer. "I cannot adjust base pay right now, but I can offer more remote days, a paid course, or extra equity." Evaluate the real value of those things. A $3,000 course does not replace $500 more per month in base. But an extra remote day might be worth more than money depending on your commute cost, time, and quality of life.
A raise is part of your career, not an exception
Asking for a raise is not embarrassing. It is career management. Every large company has a merit cycle. Every mid-size company has a retention budget. Every startup has a funding round that unlocks budget for key people.
The professional who never asks for a raise is betting that someone will remember them out of the blue. In over a decade of watching careers, I have seen that work fewer times than I can count on one hand.
Prepare the numbers. Pick the timing. Follow the script. And if your case is solid and the company does not respond, the market will.