FIELD GUIDE · BUYING SIGNALS
B2B buying signals: how to check them before outreach
Use hiring, leadership changes, and public statements to decide which accounts to research. This guide shows how to check each source and choose language it supports.
THE SHORT VERSION
Key takeaways
- A buying signal helps prioritize research. It does not establish that an account is ready to buy.
- Fit, event, evidence, recency, and ownership must align before a signal becomes actionable.
- When no fresh event exists, use honest problem-level outreach instead of inventing a trigger.
Most prospecting begins with a static question: Who matches our ICP? Buying-signal prospecting adds a second question: What happened that makes this account worth investigating now?
Your ICP describes companies that could buy. It cannot tell you whether the problem is active, whether a particular person owns it, or whether a message has a credible reason to arrive today.
A buying signal is an observable change or behavior that may make a purchase more likely or urgent. It still needs investigation before you can describe the company as ready to buy.
An observable event or behavior that, when combined with account fit and relevant evidence, makes an account more useful to evaluate now than it was before.
Decide which changes matter to your offer
A list of popular signals is easy to produce: funding, hiring, executive changes, website activity, product launches, public comments, technology changes. The harder and more valuable work is deciding which combination predicts a real problem for your offer.
Begin with the sentence: “Companies are more likely to need us when…” Complete it using patterns you have observed in customer conversations, closed-won deals, failed deals, and the operating reality of your market.
“A B2B SaaS company may need better prospecting data when it hires a new sales leader and expands its SDR team.”
B2B SaaS · new VP Sales · five or more SDR roles · recent public data-quality concern
The hypothesis specifies which job changes matter to your offer. Add a freshness window so old events stop triggering new outreach.
Five layers make a signal actionable
- 01
Fit
Does the company match the market, operating model, and deal economics your product serves? A fresh event at the wrong account is still the wrong account.
- 02
Event
What changed? Define the event precisely enough that two researchers would reach the same conclusion.
- 03
Evidence
What source supports the event? Preserve the source, date, relevant excerpt, company, and person rather than storing a vague label.
- 04
Recency
How long does this event remain useful? A pricing-page visit may decay quickly. A new executive hire may remain relevant for weeks.
- 05
Ownership
Who is likely to own the problem created or exposed by the event? Account-level intent is incomplete until it resolves to a buyer.
Buying signal examples and their limits
| Signal | Strength | TTL | Likely owner | Allowed claim | Does not prove |
|---|---|---|---|---|---|
| Named leader describes a relevant problem | High | 14 to 30 days | The speaker or their functional lead | Attribute the exact problem to the speaker. | Budget, an evaluation, or willingness to change. |
| New VP Sales | Medium | 30 to 60 days | VP Sales / Revenue Operations | Acknowledge the role change. | The company is replacing its sales stack. |
| Five SDR roles opened | Medium | Until roles close, checked weekly | VP Sales / Head of SDR | State that the team is hiring SDRs. | The existing motion or data is broken. |
| Repeated high-intent web behavior | Medium when identity is reliable | 1 to 7 days | Role mapped from the visited problem | Prioritize research; avoid citing surveillance. | Purchase intent, authority, or budget. |
| Enterprise product launch | Low to medium | 14 to 45 days | Owner of the affected workflow | Reference the public launch. | A specific security or compliance project exists. |
| SOC 2 preparation mentioned | High for trust workflows | 30 to 90 days, source dependent | Security / Compliance / Operations | State that preparation was mentioned. | The company will buy your category. |
TTL is a review policy, not a universal market constant. Every recipe should define its own expiry rule and the source that refreshes it. Use the signal-recipe template to record strength, freshness, buyer ownership, allowed language, and the explicit stop condition together.
The right-hand column is where most weak personalization begins. The system observes one thing, infers another, and quietly writes the inference as fact. Claim-level verification is what keeps that inference from becoming fabricated personalization.
Stack signals to reduce coincidence
One event can be useful, but combinations are usually more discriminating. A funding announcement alone is broad. Funding plus a new functional leader plus role-specific hiring creates a narrower operating pattern. Add a direct public statement about the problem and the evidence becomes more useful still.
Define what each condition contributes: account fit, a recent change, a relevant problem, or a likely buyer. Keep those reasons visible alongside any combined score.
Compare what happens after a signal appears
When comparing products, follow the same signal through research, drafting, review, and sending. Check which steps each product handles and which your team must configure.
Nolina keeps the source with the signal, checks the company and date, identifies a likely buyer, and prepares a draft for review.
Choose the outreach lane after verification
Not every qualified account needs a fresh event. That leads to two honest paths:
Fresh event, source, date, person
Use a specific contextual opener tied to what the source actually supports.
“I saw your comment about stale prospecting data…”
Strong fit, no fresh event
Use role- and problem-level language. Do not manufacture a trigger.
“Revenue teams often lose time to stale prospecting data…”
Both lanes can produce good outbound. The mistake is disguising the second as the first.
A practical signal-recipe template
Account fitWho can realistically buy and benefit?
Observable changeWhat event should cause the account to enter research?
Evidence ruleWhich sources and attributes are required?
FreshnessHow long does the event remain relevant?
BuyerWhich role is likely to own the exposed problem?
Allowed languageWhat may the message say with or without a verified event?
OutcomeWhich replies, meetings, and losses should update the recipe?
Copy the complete signal-recipe template for a review-ready version that also captures contradiction checks, suppression, execution state, and learning outcomes.
Give the seller enough context to decide
For each prioritized account, show the fit, event, supporting source, and likely buyer together. A seller should be able to decide whether the proposed next step is justified.
Keep any uncertainty visible, including missing dates or an unconfirmed buyer. The rep can then request more research or write a broader message.
COMMON QUESTIONS
Frequently asked questions
What are B2B buying signals?
B2B buying signals are observable events or behaviors that make an account more useful to investigate now. They can indicate a change in probability or urgency, but they are not proof that a company is actively buying.
Which B2B buying signals are strongest?
The strongest signals combine account fit, a relevant operating change, a recent source, and a buyer who plausibly owns the exposed problem. A direct public statement is usually more specific than a generic company event.
Is a pricing-page visit proof of purchase intent?
No. A pricing-page visit can justify prioritization, especially when repeated or combined with other behavior, but it does not prove budget, authority, an active evaluation, or readiness to buy.
How should sales teams act when there is no fresh signal?
Use audience-level outreach based on role, category, and a credible problem pattern. Do not imply that a specific event happened. Strong fit can justify a conversation without manufacturing a why-now claim.
SOURCE NOTES
Sources and further reading
- How to Identify and Act on Buying SignalsClay ↗
- Select the Right Buying SignalsCommon Room ↗
- State of Sales, Seventh EditionSalesforce ↗
Vendor sources describe definitions, workflows, and platform policies. They do not independently establish product performance.
TRY A PILOT