Skip to Content

Run It Weekly

Outcome: a scheduled tracker costing roughly 40 credits a week per 500 tracked people, producing a digest and a small queue of warm, well-timed leads.

Surface
App
Level
Intermediate
Uses
Scheduled runs · the columns from lessons 02–06
Credits
~40 per week per 500 tracked
Prerequisite
Lessons 02–06

The shape of the weekly run

Detect

Job change and promotion checks across the tracked list. This is the only step that runs on everyone.

Gate on moved

Everything downstream runs only on movers. Typically 2% of the list in a given week.

Qualify

Destination company enrichment on movers only.

Enrich

Contact details on qualified movers only.

Route

Congratulations note, population-specific sequence, or internal introduction.

Report

A digest, whether or not anything moved.

The gate after detection is what makes the economics work: you pay a full check on 500 people and everything after that on ten.


Where the cost actually goes

500 tracked, 10 movers, 6 qualifying.

StepRowsCost eachTotal
Job change + promotion check5001.0500
Qualify destination103.030
Contact enrichment61.38
Copy61.06
~544

Detection is 92% of the cost, which points at the only real lever: the size and quality of the tracked list. Adding a hundred people who will never move to a company you can sell to costs a hundred credits a week forever. Pruning is the optimization here, not provider choice or cadence.

To bring it closer to the 40-credits-a-week figure, tier the cadence: past customers weekly, blocked champions fortnightly, past evaluators monthly. Same coverage, a quarter of the detection spend.


List maintenance

A tracked list needs pruning as much as it needs appending.

Prune:

  • People who moved out of your buying centre entirely
  • People at companies you cannot sell to, who have not moved in a year
  • Rows that never resolve to a profile
  • Anyone who asked not to be contacted — permanently

Append:

  • Every new closed-won contact
  • Every named advocate on a new closed-lost
  • Every completed demo or trial

Automate the append from your CRM. Review the prune quarterly.


The digest

Five lines, weekly, whether or not anything happened.

Champion tracker — week of <date> 7 moved 4 qualified destinations 1 joined an existing customer → routed to <owner> 1 joined a competitor → dropped 3 verified contacts, congratulations notes sent Tracked: 512 · never-resolved: 34 · pruned this week: 6

The “joined an existing customer” line is the one people read. It is also the outcome most likely to produce revenue and least likely to be noticed without a digest.


Guard against silent failure

A scheduled job that stops working looks identical to a quiet week.

  • Alert on zero. If detection returns no changes at all across 500 people, something is wrong — a normal week has some movement.
  • Alert on a spike. Fifty movers in a week means a detection change or a data error, not a hiring boom.
  • Check credit balance covers several weeks, not one. A run that stops mid-way leaves the table in a mixed state.

Do this now

Schedule detection weekly

Early in the week.

Gate everything downstream on moved

Tier the cadence by population

If cost matters.

Automate the append from your CRM

Diarize the quarterly prune

Build the digest

Five lines plus tracked-list health.

Add zero and spike alerts

Check consumption on runs two and four


Check your work

  • Only detection runs on the full list
  • Cadence is tiered by population if cost is a concern
  • New closed-won and closed-lost contacts are appended automatically
  • A digest is delivered weekly, including on quiet weeks
  • Zero-result and spike alerts are configured

Where this breaks

An unpruned tracked list grows forever and its cost grows with it — and because the cost is dominated by detection on people who never move, the growth is pure waste. A list that doubles in two years doubles the weekly bill while producing roughly the same number of leads. Prune quarterly, and treat the tracked count as a number to manage rather than a number to grow.


Course complete

You now have three tracked populations built from data you already owned, weekly job-change and promotion detection, a filter that separates real moves from noise, a qualification gate on the destination company, verified contacts at the new employer, three message shapes, and a scheduled run that reports on itself.

Where to go next:

You wantCourse
More trigger typesSignals & ABM
To keep the underlying records freshCRM Enrichment
To sequence the movers properlyAutomated Outbound
The digest by chat insteadAI for RevOps

Reference for this lesson: check_job_change, CRM integrations, Workspace integrations, Credits.