How to Negotiate a Raise After Your Number Is on the Table

The hard part is not naming the number. It is the ten seconds after.

You said $110,000. Your manager did not say yes and did not say no. They said something in between, and now you are improvising about your own salary with no plan and a raised heart rate.

The sentence that loses it here is "I mean, there is some flexibility on that." Nobody asked. In seven words you told your manager that the number you spent three weeks building a case for was a suggestion, and that they can find the real one by waiting.

All of this assumes the ask is made. If you are not there yet, the ask itself is a different job. What follows is the part after: five answers your manager can give, and the words for each.

Pick one number and let it sit there

A range is not heard as a range. It is heard as your floor with decoration on top. Say "somewhere between $105,000 and $115,000" and you will be offered $105,000, and nobody will mention the top of your range again, including you.

One number becomes the thing the conversation is organized around. Every counter is measured against it, and the person who has to justify something different is your manager, not you.

How to pick it:

• Start from the job you do now, not the one in your offer letter. Market data for your old title is the wrong input once your scope has outgrown it.
• Take the top of what your evidence supports. Evidence means delivery in the company's units plus scope you absorbed that nobody paid for.
• Make it look like arithmetic. $112,000 reads as a calculation. $120,000 reads as a wish, and wishes get rounded down.
• Sanity check it internally. What the band for your level tops out at, and what the person one level up actually makes.

On how much: for an internal raise, the number that gets treated seriously is usually ten to twenty percent above what you make now. Below that you are asking for a rounding error and you will get one. Much above it and you are not asking for a raise, you are asking for a promotion, which is a different conversation with a different case.

The five answers, and the words for each

There are only five. Once you can name which one you just got, you stop improvising.

A flat no

A bare no is rare, and it is usually not about you. A budget closed. Headcount froze. Your manager has less authority than they implied. Arguing is the worst available move, because you end up defending your worth to someone who already agrees and cannot act.

Find out which no it is instead. A no for this cycle is a scheduling problem. A no for this role is a career decision, and you would rather learn that today than in eighteen months.

A lower counter

The most common real answer, and the best one. They say $98,000 against your $110,000. That is not a rejection, it is the first true information you have had all meeting.

Do not accept it in the room. Do not reject it either. And do not split the difference on reflex: meeting in the middle is a habit, not a strategy, and it rewards whoever anchored harder.

"Not this cycle"

A deferral is a no with a maybe stapled to it, and it decays fast. It becomes real only with two things attached: a date, and a condition you can actually satisfy. Without those you have agreed to repeat this conversation in six months from the same starting position.

"Let me take it to HR"

Sometimes true. Often it is how a decision moves to a room you cannot enter. Either way, your case is about to be retold from memory by someone who was not persuaded by it. So write it down. The version that survives is the one your manager can paste into an email.

A yes with strings

"Yes, and I want you to pick up the Meridian account." Read that again. The number was agreed and then a second negotiation opened while you were still relieved.

Take the yes. Do not take the string in the same breath. That is how people end up paying for their own raise, and making the trade visible is its own conversation.

Every one of those is short and ends in a question. That is not style. A short sentence has no room for the concession you did not mean to make, and a question puts the next move back across the table.

The currency that is not salary

Base salary is the hardest yes in the building. It recurs forever, it compounds, and it sits in a band chart someone other than your manager has to defend. Almost everything else you want is cheaper to approve, which is exactly why you never open with it.

Things that are often easier to say yes to:

• A title, especially one that matches work you already do.
• Scope: an owned surface, a workstream, a team of two instead of a team of none.
• A budget line: a contractor, a tool, a training allowance.
• A headcount requisition, which is scope with a number attached.
• A reporting change: a skip level, or a move into an org with more room.
• An equity refresh or off-cycle grant, often a different pool than salary.
• A one-time bonus, money that does not touch the band.
• A review date with a specific number attached.

Name your salary number first anyway. Always. These are trades, and a trade needs something on both sides. Open with the title and you have spent your only leverage on the thing that costs nothing.

When you actually have another offer

A real offer is real leverage, and the way to spend it is plainly and once. No hints, no "I have been approached recently," no letting it hang in the air to be inferred. Say the number, say you would rather stay, say when you need an answer.

Weigh two things first. A counteroffer changes how you are read, so assume the next staffing conversation includes the words "they nearly left last year." And once you accept it, the leverage is spent.

Get it in writing, and what to do when the date passes

Send the summary the same day, while the meeting is still accurate in both your heads. Three lines, no argument in it. The point is not pressure. Managers change and budgets get reallocated, and the version of this conversation that survives is the written one.

Get four things down: the number agreed, the effective date, anything conditional and what the condition is, and the date you revisit it.

Say that first in the meeting, not last, and do not apologize for raising it. If a second agreed date passes with nothing, stop reading it as a budget problem. Two missed dates is an answer, and the next useful step is usually outside the building.

This does not work if the budget is already allocated for the year. In most companies the pool is set months before the review, so a good conversation in November moves a number that was fixed in September. Ask when the pool is decided, and have this conversation two months before that date.

The silence you have to sit in

Look back at the five responses. Every one of them ends, and then nothing happens. That gap is where this conversation is actually decided.

Most people concede in it before their manager has said a single word. The number lands, three seconds of nothing follow, the quiet becomes unbearable, and they fill it. "But I know budgets are tight." "Obviously that is negotiable." Nobody pushed back. You negotiated against yourself in an empty room, and then you heard the counter you had just made.

You already know not to do that. Knowing is not the skill. The skill is holding a flat, calm sentence in your mouth while someone senior to you looks at the table and says nothing, and then not adding to it. That does not come from reading the words. It comes from having said them out loud, more than once, to someone who pushes back and then pushes back again, until the sentence comes out level instead of tilting up at the end like a question.