FIELD GUIDE · SIGNAL-BASED SELLING
Signal-based selling: from an event to a first message
Check who the event concerns, when it happened, and what it supports in a message. Then decide whether to research further, draft an opener, or hold the account.
THE SHORT VERSION
Key takeaways
- A trigger changes research priority; evidence determines what can be claimed.
- Every signal recipe needs a strength, freshness window, buyer owner, and no-signal fallback.
- A reply is part of signal learning because it can correct the buyer, problem, or trigger hypothesis.
Job changes, funding announcements, website visits, and public activity can help prioritize accounts. To use one in outreach, verify the observation and decide how it relates to your offer.
The trigger-to-action chain
Each arrow can fail. A trigger may belong to the wrong entity. A source may be stale. The buyer may not own the problem. The claim may add an unsupported motive. The account may opt out before dispatch. Record a failed check before proceeding to the next step.
Define signal strength and TTL before collecting volume
| Signal | Strength | Typical TTL | Buyer owner | Does not prove |
|---|---|---|---|---|
| Named problem statement | High behavioral | 14 to 45 days | Speaker or functional owner | Budget or active evaluation |
| Relevant hiring cluster | Medium attributive | 30 to 60 days | Leader hiring the function | Current process is broken |
| Executive role change | Medium attributive | 45 to 90 days | New leader or adjacent owner | Stack replacement |
| Anonymous web visit | Low/medium behavior | 1 to 14 days | Unresolved | Which person visited |
These windows are starting hypotheses, not universal constants. Measure whether a signal still changes response quality as it ages, then adjust the recipe.
Signal strength grants different language rights
Attributed behavior
Reference the statement or action when the source and person are verified.
“I saw your comment about stale prospecting data…”
Observed company event
Name the event without assigning intent, motive, budget, or dissatisfaction.
“I noticed the team opened seven SDR roles…”
Use the claim examples to see which observations permit specificity and which require a rewrite.
No fresh signal is a valid state
A strong-fit account can still justify outreach. The message must remain at the role and problem level and pass human review until the audience recipe is proven. State the role or problem directly without implying that a recent event occurred.
The lifecycle continues after the claim. Send-time suppression, delivery reconciliation, replies, and follow-up determine whether the original signal can produce another action.
COMMON QUESTIONS
Frequently asked questions
What is signal-based selling?
Signal-based selling prioritizes accounts using observable events or behaviors, verifies what those signals support, and adapts the buyer, message, and timing accordingly.
Which sales signals are strongest?
Direct attributed behavior is usually more specific than a generic company event. Strength also depends on account fit, recency, source quality, and whether the signal exposes a problem your offer solves.
How long should a signal remain fresh?
Use a TTL tied to the event. Website behavior may decay in days, hiring in weeks, and executive changes over a longer onboarding window. An expired signal can still inform history but should not justify a why-now claim.
What if an account fits but has no signal?
Use an audience lane based on verified role, company, and problem context. Do not invent an event or imply that something changed.
SOURCE NOTES
Sources and further reading
- How to Identify and Act on Buying SignalsClay ↗
- Select the Right Buying SignalsCommon Room ↗
- Intent Data: What It Is and How to Use ItSalesforce ↗
Vendor sources describe definitions, workflows, and platform policies. They do not independently establish product performance.
TRY A PILOT