Set the new standard in revenue orchestration.Start creating playbooks to fast-track your success.
Turn champion job changes into new opportunities.
This template explains a Play that automatically detects when one of your product champions switches to a new company, enriches their fresh contact details and allocates the opportunity to the right sales representative who has previously had a good relationship with that champion.
This workflow monitors your champion contacts and:
Configure the following input variables in the variables node at the beginning of the workflow:
Enrich the champion using Cargo’s LinkedIn Enrich action. The action returns an object that includes the person’s current employer, domain, seniority, etc.
Use a filter to ensure that the output contains a valid company LinkedIn URL, which in some edge cases may be missing. This is important to evaluate whether a champion has changed jobs or not.
Compare the LinkedIn company URLs between what is provided by the LinkedIn node and what was contained in the CRM. If these two values are not the same, it usually means that the champion has started a new role.
If they match: The champion has not changed jobs – the flow proceeds down the No branch and ends by updating the lastCheckDate.
If they differ: The champion moved to a new company and the workflow advances to the prospecting steps below.
Note: Comparing LinkedIn company URLs is a more robust approach than comparing website domains or company names. However, this does assume that this field is properly enriched in your CRM for your champions. If not, consider using an LLM to compare the LinkedIn payload versus the associated company in the CRM for that champion.
Under the Yes branch (new employer detected), Cargo’s waterfall email tool queries a cascade of email providers to find a valid email for the champion’s new company.
The node returns a validated work email that will be attached to the new contact record.
Another Branch node answers the question: Is this champion already owned in the CRM?
If YES:
If NO:
The Allocate node returns ownerSlackID which will be used for internal alerting.
Depending on the branch chosen above:
Finally, update lastCheckDate so the loop will skip this champion in the next cycle.
Best practice note: The consensus among the RevOps community is that it’s better practice to treat a contact with a unique email as net new (even when it represents a pre-existing person). This means that if a champion has moved companies and has a new work email, we will create a new contact for the same person (no, it’s not a duplicate) while tagging the older contact as obsolete. This is helpful for keeping the legacy information attached to the previous contact (amongst deals, transcripts, etc.). See this workshop we held with the GTME community to learn more about the debate around this topic.
Use a Slack – Send message node to notify ownerSlackID that their champion, \{\{vars.firstName \}\} \{\{vars.lastName \}\}, just joined \{\{ nodes.enrichChampion.output.company.name \}\}. Include the LinkedIn profile and a suggested opening line.
Timely action here dramatically improves win-rates.
Schedule the play to run every few weeks against the list of champions in your CRM. Cargo will quietly watch for job moves and surface warm opportunities straight into Slack – letting your team focus on closing, not prospecting.
