We pulled six months of closed-won data from a UK IT services firm. Seventeen of their 31 new clients had a decision-maker join the account within 90 days of signing the contract. The new hire was evaluating every supplier relationship they'd inherited. When we built a system to track those job changes and fire a four-touch sequence the day a LinkedIn profile updated, their conversion rate on that contact segment stopped being luck and became 18% contact-to-booked-call.
The window is real: a new VP Operations or Head of Procurement arrives at a target account carrying no supplier loyalty, a mandate to show early competence, and a calendar actively filling with vendor conversations. Reach them in week one or two and you're competing on merit. Miss it and you're cold-outreaching a contact who's already made decisions.
Why job changes are the highest-signal trigger in UK B2B outbound
Most intent signals are indirect — a contact reading your pricing page, a company posting a job ad implying budget. A job change is direct: a named individual just moved into a buying seat at a company you want in your pipeline.
The 30-day window is not marketing mythology. Gartner's B2B buying research shows newly appointed leaders make a disproportionate share of vendor decisions in their first quarter. In UK professional services, new hires spend weeks 2–8 mapping existing commitments and scheduling introductory vendor calls. The signal is also specific enough to personalise genuinely — you know the company, the person's previous role, and roughly what challenges a new Head of IT at a 200-person UK manufacturer typically inherits.
| Signal | Specificity | Timing precision | Typical conversion lift vs cold |
|---|---|---|---|
| Job change announcement | High — named person, role, company | ±1 day | 3–5× |
| Website visit (pricing page) | Medium — company, not individual | Real-time | 1.5–2× |
| Job posting (buying intent) | Low — implies budget, not buyer | Weeks lag | 1.2× |
| Funding announcement | Medium — company signal only | Same day | 1.3–2× |
| Content download (gated) | High — named person, interest area | Real-time | 2–3× |
Job change outperforms every other trigger on specificity: named contact, clear reason to reach out, predictable evaluation window.
Tracking job changes at scale: LinkedIn Sales Navigator, Clay, and Surfe for real-time alerts
Manual LinkedIn monitoring breaks above 50 contacts. At 500 target accounts you need an automated feed.
LinkedIn Sales Navigator — the most reliable source. Set up Account Lists for target companies and Contact Lists for tracked decision-makers. Sales Navigator pushes alerts within 24–48 hours of a profile update. Pull them via the Sales Navigator API (enterprise tier) or via a Make/n8n connector.
Clay — the enrichment layer. When an alert arrives, Clay runs a waterfall of lookups: verified email at the new company (via Hunter, Apollo, and Datagma as fallbacks), mobile, company revenue, and headcount. The Clay enrichment documentation covers waterfall priority. Set "verified email only" — unverified emails kill deliverability.
Surfe — the CRM push layer. Surfe (formerly Leadjet) connects LinkedIn directly to HubSpot and pushes updated contact records. When the contact already exists from their previous company, Surfe updates rather than duplicates.
The flow: Sales Navigator alert → Clay enrichment → Surfe CRM push → HubSpot sequence enrolment. Each step connects via native integration or webhook.
Signal routing: getting the right account into the right sequence automatically
Not every job change should trigger the same sequence. A former champion joining a target account is a different play from a new decision-maker at an account you've never touched. Routing logic gates which sequence fires.
Job change alert
│
▼
Is the new company a target account (ICP match)?
│
Yes │ No
│ └──► Enrich only, tag "monitor", no sequence
▼
Is the contact a known champion (prev customer / eval)?
│
Yes │ No
│ └──► Standard new-hire sequence (4-touch)
▼
Champion re-engagement sequence (2-touch — warm intro, no cold context needed)
The ICP check runs before any enrolment decision:
- New company must match ICP criteria (headcount 50–500, UK-registered, target industry sector)
- Contact's new role must be in the buying committee (VP/Head/Director of Ops, Finance, Procurement, IT)
- Contact must not already be enrolled in an active sequence (dedup check — covered in the HubSpot section)
If all three conditions pass, the sequence enrols automatically within two hours of the alert arriving.
Four-touch sequence design: day 1 LinkedIn connect, day 3 email, day 7 personalised video, day 14 phone
The timing is deliberate. Day 1 is the minimum reaction time — you want to arrive before the calendar fills, not the same day the person updated their profile at 9am. Most contacts update LinkedIn in the first week of starting; reaching out the day the alert arrives reads as attentive, not pre-emptive.
Day 1 — LinkedIn connection request with a personalised note referencing the new role. 300-character limit. One sentence on why the connection makes sense. No pitch. Connection acceptance rate with a genuine note referencing the hire runs around 38–42% in our client data.
Day 3 — Cold email from a named sender. Subject line uses the new company name, not the contact's name. Body: one paragraph on the challenge new hires in this role typically face, one paragraph on how you've solved it for similar companies, one direct ask for 20 minutes.
Day 7 — Personalised video via Loom or Vidyard. 60–90 seconds. Screen-record a relevant case study or the contact's company website while narrating. In a test across 120 sequences, video at touch three generated 2.3× the reply rate of a third plain-text email — the highest-performing touch in the set.
Day 14 — Phone call with a voicemail script if no answer. The voicemail references the video: "I sent a short clip last week showing how we helped a similar ops team…". Keep voicemails under 25 seconds. After day 14: pause, flag for SDR review. No further automated touches.
Copy and personalisation: using the hire announcement as the opener without sounding like a stalker
There is a line between "I noticed you joined X" and "I've been monitoring your LinkedIn profile." The first acknowledges a public announcement. The second implies surveillance.
The opener that works: "I saw [Company] come up as your new home — congratulations on the move." Subject lines that perform: "[Company] — quick question" or "New to [Company]?" Subject lines that fail: "Congratulations on your new role at [Company]!" — scraper template, registers immediately.
Don't mention the source of the alert (Sales Navigator, Clay, LinkedIn). Drop the word "noticed" — it's so tied to outreach templates that it reads as automated. Don't cite the exact start date.
The formula: role challenge + company context + one proof point. "Ops leaders at mid-size UK manufacturers typically inherit three or four fragmented supplier systems in the first month. We helped [Reference Client] consolidate their supplier onboarding to one automated flow in six weeks. Worth 20 minutes?" See our LinkedIn AI SDR portfolio case for this formula applied at volume.
PECR and GDPR: what the ICO expects when you're targeting new hires in UK companies
Cold email to UK business addresses falls under both PECR and UK GDPR. The critical distinction: PECR's soft opt-in rule applies to consumers; B2B email to a named contact's work address is governed mainly by UK GDPR's legitimate interests basis.
The ICO's direct marketing guidance is the primary reference. In short:
- You can email a business contact at their work address without prior consent under legitimate interests, provided the subject matter is genuinely relevant to their professional role.
- You must identify yourself clearly, provide a working unsubscribe link in every message, and honour opt-outs without undue delay.
- The email must relate to their business activities, not their personal life. An email to a new Head of Procurement about procurement automation is legitimate. The same email to their personal Gmail is not.
LinkedIn automation is a separate issue. LinkedIn's User Agreement prohibits automated messaging and connection requests via third-party tools. The day-1 connection request must be sent manually or via a tool with a documented LinkedIn API partnership — in 2026, that list is short.
Document a legitimate interests assessment (LIA) before running the sequence. If the ICO audits, a written LIA showing you assessed necessity and proportionality is your evidence of due diligence. For a deeper look at UK outbound compliance, see our post on cold email deliverability for UK SMEs.
CRM plumbing: creating the trigger, enrolling the contact, and avoiding duplicate sequences in HubSpot
The HubSpot workflow has four components: trigger property, enrolment criteria, dedup check, and sequence enrolment action.
{
"workflow_name": "Job Change — New Hire Sequence Enrolment",
"trigger": {
"type": "contact_property_change",
"property": "job_change_detected",
"value": "true"
},
"enrolment_criteria": [
{
"property": "associated_company_is_icp",
"operator": "is_equal_to",
"value": "true"
},
{
"property": "contact_role_type",
"operator": "is_any_of",
"values": ["decision_maker", "champion"]
},
{
"property": "hs_is_currently_enrolled_in_sequence",
"operator": "is_equal_to",
"value": "false"
}
],
"actions": [
{
"type": "delay",
"delay_amount": 2,
"delay_unit": "hours"
},
{
"type": "enrol_in_sequence",
"sequence_id": "JOB_CHANGE_4TOUCH_V2",
"sender_user_id": "{{contact.hubspot_owner_id}}"
},
{
"type": "set_contact_property",
"property": "enrolled_from_trigger",
"value": "job_change"
}
]
}
The hs_is_currently_enrolled_in_sequence check is the dedup guard. Without it, a contact already in a nurture sequence from their previous company will get enrolled again. HubSpot's native sequence tool enforces single enrolment per sequence, but workflow-triggered enrolments bypass that guard unless you code the check in explicitly.
The enrolled_from_trigger property enables cohort reporting: which contacts came from job change signals versus other sources. This is how you measure 18% conversion as a distinct segment rather than blended into overall sequence stats. For HubSpot setup decisions, see also HubSpot vs Salesforce for UK SME outbound.
What changed in 2025–2026: LinkedIn's automation crackdown and the shift in job-change signal sources
LinkedIn accelerated restrictions on third-party automation throughout 2025. By Q1 2026, browser-extension tools — Dux-Soup, Expandi, MeetAlfred, LinkedHelper — had generated account restrictions at scale. LinkedIn flagged profiles sending more than 25–30 connection requests per week from non-Sales Navigator accounts, and Sales Navigator itself saw several data-export endpoints deprecated.
The practical impact: teams now send day-1 connection requests manually, batching 10–15 per day from a warmed account with 500+ connections and regular organic activity.
The alternative gaining adoption in 2026 is People Data Labs, which aggregates job change data from job boards, company websites, and press releases rather than relying solely on LinkedIn profile updates. The tradeoff is 12–24 hours slower than Sales Navigator on average, but significantly less dependent on LinkedIn's platform decisions. Proxycurl offers a similar aggregated signal via a documented REST API.
A counterpoint worth considering: Salesloft's 2025 B2B prospecting report notes that job change outreach is saturated in financial services and SaaS, where prospects receive three to five messages within 48 hours of announcing a move. The saturation is real; the answer is tighter ICP filters and differentiated copy, not abandoning the signal. Teams doing this well in 2026 run dual-source signals — Sales Navigator for speed, PDL or Proxycurl for resilience — with dedup logic to prevent double-triggering.
Good / Bad / Ugly: three job-change sequence designs and their actual conversion rates
Good — 18% contact-to-booked-call (the UK IT services firm from our opening)
Tight ICP filter: UK companies, 100–400 headcount, IT budget holder as defined role. Signal from Sales Navigator plus Clay enrichment. Day-7 video recorded by the account owner, not a generic brand clip. Day-14 call from a real number with a tailored voicemail. Sequence enrolled 340 contacts over six months — the restraint kept quality high. For more on how we built the underlying SDR system, see our LinkedIn AI SDR case study.
Bad — 3.2% contact-to-booked-call (a SaaS client who built their own version before coming to us)
They enrolled every job change alert with no ICP filter, which meant sequences firing on contacts at 10-person companies with no realistic budget. Email copy used "we noticed you changed jobs" as an opener. No video touch. The sequence ran 30 days with eight emails rather than four — complaint rate exceeded 0.3%, which damaged the sending domain's reputation. The multi-channel outbound sequence post covers frequency limits in more detail.
Ugly — 0.4% and a domain blacklisting (a lead generation agency we were asked to recover)
Fully automated LinkedIn connection requests at 250 per day via browser extension triggered account restrictions within 12 days. The sending domain was registered three weeks before the sequence launched with no warm-up period. Job change data came from a third-party broker that had not updated its GDPR data processing agreements since 2021. All three failures compounded: restricted LinkedIn account, blacklisted domain, and an ICO inquiry triggered by a complaint. Recovery took 11 weeks.
The pattern: conversion rate on job change signals tracks ICP discipline almost exactly. Generic copy against an unfiltered list performs worse than cold outreach — the personalisation context raises an expectation of relevance that the message then fails to meet. The B2B intent data guide covers layering job change alongside other signals for a multi-trigger approach.