Asking for a raise is a skill, not a personality trait. Here is when to ask, how to research what you are actually worth, and word-for-word scripts you can adapt for the conversation.
Most people are underpaid not because they lack the skills but because they never ask, or they ask badly. The good news is that negotiating a raise is a learnable process with three parts: timing the conversation, backing your number with evidence, and knowing what to actually say when your palms are sweating. Do those three things and you shift the odds dramatically in your favor. Here is how each part works, with scripts you can adapt word for word.
Time the Ask Around Leverage, Not Anniversaries
The worst time to ask is when it is convenient for you and invisible to your manager. The best time is when your value is freshly visible. Right after you ship a major project, land a big client, absorb a departing colleague's work, or get praised in front of others, your leverage is at its peak. Bring it up while that memory is warm.
Also align with your company's calendar. Budgets for the next year are usually set one to two quarters before it begins, so raising the topic weeks before those decisions are locked is far more effective than asking the day salaries are already frozen. If you wait for the formal annual review, the number is often already decided, so open the conversation four to six weeks earlier.
Avoid asking during a visibly bad week, right after layoffs, or when your manager is underwater. Timing is not manipulation. It is choosing a moment when the person can actually say yes and is inclined to.
Research What You Are Actually Worth
Walking in with a feeling gets you a feeling in return. Walking in with data gives your manager something to take upstairs. Before the conversation, build a defensible number using several sources rather than one.
- Check market ranges on Levels.fyi, Glassdoor, LinkedIn Salary, and Payscale for your title, location, and years of experience.
- Ask trusted peers in your field directly, since a real number from someone you know beats any aggregate.
- Look at what your company pays in current job postings for your role, which sometimes lists a range by law.
- Factor in your specific scope: if you manage people or own revenue, you sit at the higher end of the range.
Then assemble your evidence. List three to five concrete accomplishments from the last six to twelve months, each with a result attached: the migration you led, the process that cut turnaround time, the target you beat. This is the proof that turns your request from a wish into a business case.
Decide on three numbers before you walk in: your target, your walk-away minimum, and an ambitious anchor slightly above target that you state first. Anchoring high is not greedy; it gives the negotiation room to land where you actually want.
You are not asking your manager for a favor. You are making the case that your pay has fallen behind the value you already deliver, and giving them the evidence to fix it.
Script One: Opening the Conversation
Do not ambush your manager. Ask for a dedicated meeting so they are prepared and not defensive. A short message works: Hi Sam, I would like to set aside twenty minutes this week to talk about my compensation and where I am headed here. When works for you?
Then, in the meeting, open with something like this. Over the past year I have taken on the onboarding revamp and the reporting pipeline, and the team's ticket turnaround dropped by about thirty percent as a result. Based on that impact and market rates for this role, I would like to discuss bringing my salary to 92,000. I want to make sure my pay reflects the scope I am now carrying.
Notice the shape: results first, a specific number second, and a calm reason to close. State your number and then stop talking. Silence is uncomfortable, and the instinct is to fill it by softening your ask. Resist that. Let them respond.
Script Two: When They Say There Is No Budget
A no is often a not right now, or a not in cash. Keep the door open and get specific. Try: I understand budgets are tight this quarter. Can we agree on the number and a timeline, so that if I hit the goals we define, the increase takes effect in the next cycle? And in the meantime, what specifically would need to be true for you to approve this?
This does two things. It turns a vague rejection into concrete, written criteria you can meet, and it prevents the goalposts from quietly moving later. If cash is genuinely frozen, pivot to other levers: If salary is not possible right now, could we look at a one-time bonus, extra paid time off, a title change, a learning budget, or a remote-work arrangement? Some of those cost a different budget line and are easier to grant.
Script Three: Responding to a Lowball Counter
Suppose you asked for 92,000 and they offer 84,000. Do not accept on the spot and do not get emotional. Acknowledge, then hold your ground with a reason. Thank you, I appreciate the movement. Based on the market data I pulled and the results from this year, I was expecting something closer to 90. Can we meet at 89,000?
If they cannot move on base pay, ask them to close the gap another way, such as an earlier review date in three months or a guaranteed bonus. Always get the final agreement in writing, even a short email confirming the number and start date, so there is no confusion when payroll runs.
After the Conversation, Whatever the Answer
If you get the raise, say a genuine thank you and ask what the next level up looks like, so you are already building the case for the following round. If you get a firm no, do not sulk. Ask exactly what would change the answer and by when, then put it in your calendar to revisit.
The single biggest predictor of being paid fairly over a career is simply being willing to have this conversation, respectfully and repeatedly. Prepare your evidence, pick your moment, use these scripts as a starting point, and treat each ask as practice for the next one. The discomfort fades, and the compounding effect on your income does not.
Written by
David Okafor
Design & Technology
David covers the tools, spaces, and interfaces we live inside. He believes good design is mostly restraint, and that the best technology is the kind you forget you are using.
0 Responses