← all systems
OUTBOUNDJOB CHANGE SIGNAL

Champion Reactivation

Champion moves jobs. Claude scores the fit. Hot ones hit sequence.

27 nodes3 workflowsn8n · Pronto · Airtable · Claude▶ watch walkthrough

The Problem

Former champions are your warmest leads — they already know your product and trust you. But tracking hundreds of past champions for job changes manually is impossible. This system does it automatically and routes the right ones into a sales sequence within hours of detection.

Stack

⚙️
n8n
Orchestrates all 3 workflows — scheduling, detection, qualification
🔍
Pronto
Job change monitoring and contact enrichment at new company
📋
Airtable
Champions database — tracks submission status, classification, and sequence state
🧠
Claude
HOT / NURTURE / NOT_NOW scoring with reasoning + first-message draft

Walkthrough

How It Works

The execution path

01Champion Synced
→
02Change Detected
→
03Claude Scores
→
04Sequence Launched
Execution flow
Airtable— champions list
WF1 submits to Pronto— Monday 8am
Pronto monitors in background— 24/7
Pronto detects job change → fires WF2— real-time webhook
WF2 enriches → updates Airtable → fires WF3
WF3 AI scores— Claude classification
HOT → sequence tool + Airtable update
Claude replaces rule-based scoring entirely. Instead of manually defining ICP criteria in code, Claude evaluates new company fit, persona match, and expansion potential in natural language — and returns HOT, NURTURE, or NOT_NOW with a reasoning string.
WF1 — Sync Champions (Monday 8:00am)

Runs once a week. Pulls every untracked champion from Airtable and registers them with Pronto's job-change monitoring API. Marks each one tracked = TRUE so they're never re-submitted.

  • ·Pull champions where tracked = FALSE from Airtable
  • ·Check Pronto API credit balance
  • ·Submit full list to Pronto /intents/leads/track_job_changes
  • ·Mark all submitted contacts tracked = TRUE in Airtable
  • → Pronto now watches these contacts 24/7
WF2 — Job Change Detected (webhook)

Pronto fires this webhook the moment it detects a job change — not in batch, not on a schedule. Real-time. WF2 validates, enriches, and hands off to WF3.

  • ·Validate: new company ≠ old company, not empty
  • ·Enrich new company via Pronto: headcount, industry, HQ, tech stack
  • ·Enrich contact at new role: updated email, updated title
  • ·Merge into single enriched record
  • ·Update Airtable: new company, new title, all enrichment data
  • ·Trigger WF3 via Execute Workflow — pass full package
WF3 — Qualify & Activate (called by WF2)

Claude receives the full enriched record and returns a classification. A Switch node routes each outcome independently — HOT leads launch into sequence automatically.

  • ·Receive: name, old company, new company, title, headcount, industry, HQ, tech stack
  • ·Claude returns: HOT / NURTURE / NOT_NOW + reasoning + first message draft
  • ·HOT → update Airtable + launch into sales sequence + sequence_sent = TRUE
  • ·NURTURE → update Airtable classification for future follow-up
  • ·NOT_NOW → update Airtable, no action taken

Key Design Decisions

🎯
Signal-First, Not Spray-and-Pray
Only reaches out when a genuine buying trigger fires. Not every job change — only ICP matches that Claude classifies as HOT.
🧠
HOT / NURTURE / NOT_NOW
Claude replaces rule-based scoring entirely. Evaluates ICP fit, persona, and expansion potential in natural language.
🔀
3-Workflow Decomposition
Scheduling, signal detection, and AI qualification are each independently deployable and debuggable.
⚡
Real-Time Detection
Pronto fires the webhook the moment a change is detected. Hours, not days.

By The Numbers

27
Nodes
3
Workflows
0
Rule-based scoring
3
Outcomes · HOT · NURTURE · NOT_NOW
← back to all systemsmatthew batterson · gtm engineer