What it does
Detects when a decision-maker at a customer account changes jobs, then branches into two plays - re-establishing at the old account with a replacement contact and an AE task, or pursuing the person at their new account as a warm-intro opportunity.
You get
a two-sided play triggered automatically on a champion's job change
How it works
Build the Job-Change Workflow
Create WorkflowCreate a workflow 'Job-change detection and dual response' triggered when a contact at an existing customer/deal account changes employer (detected via scheduled enrichment refresh OR signal provider webhook). Branches into two parallel plays: protect the old account, pursue the new account.
Daily Enrichment Refresh for Key Contacts
configure_workflow_wait_until_stepConfigure scheduled trigger: every Monday morning, scan all contacts marked as 'champion' or 'economic buyer' on active deals + customer accounts. The job-change-detection cadence is the key infrastructure for this workflow.
Refresh Contact Enrichment
configure_enrich_stepConfigure enrich step that refreshes employment data for tracked contacts. Most providers (Clearbit, Apollo, LinkedIn-feeds) flag when an email-domain → company mapping changes — that's the signal. Output: list of contacts whose company changed since last refresh.
Branch by Account Relationship
configure_workflow_branch_stepBranch: was the contact at a CUSTOMER account, OPEN-DEAL account, or PROSPECT account? Each gets different downstream treatment. Customer → champion-departure rescue. Open-deal → urgent multi-threading. Prospect → warm-follow at new company.
Old-Account: Find Replacement Contact
configure_ai_research_stepAI research step on the customer/deal branch: scrape the old company's leadership page + LinkedIn-via-public-search to identify likely replacement decision-makers in similar roles. Outputs 2-3 candidate names with titles and inferred contact info. Saves AE the manual hunt.
Old-Account: Create CSM/AE Task
configure_create_task_stepCreate urgent task for the assigned CSM (customer) or AE (open deal): 'Your champion [Name] just left for [New Company]. Replacement candidates identified: [list]. Suggested action: warm intro through [Departed champion] if relationship is good, else cold outreach to replacement.' SLA: contact within 5 business days — champion-gone deals stall fast.
New-Account: Match or Create
configure_find_records_stepFind-records step on the departed-to-new-company branch: is the new company already in our CRM? If yes — link the contact, surface the relationship to the assigned AE. If no — create new Account + contact record with 'warm signal: ex-customer champion now here' flag.
New-Account: Create SDR Task
configure_create_task_stepCreate SDR task for the new-company outreach: 'Warm signal — [Champion name] (your ally at [Old company]) just joined [New company]. Suggested outreach: congratulate the move, ask if they could use the same approach at their new role.' Priority: HIGH (warm signals decay; reach out within 30 days of job change).
Validate and Publish
publish_workflowValidate and publish. Monitor: job-change detection volume per quarter, old-account-save rate (champion-departure deals that DIDN'T stall), new-account-conversion rate (departed-champion pursuits that became meetings). These are some of the highest-quality signals in B2B.
Ready to run this recipe?
Tell Blu what you need. It builds the segment, content, journey, and dashboard in minutes.
Sign up free