Rational & Practical Salary Negotiation Prep (With Script)

6 min read Original article ↗
Career

Salary Negotiation Prep Pack: Strategy, Numbers & Script

Use a lightweight monthly–quarterly–annual system to build evidence, benchmark your role, and make a clear ask with a clean fallback—without improvising in the meeting.

Salary Negotiation Prep Pack: Strategy, Numbers & Script
Photo by Christina @ wocintechchat.com M

Jamie walked into a compensation talk with one argument: “I’ve been working really hard.” The manager didn’t disagree—but still couldn’t justify a change on the spot. The meeting ended with “Let’s revisit next cycle,” which often translates to: bring evidence, a market anchor, and a specific request that’s easy to evaluate.

The fix is boring and effective: treat compensation like portfolio hygiene. You don’t “hope” markets pay more—you track outcomes, check pricing, and rebalance your approach on a calendar. Below is a copy/paste script plus a prep system that turns the next 12 months into a steady evidence runway (and a one-page brief you can send ahead).

What to bring to the meeting

  • 1) A scope snapshot: what you own now (and what risk/complexity you carry) vs. 6–12 months ago.
  • 2) A market range: low / mid / high for the same scope in your location or remote band (document where each number came from).
  • 3) 3–6 outcome bullets: each with a metric and proof link.
  • 4) One clear ask: a specific compensation outcome + an effective date.
  • 5) A fallback ladder: ranked alternatives that are still measurable (milestones + timeline, not “we’ll see”).
One-page brief field What “good” looks like Common weak version to avoid
Role + scope Title/level, team size, stakeholders, systems owned, on-call or risk profile Just your title
Market range Low/mid/high + notes (location, company type, recency) One number with no context
Evidence bullets Action → Outcome → Metric → Proof link (doc/dashboard/ticket) “Worked hard,” “led projects,” “helped team”
Your ask Exact compensation change requested + effective date “Any raise?”
Fallback Milestones + decision owner + timeline + next meeting date “Let’s revisit later”

Monthly routine: build evidence in 10 minutes

  • Maintain an evidence log (10 minutes/month):
    • Format: What I did → what changed → by how much → proof.
    • Metrics menu (pick what fits your job): revenue influenced, costs avoided, cycle time reduced, SLA improved, defect rate reduced, incidents prevented, accuracy improved, conversion rate changed, customer satisfaction signal, throughput increased.
    • Proof examples: dashboard link, PR/commit, ticket IDs, postmortem, stakeholder email, customer note, meeting notes with decisions.
  • Update “scope creep” notes:
    • Write one sentence: “This month I started owning ______ that I didn’t own 6 months ago.”
    • Flag if you’re now the escalation point, signing off on spend, or coordinating cross-team delivery.
  • Do one manager alignment question in a 1:1:
    • Ask: “What would make you comfortable saying I’m operating at the next level?”
    • Write the answer verbatim. Those phrases become your milestone checklist later.

Quarterly routine: re-price and package

  • Refresh your market notes (30–45 minutes/quarter):
    • Save 2–4 comparable job postings (same scope, not just same title). Record their range if listed.
    • Capture any recruiter range shared with you (only if explicitly provided).
    • Write a 2-line “range rationale”: what’s comparable and what’s not (location, remote band, company stage, responsibilities).
  • Convert your log into a manager-ready packet:
    • Pick 3–6 bullets max. If you need 12 bullets, you likely don’t have a headline impact yet—prioritize building one.
    • Add a “next quarter plan” paragraph: 2–3 deliverables you expect to ship or own, with how success will be measured.
  • Timing map:
    • Write down your company’s decision windows: performance cycle, promotion committee timing, budget planning months.
    • If unknown, ask neutrally: “When are compensation adjustments typically decided, and what’s the process?”

Annual routine: choose your lane and fallback

  • Pick one primary ask type:
    • Base-first ask: easier to compare and budget; fewer moving parts.
    • Total-comp ask: more levers (base/bonus/one-time/equity where applicable) but needs scenario modeling for clarity.
  • Decision rules to keep it clean:
    • If your current pay is below the midpoint and your scope matches peers: anchor your ask around midpoint with evidence.
    • If you’re near the top of the band: focus on level change criteria and timeline (not a vague “raise”).
    • If budgets are frozen: prioritize a written milestone plan + next decision date, and discuss non-base levers only if your employer uses them.
  • Send the one-page brief 24–48 hours before the meeting: it turns a surprise negotiation into a scheduled decision discussion.
  • Create a ranked fallback ladder:
    • 1) Compensation change now (your primary request)
    • 2) Compensation change on a defined future date (with what must be true)
    • 3) Level/title review with explicit criteria and a calendar date
    • 4) One-time bonus or equity refresh (only if your company uses these)
    • 5) Scope adjustment that triggers a level review (documented, not informal)

Worked example

Scenario (illustrative): You’re a Senior Analyst. Current base pay is $80,000. Your documented market range for comparable scope is $90,000–$110,000, with an estimated midpoint around $100,000. Over the last two quarters, you shipped measurable outcomes with proof links.

  • Evidence bullets (example format):
    • Automated weekly reporting → cycle time reduced from 6 hours to 45 minutes → saved ~5.25 hours/week → dashboard + repo link.
    • Rebuilt forecasting model → accuracy improved from 72% to 85% → reduced stockouts in key segment → backtest + stakeholder note.
    • Partnered with Sales Ops → lead-to-meeting conversion improved by 9% → experiment doc + CRM report.

Ask: Adjust base pay to $100,000 effective next pay cycle (or the next standard compensation window), aligning to midpoint for the current scope.

Item Current Proposed Difference
Annual base $80,000 $100,000 $20,000
Monthly base (approx) $6,667 $8,333 $1,667

Fallback if the answer is “not now”: “Let’s document the 2–3 milestones that would justify approval, confirm who signs off, and set a follow-up date (e.g., 90 days). If available in this company’s comp system, we can also discuss an interim lever like a one-time bonus or an equity refresh.”

Email to request the meeting (copy/paste):
Subject: Scope and compensation alignment
Hi [Manager], I’d like to schedule 30 minutes to review my current scope, recent outcomes, and compensation alignment. I’ll send a one-page summary (impact + market range + proposed adjustment + fallback options) 24–48 hours ahead so the discussion is straightforward. What time works this week or next?

Meeting script (say this, then pause):

  • “I’d like to review whether my compensation matches the scope I’m operating at.”
  • “Here are three outcomes from the last six months with metrics and proof.”
  • “Based on the market range for this scope, I’m requesting base move to $100,000, effective [date].”
  • “If that timing isn’t possible, can we agree today on the milestones, the decision-maker, and the date we’ll revisit?”

Risks and trade-offs to plan for

  • Pay bands can cap raises: if you’re near a band ceiling, the practical path is often a level review with explicit criteria.
  • Process timing matters: outside budget cycles, approvals can be structurally hard even with strong evidence.
  • Ambiguity is the enemy: if you accept “later,” convert it into milestones + date + owner before leaving the room.
  • Comparability is tricky: postings and ranges vary by location, remote band, and company type—benchmark the scope, not the title string.
  • Variable components reduce certainty: if discussing bonus/equity, model a simple worst/base/best outcome so you understand variability.