B2B Lead Intelligence · Signal evidence
Signals can help sales teams decide which accounts deserve attention first, but only when the underlying event is observable, attributable and recent enough for the use case.
Direct answer
A B2B buying signal is an observable event or change that can make a business problem more likely to be active, such as relevant hiring, expansion, technology change, channel activity or a public solution requirement. It should be stored with the source and date, then evaluated against ICP fit. The signal supports prioritization; it does not prove purchase intent.
The fact is what can be verified: a company published a role, announced a new facility, changed a public technology requirement or opened a distributor program. The inference is why that event may matter to the offer.
Keeping those layers separate makes the record reviewable and prevents a research trigger from becoming an unsupported sales claim.
A useful signal is not universal. The same event can be highly relevant for one product and irrelevant for another, so the brief should define which events are meaningful before research starts.
At minimum, preserve the event, the source, the relevant date and the reason the event matters to the agreed ICP or offer. Add a last-verified date when the signal or account state can change quickly.
| Field | Purpose |
|---|---|
| Observed event | States the factual change without sales interpretation |
| Source | Lets a reviewer verify the event and context |
| Published / observed date | Shows whether the timing is still relevant |
| Commercial inference | Explains why the event may matter to the offer, clearly labeled as inference |
A recent event is not automatically strong. Prioritization improves when the event is directly related to the problem the product solves, the source is credible enough for the decision and the company still fits the ICP.
Avoid universal signal scores or conversion multipliers unless your own historical data supports them. D2 does not publish a generic formula that claims one signal always converts better than another.
Some high-fit accounts will not have a recent public event. They can still enter an account-fit research lane if the brief allows it. The correct output is 'no relevant observable signal found', not a speculative why-now story.
Decision checklist
Related decisions
See how signal evidence moves from research trigger into account prioritization and sales handoff.
Read nextUse signals inside a broader quality contract that also checks ICP, buyer and contactability.
Read nextSee how the same signal rules apply to a supported target geography without turning market language into a buyer-location assumption.
Read nextFAQ
No. It is a research and timing indicator. Purchase intent would require stronger direct evidence and still would not guarantee a sale.
Only when the project scope requires signal-based prioritization. Account-fit research can be valid without a recent observable event.
Yes, if the brief defines which signal categories matter and how evidence, recency and ICP fit should influence priority. D2 avoids universal scores that are not supported by the client's use case or data.
B2B Lead Intelligence
D2 can scope a Lead Intelligence pilot that records observable signals, source/date, ICP fit, buyer context and verified contactability in one handoff.
