Ops

Track champion job changes

This play monitors customer contacts for job changes using Lusha Signals. When a champion moves to a new role or company, the workflow updates your CRM and triggers tailored follow-up actions—such as alerts, tasks, or outreach—so your team can preserve relationships, prevent churn, and open new expansion paths.

The result: no more learning about champion moves too late. Your team stays connected as influence shifts.

Why this works

Customer champions are critical—but they don’t stay put forever. When they move, teams often find out weeks or months later, after momentum is lost or churn risk increases.

This play turns career moves into actionable signals, helping you:

  • Protect existing accounts when champions leave
  • Re-engage champions in their new roles
  • Create warm expansion opportunities at their new companies

What you get

  • Automatic detection of job changes via Lusha Signals
  • CRM updates reflecting new role or company
  • Immediate alerts or tasks for follow-up
  • Tailored outreach triggers for retention or expansion
  • Stronger long-term relationship continuity
Built by: Lusha
Difficulty: Medium
Tools: HubSpot, Lusha, Outreach, Salesforce, Slack, Zapier

How to set it up

01

Connect your apps in Zapier

Ensure active connections for:

  • Lusha: access to contact-level job change signals
  • CRM: Salesforce or HubSpot
  • Slack / Email / Outreach: for alerts and follow-up
02

Define which contacts to track

Focus on:

  • Customer champions
  • Power users
  • Executive sponsors

You can tag these contacts in your CRM and scope the Zap accordingly.

03

Configure Lusha signal detection

Track signals such as:

  • Job change
  • Promotion
  • New company

Optionally filter by:

  • Seniority level
  • Department (IT, RevOps, Finance, Ops, etc.)
04

Update CRM records

Write back:

  • New title
  • New company
  • Job change date
  • Custom “Champion Moved” flag

This preserves historical context.

05

Trigger tailored follow-up

Based on the signal:

  • If champion leaves a customer account:
    • Create a CSM task to secure a new internal champion 
  • If champion joins a new company:
    • Notify sales
    • Trigger a warm outbound or intro sequence
06

Test end-to-end

Simulate a job change and confirm:

  • CRM updates correctly
  • Alerts or tasks fire
  • No action occurs for irrelevant moves

What to do next

  • Create two playbooks: One for retention risk (champion leaves) and one for expansion (champion joins new org).
  • Automate congrats outreach: Trigger personalized “congrats on the new role” messages.
  • Layer company signals: Combine job moves with funding or growth signals for stronger prioritization.
  • Track churn prevention: Measure retention impact when champion moves are handled proactively.
  • Standardize across CS teams: Use the same logic for all strategic customers.

The goal: Champions move. Relationships shouldn’t break when they do. This play ensures your team stays one step ahead—turning job changes into retention protection and expansion opportunities instead of surprises.

No FAQ items available at this time.

Ready to build this?

Get started with Lusha and set up this play in minutes.