How to Ask for a Raise in the US: Timing, Numbers and Three Scripts

Most raises go to people who ask with a market number and a documented case. How to time the conversation, research your range, and three scripts for the meeting itself.

How to Ask for a Raise in the US: Timing, Numbers and Three Scripts

Raises in the US rarely arrive because someone noticed. Budgets get set in a specific month, managers get a fixed pool to distribute, and the people who capture the larger share are usually the ones who walked in with a number and a case. The ask is not the awkward part. Arriving without evidence is.

Timing: when the conversation can actually succeed

There are three windows worth targeting.

  • Two to four weeks before the annual review cycle. By the time reviews happen, the pool is already allocated. Asking earlier puts you in the conversation while your manager can still influence the split.
  • After a visible win you can point to. A launch that hit its target, a client you retained, a system you rebuilt. The week after the win is when your value is least arguable.
  • During budget planning, usually late Q3 or early Q4 for a January fiscal year. Ask your manager when comp planning happens — it is a normal question and it gives you a calendar.

Three moments to avoid: the same week as layoffs or a hiring freeze, the day after a bad quarter gets announced, and your first week back from a leave you did not explain.

Build the case with a number, not a feeling

You need a range, and you need to be able to say where it came from. Pull three sources: your employer's own job postings for a similar title, a salary data site filtered to your metro or to "remote, US," and one or two conversations with people in comparable roles at other companies. Levels.fyi is the strongest source in tech, Glassdoor and Payscale are the broadest, and your state's labor department publishes wage data by occupation if you want a public reference.

Then adjust for your situation. A fully remote role paid against a national band may sit below San Francisco numbers and above Midwest numbers — quoting a Bay Area figure at a company with national bands invites a dismissal. If your title undersells your work, present the case in terms of scope and responsibilities rather than the title alone.

Write down three or four accomplishments with numbers attached: "Reduced onboarding ticket volume 34% by rewriting the support docs," "Closed $180K in renewals in Q2," "Cut deploy time from 22 minutes to 6." Vague praise about being a team player moves nothing.

Three scripts you can adapt

Script one, direct ask: "I want to talk about my compensation. Based on what I have delivered this year and on market data for this role in the US, I am looking for a base of $X. Is that something you can support, and if not, what would need to happen for it to be possible?"

Script two, after a win: "Now that the migration is live and we have two months of clean data, I want to revisit my compensation. I am at $Y and the market range for my scope is $Y to $Z. I would like to get to $Z this cycle."

Script three, when you suspect the band, not your performance, is the limit: "If my current title is capped at this range, what would a promotion to [next level] require, and what timeline are we looking at? I would rather work toward a specific bar than guess."

All three end with a question that keeps the conversation going. Never end on a flat demand with no exit — it forces a yes-or-no answer while your manager is still absorbing the number.

Handling "not right now"

"Not now" is a real answer in most US companies, but it should have a shape. Ask three follow-ups before you leave the room: what specifically needs to be true for this to happen, when can we revisit, and can the agreement be confirmed in writing. Then send a short recap email the same day: what you asked for, what was discussed, and the date you agreed to revisit. A documented conversation has a way of showing up on the next cycle's agenda.

If you get a firm no with no path and no timeline, that is information. Quietly update your resume, check what the market is paying, and decide with real data rather than frustration.

What never helps

  • Threats you will not execute. "I will leave if this does not happen" only works if you are prepared to, and it costs you leverage if you stay.
  • Comparing yourself to a named coworker. Comp conversations are confidential, and the mention reads as a grievance rather than a case.
  • Personal expenses. Rent and inflation are context, not a business justification. The case is your scope and the market.
  • A number you would be embarrassed to accept. Ask for the real target, then negotiate from a range you have researched.