Job Change Play

What it does

When a customer's champion changes jobs, Job Change Play writes the two plays you run at once: protect the account they left, and open the door at the company they just joined. On the account they left, it tells you to find whoever inherited their responsibilities and reach out within 5 days with a usage summary and account history, not a pitch, just help during the handover. On the company they just joined, it tells you to wait until day 14 to 21, deliberately not day 1, because the first two weeks are onboarding chaos and nobody is evaluating new tools yet. It writes a real 7-day, 3-touch sequence (email, LinkedIn message, value-add email) and a CRM hygiene checklist so both the old and new records get updated correctly.

It doesn't watch LinkedIn, your CRM, or Sales Navigator for you. You supply the job-change signal yourself, and it tells you exactly what to do once you know.

Who it is for

This is for anyone running sales or customer success who has ever lost a renewal because the person who championed the deal quietly left, and nobody on the vendor side noticed until it was too late. It replaces the job of remembering to do two things at once when a job change happens: protect what you already have, and go after what just opened up.

What it is and what it runs in

• It's a skill. Think of it as a playbook Claude follows. There's no app to download.
• It runs in Claude Code. It also works in Codex, Cursor and other tools that support skills.
• It's free. No API keys, no signups, no paid accounts.

Before you start

• Claude Code installed (or another agentic tool that supports skills).
• git installed. On a Mac, if it's missing, your computer offers a one-click install the first time Step 1 runs.
• A job change signal already in hand: this agent doesn't detect changes itself, you need to already know a champion moved (LinkedIn, your CRM's job-change alert, Sales Navigator, or similar).

Install

Open Claude Code (or your agentic tool) and run these two steps.

Step 1: Download the skills library

git clone https://github.com/LeadMagic/gtm-skills.git

Step 2: Copy Job Change Play into Claude Code

mkdir -p .claude/skills
cp -r gtm-skills/skills/sales-plays/job-change-play .claude/skills/job-change-play

Run it

Give Claude the situation, for example:

Our champion at Brightwell Logistics, Jordan Ellis (VP of
RevOps), just left. LinkedIn shows Jordan started a new role
last week as VP of RevOps at Northgate Freight Corp, which
isn't a customer yet. Build the job change play: protect
Brightwell and open the door at Northgate.

You get back something like:

Track 1, Brightwell (old company): identify who inherited
Jordan's role, reach out within 5 days with a usage summary
and account history. No pitch.

Track 2, Northgate (new company): wait until Day 14-21, not
Day 1. Draft email bridges Jordan's result at Brightwell to a
likely problem at Northgate.

7-day sequence: Day 1 email, Day 3 LinkedIn message, Day 7
value-add email, Day 14+ falls back to standard nurture.

CRM hygiene: update Jordan's record, create a new opportunity
at Northgate, flag Brightwell for champion-replacement
follow-up.

Troubleshooting

Claude doesn't seem to use the skill. Make sure you opened Claude Code in the same folder you ran the install steps in. You can also call it directly by typing /job-change-play.

The output feels generic instead of specific to your accounts. Give it the actual names, account value, and renewal date, the way the sample above does. The skill fills in real specifics when you give it real specifics.

You don't actually know about the job change yet. This skill doesn't detect job changes on its own, you need a signal first, from LinkedIn, a CRM alert, or Sales Navigator, then hand that to the skill.

Credit

Built by LeadMagic (https://github.com/LeadMagic/gtm-skills), MIT license, 53 stars. Free and open source.