The problem this solves
Champions leave. The person who bought your product moves to a new company, and the account that depended on them goes quiet without anyone noticing until the renewal conversation reaches a stranger. Meanwhile the champion has a new job, a new budget and a proven reason to buy again, and nobody calls them because the CRM still lists them at the old company.
Both halves of that story are enrichment problems. Checking every contact at won accounts for a change of employer keeps the account record honest; finding the replacement keeps the account covered; and marking the mover's new company opens a warm expansion opportunity. Done every quarter by hand it is a spreadsheet nobody finishes; done as a mission it is a report the customer success and sales teams both read.
How the mission runs
- Select contacts at closed-won accounts. The Enrichment Agent reads HubSpot for companies with closed-won deals and the contacts associated with them, prioritizing decision-makers and champions where the role is recorded.
- Check each contact for a job change. People data is checked for each contact's current employer and title. Where the employer changed in the last 90 days, the contact is marked as a mover with the new company, new title and the date the change was detected.
- Find and verify the replacement. For each mover, people search finds the person now holding the equivalent role at the original account, and the email finder plus verification produce a deliverable address. Where no direct replacement exists yet, the next most relevant stakeholder is proposed.
- Update HubSpot with both records. The mover's record is updated with the new employer and a note, the replacement is added as a contact on the account with a note explaining the change, and the batch is reviewed before it is written.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
HubSpot updated at every closed-won account where a contact changed jobs in the last 90 days: the mover marked with their new company and title, the replacement added as a verified contact with a note explaining why, and a report listing every change for customer success and sales. Movers who landed at companies that fit your ICP are highlighted as expansion leads.
Make it yours
- Run it across open deals as well, where a champion's departure is even more urgent.
- Create a separate list of movers at ICP-fit companies and hand it to the personalization playbooks for a warm first touch.
- Point it at Pipedrive, Attio or Zoho CRM instead of HubSpot.
- Limit the check to contacts with a champion or decision-maker role recorded in HubSpot to keep the run focused.
Frequently asked questions
How does the agent detect a job change?
By comparing the contact's current employer and title in people data with the company on the HubSpot record. Changes carry the date detected so you can judge how fresh they are.
Is the mover deleted from the account?
No. The record is kept and marked, since the history matters, and the new employer is recorded on it.
Can this run on a schedule?
Yes. Quarterly is common; monthly for accounts with many contacts. Each run reports only new changes.
Can it also assess the mover's new company?
Yes. Each mover's new employer is enriched and scored against your ICP, and movers at high-fit companies are listed first in the report as expansion leads, with a verified address at the new company where one exists.
How far back does it look?
Ninety days by default, which keeps the changes fresh; ask for a longer window on the first run to catch older moves.