HOME SIGNALS JOB CHANGE SIGNALS
BUYER SIGNAL · TIER 1 · TRIGGERED EVENT

Job Change
Signals

When a champion, decision-maker, or buyer changes jobs — and how to convert that move into pipeline before the new role's vendor stack is locked in.

01What are job change signals?

A job change signal fires when someone in your ICP, customer base, or champion list moves to a new company, gets promoted, or is hired into a new role. The signal is detected from public LinkedIn updates, press announcements, and CRM contact monitoring — and matters because the new role almost always reopens the vendor evaluation window.

The pattern is well-documented: 92% of B2B buyers start their next purchase with at least one vendor in mind, and 41% already have a single preferred vendor selected before formal evaluation (Corporate Visions, 2026). Past champions who change jobs disproportionately bring their preferred stack with them — which is why this signal converts 2 to 3x better than cold outbound on every benchmark we have seen.

02How to use job change signals in outreach

Treat a job change as a warm reintroduction, not a fresh cold opener. The contact already knows your product if they were a champion or user previously; the goal is to get back in front of them in the first 30 to 60 days of the new role, before they finish auditing the existing stack.

Industry benchmarks place signal-triggered outreach at 8 to 15% reply rates versus the 2 to 5% baseline for cold sequences from static lists (Amplemarket, signal-based selling). The teams that win on this signal are the ones with a 24 to 48 hour SLA from detection to first message — not the ones who batch job changes into a weekly enrichment job.

03Job change signal schema

fl0 emits this payload to your webhook the moment a job change is detected. It is shaped to drop directly into Clay, HubSpot, Salesforce, or a Common Room enrichment chain.

POST /webhooks/job-change JSON
{
  "signal_type": "job_change",
  "detected_at": "2026-05-04T08:14:22Z",
  "contact": {
    "name":               "Jamie Rivera",
    "linkedin_url":       "https://linkedin.com/in/jamie-rivera",
    "prior_role":         "VP Sales, Acme Corp",
    "new_role":           "CRO, Vector Logistics",
    "start_date":         "2026-05-01",
    "prior_relationship": "former_user"
  },
  "new_account": {
    "domain":    "vector-logistics.com",
    "icp_match": true,
    "size":      410
  },
  "score":              0.91,
  "recommended_action": "sequence_within_48h"
}

04How sales teams use job change signals

SDR

Reintroduction sequences

When a former champion lands at a new ICP-fit company, the SDR has a 48-hour SLA to send a congrats-plus-context opener. No pitch in message one — just relationship continuity.

AE

Existing-account expansion

When a buyer at a current customer is promoted, route the alert to the AE so they can re-anchor the relationship and pre-empt churn risk from a new team owner.

RevOps

Champion tracking

Maintain a "champions on the move" report. Quarterly, this becomes the most reliable expansion-pipeline forecast in the business — typically 2 to 3x better than cold.

Marketing

Account-level retargeting

Push the new-account domain into LinkedIn and Google ABM audiences for 90 days post-detection — covering the new buyer's vendor-audit window with brand impressions.

05FAQ

How is a job change signal different from a cold outbound list?

A cold list is "looks like ICP." A job change signal is "this specific person is in a fresh evaluation window right now." Signal-triggered sequences hit 8 to 15% reply versus 2 to 5% for cold (Amplemarket benchmark), and job change signals specifically convert 2 to 3x better than cold (UserGems data).

Which job change events are worth tracking?

All of them, but they have different conversion profiles. Promotions of existing champions inside current customers are highest-value (expansion). Champions or users moving to new ICP-fit companies are second (warm reintroduction). External hires into your buyer-persona role are third (new logo). Track all three; route them to different teams.

How fast does fl0 detect a job change?

Typically within 24 hours of the LinkedIn or press announcement. Detection is continuous, not batched, so the signal lands in your CRM and Slack within minutes of fl0 picking it up.

Can fl0 detect job changes for accounts that are not in my CRM yet?

Yes. The system monitors your CRM contacts for moves and also watches your defined buyer persona across the broader market. New ICP-fit hires fire as net-new logo signals.

Does this replace UserGems or Common Room?

It depends on your stack. fl0 is a signal-driven AI revenue engine — job change is one of several triggered events it acts on (alongside leadership moves, hiring, funding, intent surges) and it ships an AI SDR that drafts and runs the outreach. UserGems is a pure job change data feed. Common Room is multi-source signal aggregation. Many teams use fl0 alongside one or both.

● COMPARE

fl0 vs Clay

Signal-driven AI revenue engine vs data enrichment platform — when to use each.

Read the comparison →
● GLOSSARY

What is buyer intent data?

Definition, sources, and where job change signals fit in the broader intent landscape.

Open glossary →