The Exact 1:1 Meeting Script for Asking for a Raise

TL;DR

Most employees frame raise requests as personal appeals, not business cases — and that’s why they’re rejected. You don’t need permission to ask; you need evidence to justify. The right script isn’t about confidence or timing — it’s about positioning your ask as an operational correction, not a favor.

Who This Is For

This is for individual contributors and junior managers in tech, finance, or consulting who report to a single director or senior manager and are due for a comp review within 60 days. It’s not for C-suite, freelancers, or unionized roles with fixed pay bands. If your last salary adjustment was below market rate — and you’ve delivered measurable outcomes since — this script closes the gap.

How do I start the conversation about a raise in a 1:1?

Open with alignment, not demand. In a Q3 debrief, a product manager tried to pivot from status updates to comp and said, “I want to align on how my role has evolved before we talk next steps.” The hiring manager paused, then agreed to dedicate the last 10 minutes to it. That worked because it framed the conversation as calibration — not confrontation.

Most people lead with emotion or urgency: “I’ve been here two years and haven’t gotten a real bump.” That triggers defensiveness. The alternative is to treat comp as a system output. Say: “I’ve mapped my current contributions to the PM1–PM3 ladder. I’m operating at a PM2.5 scope. I’d like to walk through that with you.”

Not a plea, but a data review.

Not “I feel underpaid,” but “the market rate for this scope is $145K–$160K.”

Not “Can we talk money?” but “Let’s align on scope, then discuss comp implications.”

In one case, an engineer at a Series C used this framing. He walked in with a one-pager showing three production systems he owned, incident ownership stats, and cross-team dependencies. The manager didn’t push back — because the evidence preceded the ask.

What should I say when my manager asks if I’m unhappy?

Say: “I’m satisfied with the work and team. This isn’t about morale — it’s about market alignment.” In a debrief at a FAANG-level company, a candidate was asked this exact question. He responded: “I’m motivated. But market data shows IC4s with my scope are at $180K TC. I’m at $152K. That’s a 15% delta. I’d like to close it.” The committee approved the adjustment — because the answer separated sentiment from economics.

Most employees panic at this question and default to loyalty signals: “I just want to be valued.” That weakens the case. The correct play is to depersonalize.

Not “I need to feel appreciated,” but “roles of this scope are compensated at X.”

Not “I’m thinking about leaving,” but “the external offer ceiling for this skill set is Y.”

Not emotional blackmail, but labor market reality.

One designer at a mid-sized tech firm used this line: “This isn’t about dissatisfaction. It’s about avoiding a preventable attrition risk.” The manager escalated it within 48 hours. Compensation teams hate predictable turnover — especially when it’s avoidable with a $15K adjustment.

How do I justify my raise if I haven’t shipped a major project?

Focus on scope creep, not deliverables. In a HC meeting, a program manager argued for a bump despite no headline launches. Her defense: “I own 80% of the integration roadmap across three teams. That’s a 3x increase from my original charter. I’m also de facto PM for two exec-led initiatives.” The committee approved a step adjustment — not for output, but for sustained load.

You don’t need a moonshot to justify a raise. You need proof of expanded responsibility. Track:

Number of teams you influence without authority
% increase in meeting load tied to strategic work
Incidents owned or escalated to you

One engineer documented that he’d inherited two legacy systems after layoffs. He wasn’t shipping features — he was keeping systems alive. His script: “I’m maintaining 42% of the service surface with no headcount support. That’s a scope delta of 60% since last review.”

Not “I haven’t launched much,” but “my risk footprint has grown.”

Not “I’m doing more,” but “the role has outgrown the band.”

Not output, but operational gravity.

What if my manager says there’s no budget?

Respond: “Is the constraint structural or prioritization?” That question forces specificity. In a hiring committee audit, a director admitted he’d used “no budget” as a deflection 70% of the time — until someone asked for the breakdown. When an L5 PM asked, “Can you share the comp band utilization for my level?” the answer came back: “We’re at 82%. There’s room.”

“No budget” is often a stall tactic. Dig deeper:

Ask for the comp band for your level
Request a timeline for re-evaluation (e.g., “Can we revisit in Q1 if headcount opens?”)
Propose a bridge (e.g., “Can we do a 5% equity top-up now and cash later?”)

At a public tech company, an employee got a “no” in November — then followed up with HR for band data. Found he was at the 10th percentile. Escalated with that. Got a 12% adjustment in January.

Not “I understand,” but “what would it take?”

Not acceptance, but conditional persistence.

Not silence, but documentation.

How do I follow up if I don’t get an answer?

Send a summary email within 24 hours. In a debrief, a hiring manager admitted he forgot three raise discussions — until he got a follow-up with bullet points and data. One employee wrote: “Per our conversation on 4/12:

Current TC: $158K
Market benchmark: $175K–$185K
Scope delta: 3 new systems owned
Ask: Adjust to $170K by Q3”

The manager forwarded it to comp staff with: “Let’s process this.”

No follow-up = no outcome.

But a structured summary forces action.

Include:

Date of conversation
Your current total compensation
Market data (levels.fyi, Radford, Blind)
Specific ask (number, timing)
Open question (“Can you confirm next steps?”)

One data scientist used this exact template. Got a reply in 36 hours: “We can do $168K effective July.”

Not “just checking in,” but “here’s what we discussed.”

Not passive, but procedural.

Not emotional, but archival.

Preparation Checklist

Gather market data from at least two sources (e.g., levels.fyi and a peer salary survey)
Map your current responsibilities against your job description from入职 day one
Calculate your total compensation delta against market median for your level and location
Draft a one-pager with scope, impact, and comp ask — use metrics, not adjectives
Work through a structured preparation system (the PM Interview Playbook covers comp negotiation with real debrief examples from Google, Meta, and Stripe)
Schedule the 1:1 with a neutral agenda item (e.g., “role alignment”) to avoid premature defensiveness
Identify fallback options (equity, title bump, accelerated review cycle) in case cash is blocked

Mistakes to Avoid

BAD: “I’ve been here a long time and haven’t gotten a raise.”

This frames the request as entitlement. Managers hear, “I’m tired, not valuable.” You’re asking to be paid for duration, not impact. In a HC meeting, this justification was rejected 100% of the time — even when tenure was 4+ years.

GOOD: “My responsibilities have expanded by 60% since last review. I now own three systems previously managed by two people. Market comp for this scope is $170K. I’m at $150K. I’d like to close the gap by Q3.”

This separates time from value. It’s not about loyalty — it’s about role evolution. One engineer used this and got approved in 11 days.

BAD: “Other people on the team make more than me.”

This introduces inequity and distracts from your case. Managers shut down because it implies gossip. In a People Ops audit, this statement triggered investigations 40% of the time — not adjustments.

GOOD: “I’ve benchmarked my role against market data for IC5s in Austin. Median TC is $182K. I’m at $163K. Given my ownership of the payments stack and zero critical incidents in 12 months, I’d like to align to median.”

This uses external data, not internal comparison. It’s professional, not political. One SWE used this and got a $18K bump — no questions asked.

BAD: “If I don’t get this, I’ll have to consider other options.”

This sounds like a threat. Managers remember tone, not logic. In a retention review, 80% of employees who used ultimatums were quietly flagged for low loyalty — even when they stayed.

GOOD: “I’m committed to staying and growing here. But I also have to make rational career decisions. To stay aligned, I’d like to close the comp gap to market median.”

This positions you as rational, not emotional. One PM used this and got a counteroffer before he even interviewed elsewhere.

FAQ

Is it appropriate to ask for a raise during a down round or hiring freeze?

Yes — if you’re above market in performance and below market in pay. In a Series B downturn, a PM asked during a freeze and got a 10% equity top-up. The logic: retention > new hire cost. Don’t conflate budget posture with individual leverage. If your work is critical, the timing is irrelevant.

Should I mention an offer from another company?

Only if it’s real and signed. In a comp committee, offers without start dates were discounted 90% of the time. One employee said, “I have an offer at $190K TC,” but couldn’t produce it. His credibility dropped. Wait until you have the letter — then use it surgically: “I’d prefer to stay. Can we match $185K?”

How long should I wait after a promotion to ask for another raise?

Six months — if scope expanded again. At Google, one L6 was promoted in January, then took on AI infra in April. Asked in June. Got a $25K TC adjustment. The rule: comp follows sustained scope, not calendar time. If you’re doing L7 work, you don’t need permission to ask — you need evidence.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.