Timing, not the message, is where outbound usually fails
Most outbound fails not because the message is wrong, but because the timing is. A perfectly written email sent to someone who has no reason to care right now gets the same result as a bad one: nothing.
Signal-based GTM flips the model. Instead of blasting a static list on a schedule, you reach out when something happened that makes the conversation actually relevant — a real event, not a spreadsheet's turn to be contacted.
What counts as a signal
Funding rounds. Hiring sprees. Tech stack changes. Website visits. LinkedIn activity. Anything that indicates a company is actively moving on the problem you solve, rather than sitting in a database matching your ICP filters in theory.
We've gone deep on the specific signal types and why they matter in What Is Signal-Based Selling? — worth reading if you want the full breakdown. The part that matters here is what happens next, because a signal by itself doesn't do anything.
From signal to conversation
A signal is only useful if it reaches the right person with the right context, fast enough to still matter. That's a harder problem than it sounds, and it's really four separate steps happening in sequence:
- Track. Something has to actually catch the event as it happens — a job change, a hiring post, a LinkedIn interaction — rather than surface it days later once the moment's passed. Most buying signals lose their urgency within 7 to 14 days, so the tracking step is where speed either gets built in or doesn't.
- Score. Not every signal on every account is worth acting on. A job change at a company with no budget for your category isn't the same opportunity as a job change paired with a funding round at a company that's hired three people in your buyer's function this quarter. Scoring is what separates "technically a signal" from "worth someone's time today."
- Route. The signal has to land in front of the right person — the rep who owns that account, or the one whose territory it falls into — without someone manually checking a dashboard for it. A signal that surfaces correctly but sits unseen for three days has mostly lost its value by the time anyone sees it.
- Write. The first line of outreach should reference the actual thing that happened, not a generic opener bolted onto a template. "Saw you just opened a VP of Sales role" is a different message than "Hope this finds you well" — same effort to send, very different odds of a reply. :::tip The hard part was never having the idea to "act on signals." It's building the plumbing that makes tracking, scoring, routing, and writing happen automatically and fast enough that the signal is still worth anything by the time someone acts on it. :::
FAQ
:::expand[Do all four steps need to be automated to see results?] No — even doing this manually with two or three signal types beats not doing it at all. But the value decays with delay, so the more of this that happens without a human needing to check a dashboard, the more signals actually get acted on before they go stale. :::
:::expand[What happens if a signal is scored but nobody acts on it in time?] It's effectively wasted. This is why routing and speed matter as much as detection — a correctly identified signal that reaches the wrong inbox, or reaches the right one three days late, produces close to the same result as never having caught it. :::
Signalist automates all four steps — tracking, scoring, routing, and drafting the first line — so the gap between "something happened" and "someone reached out" is measured in hours, not days. See how it works