TL;DR
A UK technology manager recently asked for a 170% pay rise. The request was legitimate. The final number landed at 140%. £58,000 to £139,000. Most career advice caps "realistic" raises at 10-15%, and that's accurate for routine reviews. For three specific situations (role expansion, absorbed senior departures, competing offers), much larger numbers are on the table. This post covers exactly what the successful request structure looks like, the five components it must have, and the timing windows that compound everything else.
I've been building CVPilot, an AI CV optimisation tool, and one pattern from the users who've landed significant pay rises is that almost none of them started with "I'd like to discuss my compensation". They started with a document.
When 50-200% is actually realistic
Three situations where the 10-15% ceiling doesn't apply:
1. Your role has quietly grown 3x
You were hired as "Marketing Executive". You're now running three channels, managing two direct reports, owning £2 million in ad spend. Title unchanged. Compensation unchanged. This is the most common trigger, and the one most employees never cash in.
2. You absorbed a senior departure
Your manager left. You've been doing both jobs for six months. HR hopes you'll keep doing both for less than the replacement would cost. Market rate for the combined role is often 60-100% above your current salary.
3. You have a competing offer in writing
You genuinely tested the market. Your current employer now faces a straightforward cost comparison: pay up, or pay recruitment fees plus ramp-up plus risk.
The 170% case study
Anonymised, UK technology manager, 3 years at the company, originally hired as "Senior Engineer". Absorbed team leadership, platform architecture, and hiring responsibilities without formal title or salary change.
His written proposal to the CTO had four sections:
Section 1: What I was hired to do. Original job description, agreed metrics, starting salary. Six bullets, purely factual.
Section 2: What I actually do now. Eleven bullets with evidence: "Own architecture decisions for the core platform (previously under Head of Engineering)", "Lead hiring for the platform team (4 hires in 2025)", "Run weekly platform review with exec team".
Section 3: Market comparison. Three comparable role titles at similar companies with published salary ranges. Levels.fyi, Glassdoor, three LinkedIn salary guides. Range: £135,000-£165,000.
Section 4: The proposal. Two options presented as a choice:
- Adjust compensation to £157,000 (midpoint of market range) effective immediately, with title change to Platform Engineering Lead.
- Re-scope the role back to the original job description, delegating the absorbed responsibilities to new or promoted hires, and recruit externally for Platform Engineering Lead.
The CTO took three days, consulted HR, came back with £139,000 plus title change. He didn't want to lose a senior person or pay recruitment plus ramp-up plus knowledge-loss cost.
The five required components
| Component | What it looks like | Why it matters |
|---|---|---|
| Written proposal | PDF or document, not verbal | Forces formal HR response, prevents renegotiation |
| Role expansion evidence | Dated list of new responsibilities | Demonstrates the gap between hire-level and now-level |
| Market data | Three public salary sources for the new scope | Anchors to external reality |
| Cost-of-loss calculation | Recruitment fees + ramp-up + knowledge risk | Makes saying no expensive in pounds |
| Alternative option | A second path that's worse for the employer | Gives HR an easy yes, because the no is harder |
Missing any one component usually results in a significantly smaller offer or refusal.
Timing is not optional
The same request lands differently depending on when:
- Budget-setting season (Sep-Nov). For most UK companies, salary budgets for next year are set in this window. Requests landing in October accommodate easily. February requests force retroactive budget.
- 2-4 weeks after a major outcome. Documented enough, recent enough.
- Within 60 days of a senior departure you absorbed. Before the extra responsibilities are assumed permanent.
Requests outside these windows get reasonable responses in smaller amounts. Timing is the difference between 40% and 100%.
Five mistakes that sink ambitious negotiations
- Making it about personal circumstances. Mortgage, children, cost of living. Valid for your decision to negotiate. Invisible to your employer's salary logic.
- Naming a number too early. Lead with role expansion, then market data, then the proposal. Numbers upfront anchor wrong.
- Negotiating against yourself. When HR counters, don't immediately accept or counter again. "Thank you, I'll consider this." Take 48 hours.
- Focusing on title over scope. Title without scope is hollow. Scope without title is a foundation for the next raise.
- Forgetting the actual ask. "I'd like to discuss my compensation" is an opener. The formal request document with a specific number is the ask.
Negotiation prep checklist
- Original job description and original salary
- Current responsibilities list, dated
- Three market salary benchmarks for your actual scope
- Recruitment cost estimate (20-30% of salary + 6 months ramp-up)
- Written proposal document with ask and alternative
- Two backup positions
All six ready = you're ready. Fewer than four = you're not.
Full guide with the negotiation scripts, counter-offer responses, and CV framing for significant raises: CVPilot blog
What's the most ambitious raise you've landed, and what was the key that made it work?
Top comments (0)