Why a guide per signal.
"Use buyer signals" is universal advice; it's also useless without specifics. Each signal has its own source list, decay window, false-positive rate, and best-fit trigger message. A funding-round signal you act on in week 7 is dead. A job-change signal where the role doesn't actually own budget is noise. The guides exist to keep you out of these traps.
The 6 signals in the library.
- Funding — how to filter by stage, geo, and round size; why Series A > Series B for new-vendor adoption.
- Hiring — which job-title patterns predict which buying motions; how to scrape ethically.
- Job change — the highest-converting signal in B2B; why champions-who-moved is a 90-day window.
- Website visitor — RB2B / Clearbit reveal; the real conversion math behind anonymous visitor outreach.
- Competitor churn — G2 review polarity, support-thread complaints, public migration posts.
- Product usage — your own free tier, GitHub stars, doc pageviews; PLG-to-sales handoff scoring.
What each guide includes.
A standard structure: what the signal is, where to detect it, what it predicts, the false-positive rate, the trigger message that converts, expected reply rate, and the guide's example workflow. A reader should be able to wire one signal into Clay in an afternoon.
How this connects.
The signals here power WF-01 Signal-based Outbound. They also feed the Signal Agent in the agent stack — same signal, two delivery surfaces.