Editorial photo for how to ask for a raise

How to Ask for a Raise Without Burning Bridges

Asking for a raise feels high-stakes. Here's how to time it, frame it, and handle every outcome, without damaging the relationship.

Most advice about asking for a raise gets the emotional part wrong. It treats the conversation like a negotiation tactic, like you’re buying a used car, and it pretends the only thing that matters is how well you deliver your pitch. That’s not how raises actually work inside companies. A raise is a relationship event first, and a math event second. If you skip the relationship part, even a perfect pitch lands badly.

I’ve sat on both sides of this table for fifteen years. I’ve watched people get double-digit bumps they didn’t really earn because they handled the conversation like grownups, and I’ve watched top performers get flat-out “no” because they made their manager feel cornered. The difference isn’t the number. It’s the choreography.

This guide walks you through the full sequence. When to time it, how to build the case, what to say in the room, and how to handle every possible answer without setting your career on fire. It isn’t a script. It’s a playbook you can adapt to your manager, your company, and your actual contribution.

Why the Raise Conversation Is Really About Your Manager’s Budget, Not Your Worth

Here’s the reframe that changes everything. Your raise doesn’t come out of your manager’s pocket, but it does come out of their budget envelope, which is a fixed number your manager is given once a year and has to allocate across every person on the team. When you ask for a raise, you aren’t asking for validation. You’re asking your manager to allocate more of a scarce resource to you, which means less of it goes to everyone else on the team.

Once you see it that way, a lot of the advice out there starts to sound goofy. “Tell them how hard you work” doesn’t move a budget. “List everything you’ve done” doesn’t move a budget. What moves a budget is showing your manager that the cost of NOT giving you the raise, meaning the risk of you leaving, or the hit to team output if you disengaged, is higher than the cost of moving the money.

That’s the case you’re really making. And that case has three ingredients. Evidence of increased impact, evidence of increased market value, and a clean, low-friction way for your manager to say yes.

Timing Is 80 Percent of the Outcome

Most raises get lost before the first word gets spoken, because the timing was wrong.

The worst time to ask is during a crisis. Layoffs announced. Budget cut mid-year. A key customer churning. A major bug in production that your team is still digging out of. In those windows, even a reasonable ask sounds tone-deaf, and your manager will remember it for the wrong reasons. Wait.

The second-worst time is right after a mistake. Even if the mistake was small and already moving past, your manager’s mental file on you is still processing it. Give it at least 60 days of clean runway before the conversation.

The best times are predictable. Two to three weeks before annual compensation reviews get locked, when your manager still has room to lobby for you but hasn’t finalized their list yet. Right after you’ve delivered something visible and measurable, where the win is fresh in everyone’s memory. And immediately after a meaningful change in scope, like taking on a direct report, owning a new product area, or inheriting work from someone who left.

If you don’t know when your company’s comp cycle locks, ask. Most managers will tell you. That single data point reframes your ask from “random inbound request” to “thoughtful preparation for the cycle,” and your manager will file it that way.

Building the Evidence Pack

Before the conversation, you need a one-page evidence pack. Not ten pages. One page. It’s for you to reference and for your manager to forward upward if they need to advocate for you. If it’s longer than a page, nobody reads it, and your manager has to rewrite it anyway.

Your evidence pack covers three categories.

Impact. Three to five specific accomplishments from the last 12 months. Each one framed as the outcome, not the task. Not “led the checkout redesign.” Rather, “led the checkout redesign that lifted conversion 8 percent and added $1.2M in annualized revenue.” If you can’t tie a number to it, use a proxy. Reduced engineering time. Fewer customer escalations. A specific stakeholder who can vouch. Numbers are the currency your manager’s manager speaks.

Scope growth. A short list of what’s on your plate now that wasn’t 12 months ago. Direct reports added. Systems you own. Domains you’ve expanded into. Meetings where you’re now the senior voice. This shows your job has grown, which is the cleanest argument that your pay should too.

Market evidence. Two to three data points on what your role pays in your market. Use levels.fyi for tech, H1B salary data for broad-market compare, BLS OES tables for non-tech roles. Don’t bring a competing offer unless you actually have one and are prepared to take it. Competing offers are nuclear weapons, not bargaining chips.

If you want a deeper look at how to quantify resume-level accomplishments, read our guide on writing resume bullet points that actually perform. The same framing works for raise prep.

The Actual Conversation, Word for Word

Book a 30-minute one-on-one with your manager. Don’t ambush them in a hallway. Don’t bring it up in a skip-level. Don’t send the ask as a Slack message. A real conversation, scheduled in advance, with enough time that neither of you is watching the clock.

Open with context, not the number. Something like this. “I wanted to talk about my comp. I’ve been thinking about where I am and where I’m heading over the next year, and I’d like to share how I’m seeing things. I want to understand how you’re seeing it, and I want to figure out together what makes sense.”

That opening does three things. It signals this is a real conversation, not a demand. It invites your manager to be part of the thinking, not a target of it. And it buys you the right to share your evidence without sounding like you’re reading talking points.

Then walk them through the evidence pack. Short. Focused. Maybe four minutes of talking. End with the ask framed as a question, not a demand. “Based on all that, I think the right number is X. I’d love to hear how you’re thinking about it.”

Now stop talking. This is the part where most people blow it. They feel the silence and fill it with hedges. “Obviously I know budgets are tight.” “I don’t want to make this hard.” “If that’s too much I understand.” Every hedge shaves percentage points off your final number. Let the silence do its work.

Your manager will respond one of three ways. They’ll say yes, in which case you say thank you and confirm the next steps. They’ll say no, in which case you go to the next section. Or they’ll say “let me look into it,” in which case you pin down a date. “When can we circle back? Next Friday?” Get a commitment, not an open-ended promise, and put it on both calendars.

When the Answer Is No, or “Not Yet”

This is where careers actually get made or broken. Most people treat a no like a rejection of them as a person, and they either blow up in the meeting or quietly check out for the next six months. Both are wrong moves.

A no is data. It tells you something about this company, this manager, or this moment. Your job is to extract the data, not react to the feeling.

Ask this exact question. “Help me understand. What would need to be true 6 months from now for the answer to be yes?” If your manager can name specific, measurable things, now you have a roadmap. Write them down. Repeat them back. Ask for another check-in in 90 days to review progress.

If your manager can’t name anything specific, that’s also data, and it’s bad data. It usually means one of three things. The company is out of money and can’t say so. You aren’t as strong a performer as you thought, and your manager doesn’t want to say that either. Or your manager just doesn’t go to bat for people, which is its own problem.

In any of those cases, don’t quit in the meeting. Thank them. Give yourself a week to process. Then start quietly looking. Not because one bad raise conversation is worth leaving over, but because a vague no is a signal about your ceiling, and ceilings don’t tend to rise after bad raise meetings.

For how to actually run a job search from a position of strength, see our guides on working with recruiters and how to evaluate a job offer.

What Not to Do, Ever

A few hard rules. I’ve watched each of these torch a career, and I’ve been on the receiving end as the recruiter who had to clean up the mess.

Don’t threaten to quit unless you’re ready to quit that afternoon. Managers remember threats, and they will quietly deprioritize you for interesting work from that moment on, even if they agree to the raise.

Don’t compare yourself to a specific colleague by name. “Jamie makes more than me” is a conversation-ender, and it puts your manager in the position of having to defend someone else’s comp while evaluating yours. Use market data instead.

Don’t bring a counter-offer you don’t intend to take. If you show your manager an offer letter, you’ve triggered a retention process that ends with you leaving or staying under awkward conditions. Only bring it out if you’re ready to walk.

Don’t ask by email. Email lets your manager draft a polite no without ever having to look you in the eye. You want a real conversation where your case lands with the weight of a real person asking.

Don’t accept a vague “we’ll try” and leave without a date. “We’ll see what we can do” is a soft no in management dialect. Pin it down or treat it as a no and act accordingly.

The 90 Days After

Whatever the answer, the 90 days after the conversation matter more than the conversation itself.

If you got the raise, don’t coast. The worst thing you can do is show up the next month looking like the raise was the goal. It wasn’t. The goal was the trajectory. Keep delivering like the raise didn’t happen.

If you got a no with a clear roadmap, hit the roadmap. Document your progress weekly. Send your manager a short monthly update that maps directly to the specific things they said they needed. Make their job of advocating for you easy.

If you got a vague no, start looking quietly. Update your resume, sharpen your LinkedIn profile, reach out to three recruiters, and give yourself a 90-day window to see what’s actually out there. You’re not quitting. You’re gathering information. The best time to look is when you don’t have to.

Asking for a raise is one of a small handful of career conversations that really moves the needle on lifetime earnings. People who do it thoughtfully, on the right timing, with the right framing, end up 20 to 30 percent ahead of equally-talented people who just wait to be noticed. The pitch doesn’t have to be perfect. It just has to happen.

Frequently asked questions

What's a reasonable raise to ask for?

In a steady market, 5 to 10 percent on top of your current base. If you've taken on a significantly larger role, 15 to 25 percent can be defensible. Anything beyond that needs a title change too.

How long should I wait between raise conversations?

At least 12 months between asks, unless something material has changed, like a promotion, a scope expansion, or a competing offer. Asking every six months without a new reason looks pushy and flattens the word 'raise' down to noise.

What if my manager says no?

Ask what specifically would get you to yes in 6 months. If they can't name a clear bar, that's real data about your ceiling at this company. Don't quit in the meeting. Quit in the 90 days that follow if the answer was vague.