How to Give a Persuasive 5-Minute Presentation
The same underlying skill — making a clear, evidenced case out loud under pressure — in its more general form.
Read the guide →
Salary conversations feel high-pressure because they're usually improvised: most people walk in with a hopeful figure and no evidence, and walk out with whatever was offered. This guide replaces improvisation with preparation. Over seven short sessions you'll research a defensible range rather than a wish, build three quantified pieces of evidence, prepare an answer to the expectations question that doesn't undersell you, rehearse the only three replies you can actually receive, and learn how to close the conversation in writing. It covers career negotiation, not financial advice — what you can afford to accept is a personal financial question, and anything involving tax or debt deserves proper professional advice.
What you'll be able to do: In one week, walk into a salary conversation with a number, the evidence behind it, and a prepared answer for every reply you might get.
Outcome: "I have a target number and a walk-away number, both based on data rather than hope."
Write down the number you'd be pleased with, before doing any research at all. Keep it. At the end of this chapter you'll compare it with what the market data says, and the gap between them is itself the lesson.
You need three numbers, not one: a target (what you'll ask for, anchored near the top of the market range), a floor (what you'd accept without resentment), and a walk-away (below which you decline, or stay put). Three sources actually help: published salary surveys for your country and sector, job ads for comparable roles that state a range, and people doing the job — asked as a range question ("does a role like this usually land between X and Y?"), which people answer far more readily than a direct question about their own pay.
Three ads for comparable roles state 42–52k, 45–55k, and "up to 58k". A published sector survey puts the median at 47k. Two conversations with people in similar roles suggest 45–55k is normal at this company size. So: market range 45–55k; target 55k, defensible because this role includes team-lead responsibility; floor 48k; walk-away 45k. The number written down before any research was 50k. An hour of research moved the ask up by five thousand and replaced a feeling with three defensible figures — which is also what makes it possible to say the number out loud without flinching.
Outcome: "I have three specific, quantified achievements ready to justify my number."
Open a blank document and write down everything you've delivered in the last twelve to eighteen months — unfiltered, unquantified, in any order. You're collecting, not editing.
A number without evidence is a wish; a number with evidence is a proposal. The strongest evidence carries a figure: money earned, money saved, time reduced, risk removed, people trained. Where no figure exists, a before-and-after description works — what was broken, what you changed, what it's like now. Three items is the right count: fewer looks thin, more sounds like pleading. Write them down in advance, because under pressure almost nobody remembers their own achievements.
(1) "First-reply time went from 31 hours to four within six weeks, with the same five people, after I re-triaged the queue by issue type." (2) "I onboarded and trained the last two hires; both were handling the full queue in three weeks instead of the usual six." (3) "I took over the out-of-hours rota nobody wanted and it hasn't had a gap in eleven months." Each is one sentence, specific, and verifiable. Together they take about twenty seconds to say and they are the entire justification for asking for the top of the researched range rather than the middle.
Outcome: "I have a prepared answer to the salary-expectations question that doesn't undersell me."
Say this sentence out loud five times: "Based on what I've seen for similar roles, I'm looking at the 50 to 55 range — does that fit your band?" Getting the words into your mouth before the meeting is most of the work.
The advice that you must never name a number first is overstated. What matters is that any number you give is anchored to research and framed as a range whose bottom you would genuinely accept — never state a range whose floor you'd resent. If they ask first and you truly lack data, deflecting once is fine: "I'd rather understand the scope first — what range is budgeted for the role?" Deflecting twice reads as evasive. In many countries employers must publish or disclose a range on request, so asking for it is normal rather than aggressive.
Recruiter on a first call — "What are you expecting?" → give the researched range with its floor at your floor: 48 to 55. Hiring manager mid-process — "Where are you on salary?" → the same range, plus one evidence sentence from Chapter 2, because now the number needs justifying rather than just stating. An application form with a mandatory single-number field → enter your target, not your floor: the field can't hold your reasoning, and whatever goes in it is treated as your opening position for the rest of the process. In all three cases the underlying range is identical, and 48 is a number you would genuinely accept.
Outcome: "I have a prepared response to yes, to no, and to 'not right now'."
Write three boxes on a page — yes, no, not now — and give yourself two minutes per box to write your response. Pressure comes from surprise, and there are only three ways this conversation can go.
"Yes" needs the least and gets fumbled most: say thank you, repeat the number out loud to confirm it, and ask for it in writing — and do not immediately start negotiating something else on top. "No" is a question in disguise: ask what would need to be true for the number to work, which converts a refusal into a criterion. "Not right now" is the most common answer and the most dangerous, because it feels like progress; it only becomes progress if you attach a date and a measure to it before the conversation ends.
Manager: "There's no budget until the new financial year." Response: "Understood. Can we agree now what the number becomes in April, and what I'd need to have delivered by then to get it? I'd rather work toward a specific target than guess." That does three things at once: it accepts the constraint without accepting the outcome, it puts a date on the calendar, and it captures the criteria while goodwill is still high. A "not now" without a date and a number attached is simply a no wearing a friendlier expression — and six months later nobody will remember it differently to how they prefer to.
Outcome: "I know how to close the conversation, and what my real options are if the answer stays no."
Draft your follow-up email now, before the meeting, with blanks where the numbers go. Writing it calm beats writing it twenty minutes afterwards with your pulse still up.
Nothing agreed verbally exists until it's written down, and the person best placed to write it is you: a short, friendly summary the same day, stating the number, the effective date, and anything else agreed. If the answer is a firm no with no path attached, there are four real options — accept and stop asking for a defined period, negotiate non-salary items that carry actual value (days, title, training budget, flexibility), set a specific review date, or start looking. What doesn't work is accepting while staying resentful: it gets noticed, and it costs you the next increase too.
"Thanks for the conversation earlier. To confirm what we agreed: salary moves to 52,000 effective 1 April, reviewed again at the usual November cycle, with the team-lead responsibilities formally added to my role description. If I've misremembered any of that, just tell me and I'll correct it." Short, unemotional, and it creates the record without demanding anything new. Had the answer been a flat no, the same email would state the no plainly, note the agreed review date, and list the two criteria discussed — so that the next conversation starts from a shared document rather than from two different memories of the same meeting.
The complete guide — all 5 chapters, every checklist and exercise — as a clean, printable PDF. No email required.
A one-page cheat sheet of the five chapters, a 75–90 minute workshop script (with role-play) to run this live with someone else, and 12 affirmations and reflections to keep nearby.
Every guide on this site is produced with the Self-Directed Learning Framework: instead of an article that explains a topic at you, the framework turns it into a structure you work through — each chapter with one outcome, a starting action under twelve minutes, the minimum you actually need to know, a worked example, a checklist, and exercises. It starts from three questions:
Topic: Negotiating salary, in a new job offer or an existing role.
Outcome wanted: Go into a real salary conversation with a researched range, three pieces of evidence, and rehearsed responses — within a week.
Starting point: Some background — has had salary conversations before, but improvised them and accepted the first number offered.
The prompt framework behind it is public: see the C.R.A.F.T. prompt framework, including the exact prompt that generated this library.
The same underlying skill — making a clear, evidenced case out loud under pressure — in its more general form.
Read the guide →Free, self-paced guides across everyday, professional and academic topics.
See all guides