The situation
You booked the one-on-one two weeks ago and put "career conversation" in the invite title, which means your manager already knows roughly what is coming. That is the easy part. The hard part starts the moment the meeting opens and you have to turn eighteen months of good work into a sentence that ends in a specific dollar number.
This conversation is different from a job-offer negotiation. There is no competing offer to point to, no recruiter reading from a band. It is just you, a manager you generally like, and a number you have to say out loud in a room you will be sitting in again next week regardless of the answer. That last part is exactly why so many people undercook the ask: it is a negotiation with someone you cannot walk away from, so it starts to feel like a favor instead of a request.
Why employees lose here
Leading with a case instead of a number. Most people open with the achievements: the project that shipped, the process that got fixed, the extra scope absorbed after a teammate left. All of that matters, but a manager listening to a list of accomplishments is waiting for the ask, and if it never arrives clearly, they can nod along and leave the meeting having agreed with everything and committed to nothing.
Treating "let me see what the budget allows" as an answer. It is a placeholder, said by a manager who would rather not name a number they might have to defend upward. Employees hear it as a soft yes and stop pushing, which converts a real ask into a hope.
Apologizing for asking. "I know this might not be the best time, but..." tells the manager the employee already expects to lose, and managers tend to give people exactly the confidence they walk in with.
No number of their own. Coming in with "I think I deserve more" instead of "I'm asking for $105,000" hands the manager the job of guessing your number, and guesses default low.
What the counterpart is actually thinking
A manager fielding a raise request is almost always doing two things at once: judging whether the ask is fair, and calculating whether they can get it approved. The second part matters more than most employees assume. A manager who agrees the ask is fair but has no number, no timeline, and no comparison to point to has nothing to bring to their own manager or to HR. A specific number backed by a specific reason is not aggressive, it is useful: it gives the manager a case to carry upstairs instead of a vague impression to relay.
Managers also expect some negotiation. A request that gets granted in full, on the spot, with zero pushback, occasionally means the number was set too low from the start. A firm, well-reasoned ask rarely damages the relationship. A vague, apologetic one just costs money without buying any of the goodwill the employee was trying to protect.
The dialogue
Priya is a fictional senior analyst at Northfield Analytics, currently earning $92,000 base. Market data for her role and tenure in her city runs closer to $107,000, and she has taken on a direct report since her last review. Marcus is her manager.
Weak handling:
Marcus: So, you wanted to talk about your career here. What's on your mind?
Priya: Yeah, I just feel like I've grown a lot this year. I took on the intern, I led the Q2 migration, and I think I've really stepped up. I was hoping we could maybe look at my comp at some point?
Marcus: Absolutely, you've had a strong year. Let me see what the budget allows and get back to you.
Priya: That would be great, thank you so much. No rush at all.
Marcus: Great, I'll follow up soon.
Priya never named a number, so "look at my comp" and "step up" are impressions, not requests. "Maybe" and "at some point" removed the urgency, and "no rush at all" told Marcus he can take as long as he wants. He leaves the meeting genuinely intending to help, with nothing specific to act on and no deadline forcing the issue.
Strong handling:
Marcus: So, you wanted to talk about your career here. What's on your mind?
Priya: I want to be direct: I'm asking for my base to move from $92,000 to $105,000. Since my last review I've taken on Amir as a direct report and led the Q2 migration end to end, and market data for senior analysts here runs around $107,000, so I think $105,000 is fair.
Marcus: That's a significant jump. I'm not sure I can approve that on the spot.
Priya: I understand it likely needs a conversation with your manager or HR. Could you get back to me by the end of next week with what's possible? I'd rather have a real number by then than an open-ended "soon."
Marcus: I can do that. Let me put the case together and talk to Sandra.
Priya: That works. And to be clear, if you land at $105,000, this conversation is done and I'm glad to keep building here.
Priya's number arrived in her first sentence, attached to two concrete reasons, so Marcus is negotiating around a specific figure instead of a general sense that she deserves "more." Naming the direct report and the migration by name, rather than saying "stepped up," gives him language he can reuse in his own case upstairs. The deadline is hers, not his, and it turns "let me see" into a dated commitment. The final line removes any ambiguity about what closes the conversation, which matters more here than in almost any other version of this ask.
How to run this live
Set up a salary negotiation scenario, load in your actual current number, your target, and one or two concrete reasons you can name specifically, and treat the counterpart as a manager with real but limited authority to approve on the spot. Goals for the run:
- Say your target number in your first or second sentence, not your tenth.
- Attach the ask to two specific, nameable reasons rather than a general sense of having grown.
- When the counterpart deflects to budget or timing, ask for a specific date to hear back rather than accepting an open-ended "soon."
- Close with a clear statement of what resolves the conversation on your end.
Run it against a counterpart that does not approve everything immediately. The version of this conversation where the manager says yes instantly teaches you nothing about holding your number when they do not.
