How to ask for a raise when your manager already thinks you are paid fairly

Your manager pulls up a spreadsheet, points to a band, and says the number is fair. You believe them—the spreadsheet is real, the band is real, the math checks out. What it doesn't check is your job, which stopped matching that band about eight months ago.

"Fair" Is a Frame, Not a Fact

Here is what actually happens when a manager tells you your pay is fair: they are checking your salary against a compensation band tied to your job title, benchmarked once or twice a year against survey data—Radford, Mercer, Willis Towers Watson, whatever your company licenses. That band was calibrated to a job description written when you were hired. It was not recalibrated when you started running the client escalations nobody else wanted, or when your team lost a headcount and you absorbed the work.

Your manager isn't wrong that you're paid fairly for the job on paper. They're evaluating a document. You're evaluating a Tuesday. The gap between those two things is your entire case, and it splits into three parts: what the market pays for what you actually do, what you've taken on that isn't in the job description, and what it costs the company if you leave. Bring all three, in that order, and you're not asking for a favor—you're presenting a discrepancy.

Market Comp Is a Number, Not a Feeling

Start with data your manager can't wave away. Levels.fyi, Glassdoor, LinkedIn Salary, and your local salary transparency listings (mandatory in Colorado, California, New York, and a growing list of states) give you a range for your actual title and years of experience in your metro area. Pull three to five data points, not one outlier.

Say the market median for your role, at your level, in your city, is $98,000, and you're at $84,000. That's not a vibe—that's $14,000 a year, or $1,167 a month, which is the difference between contributing to a 401(k) match cap and not. Write the number down. Say it out loud before the meeting so it doesn't come out as a question.

Don't lead with a single job board screenshot—managers have seen those and have a reflexive dismissal ready ("that site skews high"). Lead with the range and the median, and name your sources. Precision reads as competence; vagueness reads as complaint.

Scope Creep and Forward Risk Are the Other Two Legs

Market comp gets you in the room. Scope creep is what makes the number undeniable. List, in writing, everything you're doing now that wasn't in your job description or your last leveling conversation—not vague responsibilities, actual deliverables with dates. "Took over vendor negotiations in March after Priya left and it wasn't backfilled." "Now the primary point of contact for the Meridian account, previously handled by a manager." Three to five items, each with a start date, is a stronger document than a paragraph of adjectives.

Then calculate forward risk—what it costs the company if this conversation goes nowhere and you leave in six months. SHRM's widely cited estimate puts the cost of replacing a salaried employee at 50% to 200% of their annual salary once you count recruiting time, onboarding, lost productivity, and institutional knowledge walking out the door. If you make $84,000, the low end of that range is $42,000—three times the raise you're asking for. You don't say this number to threaten anyone. You say it because it reframes the raise from an expense into a hedge, and managers who approve budgets understand hedges.

The Meeting Script

Don't open with "I feel like I deserve more." Feelings are easy to table. Open with the structure: market, scope, risk, ask. Here's the shape of it:

"I want to walk through three things and then make a specific ask. First, market data for my role and level in this city puts the median at $98,000—I'm at $84,000, and I've pulled listings from three sources to back that up. Second, since my last review I've taken on the Meridian account and vendor negotiations, both outside my original scope, starting in March. Third, I want to be straightforward: I like this job and I'm not shopping around, but I know what the market rate is for what I'm doing, and I'd rather solve this internally than have to decide later. I'm asking for $96,000, effective next pay cycle. What would you need from me to make that happen?"

That last question matters more than the ask itself. It converts a yes/no moment into a negotiation with a path, and it puts the burden of the next move on them, which is where it belongs—they control the band, not you.

If the answer is "the budget doesn't allow it right now," don't accept a vague future promise. Ask for specifics:

"Understood. Can we put a number and a date on this—say, revisit at $92,000 in Q3—so it's on the calendar and not just a conversation we had once?"

A manager who won't commit to a number and a date is telling you something about how this will actually resolve. That's useful information, even when it's not the information you wanted.

Open a spreadsheet tonight and log three market data points for your exact title and city, plus every task you've absorbed since your last review with a date attached. That document is the raise case. Schedule the meeting before you talk yourself out of it.