NegotiationConversation Note

How to ask for a raise without sounding entitled (or apologetic)

What to say when you ask for a raise, how to handle 'the budget is tight', and the sentence that keeps the conversation open when the answer is no. Scripts included.

TalkCraft Editorial5 min readPublished 11 Sept 2026Updated 8 Oct 2026

Part of: Negotiation

In this guide

Imagine this fictional example: you've booked the 1:1, documented a larger role and found salary estimates about 15% above your current base pay. Your manager says, "So, you wanted to talk about compensation. Go ahead." The percentage is an illustration, not a benchmark for your own role.

And this is where a lot of people say something like: "I know this might be a bad time, but I wanted to ask about maybe possibly getting a raise, if the budget allows?"

That opening makes it difficult to tell what you are requesting. You can be courteous and still state a number and a reason.

The two ways this usually goes wrong

Apologetic. Hedges, qualifiers, "if it's possible", "I know it's a lot". The ask shrinks until there's nothing left to say yes to.

Unsupported. "I should be earning more" needs context. Tenure may matter under your employer's pay structure, as may internal equity, expanded responsibilities and performance. Explain the relevant basis rather than expecting the assertion to carry the case.

Treat it as a compensation discussion: present evidence, make a request and ask how the decision is made.

Why this works

Your manager may recommend a raise without having authority to approve one. Ask who decides, what evidence is needed and when the budget is set. Harvard's Program on Negotiation highlights the importance of understanding negotiating authority and options; do not assume a supportive manager can make the final call.

Check the evidence before the meeting

Bring a short summary, not a pile of unrelated salary figures:

  • Comparable role and level: match responsibilities, not only titles.
  • Location and work arrangement: use the relevant labor market and your employer's pay policy.
  • Date and source: record when each estimate was collected and whether it is a posted range, survey or self-report.
  • Compensation components: separate base salary, bonus, equity and benefits.
  • Expanded scope and results: show what changed, when, and what you delivered.
  • Internal equity or pay bands: ask how your pay sits within the applicable structure. Coworker comparisons can be relevant, but check whether the roles and components are comparable.

Benchmarks are estimates. If two credible sources differ, bring the range and uncertainty instead of presenting one number as an agreed market fact.

Value, ask, question

Three moves.

1. Lead with what you delivered. Specific, recent, and in the language your manager uses for results.

Script
Over the last 18 months I've taken on the API migration, led the Q3 launch, and consistently hit my OKRs.

2. Make the ask specific. A number or a range, and what it's based on.

Script
Based on that, and on market data showing I'm around 15% under for this role, I'd like to discuss adjusting my compensation to reflect it. The number I have in mind is [X].

3. Ask a question that invites problem-solving. Then stop talking.

Script
What would need to happen for that to be possible — either now or in the next cycle?
Debrief

The number arrives with its reasons attached. The final question opens discussion of the process, but it may still produce a no. Pause so you can hear the answer rather than supplying concessions before any are requested.

When they say the budget is tight

Find out whether the constraint is this cycle's budget, the pay band, the evidence for an adjustment, or something else. Do not assume the stated reason is a negotiating tactic.

Script
I understand the budget constraints. What would need to happen for a raise to be possible — either now or in the next review cycle?
Why this works

This asks whether a path exists. If there is one, clarify the conditions, decision owner and review date. Those conditions are not a guarantee of approval unless the decision-maker actually commits to that.

If you have market data
I also have market data showing I'm about 15% below rate for this role. I'm not trying to pressure you — I want to make sure we're both looking at the same picture.
Make the comparison inspectable

Show the source, role match and compensation components. Ask whether the employer uses a different benchmark, and compare the assumptions rather than treating your estimate as a settled fact.

Scripts for the whole conversation

Opening

Script
Thanks for making time. I want to talk about my compensation. Over the last [period] I've [two or three specific things]. I'd like to discuss adjusting my pay to reflect that.

The number

Script
Based on the scope I'm carrying now and the market range for this role, I think the right number is [X]. What would it take to get there this cycle?

If they ask you to justify it

Script
Happy to. The two biggest things are [project] — which [result] — and [second thing]. I've written them up if that's useful for the case.

If they say "let me look into it"

Script
Great. When should I check back? And is there anything you need from me to make the case?
Debrief

Agreeing a date gives you a follow-up point. Confirm what will be available then: a decision, an update, or simply the next step in the approval process.

If the answer is no

A no may be final. If further discussion is possible, ask about:

  • The conditions. "What would need to be true for a yes?" and write down the answer.
  • The date. "When can we revisit this?"
  • The alternatives. A bonus, a scope change, a training budget or an earlier review, if those would actually help you. A title change is not a substitute for pay unless it meets your goals.
Script
Understood. Can we agree what would need to be true for this to be a yes at the next review — and put a date on it? In the meantime, is there anything else on the table, like [title / scope / an earlier review]?
Why this works

If there is no budget, no approval path and no review date, record that answer accurately. You can then evaluate your own options rather than treating more effort as a promise of higher pay.

What not to say

  • I know this might be a bad time. It might. Ask anyway; let them say so.
  • I think I deserve… Swap for what you delivered.
  • Other people on the team make more. If internal equity is the concern, explain the comparable role, scope and pay components and ask how the difference is determined.
  • If I don't get this I'll have to consider my options. Do not bluff about an offer or decision. State an actual constraint only if you are prepared to act on it.

Try this today

Write your opening in three lines: one line of what you delivered, one line with the number, one question. Read it out loud twice. If it contains "just", "maybe", "possibly" or "if that's okay", delete those words and read it again.