Detect when someone who already bought from you turns up somewhere new, and get there before the competition does.
A contact who championed you at their last company is the warmest lead in your database, and almost nobody watches for them. They already know the product, they already chose it once, and at a new company they have budget and a mandate to change something. The whole play is noticing in time.
This is a monthly sweep rather than a real-time pipeline, and it should be. Job changes do not need detecting within a minute; they need detecting within a month and acting on within a week. That makes this one of the cheapest workflows here to run and one of the easiest to justify, because the output is named accounts rather than an improvement in a field.
Do not sweep your whole database. Sweep the contacts attached to closed-won deals, plus anyone with a meaningful activity history who did not buy. Those are the people whose move is worth an alert. Everyone else generates noise and costs credits, and the alert stops being read within a month.
5 steps. The ones in blue are the data layer; everything else is plumbing you already own or can stand up in an afternoon.
A CRM list of contacts on closed-won deals, plus lost deals where the contact was an advocate. Keep it to hundreds rather than thousands: this is a precision play, not a coverage one.
Reverse Contact returns current role and company against the identity you already hold, with a last-updated timestamp on every response so you can tell fresh data from cached.
Company changed, title changed, or both. The comparison is the workflow: the enrichment is only interesting where it disagrees with the record you already have.
A low-confidence answer is not a job change, it is a maybe. Set a threshold, and send anything under it to a review queue rather than to a rep. Reverse Contact lets you raise the precision threshold on the request itself.
A new contact at the new company, linked to the old one so the history is visible, and one Slack message to the account owner naming both. This is the part that turns a data point into pipeline.
This workflow ships as a skill file: the API surface of every tool in the chain, the build order, the limits that break it, and how to check it worked. Point an agent at it and it has what it needs without reading 3 sets of vendor docs first.
--- name: champion-job-change-alerts description: Build a monthly sweep that detects when a past customer contact changes co mpany and turns it into pipeline: re-resolve the champion list, diff against... --- # Champion job-change alerts ## What you are building ## Prerequisites ## The tools, and how to call them → Reverse Contact, HubSpot, Slack, n8n ## Build it → 6 steps ## Gotchas ## What breaks, from the vendors' own docs ## How to verify it works → 5 checks
mkdir -p .claude/skills/champion-job-change-alerts curl -o .claude/skills/champion-job-change-alerts/SKILL.md https://www.reversecontact.com/integrations-hub/skills/champion-job-change.md
For Codex, Cursor, or anything else that reads a file or fetches a URL, hand it https://www.reversecontact.com/integrations-hub/skills/champion-job-change.md directly. It is plain markdown with YAML frontmatter and no tool-specific syntax, so nothing in it depends on which agent is reading it.
3 of the joins in this chain have a full guide behind them, HubSpot and Reverse Contact and HubSpot and Slack among them. The chain crosses 3 of the seven layers a stack splits into, from the CRM layer outward, which is why no single vendor owns it.
Documented by one of the vendors in the chain, and easier to design around than to discover.
All four are documented by a vendor rather than observed by us, which is the useful part: a limit you can read is a limit you can design around before it costs you a week.
What each component bills on, and which line actually scales with your volume.
| Component | Billing | What drives it |
|---|---|---|
| HubSpot | Any tier | A list, a comparison and a record creation. The sweep runs outside HubSpot, so no Data Hub requirement. |
| Reverse Contact | Per credit | One call per champion per month. A 500-person champion list is 500 calls a month, which is the smallest metered line on this site. |
| Orchestration | Free self-hosted | n8n on a monthly cron, or a Clay table with auto-update if a non-engineer owns the segment. |
| Slack | Free plan works | A handful of messages a month by design. |
This is the workflow with the best ratio of cost to outcome on the site, and the reason is the segment. Hundreds of calls a month against a list of people who already bought from you, producing a small number of named, warm accounts.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, with a confidence score your logic can branch on. The free trial takes no card and runs until the 500 credits a new account starts with are spent, which is enough to run this end to end before anyone signs anything.
Free trial, no card required, and 500 credits to start.
It returns current role and company against an identity you already hold, with a last-updated timestamp, and markets change-aware signals for tracking updates across people and companies. The change detection itself is a comparison you run: current answer against what your CRM believes. The workflow is the diff, not the lookup.
Monthly. Profile data reflects a move when it becomes public, which is days to weeks after the fact, so a daily sweep costs twelve times as much to catch the same moves slightly earlier. Weekly is defensible for a small, very high-value champion list.
No. Create a new contact at the new company and link it to the original. The deal history on the old record is the reason this person is worth an alert; edit it away and you have destroyed the asset while capturing the signal.
Send it to a review queue rather than to a rep. Reverse Contact returns null with a confidence score instead of a best guess, and you can raise the precision threshold on the request. One wrong alert costs more credibility than three missed ones cost pipeline.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.