The Job-Change Trigger Playbook: Turn a Champion's Move Into Pipeline

A past champion, buyer, or power user has just moved to a new company. This playbook is for founders selling their own product, account executives, SDR leads, and partnerships teams who want to re-engage that person and open the new account before a competitor gets there first. It carries the job end to end: build the watch list, detect the move within hours, qualify the new employer, and run a first-touch that turns a relationship into pipeline.

Most sales guides stop at "set up an alert." This one specifies who to track, how fast to move, how to decide whether the new company is worth an account, and exactly how to write the re-entry message. The single most reliable person-level signal in outbound is a known contact changing employers, and it deserves a procedure rather than a tip.

Why a tracked job change beats every firmographic trigger

A tracked contact's move is a discrete, person-level, verifiable event, unlike inferred firmographic intent. It is one named human with a known budget history, which is why the win rates dwarf cold outreach.

The numbers make the case bluntly. Selling to known contacts - former customers and past champions who changed jobs - wins at 37% versus 19% for cold outreach. Break it down by relationship and the gap widens: someone who sat on a previous buying committee is almost 3x more likely to buy again, at a 49% win rate. Deals with a former champion carry a 17% higher win rate than deals without one.

Compare that to the state of intent data. Forrester's Q1 2025 Intent Data Providers Wave found that 50% of companies leveraging B2B intent data report too many false positives. The ambiguity is structural: a spike in research activity may come from a student, a consultant, a competitor, or a low-authority employee, and most third-party intent data identifies companies, not individuals. You know a company is researching but not which of their employees is driving it.

A job change removes that ambiguity. You are not guessing at a company's mood. You know the person, you know what they bought or evaluated before, and you know they just walked into a new building with a new budget.

Intent tells you a company is curious. A job change tells you a named buyer just got a new checkbook.

Who to put on the watch list

Track people who already know you before you track strangers: past champions and advocates, closed-won buyers, closed-lost evaluators, and product users. These four relationship types are the entire addressable base for this play, and each converts differently.

The order of value is well documented. Prior buying-committee members are the strongest, followed by customer-success contacts, then product users. Here is the repeat-purchase data laid against the cold baseline.

Read the multiples: buying-committee members win at 2.6x the cold baseline and product users at 1.7x. Even the weakest tracked relationship beats cold by a wide margin, so a complete list is worth more than a perfectly filtered one.

The trap is the CRM. On average, CRMs are missing 78% of former champions with qualified job changes, and of the champions that are in the CRM, only 50% have ever been engaged. That means a CRM-only watch list is silently thin. You will feel like you are running the play while missing most of the moves worth acting on.

The addressable base favors VP-level lists

If you gate your watch list to the C-suite, you forfeit most of the volume while chasing the same first-90-days budget. In Refolk's index of professional profiles, US VP of Sales titles outnumber CRO and CSO titles roughly 6 to 1.

Two things fall out of this. First, a list built on VP-level movers has a far larger base than a C-level-only list, so widen the seniority band rather than restricting it. Second, geography compounds scarcity: the US VP of Sales pool is about 75x the UK pool. A UK-focused team must widen relationship types - reach for product users and closed-lost evaluators far earlier - to keep the watch list large enough to produce a steady flow of alerts.

The window: how fast you have to move, and why

Move within 30 days of the detected change. Reply rates for job-change outreach drop measurably after 30 days, and after 60 days the contact is no longer new and the signal has substantially decayed. Sources cluster on a 30 to 90 day runway but disagree on the exact sweet spot.

The consensus floor is about 7 days: avoid week one, when the mover is still onboarding. The consensus ceiling is 30 to 90 days, after which they have inherited the existing tech stack and made their vendor decisions.

The decay is a budget-calendar effect, not just an inbox one. New buyers spend roughly 70% of their budget in the first 100 days. New executives evaluate new vendors 3 to 5x more often than incumbents and initiate technology decisions within their first 90 days. And they are under pressure to show results: average VP of Sales tenure is now about 19 months, down from 26. The person is motivated to make changes early because their own clock is short.

On day-one timing there is a genuine disagreement worth resolving in your own process. Some sources put a congratulations note on day one. Others find week two to three outperforms day one: let the mover get settled enough to have context but reach them before priorities lock. My read of the evidence is to split the difference. A short congrats-only note can go early because it carries no ask. The substantive value message should wait until roughly week two, when the new hire starts auditing what they inherited.

Run the play, step by step

This is the full sequence from watch list to opportunity. Each step names the owner, the rough time cost, and what done looks like. The two five-step frames in the field - track, alert, route, respond, personalize, and the parallel aggregate, filter, enrich, route, track - both collapse into these seven concrete moves.

Detection is not the hard part. Vendors claim job-change detection within 24 to 72 hours by monitoring public professional profiles, CRM contact updates, and conversation data. The hard parts are completeness of the list, correct routing, and honest qualification. Those are the three places the play actually breaks.

Refolk is where the list-completeness problem gets solved. Because the CRM misses most qualified champion moves, you need an external index you can query in plain English to surface who has moved and where they landed - across public LinkedIn and the open web - rather than waiting for a CRM field to update.

Qualifying the new employer as an account

Before the first touch, decide whether the mover's new company is worth an account at all. Combine firmographic gates with signal validation, and drop non-ICP accounts even when the person is warm. A friendly reply from a bad-fit company is a false positive, not a win.

ICP fit is defined by three layers. Treat them differently in your scoring.

The strongest single predictor is a combination: a new CxO hire paired with aggressive recruiting in a function signals both budget authority and operational urgency. When your mover is the new CxO and their company is hiring hard in their area, you have both the buyer and the mandate.

Turn the read into a tiering decision. A Tier 1 account plus a leadership-change signal earns immediate personalized outreach. A Tier 2 account plus a funding event escalates to Tier 1 treatment. Everything below the ICP gate gets dropped no matter how warm the contact.

Keep the account list disciplined. A workable target-account list is 100 to 500 accounts; more than that is outbound, not account-based selling. The job-change signal should feed that list, not replace the fit criteria that make it a list worth working.

The first touch and the follow-up

The first message congratulates and asks for nothing. A short, genuine note acknowledging the new role with no ask creates a positive association before you need anything. The value follow-up comes later, framed around the mover's new mandate rather than your product.

Leading with a demo request on day three annoys and burns the relationship you spent years earning. The uplift here is fragile precisely because it rests on goodwill. Signal-personalized job-change emails hit 18% reply rates versus 3.4% for generic outreach, and one practitioner team reports 17% or higher reply rates with a 10% booked-meeting rate on these plays. That lift evaporates the moment the message reads like a sequence.

Subject: Congrats on the new role

Hi [First name],

Saw you started at [New company] as [New title] - congratulations, that's a great move. [One specific, genuine line about the company or the mandate.]

No agenda here, just wanted to say it's good to see where you landed. Rooting for you.

[Your name]

Subject: [Their function] priorities in your first quarter

Hi [First name],

Now that you're a couple weeks in - when we worked together at [Prior company], the thing that moved the needle fastest was [specific outcome].

At [New company], if [likely first-quarter priority] is on your list, I put together [a resource, benchmark, or intro] that might save you some ramp time. Happy to share it, no strings.

Want me to send it over?

[Your name]

Do not single-thread. With buying committees averaging 13 people, a deal that rests on one champion is fragile, and a single departure can kill it. Engage three or more contacts at the new account so the opportunity survives if your mover moves again.

How this play goes wrong

The failure modes are consistent across sources, and every one of them has a specific check. Most of them are execution errors, not detection errors, which is why tracking the program separately matters so much.

The one worth dwelling on is routing, because it quietly destroys the most value. Every vendor detects a move within 24 to 72 hours, so detection is a solved problem. But if you hand that alert to a new SDR, the response rate reverts to the cold baseline of around 2%. The play converts at warm rates only when the person who already owns the relationship sends the message. Automate the detection; never automate the sender.

The second underrated failure is false positives from intent overlays. It is tempting to stack a third-party intent signal on top of the mover to feel more confident. Resist it. Half of intent-data users already report too many false positives, and a prospect showing content activity receives 36 or more vendor outreaches within two weeks. The job change is your clean signal. Muddying it with noisy intent lowers precision rather than raising it.

Verify before you call it done

Run this checklist before you treat the play as live. It maps directly to the failure modes above, so a passing checklist means the common ways to lose the signal are closed off.

Keeping the watch list alive

A job-change play is not a one-time setup; it is a standing program that decays if the list stops growing. Two forces work against you: median US employee tenure dropped to 3.9 years in 2024, the lowest since tracking began in 2002, and VP tenure sits near 19 months. Your best contacts will keep moving, which is good for pipeline and bad for a static list.

Re-run the list build monthly. Add every newly closed-won buyer, every closed-lost evaluator from recent quarters, and net-new product users as they appear. For teams in thinner geographies, widen relationship types before you widen seniority, because the pool math forces it: a UK team cannot lean on VP-level movers alone the way a US team can.

Finally, revisit the window and routing rules against your own data. The published windows range from 7 to 90 days for good reason, and your reply-rate curve by days-since-move will tell you where your own cliff is. Measure it, hold to it, and the play compounds every time one of your former buyers walks into a new building.