Signals
One Clay hub. Champion switches first
Six monitors dump into one table. Score the trigger. Write copy for that trigger. Champion moves go first; the rest only fills volume.
The loop
- 01Wire six monitors into one Clay hubChampion switches, job postings, website visitors, LinkedIn engagers, role switchers, new followers. One table, not six lists.
- 02Score ICP fit × trigger valueA former-customer VP move is not a post like. Rank the row before anyone writes.
- 03Generate AI context per trigger typeHiring copy ≠ congrats copy. The trigger decides the angle.
- 04Launch lemlist with a sequence per triggerSeparate sequences. Do not mash every signal into one cadence.
- 05Gate the sendNo send without score + trigger-specific copy. Champion switches first; other triggers only fill volume.
Most signal stacks run each source as its own list. Ruben’s constraint is the hub: every monitor lands in one Clay table so scoring and copy stay comparable.
Champion switches carry the pipeline. The other five monitors exist to keep volume up after the high-value rows are queued.
