# Champion Job Changes to a Ranked, Timed Warm Queue

*You will assemble a tiered champion list, monitor it for job changes, verify each landing spot, and ship a ranked queue timed to each outreach window.*

- Canonical URL: https://www.refolk.ai/guides/champion-job-changes-warm-queue
- Pillar: Sales and go-to-market
- Format: Playbook
- Published: 2026-10-15
- Last reviewed: 2026-10-15
- Reading time: 17 min
- Keywords: champion tracking, job change alerts for sales, track past customers new job, turn job changes into pipeline, champion job change outreach

## Key takeaways

- Roughly 20% of customers change jobs every year, and 91% of past champions never return on their own even after 90-plus days at the new company, so the ranked queue is the whole game.
- A B2B contact list decays at about 2.1% per month, compounding to roughly 22.5% annually, which means re-verification must be monthly because continuous decay outruns quarterly cleanups.
- Sources disagree on the exact outreach window (2-4 weeks, 14-30 days, or 30-60 days) but all agree day-1 outreach is noise and post-90-day outreach is late.
- In Refolk's index there are 8,830 US VP of Marketing profiles versus 203 in the UK, so thin-market teams must widen tiers down to Director level to keep the queue full.
- Power users and day-to-day admins carry stronger advocacy than the economic buyer who signed, because they can re-spec the product from memory at the new company.
- The widely cited 114% win-rate lift, 54% larger deals, and 12% shorter cycles come from one vendor's 5,000-opportunity study, so measure your own champion-sourced win rate before forecasting on them.

Your best buyers do not stay put. Roughly one in five customers changes jobs each year, and when a past champion lands somewhere inside your ICP, that move is the warmest pipeline you will ever get - if you catch it, verify it, and reach out inside a narrow window. This playbook is for founders selling their own product, account executives, SDR leads, and partnerships teams who want to run champion tracking as an operation, not a scramble. It takes you from list assembly through continuous monitoring to a ranked, timed queue, so you execute the whole thing start to finish without improvising.

Most sales guides stop at scoring a single move or reactivating dead accounts. This one builds the machine: who goes on the list, how you tier them, how you fight data decay, how you verify each landing spot, and how you sequence outreach to the right day. It is tool-agnostic. Where the evidence is thin or vendor-sourced, I say so and tell you what to measure locally.

## Why champion tracking is worth running as a system

Champion tracking is the practice of following your past buyers and advocates across job changes and turning each move into warm pipeline at their new company. It is worth systematizing because the pipeline does not self-activate: even for category leaders, 91% of past champions did not come back on their own, even after 90-plus days at a new job.

That single number reframes the job. Goodwill is real, but it is inert. A champion who loved your product will not email you when they land somewhere new. The queue - the ranked, timed list of moves with a first-touch date on each - is the entire mechanism that converts goodwill into meetings. Without it you are relying on movers to remember you, and the data says they will not.

The economics are strong but almost entirely vendor-sourced. One study of over 5,000 opportunities found that when a past champion was involved, the win rate rose 114%, deal sizes rose 54%, and the sales cycle was 12% shorter. A customer case reported 81% shorter deal cycles and 17% bigger contracts. These come from one vendor's own data science, not a neutral third party. Use them to justify building the system, not to forecast your own numbers until you have measured your own champion-sourced win rate against your cold baseline.

**91% - Past champions who did not return on their own**

> **Note:** Treat uplift stats as directional
>
> The 114% win-rate, 54% deal-size, and 12% cycle figures all trace to one vendor's 5,000-opportunity study. They justify the investment; they are not your forecast. Measure your own champion-sourced win rate against your cold baseline before you put them in a board deck.

## The asset compounds while every record rots

A champion list is an appreciating asset with a leak: every closed deal adds advocates, but the records decay continuously. The canonical B2B contact decay rate is 2.1% per month, which compounds to roughly 22.5% a year. A 10,000-contact list loses between 2,250 and 3,000 valid addresses every 12 months even if you never send a single email.

That decay is not evenly spread across fields, and it is not seasonal. Because it is continuous, quarterly cleanups run permanently behind - by the time you re-verify, the next quarter's worth of records has already gone stale. The planning implication is blunt: re-verify monthly, or accept that a meaningful share of your alerts are firing against dead records.

#### Where a champion record decays

1. **Job title / function** - 65.8% changed within 12 months, the fastest-moving field
2. **Email address** - 23% go bad per year, down from 28% the prior year
3. **Phone number** - 42.9% changed within 12 months
4. **Overall record** - ~22.5% annually canonical, up to 70.3% worst case

*Different fields rot at different speeds, which is why a single annual cleanup never catches up.*

The field-level numbers below come straight from published decay research. Note that title and function change faster than email - which is exactly the signal you want, because a title change is often the job change you are hunting for.

| Field | Annual decay | Source |
|---|---|---|
| Overall contact record | 22.5% canonical, up to 70.3% worst case | industry decay benchmarks |
| Email address | 23% (down from 28% the prior year) | large-scale verification report |
| Job title / function | 65.8% changed within 12 months | field-level decay study |
| Phone number | 42.9% changed within 12 months | field-level decay study |

One champion-base evaluation found about 25% of the database was stale due to frequent job changes among its customers. And stale records are not free: a common data-quality model estimates each stale record costs about $100 to carry downstream. The point is not to panic at the decay rate - it is to build monthly re-verification into the operation from the start, so the asset grows faster than it rots.

> The list appreciates only if you re-verify monthly, because continuous decay beats a quarterly cleanup every time.

## Who goes on the list, and how to tier them

A champion is not anyone with a buying-committee title. It is someone who actively advocated for your solution, influenced the buying decision, or removed internal obstacles. The cleanest way to build the list is to pull from your CRM on objective criteria rather than memory, then tier what you pull.

Pull a contact onto the list if they meet any of these:

- A past buyer on a deal you closed-won.
- A power user who hit your key product engagement threshold.
- A contact with a strong NPS score, or who submitted a review or case study.
- Anyone who expanded a contract or sent a referral.
- Anyone your AEs named as a decisive influence in a win-call debrief.

Then tier. Tier 1 is a buying-committee title match - the economic buyer or decision-maker champion. Tier 2 is power users and day-to-day admins. Tier 3 is other customer contacts. Here is the counterintuitive part worth internalizing: track power users and admins, not just the economic buyer who signed. The person who lived in your product carries the strongest advocacy, because they can re-spec it from memory at the new company and compress the education phase that drives the shorter sales cycle.

Tiering also sets your reach-depth at the new company. Buying committees are large - Gartner puts them at 6 to 10 decision-makers, and Forrester's State of Business Buying counted 13 stakeholders. A multi-threaded deal that also involves a previous champion showed an additional 63% higher win rate and 66% larger deal size in vendor data. So a Tier 1 mover is not just one contact; they are your entry point into a committee you then multi-thread.

> **Watch out:** A title is not advocacy
>
> A buying-committee title on a deal you lost can look like Tier 1 while the person was actually a blocker. Before you tag anyone Tier 1, check the win-call debrief and whether they genuinely influenced the decision. A false champion wastes your best outreach window.

## Detect and verify before anything gets routed

Detection monitors multiple surfaces continuously; verification confirms the landing spot before a single move reaches a rep. These are two separate jobs and skipping the second one is how teams embarrass themselves.

Detection watches LinkedIn signals, CRM contact-field updates, email-signature changes, and company team pages - continuously, not weekly or monthly. Reported detection latency is a median under 24 hours, usually 6 to 14 hours after the change goes live on LinkedIn, though that figure is vendor self-reported. There is a timing subtlety that works in your favor: profile updates often lag the actual start date by weeks, so firing on the start date rather than the profile-update date usually lands your alert right inside the outreach window.

Verification has two parts. First, confirm the new company fits your ICP. Second, confirm the person is actually there. LinkedIn's own workplace verification works by confirming a current company email domain via a code sent to that address. For independent verification, cross-check the official company domain and the company's careers or team page, and look for the on-profile verification badge.

> **Rule:** A verification badge is not current proof
>
> LinkedIn work-email verification confirms employment at the moment of verification, and the badge expires after 365 days. An old badge is a false still-there signal. Re-confirm current employment via a current-domain email or the live team page before you route the move.

Sourcing the list and finding movers who match your ICP is exactly the kind of plain-English query you should not be doing by hand across a dozen tabs. This is where [Refolk](/) removes the friction: describe the people and the move, and get the matches back verified.

I ran this search: `Find VP and Director of Marketing in the US who left a company in the last 90 days and just started a new role at a SaaS company with 200+ employees.` - [see the full result list](https://www.refolk.ai/s/0w9ngckz2y).

*Returns recent movers in those titles with their new company, so you can score them straight into the queue.*

Geography reshapes how deep you have to tier. In Refolk's index there are 8,830 current VP of Marketing profiles in the US against only 203 in the UK - the US pool is about 43.5 times larger. In a thin market the champion pool per senior title is tiny, so you widen tiers downward to keep the queue full. Director of Marketing in the US alone runs to 27,062 profiles, about 3.06 times the VP pool.

| Segment | Current profiles | Derived ratio |
|---|---|---|
| VP of Marketing, US | 8,830 | baseline |
| Director of Marketing, US | 27,062 | 3.06x the VP pool |
| VP of Marketing, UK | 203 | ~43.5x smaller than the US VP pool |

**43.5x - How much larger the US VP-of-Marketing pool is than the UK's**

## The end-to-end procedure

Run these nine steps in order. The whole build from export to live monitoring takes roughly four to five working days; after that the operation runs continuously with a monthly cadence for measurement and re-verification. Ownership is called out per step because this straddles RevOps and the reps.

#### From champion list to timed warm queue

1. **Assemble the champion list** - Export from CRM on objective criteria - closed-won buyers, power users past an engagement threshold, NPS promoters, reviewers, referrers, contract expanders, and win-call-named influencers. Done means a deduped list where every row carries its source deal or account.
2. **Tier each contact** - Tier 1 is a buying-committee title match, Tier 2 is power users and admins, Tier 3 is other customer contacts. Done means every row carries a tier and the account it came from.
3. **Baseline-verify and enrich** - Verify current email, title, and company before monitoring, since ~22.5% annual decay means the export is already partly stale. Done means each record has a verified current state and a last-verified date.
4. **Stand up continuous monitoring** - Watch LinkedIn, CRM contact fields, email-signature changes, and company team pages continuously. Done means alerts route into the account owner's daily tool, not a separate dashboard.
5. **Detect and verify each move** - On a fired signal, confirm the new company against ICP and confirm the person is really there via official domain, careers page, and profile badge. Trigger on start date, not profile-update date. Done means a verified new role, company, and ICP-fit score.
6. **Score into a ranked queue** - Score each verified move by ICP fit, tier, title seniority at the new company, and recency, then sequence by the outreach window. Done means a ranked queue with a target first-touch date per move.
7. **Time the outreach** - Hold until the window, set first touch inside the earliest band and before month 3, and stay ready within 72 hours of signal even if the send is scheduled later. Done means a warm, relationship-led note sent in-window.
8. **Work the vacated seat in parallel** - Treat the old seat as a churn risk and engage the successor on the source account. Done means a defensive play opened for every detected move.
9. **Measure and re-verify monthly** - Track moves detected, signal-to-touch time, meetings, and pipeline, and re-verify stale records monthly. Done means a monthly report and a refreshed list.

## Timing the touch: the window band

Reach out after the congratulations flood dies down but before the new hire has locked their tool decisions - roughly the first few weeks, never day one, and before month 3. Published guidance disagrees on the exact days, so the floor and ceiling matter more than the precise band.

| Source | First-touch window | Too-early penalty | Too-late penalty |
|---|---|---|---|
| Vendor A | 2-4 weeks | day-1 feels presumptuous | after month 3, decisions made |
| Vendor B | 14-30 days | buried in the congrats flood | heads-down on operating priorities |
| Vendor C | 30-60 days | first-week noise | past 90 days feels dormant |
| Vendor D | first 90 days, sooner better | week-1 kills the relationship | budgets commit, advantage cools |

The real clock is the new hire's stack-audit window. In week 1 they are doing HR paperwork and meeting the team. By weeks 2 to 4 they are assessing the stack and identifying gaps - the sweet spot. By months 2 to 3 the opportunity is still live but competitive, and after month 3 the key tool decisions are often made and you are playing catch-up. So sequence to "after the congrats flood, before the budget commit" rather than one fixed day.

Speed matters on a different axis. The operational benchmark is under 72 hours from signal to readiness - that is how fast you should have the move verified, scored, and the note drafted, even if the actual send is scheduled for day 14. Readiness and send timing are separate levers; keep them separate.

#### From list to meeting

| Stage | Figure | Note |
| --- | --- | --- |
| Champion list | 500 | deduped, tiered, baseline-verified |
| Job changes detected | 100 | ~20% move rate per year |
| Warm opportunities | 100 | vendor rule of thumb from 500 champions |
| In-window first touches | 100 | sent inside the earliest band, before month 3 |

*Illustrative volumes showing how a verified champion list narrows to warm meetings over a year.*

**In-window re-engagement note**

```
Subject: Congrats on the new role at {{new company}}

Hi {{first name}},

Saw you've landed at {{new company}} - genuinely pleased for you.

No pitch today. Back at {{old company}} you were the one who {{specific thing they did: pushed the rollout through, re-specced the workflow, championed the renewal}}, and it stuck with me.

If and when you're mapping the stack at {{new company}} and hit the same gap we solved together, I'd be glad to pick up where we left off - on your timeline, not mine.

Either way, good to be back in touch.

{{your name}}
```

*Send inside your earliest window band, never day 1. Swap the product reference and the prior-win detail for your own.*

#### Per-move routing decision

Horizontal axis runs from Weak ICP fit to Strong ICP fit. Vertical axis runs from Late in window to Fresh in window.

| Quadrant | What it means |
| --- | --- |
| Nurture lightly | Keep on list, re-check next move, no urgent touch |
| Reach now | Top of queue, first-touch date set inside the earliest band |
| Pass for now | Park it, requeue only if ICP or title changes |
| Fast-track verify | Verify landing spot immediately, then schedule in-window |

*Score each verified move on ICP fit and how fresh the move is, then route accordingly.*

## How this goes wrong

The failure modes below are where champion tracking quietly produces noise instead of pipeline. Each one has a tell and a check. Give this section the most attention, because a program that fires confident alerts against wrong data is worse than no program.

- **Title match without real advocacy.** A buying-committee title on a lost deal reads as Tier 1, but the person may have been a blocker. The false positive is a "champion" who will not take your call. Check against win-call debriefs and whether they actually influenced the decision before tagging Tier 1.
- **A stale list masquerading as monitored.** If you monitor a list that was already ~22.5% wrong at import, your moves fire against dead records and you never notice. Check with a baseline verification at import and a monthly re-verify, because decay is continuous, not quarterly.
- **Firing on the profile-update date, not the start date.** Profiles lag real start dates by weeks, so a "fresh" alert can already be past the window - or a cosmetic profile edit triggers a false move. Verify the new role via company domain and team page before routing, and anchor your window to the start date.
- **The day-1 send.** Automation blasts the moment the signal fires, the note lands in the congratulations flood, and it reads as predatory. Check that first touch is scheduled inside the window, not at detection.
- **An unverified landing spot.** Routing on an unconfirmed company sends outreach to a role the person never took, or to a lookalike domain. Check the official company domain and the workplace badge, remembering the badge expires at 365 days so an old one is not proof of current employment.
- **Treating vendor uplift stats as universal.** The 114% / 54% / 12% figures are one vendor's 5,000-opportunity study. Applying them to your forecast is a false positive if your ACV or segment differs. Check by measuring your own champion-sourced win rate against your cold baseline.
- **Ignoring the vacated seat.** You work the mover and miss that the source account just lost its advocate and is now exposed to a less loyal successor. Check that every detected move opens a parallel defensive play on the old account.

> **Tip:** Every move is two plays
>
> A detected job change is an offensive play at the new company and a defensive play at the old one. Open both from the same alert. Working only the mover leaves half the value - and a churn risk - on the table.

## Before you call the operation live

Run this checklist once at build time, then re-run the data-quality and routing items each month. It is the difference between a system that compounds and a dashboard nobody trusts.

#### Champion-tracking go-live check

- [ ] Every row on the list came from an objective CRM criterion, not memory.
- [ ] Every row carries a tier (1, 2, or 3) and its source deal or account.
- [ ] The list was baseline-verified at import, with a last-verified date per record.
- [ ] Monitoring watches LinkedIn, CRM fields, signatures, and team pages continuously.
- [ ] Alerts route into the account owner's daily tool, not a separate dashboard.
- [ ] Each fired move is verified against the official domain and a live team page before routing.
- [ ] The outreach window is anchored to the start date, with first touch scheduled in-band and before month 3.
- [ ] Every detected move opens a parallel defensive play on the vacated seat.
- [ ] A monthly re-verification and reporting cadence is scheduled and owned.

## Keeping the queue current

The operation is never "done" - it is a monthly loop. Each month, re-verify the stale slice of the list, because 2.1% per month is leaving even if you do nothing, and report the four numbers that tell you whether the machine works: moves detected, signal-to-touch time, meetings booked, and pipeline created. If signal-to-touch is drifting past 72 hours, your detection or verification step has a bottleneck. If meetings lag detected moves, re-read your window timing and your note.

Widen or tighten tiers by market. In deep title pools you can run Tier 1 alone and still fill the queue; in thin ones - like the UK VP-of-Marketing pool at 203 profiles against 8,830 in the US - drop to Director level to keep volume up. Re-check the window guidance against your own conversion data over time: the published bands are a starting point, but your segment's real stack-audit clock is the figure you should eventually trust. Keep the list growing from every closed deal, keep it verified, and keep the queue timed, and the asset will outrun its own decay.

## Frequently asked questions

### How many warm opportunities should a champion list actually produce?

One widely cited rule of thumb is that 500 past champions generate around 100 warm opportunities per year from job changes alone, built on the base rate that roughly 20% of customers change jobs annually. Treat this as a vendor estimate, not an independent study. It also assumes a verified list rather than a raw export, so your real yield depends on how aggressively you re-verify and how tightly the new companies match your ICP.

### When exactly should I reach out after a champion changes jobs?

Reach out inside the first few weeks but not on day one. Sources cluster around three bands: 2-4 weeks, 14-30 days, and 30-60 days. They all agree day-1 outreach gets buried in the congratulations flood and reads as predatory, while post-90-day outreach is late because tool decisions are often locked. Set first touch inside the earliest band and before month 3, and stay ready to send within 72 hours of the signal.

### How often does my champion list need re-verification?

Monthly. The canonical B2B decay rate is about 2.1% per month, compounding to roughly 22.5% a year, and decay is continuous rather than seasonal. Quarterly cleanups therefore run behind. One champion-base evaluation found about 25% of the database was stale due to frequent job changes, so a baseline verification at import plus a monthly refresh keeps alerts from firing against dead records.

### Is a LinkedIn verification badge proof the person still works there?

No. LinkedIn work-email verification confirms employment at the moment of verification, and the badge expires after 365 days. An old badge is a false still-there signal. Confirm current employment independently by checking the official company domain, the careers or team page, and whether a current-domain email resolves, especially before routing a move into outreach.

### Should I track the economic buyer or the power users?

Track both, but weight power users and day-to-day admins highly. Guidance is explicit that the person who lived in the product carries the strongest advocacy, because they can re-spec your solution from memory at the new company and shorten the education phase. The economic buyer who signed is still Tier 1 when their title matches the buying committee, but a decisive, hands-on advocate often converts faster.

---

*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/champion-job-changes-warm-queue*