The raise request works when it is a calibration conversation, not a confession. In a Q3 comp review I sat through, the PMs who got traction named the number early, tied it to scope, and made the manager choose a path; the ones who drifted into gratitude and vague pressure got a polite delay.
1on1 Raise Request Template for Tech PMs: Downloadable Script
TL;DR
The raise request works when it is a calibration conversation, not a confession. In a Q3 comp review I sat through, the PMs who got traction named the number early, tied it to scope, and made the manager choose a path; the ones who drifted into gratitude and vague pressure got a polite delay.
This template is for tech PMs whose work has outgrown their current pay band or level. Not "I feel underpaid," but "my scope and compensation no longer match." If the gap is real, ask directly, set a date, and force a decision.
Not a plea, but a business case. Not a performance recap, but a compensation comparison. Not a hoping-for-a-good-vibe conversation, but a written ask that survives calibration.
Running effective 1:1s is a system, not a talent. The Resume Starter Templates includes agenda templates and question banks for every scenario.
Who This Is For
This is for PMs who have already shipped, already absorbed more scope, and already heard some version of "let’s revisit this later." In practice, that means L4s acting like L5s, L5s carrying cross-functional ownership without the title, or anyone who has gone through one review cycle and come out still under-leveled or underpaid.
It is also for the PM who knows the manager is sympathetic but slow. That is a different problem from lack of merit. In a manager 1:1 I sat in last year, the hiring manager said, "She deserves more," then spent the next month waiting for a budget slot that never appeared. Sympathy does not move money. Timing, framing, and escalation path do.
What should I say in the 1:1?
Say the ask in the first sentence and make it hard to misunderstand. In a comp conversation, the manager is not listening for your life story. They are listening for scope, number, and urgency.
The strongest opening is blunt, calm, and specific. Not "I wanted to chat about how things are going," but "I want to discuss my compensation because my scope has expanded materially, and I believe my current pay no longer matches the work."
Use this as the downloadable script.
`text
Can we use this 1:1 to talk about my compensation?
Since my last review, I have taken on [scope 1], [scope 2], and [scope 3].
I now own work that sits above my current level, especially in [area].
I want to request a compensation review for a base adjustment to [$X], or a dated plan to get there by [date].
If that number is not in range, I want to understand the exact gap and what evidence would close it.
I am not asking for a vague promise.
I am asking for a decision or a clear path to one.
`
In a Q4 calibration meeting, I heard a PM spend six minutes proving loyalty before ever naming the number. The manager cut in with one sentence: "What are you actually asking for?" That was the real test. The problem was not the answer. The problem was the lack of judgment signal.
Use "I want" language, not "I was hoping" language. Not softening, but clarity. Not reassurance-seeking, but decision-making. Managers trust directness because it reduces ambiguity and protects them in the room where compensation gets discussed.
If your company is bureaucratic, make the ask even tighter. "I want a base adjustment to $X, or if that is not possible this cycle, I want the criteria and date for reconsideration." That line does two things. It prevents the conversation from becoming emotional theater, and it forces the manager to reveal whether there is real budget or just social buffering.
> 📖 Related: Volkswagen product manager career path and levels 2026
When is the right time to ask for a raise?
The right time is before budget locks and after you have clean evidence of scope expansion. Ask too early and you sound premature. Ask too late and the decision is already frozen.
In most tech orgs, the useful window is 4 to 6 weeks before annual review or comp planning closes. If your company does mid-year calibration, move earlier. If your manager needs finance approval, give them enough runway to socialize the request before the packet deadline. The meeting is not the beginning of the decision. It is often the last chance to shape it.
I watched one PM bring up pay two days before a comp freeze. The manager was not hostile. They were trapped. They could not get the request through, and everyone pretended the delay was procedural. It was not procedural. It was timing failure dressed up as process.
Not when you feel frustrated, but when your manager can still act. Not after the review cycle, but before the numbers harden. Not when you are emotionally ready, but when the org is still mechanically able to move.
There is also a timing signal inside your own scope. If you have taken on a new product area, a major launch, or a rescue assignment in the last 60 to 90 days, do not wait for someone to "notice." That is how PMs get underpaid for extra responsibility. Companies are slow to reprice work once it becomes normal.
The clean judgment is this: ask when your evidence is fresh, your manager still has leverage, and the budget calendar is open. Anything else is a hope, not a strategy.
How much should I ask for?
The ask should be a round number, not a feeling. If the gap is modest, name a base adjustment. If the gap is structural, ask for leveling. If the company is stingy on base but flexible on equity or bonus, say that explicitly.
For many tech PM situations, the request belongs in a concrete range like a $10,000 to $25,000 base adjustment, or a level review if the scope gap is larger. If you are asking for something outside that band, you are probably not making a raise request. You are making a role reclassification request. Treat it that way.
A manager once told me in a compensation review, "I can defend a number. I cannot defend a vibe." That is the right standard. The number has to be easy to repeat in the room where your manager is not present. If they cannot explain it in one sentence, it will die in calibration.
Not "pay me more because I worked hard," but "my current band is misaligned with my current scope." Not "whatever you think is fair," but "I am asking for $X because I am already operating at Y scope." Not "can you do anything," but "what is the realistic path to this number, and by when?"
The real judgment is whether your ask matches the kind of problem it is. If you own one extra project, a raise is the right lever. If you own an entire new surface area, a title or level change may be the right lever. If you have become indispensable but still lack measurable scope, then you do not yet have a pay problem. You have a documentation problem.
The number should feel defensible to a manager who has to say it out loud in a meeting. That is the standard. Not sentimental. Not aspirational. Defensible.
> 📖 Related: Skip-Level Meetings: An Alternative When Your Direct 1:1s Stall
What evidence actually moves a tech PM manager?
Managers move on scope, leverage, and calibration risk, not on effort. In the room where comp decisions get made, "worked hard" is background noise. "Now owns the highest-friction area" gets attention.
The strongest evidence is a pattern, not a single win. A launch that required cross-functional alignment. A messy area that is now stable because you took ownership. A team or stakeholder group that trusts you because you reduced escalation. A project that had visible business risk and you brought it back into control.
In one HC-adjacent debrief I sat through, the hiring manager kept returning to a PM who had not just shipped features, but had changed the operating rhythm of the team. That mattered more than the feature list. The manager was not impressed by activity. They were responding to organizational leverage.
Not "I did a lot," but "the company now relies on me differently." Not "I learned fast," but "I changed the shape of the work." Not "I am ready," but "I am already operating above this band."
You also need evidence that survives manager turnover. If your raise case depends entirely on personal goodwill, it is fragile. If it rests on scope, process ownership, and visible dependency from other teams, it becomes harder to dismiss. That is the hidden psychology: calibration rewards work that is legible to other leaders, not just to your direct manager.
Use three proof points. One on scope. One on business impact. One on comparative level. The third point is the one people skip. It is the most important. If the work looks like the next level in every adjacent PM org, say so. Managers know when someone is already doing the job.
How do I handle pushback without losing leverage?
Pushback is usually delay dressed as process. Treat it that way. The manager's first objection is often not the final answer. It is a test of whether you will accept ambiguity and leave the room.
If they say, "Budgets are tight," do not argue about the economy. Ask, "What is the decision path and when will it be revisited?" If they say, "I need more evidence," ask, "What evidence specifically, and by what date?" If they say, "Others are also waiting," ask, "What distinguishes my case from the others?"
In a manager conversation I watched, the PM kept saying, "I understand if now is hard." The manager heard permission to postpone. The better response was more disciplined: "If now is hard, I want the exact criteria and date for reconsideration." That line changes the shape of the conversation. It converts a soft no into a tracked commitment.
Not accepting a vague "later," but forcing a date. Not seeking comfort, but seeking criteria. Not waiting to be chosen, but requiring the manager to state the gap in plain language.
There is also a tactical rule here. If the manager cannot give you a date, they do not have a plan. If they cannot give you criteria, they do not have a standard. In both cases, the answer is not ready, no matter how politely it is packaged.
The cleanest close to a pushback conversation is this: "I am fine with a later decision if we write down what has to be true and when we revisit." That line is cold, and it should be. Comp conversations are not therapy. They are commitments.
Preparation Checklist
Prepare the request like a decision memo, not a personal diary.
- Write one sentence that names the ask, the amount, and the date. If you cannot say it in one sentence, the manager will not repeat it in calibration.
- Pull three proof points: scope added, outcomes delivered, and level mismatch. Do not bring ten anecdotes. Ten anecdotes signal no judgment.
- Decide the lever before the meeting: base, bonus, equity, or level. A vague "compensation" request is weaker than a specific lever.
- Rehearse the likely objections and your responses. The manager will usually choose between "not now," "need more evidence," or "budget issue."
- Work through a structured preparation system (the PM Interview Playbook covers compensation framing and manager debrief examples in the same blunt language real calibration meetings use).
- Time the conversation 4 to 6 weeks before review or budget lock, not after it.
- Leave with a written next step, an owner, and a date. If you leave with encouragement only, you left with nothing.
Mistakes to Avoid
The worst mistakes are soft asks, vague timing, and no fallback.
- Bad: "I wanted to see if there’s any possibility of a raise." Good: "I want a compensation review for a base adjustment to $X by [date]."
- Bad: "I think I’ve been doing a lot." Good: "My scope now includes [area], [area], and [area], which is above my current level."
- Bad: "I understand if not now." Good: "If not now, what exact criteria and date reopen this discussion?"
The first bad pattern turns the request into a social favor. The good version turns it into a managerial decision. Those are not the same thing.
The second bad pattern confuses effort with leverage. PMs do this constantly. It is a category error. The company pays for ownership and decision quality, not for visible struggle.
The third bad pattern accepts indefinite delay. That is how managers preserve peace without making a commitment. The right response is not pressure. It is specificity.
Another common failure is asking for a raise before you have a narrative the manager can repeat. If the manager cannot explain your case in one sentence to compensation, your case is not ready. That is the standard that matters.
FAQ
- How direct should I be in a raise request?
Direct. The right opening names the ask and the number. If you hide the point behind small talk, you are signaling uncertainty, and managers often read that as a weak case.
- Should I ask for a specific dollar amount?
Yes. A precise number is easier to evaluate than a vague request. If the gap is structural, ask for a level review instead of pretending a small raise will fix it.
- What if my manager says there is no budget?
Treat that as a process answer, not a final answer. Ask for the criteria and the date for reconsideration. If they cannot give either, the answer is effectively no.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.