Why Job Changes Are Your Highest-Converting Signal
Outcome: a counted champion population split into three lists, and a decision on your tracking window and cadence before you spend a credit on detection.
- Surface
- App and MCP server
- Level
- Intermediate
- Uses
check_credits- Credits
- 0
- Prerequisite
- Access to your CRM's closed-won and closed-lost history
Four mechanisms, not one
“Warm intro” undersells what is actually happening. A move stacks four independent advantages, which is why it outperforms every other trigger.
The relationship survives the company
Trust attaches to people. Your champion’s opinion of your product moved with them; their old employer’s procurement process did not.
The blocker is gone
Most losses are not product losses. They are budget-cycle losses, incumbent-contract losses, or a competing priority. A champion who lost that argument arrives at a company where the argument has not happened yet.
New hires get a mandate
People are hired to change something, and the first two quarters are when they are expected to. Tooling decisions cluster in that window because it is the one time nobody is defending the status quo.
They know the evaluation already
The single most expensive part of a deal is teaching someone what category you are in and why it matters. A returning champion skips it entirely.
No cold signal does all four. Funding tells you there is money; hiring tells you there is a project. Neither tells you there is someone inside who already wants this.
The window
Conversion is not flat across time since the move. It has a shape, and the shape dictates your run cadence.
| Time since move | What is happening | Your move |
|---|---|---|
| Week 0–2 | Onboarding, no authority, no budget yet | Congratulate only. Do not pitch. |
| Week 3–12 | Auditing the stack, forming the plan, spending the mandate | The window. This is where the course aims. |
| Month 4–9 | Plan is set, budget is committed | Still workable, longer cycle |
| Month 10+ | Effectively a normal cold account with a friendly contact | Nurture, not sequence |
Two consequences:
- Weekly detection is the point. A monthly run means a champion is on average two weeks into a twelve-week window before you know, and quarterly detection means you mostly find people in month four.
- Speed beats polish. A plain, correct message in week four beats a beautifully researched one in month five.
Week 0–2 still matters — it is when a congratulations note is genuinely welcome and costs you nothing. Send it, do not attach anything to it, and let lesson 06’s sequence pick up in week three. The people who reply to the note are your warmest subset.
Three populations
Track all three, message them differently. Lesson 02 builds each from data you already own.
| Population | Where it comes from | Why they convert | Relative volume |
|---|---|---|---|
| Past customers | Closed-won accounts, product users | Know the product works, know the ROI story | Smallest |
| Past champions who lost | Closed-lost, with a named advocate | Wanted it, were blocked by something company-specific | Medium |
| Past evaluators | Demo attendees, trial signups, active opps that stalled | Understand the category, no education cost | Largest |
The mistake is tracking only the first. Past customers are the highest-converting list and usually the smallest — for most teams the lost-champion list is several times larger and converts well enough to be worth the same weekly run.
Do this now
Before building anything, count what you already have. The size of this population decides whether this is a weekly automated pipeline or a monthly manual review.
- Export closed-won contacts from the last 3 years. Names, emails, companies, close dates.
- Export closed-lost opportunities from the same period, and identify the individual who advocated internally — one name per opp, not the whole contact list.
- Export demo attendees and trial signups who never became opportunities.
- Deduplicate across all three. Someone can appear in two.
- Count the total, and count how many are still at the company where you met them. That second number is your trackable population.
- Run
check_creditsand note the balance — lesson 03 costs roughly one credit per person checked, so the count you just took is your weekly run cost.
If step 5 gives you fewer than about 100 trackable people, run detection monthly rather than weekly and skip the scheduling work in lesson 07. The pipeline is real at that size but the automation overhead is not worth it yet. Come back when the number grows.
What counts as a move
Not every title change is a move, and paying to sequence the ones that are not will erode trust with exactly the people you least want to annoy.
| Change | Is it a trigger? |
|---|---|
| New company, comparable or senior role | Yes — the core case |
| New company, junior role or a career pivot out of your buying centre | No — relationship intact, authority gone |
| Same company, promotion into buying authority | Yes — lesson 04’s trigger |
| Same company, title normalization (“Manager” → “Sr. Manager”) | No |
| Contract, advisor or interim role | Usually no — no budget authority |
Lesson 03 covers the detection mechanics; the filter above is what you apply to its output.
Check your work
- You have three deduplicated lists with real counts, not estimates
- You know how many of those people are still at the company where you met them
- You have a run cadence chosen against your population size
- You can state what you will not treat as a move
Where this breaks
The failure that costs you the relationship is treating the move as a sales trigger rather than a personal one. A champion who gets a templated “I saw you joined Acme — 15 minutes to discuss our platform?” in their first week learns that you were monitoring them, and the warmest lead in your database becomes a cold one permanently. The sequence in lesson 06 opens on the person and their new role, and mentions the product only after they respond.
Further automation
Once the three lists exist, the highest-value addition is not more detection — it is writing the result back. A champion_moved flag on the CRM contact, with the old company and the new one, means account owners see the context without needing the pipeline explained to them. CRM integrations covers the write path; lesson 07 wires it into the weekly run.
Next lesson
02 — Build the champion list, turning the three exports into one table with the profile URLs that lesson 03’s detection needs.
Reference for this lesson: Job change, Recently promoted, Past role, CRM integrations.