── SKILL

job-change-watchlist✓ APPROVED

Never miss a contact's job change again.

A standing watchlist that tracks every champion, user, and past buyer for job changes. Tiered detection, a weekly diff that filters title cleanups, and every real move routed to a named owner with a deadline.

In plain English: “Who changed jobs this month?”

Inside: The tiering scheme, the detection ladder per tier, the weekly diff routine, and the routing rules.

01 / HOW TO USE

Install it in one line, or paste it in.

In Claude Code (one command)

Copy the install line, paste it into your terminal, and restart Claude Code. The skill installs itself to ~/.claude/skills/ and runs automatically when it is relevant.

In Claude, ChatGPT, or a Project (no terminal)

Open the file, then upload it to your chat or paste its contents in. A skill is just a markdown file of instructions, so any capable AI can follow it.

New to skills? A skill is a plain-text file that teaches your AI a workflow. Point any capable assistant at it and it follows the steps, on your data.

02 / MAKE IT YOURS

Connect your context. Set it to your motion.

CONNECT YOUR CONTEXT · AND WHY IT HELPS

a CRM

it builds the watchlist from contact roles, account status, and closed-lost history automatically.

an enrichment tool (Clay, Common Room)

scheduled refreshes catch moves without anyone checking manually.

Slack

routed alerts land in front of the owner the day the move is confirmed.

SET IT TO YOUR MOTION

This was built for a B2B SaaS org with a customer base, open pipeline, and a closed-lost history worth mining. Set these to your book:

The thresholds are yours. A PLG motion might tier on product usage instead of ARR. The system does not change.

Set this	What it is	Default / Example
TIER 1 threshold	who gets the closest watch	Champions at accounts over $25K ARRengaged contacts on open deals
TIER 2 threshold	who gets the standard watch	Active users at customer accountsbuyers on deals closed-lost under 12 months
TIER 3 threshold	who gets the cheap watch	Everyone else with real engagement in the last 18 months
TIER 1 refresh	enrichment cadence for Tier 1	Weekly
TIER 2 refresh	enrichment cadence for Tier 2	Monthly
TIER 3 refresh	enrichment cadence for Tier 3	Quarterlyplus bounce tripwires only
CUSTOMER moves route to	owner of a customer-contact move	The account's CSM2-business-day deadline
DEAL moves route to	owner of an open-deal-contact move	The deal's AEsame-day deadline
ALUMNI moves route to	owner of a past-champion move	Whoever owns new pipeline5-business-day deadline

03 / THE FULL SKILL

Everything the skill does, in full.

── WHAT THIS DOES

Builds and runs the standing system that watches your contacts for job changes. It decides who earns a watchlist slot, assigns each contact a tier, picks the cheapest detection method that works for that tier, and runs a weekly diff against the last known title and company. Every confirmed move gets routed to a named owner with a deadline. A champion who lands somewhere new is the warmest pipeline you will ever get, and this is the system that makes sure you hear about it first. What happens after detection, the outreach play itself, belongs to the champion-move-detection skill, which consumes this watchlist's alerts.

── THE METHOD

1
Build the watchlist
Not every contact earns a slot. A slot costs refresh budget and reviewer attention, so gate on three things: engagement depth (they showed up to calls, replied, used the product), role (champion, active user, economic buyer), and account value (ARR for customers, deal size for pipeline, deal size at loss for closed-lost). Three source pools: champions and users at customer accounts, engaged contacts on open deals, and past champions at closed-lost accounts. Score each contact against the tier thresholds and assign exactly one tier.
2
Choose the detection method per tier
Match the cost of detection to the value of the contact.
- Tier 1: scheduled enrichment refresh (Clay or Common Room) weekly, plus a manual LinkedIn check when a refresh looks off.
- Tier 2: enrichment refresh monthly, plus title-change diffs on every CRM sync.
- Tier 3: email bounce tripwires and quarterly refresh only. A hard bounce on a work email is a free, high-precision move signal. Never pay weekly refresh rates for Tier 3.
3
Run the weekly diff
Once a week, diff current title and company against last known. A real move is a company change, or a title change plus a domain change, or a hard bounce plus a LinkedIn mismatch. A title cleanup is the same person at the same company with a reworded title, "Sr. Manager" becoming "Senior Manager, Demand Gen." Cleanups update the record silently. Only real moves generate alerts.
4
Route every move
Every confirmed move gets an owner and a deadline the day it is confirmed. Customer-contact moves route to the account's CSM, who now has both a retention risk at the old account and a warm door at the new one. Open-deal moves route to the AE, same day, because a deal just lost or gained a thread. Alumni moves route to whoever owns new pipeline. The alert carries the contact, the old and new company, the evidence, the owner, and the deadline. What the owner does next is the champion-move-detection play.

── QUALITY GATES

No move alert without evidence: the source, the old value, the new value, and the date detected.
Title cleanups never generate alerts. Same company plus reworded title updates the record silently.
Every alert has a named owner and a deadline. An unrouted alert is a dropped one.
A bounce alone is a tripwire, not a confirmation. Confirm against a second source before routing.

── OUTPUT (EXAMPLE)

EXAMPLE OUTPUT

JOB-CHANGE WATCHLIST · weekly diff · 214 contacts watched (sample data)
Contact         Was                          Now                       Tier  Route
Dana Reyes      VP Ops, Northwind (cust)     VP Ops, Vertex Labs       1     CSM J. Park, 2 days
Sam Okafor      Dir Eng, Acme (open deal)    Dir Eng, Fabrikam         1     AE M. Cole, today
Lee Tran        Mgr RevOps, Contoso (lost)   Sr Dir RevOps, Globex     2     Pipeline: T. Nash, 5 days
Priya Nair      "Sr. Mgr" -> "Senior Manager", same company            2     Cleanup, no alert

3 moves routed. 1 cleanup absorbed. 2 Tier 3 bounces pending confirmation.

── EXAMPLE CHAT

EXAMPLE CHAT

You

Build me a job-change watchlist from this contact export. [pastes CSV]

CLAUDE

Tiered all 214 contacts. 31 in Tier 1 (champions at accounts over $25K plus engaged contacts on your 9 open deals), 88 in Tier 2, 95 in Tier 3. Detection plan: weekly enrichment refresh on Tier 1, monthly plus CRM title diffs on Tier 2, bounce tripwires only on Tier 3. One gap: 14 Tier 1 contacts have no LinkedIn URL on file, so a refresh cannot verify them. That is the first thing to fix.

You

Who changed jobs this month?

CLAUDE

Two real moves and one cleanup in this month's diffs. Dana Reyes left Northwind, a customer account, for Vertex Labs: routed to the CSM with a 2-day deadline, because Northwind just lost its champion and Vertex Labs just gained one. Sam Okafor moved off your open Acme deal: routed to the AE, same day. Priya Nair's title change at Contoso is a rewording, same company, so the record updated silently with no alert. One sharpener: connect Slack so these route the day they are confirmed instead of waiting for the weekly review.

04 / GO FURTHER

Where an operator takes this next.

The manual weekly diff proves the system. Here is where an operator takes it once it earns its keep.

The watchlist is only as good as its refresh rate. Automate the refresh.

Automate the refresh

Put Tier 1 on a weekly Clay or Common Room enrichment run so title and company updates arrive without anyone checking profiles by hand.

Catch moves between refreshes

Turn on Salesforce field history for contact Title and Email, so any change written by a sync or a rep becomes a diff the same day.

Route alerts where owners live

Post each confirmed move to Slack, tagged to the CSM, AE, or pipeline owner, with the deadline in the message.

Schedule the diff itself

A scheduled Claude task runs the weekly diff every Monday, absorbs the cleanups, and posts only the real moves.

Verify the ambiguous ones

Keep LinkedIn Sales Navigator as the confirmation source when a bounce or a partial refresh needs a human-grade check before routing.

05 / PART OF A BIGGER PLAY

One skill is the on-ramp.

A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.

PART OF THESE PLAYBOOKS

Work the deal signals before the forecast slips

7 skills chained · Sales

PAIRS WITH · DEAL SIGNALS

Turn a champion's job change into two plays.

When a champion or key deal contact changes jobs, one event becomes two motions: a churn or deal risk flag with a named owner, and a door-opener to the company they just joined. Verify the move, score both sides, ship both the same week.

Turn job postings at your accounts into deal moves.

Watches job postings at the accounts already in your pipeline and customer book, and reads each one as a deal signal. Every read ties to a named deal and ends in one dated move, not a cold sequence.

Find the warm intro before you ever go cold.

Sweeps your team's network, customers, past colleagues, and shared investors for every warm path into a target account, scores each one, and picks the single best connector. When no path clears the bar, it says go cold and names the signal to anchor on.

Map the buying committee and widen every live deal.

Maps the committee each deal should have at its stage, scores who is actually engaged, and hands you the widening play for every missing role. Ends with a per-deal move list, not a warning.

── GET NEW SKILLS IN YOUR INBOX