The short answer
Asking for a raise is a proposal, not a request for a favour, and it is won in the months before the meeting rather than in the meeting itself. Build a written record of what changed since your pay was set, learn when the budget is actually decided, ask early enough to be in that cycle, and make your manager's internal case for them.
What matters most
- Pay decisions are usually made in a budget cycle. Ask before it is set, not when you feel ready.
- The case is about what has changed since your pay was last agreed — scope, results, responsibility — not about loyalty or need.
- Write it down and give it to your manager. They have to repeat your argument to someone else, often weeks later.
- A no should end with a written plan and a date, not with vague encouragement.
Why timing decides most of it
The most common reason a good case fails is that it arrives after the money is gone. Budgets for salary increases are typically set once a year, weeks or months before anyone hears the outcome, and once allocated they are extremely difficult to reopen. A strong argument made in the wrong month competes with nothing; the same argument made before allocation competes on its merits.
So the first task is not building your case. It is finding out when the decision happens.
- Ask your manager directly when salary decisions are made and what the process is. This is a normal question and does not commit you to anything.
- Work backwards. Aim to have the conversation comfortably before the budget is set, so your manager can put you into the plan rather than argue for an exception afterwards.
- Note the other natural openings: the completion of a significant piece of work, a formal change in your responsibilities, a colleague leaving whose work you have absorbed, or the point at which you take on managing people.
- Avoid the obviously bad moments: a hiring freeze, a redundancy round, the week a large client leaves, or the fortnight your manager is buried in something else.
- If you were promised a review at a defined point when you joined — the six-month review from your original negotiation — diarise it and raise it yourself. Nobody else will.
Building a case that can be repeated
Your manager will not be the person who approves this. They will have a short conversation with someone more senior, possibly weeks after speaking to you, and they will reproduce roughly as much of your argument as they can remember. That fact should shape everything about how you present it: write it down, keep it short, and make it about things that can be verified.
- 1Establish the baseline
When was your pay last set, and what was the job at that point? Everything that follows is the difference between then and now. Without the baseline the argument has no shape.
- 2List what changed in scope
More people, larger budgets, more systems, a wider region, work you have absorbed from someone who left. Scope changes are the most persuasive category because they are factual and nobody can argue with them.
- 3List results, with evidence
Specific outcomes with numbers where you honestly have them. If you do not have numbers, describe the thing precisely instead of reaching for a statistic you cannot support — a vague figure that gets challenged destroys the rest of your case.
- 4Note what you now do that is scarce
The system only you understand, the client who deals only with you, the certification the team needed. This is not a threat and should never be framed as one; it is a statement of where replacement risk sits.
- 5Establish the external picture
What the role pays elsewhere, from sources you could show. This is context rather than the argument itself, and it works best stated calmly and once.
- 6Write one page and send it
Baseline, what changed, results, and the ask. One page, sent after the conversation, is what your manager forwards. A conversation with nothing written after it is a conversation that has to be reconstructed from memory by someone with a busy week.
What to say
I have been here nearly three years now and I have not had a proper rise in all that time. I have always worked hard and I am pretty sure I am underpaid compared to other people doing this job. Costs have gone up a lot as well. Is there anything that can be done?
I would like to talk about my salary, and I have put a page together so you have it in writing. When my pay was set two years ago I was running the one reporting line; since then I have taken on the second region after Marco left, I am the only person here who can maintain the forecasting model, and the quarterly close has gone from nine days to four since I rebuilt it. Looking at what comparable roles are advertised at, I think the level of the job has moved and my pay has not. Could we look at bringing it in line before the budget is set?
When the answer is no
A no is common and is not the end of the process. What matters is whether you leave the room with something concrete or with encouragement, and that depends almost entirely on the questions you ask in the next two minutes.
- Ask why. "Not now" and "not at this level" are different answers requiring different responses. One is about timing; the other is about the job you are in.
- Ask what would change it. Get specifics — what would have to be true, and by when. If nothing your manager can name would change the answer, that is a genuinely useful thing to have learned.
- Ask for a date. A commitment to revisit at a defined point, written in an email you send afterwards, is worth far more than sympathy.
- Ask about the other levers. If cash is frozen, a title change, a development budget, extra leave, changed hours or a formal change of responsibilities may not be. Some of those improve your position for the next conversation as well.
- Send the summary. Two paragraphs recording what was discussed and what was agreed. Not a challenge — a record, which means the plan survives your manager's inbox and their possible departure.
What a repeated no tells you
If you have made a solid case at the right point in the cycle, been told no without a reason you can act on, and found that the promised revisit did not happen, you have your answer about this employer. That is worth knowing without drama. The reliable route to a substantial pay increase, for most people in most fields, remains changing jobs, and it is easier to look while employed and calm than after resentment has built.
You do not have to decide anything immediately. Update your resume, look at what the market is advertising, and see whether the outside picture matches the story you have been told internally. If it does, you can stop wondering. If it does not, you have a stronger position for the next internal conversation and a genuine alternative — the honest kind, which is the only kind worth having. If your organisation has no published pay structure at all, it is worth seeing what one looks like: the US federal pay tables show a full ladder of grades and steps in public, which is a useful contrast when you are trying to establish how your own employer decides these things.
Preparing the conversation
- You know when the salary budget for your team is set.
- You can state the date your current pay was agreed and what the job looked like then.
- You have at least three specific changes since, with evidence you could show.
- You have checked what the role is advertised at elsewhere, from sources you could name.
- Your case fits on one page and contains no figure you cannot support.
- You have decided what you would accept instead if cash is genuinely frozen.
- You have planned the two follow-up questions for a no: what would change it, and by when.
- You have not framed anything as an ultimatum, and you have not referred to an offer you do not have.
If you would rather open the conversation in writing, the salary negotiation letter builder and the promotion request letter builder both give you a structure to put your own evidence into. And if the answer turns out to be a permanent no, the resume builder is where the alternative starts.
Questions people actually ask
When is the best time to ask for a raise?
Before the salary budget for your team is set, which is usually weeks or months before anyone hears an outcome. Ask your manager when that happens and work backwards. Failing that, the natural moments are the completion of significant work, a formal increase in responsibility, or absorbing the work of someone who has left.
How much should I ask for?
Enough to close the gap your evidence demonstrates, and grounded in what the role is advertised at elsewhere rather than in a percentage you picked. We do not publish salary figures, because the right number depends on your market, level and location — build it from sources you could show your manager.
Should I mention that I have another offer?
Only if you genuinely have one and are genuinely prepared to take it. Using a real offer as leverage sometimes works and often changes how you are seen afterwards. Inventing one is the worst option available: it is checkable, and the consequence is not a failed negotiation but a lost job.
What if my manager says there is no budget?
Ask what would change the answer and by when, ask for a specific date to revisit, and ask what non-cash items are available — title, responsibilities, development budget, leave, hours. Then send a short email recording what was agreed, so the plan survives a busy quarter and a possible change of manager.
How do I ask for a raise without seeming ungrateful?
Frame it as a proposal rather than a complaint, and make it about the job rather than about you. A calm account of how the role has grown since your pay was set, with evidence, does not read as ingratitude to any reasonable manager — and a manager who treats one such conversation as disloyalty has told you something useful.