Check Job Change
/check-job-changeCheck any LinkedIn profile for a recent job change and get back the new company and new title, at 2 credits per person.
Overview
Check Job Change is a SyncGTM MCP tool that takes one LinkedIn profile URL and returns whether that person recently moved companies, along with their new company and new title. It answers a single question, so it is cheaper to read and act on than a full profile enrich. Use it to catch a new hire inside their first 90 days, and to find the dead contact records and churn-risk accounts sitting in your CRM.
What it does
- 1
Takes one input: `profile_url`. A full LinkedIn URL or a bare username both work.
- 2
Checks one profile per call. There is no batch parameter, so a 60-person CRM sweep is 60 calls.
- 3
Returns four fields: `profile_url`, `job_change` (true or false), `new_company` and `new_title`. `new_company` comes back as a company name like "Ramp", not a domain.
- 4
Does not return an email or a phone number. Chain `find_work_email` for the address at the new company.
- 5
Does not detect internal promotions. Someone who moved up at the same company reads as no change, so use `check_promotions` for that signal.
- 6
Costs 2 credits per check, flat. Run `check_credits` (free) before sweeping a large list.
How to use it
- 1
Download the skill file — it saves as check-job-change.zip.
- 2
In Claude, open Settings → Capabilities → Skills and upload the .zip (or unzip the check-job-change/ folder into .claude/skills/ for Claude Code).
- 3
Connect the SyncGTM MCP server using the setup guide for your client. Browser sign-in, no API key.
- 4
Run /check-job-change and paste in a single LinkedIn URL, or the LinkedIn column from a CRM export. The skill deduplicates the list and prices the run before it spends anything.
- 5
Set the batch cap. Ask for "movers only, stop after 50, report credits used" — at 2 credits per profile, the cap is the one setting that controls spend.
Use cases
New-hire buying window
Catch a prospect in their first 90 days at a new company, while they are rebuilding the stack and replacing tools they inherited. That window closes fast.
Champion churn alerts
Sweep closed-won contacts to find which champions left. The account is now a renewal risk and the contact record in your CRM is dead.
Warm re-entry lists
A champion who moved to a new company is the warmest opener you will get at that company. Build a re-entry list from the movers.
List hygiene before a campaign
Run it over dormant leads before a re-engagement send, so marketing stops mailing addresses that died when the person moved.
GTM workflow examples
Monday champion sweep on closed-won accounts
- 1Call `check_credits` (free) to confirm the balance covers the run. 80 deduplicated champion URLs at 2 credits each is 160 credits.
- 2Call `check_job_change` on each of the 80 URLs and keep only the rows where `job_change` is true, with `new_company` and `new_title`.
- 3Call `find_work_email` (1 credit) with each mover's profile URL as `linkedin_url` to get the address at the new company. The CRM email at the old company is dead.
- 4Call `verify_email` (0.3 credits) on each new address so the re-entry sequence does not bounce on send.
- 5Resolve each mover's `new_company` name to a website domain — the tool returns a name, not a domain — then call `enrich_organization` (2 credits) on that domain for industry, size and funding, and split movers into worth-working and ignore.
Outcome: Two lists by lunchtime: churn-risk accounts where the champion left, handed to CS, and warm re-entry accounts with a verified work email and a fit score on the mover's new company.
Pre-forecast pipeline hygiene
- 1Call `check_job_change` on the champion and the economic buyer for every deal in commit and best case, capped at 40 profiles for 80 credits.
- 2Call `check_promotions` (2 credits) on the profiles that came back false, to catch the ones who moved up internally and now own a bigger budget.
- 3Call `find_people_within_company` (1.5 credits) with the `domain` of every deal that lost a champion, and a `job_title` array for the same function, to name the replacement.
- 4Call `find_work_email` (1 credit) on each named replacement so the AE has a live contact before the forecast call.
Outcome: A forecast note that flags exactly which deals lost their champion, each with a named replacement and a verified email, instead of a slipped deal nobody saw coming.
Reactivating dormant inbound leads
- 1Call `check_job_change` on the 60 highest-scoring leads that went dark 12 months ago, capped at 60 profiles for 120 credits, returning movers only.
- 2Resolve each mover's `new_company` to a website domain, call `enrich_organization` (2 credits) on it, and drop anyone whose new employer falls outside ICP on size or industry.
- 3Call `linkedin_profile_posts` (0.3 credits) on the surviving movers to pull a recent post to reference in the first line.
- 4Call `find_work_email` (1 credit) to get the new work address for each mover that cleared the ICP filter.
Outcome: A reactivation segment of movers who now sit at ICP-fit companies, each row carrying a new work email, new title and one recent post to open with.
Prompts
Paste any of these into Claude once the skill is installed and the SyncGTM MCP is connected.
Has linkedin.com/in/janedoe changed jobs recently? Use check_job_change and tell me the new company and new title.Here are 50 LinkedIn URLs from our closed-won accounts. Deduplicate them, run check_job_change on up to 50 profiles, and return only the people who moved with their new company and new title. Report credits used.Check these 25 dormant marketing leads for a job change. Cap the run at 25 profiles, and for every mover pull their new work email with find_work_email.Run check_job_change on the 30 champion LinkedIn URLs in this CSV, limit 30 profiles. Flag the old account as churn risk for anyone who moved, then look up each new company's website domain and enrich that domain with enrich_organization.Check whether linkedin.com/in/janedoe changed jobs. If check_job_change comes back false, run check_promotions on the same profile before concluding nothing happened.Best practices
Say "changed jobs", not "got a new role". The vague phrasing can route your client to `check_promotions`, a different signal at the same 2 credits.
Deduplicate before every run. CRM exports repeat the same champion across accounts, and each duplicate is another 2 credits for an answer you already have.
Ask for movers only. "Return only the people who moved" cuts a 60-row report down to the rows you will actually work, instead of a wall of false.
Treat a false as "nothing detected", not proof they are still in the seat. The signal depends on the person updating their own LinkedIn, and plenty of people update months late.
Re-check monthly, not weekly. Job changes are slow-moving, so re-running the same list every week doubles your spend for almost no new signal.
Watching a company rather than a named person? `newly_hired_executives` bills 0.5 credits per profile returned and is far cheaper than checking each employee one by one.