You Deserve More Money. The Conversation Is the Hard Part.

You've rehearsed it in the shower. You've drafted the message three times and deleted it three times. Then your manager walks past your desk, says something about the Q3 deadline, and the moment evaporates again.

Almost everyone I've talked to about pay describes the same thing: the money isn't the hard part. The conversation is. It feels presumptuous, or greedy, or like you're asking a favor from someone who already knows what you're worth and has decided otherwise.

Here's the reframe that helps. A raise conversation isn't a favor request. It's a budget conversation — and your manager is in it too, usually with less information than you assume and less power than you fear. Their job is to argue your case upward to someone else. Your job is to hand them the argument.

The person you're asking is rarely the person who says yes. Give them what they need to win the meeting you won't be in.

The odds are better than the dread suggests

The fear of asking is wildly out of proportion to the downside. Fidelity's research on pay negotiation found that roughly 85% of people who countered on salary, benefits, or both got at least some of what they asked for — and the rate was slightly higher for professionals in their late twenties and early thirties. Not "got everything." Got something. That distinction matters, because "something" compounds for the rest of your career.

Think about what a 4% raise actually does. On a $70,000 salary, it's $2,800 this year. But it also resets the base that every future percentage raise multiplies against. Five years of 4% on a $70,000 base lands you near $85,000; five years of 4% on a $72,800 base lands you near $88,600. The gap isn't the $2,800 — it's $2,800 plus every raise that stacked on top of it. This is why pay negotiations early in a career matter more than they feel like they should.

And the downside? In most healthy workplaces, the worst realistic outcome of a well-prepared ask is "not right now, here's what would change that." That's not a rejection. That's a roadmap, and it's more than most people ever get, because most people never ask.

Timing beats eloquence

You can deliver a flawless case at the wrong moment and get nothing. You can deliver an average case at the right moment and get the number.

The right moment usually has three properties. Budget exists or is being set. Most companies plan compensation on a cycle — often 4 to 8 weeks before the fiscal year or review period closes. Once the numbers are locked, your manager genuinely cannot move them, no matter how convincing you are. Ask your manager directly: "When does comp planning happen here, and when should I raise this so it's actually in the window?" That single question puts you ahead of most of your colleagues.

You've just done something visible. Shipping a project, closing a quarter above target, absorbing a departed teammate's workload — these are natural on-ramps. A positive performance review is the classic one, because someone senior has just put your value in writing.

Your manager isn't underwater. Don't do this the morning of a board presentation or during an incident. Ask for 30 minutes on the calendar with a subject line that doesn't ambush them: "Career and compensation check-in." Surprise is not your friend here. A manager who knows what's coming can pre-check the budget and arrive prepared to help.

Build the case out of evidence, not feelings

The single most common failure mode is arguing from need rather than value. Rent went up. Your friend at another company makes more. You've been here three years. None of these are arguments your manager can carry into a budget meeting, because none of them are about what you produce.

Swap each one for its evidence-based cousin:

The pattern is scope, outcome, number. What did you take on that you weren't hired to do? What changed because you did it? What's it worth in hours, dollars, retained customers, or reduced risk?

Keep a running file for this. Not a polished document — a plain text note where you dump one line every time something goes well. "Fixed the export bug that generated 40% of support tickets in March." Six months later, that note is the entire meeting. Trying to reconstruct a year of contributions the night before is how good work gets forgotten.

Then get outside data. Public salary bands, industry salary guides, recruiter conversations, and role-specific ranges on job postings in your city will get you a defensible window. Two rules: use ranges for your scope and location, not just your job title, and never cite a friend's salary. Titles mean wildly different things across companies, and a specific colleague's number turns a business conversation into an interpersonal one.

What number to actually say

Two different situations, two different math problems.

Internal raise. Most U.S. employers budget around 3–5% for annual merit increases across the board. That's the gravitational field you're working against. A request in the 5–10% range is defensible if your scope has genuinely grown; anything above that usually needs a trigger — a promotion, a title change, a documented market gap, or an outside offer. Asking for 25% inside the normal cycle without one of those tends to read as uncalibrated rather than ambitious.

External offer. This is where the leverage lives. A counter of 10–15% above the initial offer is standard practice when the offer sits at or slightly below market median, and it's very rarely taken badly. Companies expect a counter and often build room for one.

Name a specific number, not a range — if you say "$95,000 to $105,000," you have just negotiated against yourself and the answer will be $95,000. And here's the underrated move: after you say the number, stop talking. The silence will feel unbearable for about four seconds. Let it sit. Filling it is how people talk themselves down before anyone has even pushed back.

A script you can actually say out loud

Adapt the specifics, keep the shape. It's short on purpose.

"Thanks for making time. Over the past year my scope has grown quite a bit — I've taken over the billing pipeline, which used to be two people, and I led the migration that cut our error rate by about a third. Looking at market ranges for this scope in our area, the band is around $88,000 to $96,000, and I'm currently at $82,000. I'd like to move to $92,000. What would it take to get there?"

Four moves, roughly 45 seconds: what changed → what it produced → what the market says → what I'm asking. Ending with "what would it take" is deliberate. It's collaborative, it's hard to answer with a flat no, and it forces a concrete response instead of a vague one.

When the answer is no

Sometimes the budget really is frozen. A "no" is only a dead end if you let the conversation end there. Three things worth doing before you leave the room.

Make it specific. "I understand. What would need to be true for this to be a yes in six months?" If the answer is vague — "keep doing great work" — push gently for a criterion: which projects, which metrics, which scope. Write it down and send a short recap email afterward. That email is the whole point: it turns a hallway sentiment into a shared record.

Negotiate what isn't cash. Budgets for salary and budgets for everything else are often separate pots. Additional PTO, a compressed or flexible schedule, remote days, a conference or training budget, a title change, or a one-time bonus can all be live even when base pay isn't. A title change is especially underrated — it costs the company nothing today and raises your floor everywhere you go next.

Set a real date. "Can we revisit this in the January cycle?" An open-ended "later" quietly becomes never. A date on the calendar doesn't.

And if you get a firm no with no path, no criteria, and no date — that's information too. It's not a failure of your pitch. It's a data point about whether this role can pay you what your work is worth, and it's better to have it than not.

The short version

Ask during the budget window, not whenever courage strikes. Build the case from scope and outcomes, not tenure and need. Anchor on market ranges for your actual work, name one specific number, and then be quiet. If the answer is no, leave with criteria and a date instead of a feeling.

Most of the discomfort here comes from treating pay as a referendum on your worth as a person. It isn't. It's an ordinary business conversation that happens to be about you — and you're allowed to be prepared for it.

Whenever you have that conversation, I hope you walk in with your notes and walk out with a number. You've already done the hard part; the asking is just the paperwork.