── SKILL
champion-move-detection✓ APPROVED

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.

In plain English: “My champion just left. Now what?

Inside: The three detection tripwires, the verification checklist, both risk and opportunity rubrics, the internal flag format, and the door-opener rules.

01 / HOW TO USE

Install it in one line, or paste it in.

1
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.
2
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
Does more connected to a CRM

it reads account status, open deals, and contact roles automatically (Salesforce, HubSpot).

an enrichment tool

Clay, Common Room, or FullEnrich confirms the new company and title without a manual check.

Slack

routes the risk flag to the account owner the moment it is written.

SET IT TO YOUR MOTION

This was built for a B2B SaaS org with a customer book and a staged pipeline. Set these to your stack:

The scoring rubrics care about behavior, not titles. Point ENGAGEMENT depth at real usage and interaction data, whatever that is in your stack.

Set thisWhat it isDefault / Example
ENRICHMENTwho confirms the moveClayCommon RoomFullEnrich
ALERT channelwhere the risk flag landsSlack #churn-risk#deal-alerts
CONTACT ROLEShow you see who is on a dealOpportunityContactRole
ENGAGEMENT depthwhat "knew the product well" meansloginssequences runQBRs attended
BOUNCE tripwirewhere email bounces surfaceyour sequencer's bounce report
STALE_DAYSdays since last engagement before depth decays90 (re-tune to your motion)
TOUCH windowhow fast the door-opener ships after verification5 business days
03 / THE FULL SKILL

Everything the skill does, in full.

── WHAT THIS DOES

Runs the play for one detected job change. When a champion at a customer account or a key contact on an open deal moves companies, this skill verifies the move is real, scores both sides of it, and produces two outputs: an internal risk flag on the account or deal they left, with a named owner, and a door-opener message to the company they joined. Someone who already knows your product just landed somewhere new. That is the warmest first touch you will ever get, and it expires fast.

This is the play, not the system. If you want the standing monitor that watches all your contacts and feeds detections into this play, that is the job-change-watchlist skill, its upstream. And if you want to build a champion inside a live deal, that is champion-plan. This skill starts the moment one move is detected.

── THE METHOD
  1. 1
    Detect the move

    Three tripwires, cheapest first. An email hard bounce from a previously good address is the earliest and cheapest signal, treat every bounce on a key contact as a possible move. Second, an enrichment lookup: run the contact through Clay, Common Room, or FullEnrich and compare current company against your CRM. Third, a manual LinkedIn check on your top contacts on a set cadence, monthly for champions at customer accounts, weekly for key contacts on open deals. If you run the job-change-watchlist skill, detections arrive from there and you skip straight to verification.

  2. 2
    Verify it is real

    A profile update is not a move. Confirm both title AND company changed. A new title at the same company is a promotion, which is a different play entirely (congratulate them, then re-map reporting lines). Require two of three before acting: LinkedIn shows the new company, enrichment confirms it, or the old email bounces. One source alone triggers a check, not the play.

  3. 3
    Score both sides

    Every verified move gets two scores, because every move is two events.

    • Old-account risk score. Higher when: the account is a customer up for renewal inside two quarters, the mover was the only engaged contact, they were the economic buyer or day-to-day power user, and no successor is named. A champion leaving a multi-threaded account with a named successor is LOW. A champion leaving a single-threaded renewal is CRITICAL.
    • New-account opportunity score. Driven by prior engagement depth, not by the new company's firmographics. Did they use the product weekly or just sign the contract? Did they attend QBRs, open your emails, expand the account? Deep behavioral history scores HIGH even if the new company looks like a stretch fit. This weighting is deliberate: when we backtested a win-scoring model against real won and lost deals, the strongest predictor of a win was a behavioral signal at 3.56x lift, against 1.13x for the firmographic fit score. What they did with your product beats where they landed.

    Engagement older than STALE_DAYS decays. A power user from three years ago is a warm lead, not a hot one. Say so in the score.

  4. 4
    Write the two motions

    Motion one, the internal flag. One paragraph in the CRM and the alert channel: who left, what they owned, the risk score with its reasons, and a named owner with a dated next step. "Champion left" with no owner is not a flag, it is a shrug. If the mover was on an open deal, the flag includes a re-map: who inside the account now owns the problem the deal was solving, and which remaining contact can tell you.

    Motion two, the door-opener. A short message to the mover at their new company, sent inside the TOUCH window. Rules: congratulate the move specifically, reference the shared history in one concrete line (a project shipped, a result they drove, a problem they solved with your product), then a soft ask, not a pitch. Never reference how you found out beyond LinkedIn. Never mention the old account's renewal, their old colleagues' status, or anything that reads as surveillance. You are a familiar name saying congratulations, with a door behind it.

── QUALITY GATES
  • No play runs on an unverified move. Two of three sources, or it stays a check.
  • No risk flag ships without a named owner and a dated next step.
  • No opportunity score without the engagement evidence behind it, listed. "They liked us" is not evidence.
  • The door-opener references at most one piece of shared history and zero facts the mover has not made public.
  • A promotion (title change, same company) never triggers this play.
── OUTPUT (EXAMPLE)
EXAMPLE OUTPUT
CHAMPION MOVE · sample data
Mover: Dana Reyes · was VP Ops at Northwind (customer) · now COO at Vertex Labs
Verified: LinkedIn + enrichment agree · old email hard-bounced 07/28

Side          Score      Why
Northwind     RISK HIGH  Renewal in Q4, Dana was 1 of 2 engaged
                         contacts, no successor named
Vertex Labs   OPP HIGH   Dana ran 14 sequences/wk, attended 3 QBRs,
                         drove the seat expansion last year

Motion 1 (internal): Flag Northwind churn-risk HIGH. Owner: account
  CSM. Next step by Fri: call remaining contact, ask who inherits
  Dana's workflows, start successor map.
Motion 2 (door-opener): Congrats note to Dana at Vertex Labs
  referencing the reporting workflow she built. Ship within 5 days.
── EXAMPLE CHAT
EXAMPLE CHAT
You
My champion at Northwind just left. Dana Reyes, she was our power user there. Here's my contact export. [pastes CSV]
CLAUDE
Verified first: LinkedIn shows Dana as COO at Vertex Labs and her Northwind email hard-bounced last week. Two sources agree, this is a real move, not a promotion. Scored both sides on sample thresholds: Northwind RISK HIGH Q4 renewal, Dana was 1 of 2 engaged contacts Vertex Labs OPP HIGH Weekly usage, 3 QBRs, drove last expansion The Northwind flag needs an owner today. Who runs that account now?
You
The CSM is Marcus. Draft both motions.
CLAUDE
Motion one, for Marcus and the #churn-risk channel: Northwind flagged HIGH, Dana owned the reporting workflows and the renewal relationship, next step is a call to the remaining contact by Friday to map her successor. Motion two, the door-opener to Dana at Vertex Labs: a two-line congratulations referencing the reporting workflow she built, with a soft offer to compare notes once she is settled. No mention of Northwind's renewal, nothing she has not posted publicly. One sharpener: connect your enrichment tool so the next move gets confirmed automatically instead of by hand.
04 / GO FURTHER

Where an operator takes this next.

The single play is step one. Here is where an operator takes it once the manual version proves out.

The door-opener window is short. Automate the detection so the play starts on day one, not day forty.

01
Stand up the watchlist

Run the job-change-watchlist skill, or UserGems-style tracking via your enrichment tool, so every key contact is monitored and detections arrive without a manual LinkedIn pass.

02
Wire the tripwires

Connect Clay or Common Room to re-enrich your champion list monthly, and pipe your sequencer's hard bounces on key contacts into the same detection queue.

03
Route flags automatically

Connect Salesforce and Slack so a verified move writes the risk flag to the account record and pings the owner in the same minute.

04
Work the network view

Use LinkedIn Sales Navigator alerts on your top 50 champions so the move surfaces the day it is announced, not the month the email bounces.

05 / PART OF A BIGGER PLAY

One skill is the on-ramp.

── GET NEW SKILLS IN YOUR INBOX

One operator-built skill a week. Free.