Signal-based outbound
Trigger outreach off buying signals that mark an account entering a buying window, instead of blasting a static ICP list.
Volume outbound is dead. The replacement is signal-based outbound: wait for a real reason to reach out, then let the system fire. The hard part is not the automation, it is knowing which signals predict a conversation.
Signal types worth wiring up
- Job changes — a champion who used your product lands somewhere new
- Hiring / job posts — a public admission of a problem they are trying to solve
- Funding — new budget, new mandates, urgency to deploy
- Technographic installs — they adopted a tool yours complements or replaces
- Website de-anonymization — a known-account visitor showing intent
- Product usage — for PLG motions, the strongest signal there is
Freshness is everything
A signal is only valuable inside its buying window. Latency between the event and the outreach is the difference between relevance and noise. Build for speed: detect, enrich, draft, send, within hours, not weeks.
Signal-to-play mapping
Each signal should map to a specific motion. A funding round is a different play than a competitor install. Aggregate signals into one prioritized queue, then branch by type. Every signal you add should survive one question: does it imply a problem I can solve, right now?
Keep reading
All guides →Enrichment waterfalls
Chain data providers in sequence so a miss from one becomes a hit from the next, maximizing coverage while paying mostly on verified data.
BuildAI & agentic workflows
Use LLMs as per-row functions and research agents inside GTM workflows: classification, extraction, qualification, and first-draft personalization at list scale.
BuildAPI & webhook integration
Connect systems programmatically through REST APIs, webhooks, and MCP so custom pipelines push and pull data outside pre-built connectors.