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

*You will build a monitored watch list, catch a champion's move within 72 hours, qualify the new employer, and send a warm first-touch inside the 30-day window.*

- Canonical URL: https://www.refolk.ai/guides/job-change-trigger-playbook
- Pillar: Sales and go-to-market
- Format: Playbook
- Published: 2026-08-07
- Last reviewed: 2026-08-07
- Reading time: 15 min
- Keywords: track when customers change jobs, champion job change sales play, past customer new company outreach, job change trigger playbook, re-engage former buyer new role

## Key takeaways

- Selling to known contacts wins at 37% versus 19% for cold outreach, and a prior buying-committee member wins at 49%, roughly 2.6x the cold baseline.
- The re-engagement window is short because budget is front-loaded: new buyers spend about 70% of their budget in the first 100 days, so reply rates decay after 30 days and the signal is largely dead by 60.
- The play dies at routing, not detection: every tool catches a move within 24 to 72 hours, but handing the alert to a new SDR reverts the response rate to the roughly 2% cold baseline.
- The CRM is the weakest link: about 78% of qualified champion moves are missing from CRM and only half of those present ever get engaged, so enrichment beats copy-tweaking for lift.
- In Refolk's index, US VP of Sales titles outnumber CRO/CSO roughly 6 to 1 (37,322 versus 6,238), so a watch list gated to the C-suite forfeits most of the addressable volume.
- Signal-personalized job-change emails hit 18% reply rates versus 3.4% for generic sends, and job-change programs should convert at 2 to 3x cold rates or execution is broken.

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.

**37% - Win rate selling to known contacts versus 19% cold**

Former customers and past champions who changed jobs, per the Salesmotion benchmark.

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.

| Contact type | Win rate |
|---|---|
| Previous buying-committee member | 49% |
| CS contact | 44% |
| Product user | 33% |
| Cold outreach (baseline) | 19% |

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.

> **Watch out:** The CRM is the weakest link in the list
>
> Roughly 78% of qualified champion moves are missing from CRM and only half the rest are ever engaged, so list completeness, not messaging, is usually the real constraint. Enrich against an external source of professional profiles rather than trusting the CRM alone.

### 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.

| Segment | Count |
|---|---|
| VP of Sales, United States | 37,322 |
| VP of Sales, United Kingdom | 497 |
| CRO / CSO, United States | 6,238 |

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.

| Source | Recommended window |
|---|---|
| firstsales.io | reply decay after 30 days, dead after 60 |
| getboomerang.ai | 30 to 60 days |
| sbl.so | 7 to 45 days |
| launchleads.com | within first 90 days |

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.

#### Where the job-change signal loses value over time

| Stage | Figure | Note |
| --- | --- | --- |
| First 100 days | ~70% | share of the new buyer's budget spent in this period |
| First 90 days | 3 to 5x | how much more a new exec evaluates vendors vs an incumbent |
| After 30 days | decay | reply rates drop measurably from the detected change |
| After 60 days | ~dead | contact is no longer "new" and the signal has decayed |

*The window narrows because budget is front-loaded, not because attention fades.*

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 to first opportunity

1. **Build the watch list** - Export past champions, closed-won buyers, closed-lost evaluators, and product users; tag by relationship type and deduplicate. Done: a tagged, filterable list, about 20 to 60 minutes of work.
2. **Set detection and alerts** - Configure monitoring so a move fires an alert into Slack or the CRM. Done: alert lands within 24 to 72 hours of the change.
3. **Route to the relationship owner** - Send the alert to the rep who owned the original relationship, never a new SDR. Done: the correct rep owns the task.
4. **Qualify the new employer** - Apply firmographic ICP gates as pass/fail, then layer funding, hiring velocity, and tech-stack signals. Done: account tiered, keep-or-drop decided, 15 to 30 minutes.
5. **Send a congrats-only first touch** - On day one of the window, send a short genuine note acknowledging the new role with no ask. Done: warm re-entry sent.
6. **Follow up with value inside the window** - Between days 7 and 45, frame around the mover's new mandate and offer value first. Done: meeting booked or opportunity created.
7. **Log, measure, iterate** - Track this program separately and report reply, meeting, and win rates against cold. Done: proof it converts at 2 to 3x cold.

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.

I ran this search: `Former customers and product champions who changed jobs in the last 90 days and are now VP of Sales or CRO at a US SaaS company.` - [see the full result list](https://www.refolk.ai/s/sbwx9fpc4r).

*Returns named movers with their prior relationship and their new employer, so a rep can qualify and route in one pass.*

## 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.

#### How to score the new employer

1. **Firmographic must-haves** - Industry, size, revenue, location - binary pass or fail gates
2. **Behavioral indicators** - Buying intent and fit signals - weighted scores, not gates
3. **Signal triggers** - Funding, hiring velocity, leadership changes - multipliers on the score

*Gate on firmographics first, then weight behavior, then apply triggers as multipliers.*

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.

> **Rule:** Qualify before you touch
>
> Apply the firmographic gates before the first message. Chasing a warm person at a non-ICP company produces a friendly reply that never becomes pipeline, which is one of the most common ways this play wastes rep time.

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.

**Congrats-only first touch (day 1 of the window)**

```
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]
```

*Swap in the real role and company. Keep it under 60 words. No calendar link, no ask, no deck.*

**Value follow-up (days 7 to 45)**

```
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]
```

*Frame around their new mandate, not your product. Reference the earlier relationship once, briefly.*

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.

| Failure mode | What it looks like | The check |
|---|---|---|
| Wrong-channel routing | A new SDR cold-emails a champion who does not know them | Route the alert to the original relationship owner |
| Day-one send | Emailing during onboarding week, reads as noise | Hold the value touch to week two, when audits start |
| Window missed | Detected the move but reaching out "sometime this week" | Measure days-since-move on every send |
| Stale intent overlay | Layering third-party intent onto the mover | Treat the job change as primary; use intent only to corroborate |
| Account never qualified | Chasing a warm person at a non-ICP company | Apply ICP gates before the first touch |
| CRM blind spot | The list is silently thin, ~78% of moves missing | Enrich against an external source, not CRM alone |
| Single-threading | One champion carries the whole deal | Engage 3+ contacts at the new account |
| Pitch-first message | Leading with a demo request on day 3 | First touch is congrats-only; value comes second |

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.

> **Tip:** Prove the program pays with a separate scoreboard
>
> Track job-change outreach separately from the rest of outbound. It should convert at 2 to 3x cold rates; if it does not, the problem is execution - routing, timing, or qualification - not the signal itself.

## 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.

#### Pre-launch checklist for the job-change play

- [ ] The watch list is tagged by relationship type: champion, closed-won buyer, closed-lost evaluator, product user.
- [ ] The list is enriched against an external source, not the CRM alone, to close the ~78% blind spot.
- [ ] Alerts fire into Slack or the CRM within 24 to 72 hours of a detected move.
- [ ] Each alert routes to the original relationship owner, never a new SDR.
- [ ] The new employer passes firmographic ICP gates before any message is sent.
- [ ] The account is tiered, with a leadership-change or funding signal noted where present.
- [ ] The first touch is congrats-only with no ask, sent inside the window.
- [ ] The value follow-up is queued for days 7 to 45 and framed around the new mandate.
- [ ] At least three contacts at the new account are targeted to avoid single-threading.
- [ ] The program is logged separately so reply, meeting, and win rates can be compared to cold.

## 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.

## Frequently asked questions

### How fast do I need to reach out after a job change?

Move within 30 days of the detected change. Reply rates drop measurably after 30 days and the signal is substantially decayed by 60. Sources disagree on the exact sweet spot, ranging from within 90 days to a tight 7 to 45 day window, but they cluster on a short runway. The reason is a budget calendar, not just inbox fatigue: new buyers spend about 70% of their budget in the first 100 days.

### Should I email on the first day of the new job?

Usually no. Several sources find week two to three outperforms day one because the mover has enough context to have a real conversation but has not yet locked priorities or inherited vendor decisions. A congrats-only note can go early, but a value follow-up during onboarding week reads as noise. Hold the substantive touch until audits start, roughly week two.

### Why not just have an SDR run the outreach?

Because a new SDR cold-emailing a champion who does not know them converts at cold-baseline rates, around 2% response, instead of warm rates. The entire uplift of this play comes from an existing relationship, so the alert must route to the rep who owned the original deal. Routing, not detection, is where the play most often dies.

### Do I still need intent data if I track job changes?

Treat the job change as the primary signal and use intent only as corroboration. A tracked contact's move is a discrete, person-level, verifiable event tied to one named human with budget history. Third-party intent identifies companies not individuals, and 50% of intent-data users report too many false positives. Layering intent onto a mover inflates noise rather than reducing it.

### What if the mover's new company is not a good fit?

Qualify the employer as an account before the first touch, or you will chase a friendly reply that never becomes pipeline. Apply firmographic gates as binary pass/fail, then layer signals like funding and hiring velocity. A leadership change plus aggressive hiring in a function is the strongest predictor of both budget authority and urgency. Drop non-ICP accounts even when the person is warm.

### Why is my CRM not enough to build this list?

On average CRMs miss about 78% of former champions with qualified job changes, and only half of those present ever get engaged. So a CRM-only watch list is silently thin and you will never see most of the moves worth acting on. Enrich against an external source of professional profiles rather than trusting the CRM alone.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/guides/job-change-trigger-playbook*