1on1 Raise Request Template for Tech PMs: Downloadable Script

What should a Tech PM say in a 1‑on‑1 to secure a raise?

The request succeeds only when the PM frames the raise as a business‑impact signal, not as a personal entitlement. In a Q2 debrief, a senior PM from a large cloud provider turned a vague “I think I deserve more” into a data‑driven narrative that secured a $22,000 increase. The judgment is simple: the script must start with quantified impact, then map that impact to market‑rate compensation, and finally anchor the ask with a concrete timeline.

The opening line should read, “Over the last 12 months my initiatives have delivered $4.3 M incremental revenue and reduced cycle time by 18 %, which places my contribution at the 85th percentile of senior PMs in our org.” That sentence alone reframes the conversation from a personal plea to a strategic business case.

How do I structure the 1‑on‑1 raise request to align with the hiring committee’s mental model?

The mental model of senior leadership is a three‑step validation: (1) impact proof, (2) market benchmark, (3) risk mitigation. In a recent hiring‑committee debrief for a senior PM role, the panel rejected a candidate who listed “leaded a team of 5” because the impact metric was missing. The judgment: the script must be a three‑act play where each act satisfies one validation node.

Act 1 – Impact Proof

‑ List the top three outcomes with hard numbers (e.g., $4.3 M revenue, 0.9 % churn reduction, 1.2 M active users).

‑ Tie each outcome to a product milestone and your specific contribution (roadmap ownership, cross‑functional alignment, go‑to‑market execution).

Act 2 – Market Benchmark

‑ Cite the latest Levels.fyi data for “Senior PM, Cloud” at comparable firms: $185 K base, 0.07 % equity, $22 K signing bonus.

‑ Show the internal band range for your level (e.g., $165 K–$190 K) and position your current package ($155 K base) three percent below the median.

Act 3 – Risk Mitigation

‑ Offer a 30‑day “impact‑review” clause: if quarterly targets slip, the raise reverts.

‑ Propose a mentorship commitment to up‑skill two junior PMs, turning your raise into a talent‑development lever.

The script’s cadence mirrors the committee’s triage: prove value, show parity, lower perceived risk.

Which exact sentences should I use before, during, and after the raise ask?

The script is a dialogue, not a monologue. In a live 1‑on‑1, a PM from a fintech unicorn used the following three‑sentence flow and walked away with a $19,500 raise. The judgment: use a pre‑ask “framing” sentence, a concise “ask” sentence, and a post‑ask “next‑steps” sentence.

Pre‑ask framing – “I’d like to review the outcomes we delivered last quarter and discuss how they align with my compensation.”

Ask – “Based on the $4.3 M incremental revenue and the market benchmark of $185 K base for senior PMs, I’m requesting an adjustment to $177 K base, effective July 1.”

Next‑steps – “If you need any additional data, I can send a one‑pager by tomorrow, and I’m happy to set a follow‑up check‑in after the next product release.”

These three lines keep the conversation goal‑oriented, avoid rambling, and give the manager a clear decision point.

What timeline should I set to keep the raise negotiation moving forward?

A timeline that ends in “sometime next quarter” signals indecision; a hard 14‑day deadline signals urgency. In a Q3 debrief, a PM who gave a vague “maybe next year” saw the request disappear. The judgment: anchor the request to a concrete date and a measurable checkpoint, not to an open‑ended future.

The script should include: “I’d like to finalize the compensation adjustment by the end of the next payroll cycle (Oct 15). I will prepare a brief impact summary by Oct 3, and we can review it together on Oct 5.” This creates a two‑week window, aligns with payroll processing, and forces the manager to schedule a follow‑up.

How can I turn the raise request into a reusable template for my team?

The template becomes a product, not a personal cheat sheet. In a recent internal PM forum, the engineering lead shared a “Compensation Request Canvas” that the org adopted as a standard. The judgment: document the script in a one‑page PDF, embed the three‑act structure, and circulate it via the team’s Confluence space.

Template sections

Header – Role, level, current compensation.
Impact Dashboard – Three KPIs with numbers, linked to OKRs.
Market Comparison – Benchmark sources, internal band, desired figures.
Risk Mitigation Clause – Review period, mentorship pledge.
Timeline & Sign‑off – Dates, responsible parties, attached impact one‑pager.

When the template is shared, junior PMs can plug in their own data, preserving the judgment framework while scaling the practice.

Preparation Checklist

- Draft a one‑page impact summary with three hard‑numbers metrics (e.g., $4.3 M revenue, 0.9 % churn, 1.2 M users).
- Pull the latest market data from Levels.fyi for “Senior PM, Cloud” (average $185 K base, 0.07 % equity, $22 K sign‑on).
- Map your current compensation to the internal band (e.g., $155 K base vs. $165 K–$190 K range).
- Write the three‑sentence script (pre‑ask, ask, next‑steps) and rehearse it aloud.
- Set a 14‑day deadline aligned with the next payroll cycle (e.g., Oct 15).
- Prepare a risk‑mitigation clause (30‑day impact review, mentorship pledge).
- Save the completed document in the team’s Confluence “Compensation Requests” folder.
- Work through a structured preparation system (the PM Interview Playbook covers “Compensation Framing” with real debrief examples, so you can see exactly how senior PMs turned impact data into salary adjustments).

Mistakes to Avoid

BAD: “I’ve been here three years, and I think I deserve a raise.”

GOOD: Open with quantified impact, then tie to market data, then propose a date.

BAD: “Can we talk about my salary sometime next quarter?” – vague timing invites postponement.

GOOD: “I’d like to finalize the adjustment by Oct 15, with a brief impact summary delivered by Oct 3.”

BAD: “I want $200 K because I’m the best PM on the team.” – personal bragging triggers defensiveness.

GOOD: “My initiatives generated $4.3 M incremental revenue, placing me at the 85th percentile of senior PMs; the market median for that impact is $185 K base, so I’m requesting $177 K.”

> 📖 Related: OpenAI SDE career path levels and salary 2026

FAQ

What if my manager says the budget is locked for the quarter?

The judgment: push the timeline forward, not the amount. Offer a “mid‑quarter review” where you can re‑evaluate impact and adjust compensation in the next payroll cycle.

How many data points do I need to prove impact?

Three strong, revenue‑or‑cost‑centered metrics are enough; more dilutes focus. Choose the numbers that align directly with the company’s FY targets.

Should I mention equity or just base salary?

Mention both if the market benchmark includes equity; it signals you understand total‑comp framing. However, keep the ask simple: “$177 K base plus 0.07 % equity,” and let HR handle the details.amazon.com/dp/B0GWWJQ2S3).

Your next 1:1 doesn't have to be awkward.

Get the 1:1 Meeting Cheatsheet → — scripts for tough conversations, promotion asks, and managing up when your manager isn't great.

TL;DR

- Draft a one‑page impact summary with three hard‑numbers metrics (e.g., $4.3 M revenue, 0.9 % churn, 1.2 M users).