The Exact 1:1 Script for Asking for a Raise Without Sounding Demanding

TL;DR

Asking for a raise is not a request for a reward, but a price correction based on market value and delivered impact. Success depends on decoupling your emotional need for more money from the business case for your increased cost. The script must shift the conversation from what you want to what the role is now worth.

Who This Is For

This is for mid-to-senior individual contributors and product leaders in high-growth tech environments who have exceeded their OKRs but find their compensation lagging behind their actual scope. It is specifically for those who fear sounding entitled and instead want to use a data-driven, clinical approach to force a compensation adjustment during a 1:1.

How do I start the conversation about a raise without it feeling awkward?

Start by framing the conversation as a professional alignment on role scope and market value, not a personal plea. In one Q2 performance review, a Senior PM tried to lead with how much their rent had increased; the manager immediately shut down, viewing it as a personal problem rather than a business one. The mistake was treating the raise as a favor, not a transaction.

The goal is not to ask for more money, but to align your compensation with the value you are currently capturing for the company. When you lead with your personal needs, you signal that you are thinking like an employee, not a business owner. A business owner focuses on the ROI of the position.

The opening line should be: I want to spend a few minutes discussing my current compensation relative to the expanded scope of my role over the last six months. This removes the emotional weight and signals that this is a strategic discussion. It transforms the dynamic from a subordinate asking for a gift to two professionals auditing a contract.

What is the exact script for asking for a raise in a 1:1?

The script must follow a logic chain of Evidence, Market Gap, and Proposed Correction. I once sat in a compensation committee meeting where a manager fought for a 15 percent bump for a lead because the candidate presented a one-page document mapping their original job description to their current daily reality. The gap was undeniable.

Use this exact phrasing: Over the last two quarters, my role has evolved from managing a single feature set to owning the entire growth funnel, which has resulted in a 12 percent increase in MAU. Based on current market data for this expanded scope in the Bay Area, the mid-point for this level of impact is between 210k and 230k base. Currently, I am at 185k. I would like to bring my salary in line with this market value to reflect the current scope of my contributions.

The power of this script lies in the lack of adjectives. Avoid words like feel, hope, or believe. The problem isn't your lack of confidence; it's your use of subjective language. By using numbers and market ranges, you make it difficult for a manager to say no without admitting they are paying you below market for the value you provide.

How do I handle it when my manager says there is no budget?

Treat a no-budget response as a request for a roadmap, not a final verdict. In a recent budget cycle, a Director told a high-performer that the headcount budget was frozen, only to find 10 percent for a new hire two weeks later. The budget is not a fixed wall; it is a priority list.

Your response should be: I understand the current budget constraints. Since we agree that my performance warrants this adjustment, what specific milestones do I need to hit, and what date can we commit to, to make this correction happen? This forces the manager to move from a vague no to a concrete plan.

The objective here is not to argue about the budget, but to secure a written commitment. If the manager cannot provide a date or a milestone, the judgment is clear: the company does not value the role enough to pay for it. At that point, you stop optimizing for the current company and start optimizing for the external market.

What evidence should I bring to a salary negotiation meeting?

Bring a Value Realization Document that contrasts your hired job description with your actual output. I have seen countless debriefs where managers wanted to give a raise but couldn't justify it to HR because the employee just said they were working hard. Hard work is a baseline expectation, not a reason for a raise.

The document should include three columns: Original Expectation, Current Reality, and Business Impact. For example, instead of saying you managed a team, write: Managed 4 engineers to deliver the checkout redesign, reducing churn by 4 percent, resulting in 1.2M in retained ARR. This is the language that HR and Finance understand.

The mistake most people make is providing a list of tasks. The problem isn't your list of achievements; it's your failure to translate those achievements into currency. Finance does not care that you worked 60 hours a week; they care that you moved a metric that affects the P&L.

Preparation Checklist

Audit your original offer letter and job description to identify where your current responsibilities have drifted upward.
Gather three distinct data points from verified sources like Levels.fyi or peer networks for your specific level and city.
Create a Value Realization Document that maps your output to specific revenue or cost-saving numbers.
Schedule a dedicated 1:1 for this topic; never tack a raise request onto the end of a project update.
Work through a structured preparation system (the PM Interview Playbook covers the compensation negotiation section with real debrief examples) to refine your value propositions.
Draft your script using only objective, non-emotional language.
Set a hard internal deadline for when you will stop waiting for a correction and start interviewing elsewhere.

Mistakes to Avoid

Mistake 1: Using tenure as a justification.

Bad: I have been here for two years now, and I think it is time for a raise.

Good: In the last 24 months, I have scaled my output from X to Y, effectively performing the duties of a Level 6 while being paid as a Level 5.

Judgment: Tenure is a measure of time, not value. Companies pay for impact, not attendance.

Mistake 2: Comparing yourself to a colleague.

Bad: I know that Sarah is making more than me, and we do the same job.

Good: Based on the market data for this role's current scope, the compensation range is X to Y.

Judgment: Bringing up a peer makes you look petty and creates a conflict for the manager. The conversation is not about Sarah; it is about the market.

Mistake 3: Asking for a percentage without a number.

Bad: I am looking for a 10 percent increase.

Good: I am looking to move my base to 215k to align with the market mid-point for this scope.

Judgment: Percentages feel like a tip; specific numbers feel like a price. Always negotiate the absolute value.

FAQ

How long should I wait between performance reviews to ask?

Do not wait for the annual cycle. If your scope changes significantly, the price should change within 90 days. Waiting for the annual review is not being patient; it is leaving money on the table while the company gets a discount on your labor.

Should I mention that I have other offers?

Only as a last resort. Mentioning other offers is not leverage; it is a threat. Use it only if you are prepared to walk out the door that day. Until then, focus on the internal value gap.

What if my manager agrees but HR denies it?

This means your manager is not a strong advocate for you. The judgment is that you have a ceiling at this company. If your manager cannot navigate the internal bureaucracy to pay you market value, they cannot help you grow your career.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.