Timing · Evidence · Script · The no

How to Ask for a Raise

The ask takes three minutes. The preparation is everything: the right week, five documented results, one specific number, and an answer ready for each way your manager can say no.

6
Timing windows
6
Evidence types
6
Script stages
6
Responses handled

When to Ask

Most raise requests fail on timing, not on merit. Find out when your organisation sets its budget and work backwards from that date.

6–8 weeks before the comp cycleBest window

Managers submit budget requests well before increases are announced. Asking after the numbers are locked means waiting a full year regardless of merit.

Within a month of a visible winBest window

A delivered launch, a renewed contract, a passed audit. The evidence is fresh in everyone's mind and does not need re-establishing.

After your scope grewWorkable

You absorbed a departed colleague's work, took on a team, or picked up a new region. Changed scope is the strongest argument that exists.

At a formal reviewWorkable

Expected and appropriate, but often too late to influence the budget. Raise the number before the review, then confirm it during.

During a hiring freeze or after a missed quarterWait

Even a well-made case is likely to be declined for reasons unrelated to you, and a declined ask is harder to revive within the same year.

The week of layoffs or a reorganisationWait

Your manager has no authority and no attention. Wait for the structure to settle, then use the new scope as your opening.

Build the Evidence Pack

Three to five items, each with a number and a date. Your manager has to repeat these to someone else — make them easy to repeat.

Revenue or cost impact

'Renewed the Meridian account at £340K after it was flagged as at-risk — a 12% uplift on the prior term.'

The strongest category. If your work touches money, lead with it.

Efficiency gains

'Automated the month-end reconciliation — 9 hours a month returned to the team and two manual handoffs removed.'

Translate hours into something the business recognises: capacity, throughput, or reduced overtime.

Scope you absorbed

'Took over the EMEA reporting line in March when Alex left, in addition to my existing remit — no backfill was hired.'

Unbackfilled work is the cleanest argument for a band change rather than a merit bump.

Quality or risk reduction

'Rewrote the onboarding checks — audit findings dropped from 14 to 2 in the following cycle.'

Risk work is chronically undervalued because nothing visibly happens. Quantify what did not happen.

People you developed

'Mentored two juniors; both promoted within the year and one now owns the deployment pipeline.'

Signals readiness for a senior band, not just a higher number in the current one.

External market data

'The published range for this title in this city is X to Y. I am currently at the bottom of it.'

Use as supporting evidence, never as the whole case. Data explains the number; your results justify it.

Choosing the Number

One figure, not a range. Whatever you name, expect the conversation to settle somewhere below it — so name the top of what you can defend.

Merit increase
roughly 3–5%

The standard annual adjustment for solid performance in an unchanged role. Rarely negotiable beyond a point or two.

Strong-performance ask
roughly 5–15%

The realistic band for a well-evidenced in-role request. Above ten percent, you need external salary data alongside your results.

Market correction
15%+

Defensible when you were hired below band or the market has moved. Requires published range data for your title, level, and city.

Promotion
Band change

A different conversation with a different approval path. If you are at the top of your band, this is the one to be having.

Percentages vary widely by country, sector, and year — treat the bands above as conversational shape, not a benchmark. Before you fix your number, check published pay ranges for your exact title, level, and city, and ask two people in your field what they would consider reasonable. Your own research beats any general figure, including these.

The Conversation, Line by Line

Six stages. The fifth one — the silence after the number — is the one people skip and the one that matters most.

1
The meeting request

"Hi Ravi — could we book 30 minutes in the next week or two? I would like to talk through my scope over the last year and my compensation. Happy to send a short summary beforehand so you have time with it."

2
The opening

"Thanks for making time. I wanted to talk about my compensation. I have been here two years, my remit has grown quite a bit in the last one, and I would like to make the case for bringing my salary in line with that."

3
The evidence

"Three things in particular. I took over the EMEA reporting line in March when Alex left and it was not backfilled. I renewed Meridian at £340K after it was flagged at-risk. And I rewrote the onboarding checks, which took audit findings from fourteen to two."

4
The number

"Based on that, and on the published range for this title in this market, I am asking for £72,000 — that is about a twelve percent increase on where I am now."

5
The silence

[Stop. Do not fill the pause, do not soften the number, do not add 'but I understand if that is not possible.' Let your manager respond first.]

6
The close

"That is helpful, thank you. Can I summarise what we agreed in an email so we are both working from the same thing? I will include the date we said we would revisit it."

The follow-up email — send it the same day

Hi Ravi,

Thanks for the conversation today. Capturing what we discussed so we are working from the same notes:

· I asked for £72,000, based on the EMEA reporting line I took on in March, the Meridian renewal, and the audit-findings work.

· You are checking what is possible before budget submissions close in October.

· We agreed to pick this up again in the week of 12 October.

Let me know if I have any of that wrong, and if there is anything else that would help the case internally.

Six Answers, and What to Say Back

Almost every response is one of these. The goal in each case is to leave with a number, a date, or a criterion — never just an impression.

They say

"There is no budget right now."

You say

"I understand. When is the budget for next cycle actually set? And if it were available today, is £72K the number you would support? I would rather know now what to aim at."

Converts a wall into a date and a number. Both are things you can hold someone to; 'no budget' is not.

They say

"You are already at the top of your band."

You say

"That is useful to know — it sounds like the conversation is about the band rather than the number. What would a promotion to the next level require, and how far am I from it?"

Reframes a dead end as a promotion track. If you are capped, the raise you want needs a title change.

They say

"Let us revisit at your review."

You say

"Happy to. Can we agree the specific things you would want to see by then, so the review is a confirmation rather than a fresh conversation?"

Without criteria, 'revisit at review' is a polite deferral. With criteria, it becomes a plan you can execute against.

They say

"I need to check with HR / my director."

You say

"Of course. What is a reasonable time to hear back — would end of next week work? And is there anything you would want from me to support the case internally?"

Gives your manager a deadline and an ally role. Most raises are actually won in that internal conversation, not yours.

They say

"Why do you think you deserve this?"

You say

"Fair question. The clearest one is the EMEA line — I have been carrying it since March without a backfill, and the reporting has stayed on time throughout. That is a scope change, not just a good year."

Answer with a single strongest example rather than repeating all five. Depth reads as confidence; a list reads as pleading.

They say

"We can do 4%."

You say

"Thank you — I would like to accept that as a first step and keep the gap to £72K on the table. Could we book a follow-up for the next cycle with the remainder as the agenda?"

Accept the money, keep the conversation open. Treating a partial yes as a closed matter forfeits the rest.

Six Mistakes That Sink the Ask

Arguing from personal need

Rent, childcare, and cost of living are real, but they are not evidence of value to the business. Lead with results; the personal reasons do not need to be in the room.

Naming a range instead of a number

Say '£72,000,' not '£68 to 75K.' A range is heard as its bottom figure, every time.

Apologising into the ask

'I know this might not be possible, but...' concedes the negotiation before it starts. State the number plainly and stop.

Ambushing your manager

Springing it on them in a corridor or at the end of an unrelated meeting guarantees an improvised answer, which is usually no.

Threatening to leave without an offer

An implied ultimatum you cannot back damages trust permanently. Only bring an offer into the room if the offer exists.

No written follow-up

Send a short summary email the same day. Verbal commitments evaporate when managers change, and they do change.

Frequently Asked Questions

How do I ask for a raise?
When is the best time to ask for a raise?
How much of a raise should I ask for?
Should I ask for a raise by email or in person?
What if my manager says there is no budget?
Should I mention a competing job offer?
What if I am told to wait for the review cycle?
Can I ask for a raise after only six months?

Rehearse It Before You Live It

Kindyra's AI salary negotiator plays your manager — including the difficult version — so the first time you say the number out loud is not in the real meeting.