‘Real time’ is a poor default for every buying signal. A pricing-page revisit may be useful for hours, a leadership appointment for weeks, and a regulatory deadline for months. Speed to signal helps when the response window matches the event and the offer.
Why signals decay
A trigger loses value as the buyer moves on, other vendors arrive, or the event stops explaining the current priority. Freshness deserves more than a date filter. It affects the chance that a decision is still active and whether the event still belongs in the message.
A practical window by signal class
- Hours to two days: high-intent first-party activity, direct product comparisons, public requests for recommendations, and urgent service incidents.
- Two to seven days: product launches, material technology changes, funding filings, and concentrated hiring bursts.
- One to four weeks: executive appointments, market expansion, partnership launches, and organisational redesign.
- One to six months: regulatory deadlines, office openings, large transformation programmes, and contract-renewal windows learned directly from the buyer.
Create signal service levels
A service level should define more than ‘contact within 24 hours.’ It should specify how quickly the event is reviewed, what evidence is mandatory, who owns the decision, and what happens when the window expires. This prevents speed from becoming an excuse to lower standards.
- 1Assign each signal type a review deadline and a message-expiry date.
- 2Route urgent events only when account fit and source confidence already clear the threshold.
- 3Use a slower research queue for high-potential events that need identity or context verification.
- 4After expiry, either demote the event to background context or suppress the send entirely.
Measure the time from verified evidence to a useful action. Detection speed alone says little if research or approval is holding the message for days.
Measure latency in stages
One average hides the real bottleneck. Track detection latency, qualification latency, contact-resolution time, approval time, and send time separately. If detection takes five minutes but the draft waits three days for review, adding another monitoring source will not improve results.
Let outcomes reset the clock
Treat the initial windows as hypotheses and compare replies and meetings by signal age at send. You may discover that first-day funding outreach is crowded while day seven performs better with a considered angle. Use that evidence to reset the window for the next batch. See recently funded company outreach for one signal-specific example.