A company announces a new site. A sales tool flags a leadership change. A careers page shows five open operations roles. Each event could justify a closer look. None proves that the company wants your product.
A useful B2B buying signal connects an observable event to a problem your offer can address, at an account that already fits. The practical task is to test that connection before spending on contact discovery or writing a message.
This guide focuses on publicly observable business events. It includes a seven-signal matrix, a copyable evidence record, an illustrative account review and a way to test whether signal-based prioritization helps your team. The methods are editorial recommendations, not a claim that these events predict conversion at a measured rate.
Buying signal, trigger event and intent data are different things
A trigger event is something that happened: an appointment, expansion, acquisition or vacancy. A buying signal is your interpretation that an observation could make a relevant buying situation more likely. Intent data is information about activities interpreted as interest, often collected and aggregated by a platform.
For example, LinkedIn describes Buyer Intent as an aggregation of signals, including activity on its platform and certain website interactions. That platform-defined score is a different evidence source from an official announcement that a company is opening a warehouse.
Keep those sources separate. A high platform score does not explain the operating need by itself. A public expansion does not identify the person evaluating a supplier. In both cases, you need fit, a relevant problem and an appropriate next action.
The seven-signal matrix
Use this matrix to decide what to investigate, not to declare that a prospect is ready to buy.
The last row is often more explicit than the others, but it still requires checking scope, eligibility, deadlines and submission requirements. A tender that has already closed is not a current opportunity merely because the page is still online.
1. Hiring: read the responsibilities, not just the job title
A vacancy can tell you what a team is expected to do. “Implement a new production planning system” is more specific than “Operations Manager.” Read the responsibilities, location and employing entity, and check whether the listing is current.
Then consider competing explanations. The vacancy could replace a departing person. It might describe a long-standing responsibility. An agency could be recruiting for an undisclosed client. A reposted vacancy might not represent a new initiative.
Useful next research question: Does the official listing describe a project your offer can support, and which entity owns it? Unsupported conclusion: This company is short-staffed and urgently needs our service.
If the role is the task you sell, check whether internal hiring complements or substitutes for your offer. A company hiring an in-house specialist may be reducing its reliance on consultants.
2. Expansion: connect the new footprint to an actual task
A new warehouse can create work in logistics, onboarding, reporting or systems integration. Which of those matters depends on what you sell. A translation agency and a warehouse automation supplier should not use the same interpretation of the announcement.
Record the announced location and expected operating date. Separate “announced,” “under construction” and “operating.” A corporate press release may discuss an entire region while your offer serves one country.
Before contacting anyone, write the missing link as a question: “Will this site share inventory reporting with existing locations?” That question is more useful than claiming the company has fragmented reporting without evidence.
3. Leadership changes: an opportunity to understand priorities
A new finance, operations or revenue leader may review processes. The appointment alone says nothing about their priorities or supplier preferences. Inspect the official announcement and any public statements about the role's remit.
Check the effective date, exact entity and whether the role is new or a replacement. An appointment at group level does not mean every subsidiary has a new budget owner.
Use the event to prepare a relevant hypothesis. Do not imply a personal relationship, private knowledge or a change mandate that was never announced. If no link to your problem emerges, the event belongs in background context rather than an outreach justification.
4. Technology projects: distinguish evaluation from installed usage
A job advertisement mentioning a technology could mean the company uses it, plans to adopt it, supports customers using it or simply values transferable experience. A script detected on a website establishes something different again.
Store the exact context. “Experience with ERP migrations” is not proof of a current ERP migration. A customer case study may describe a project completed years ago. Neither should become an active project field without further support.
For an integration service, a documented new API or migration announcement can justify researching requirements. For a replacement product, an existing installation may create a long procurement horizon rather than immediate opportunity.
5. Acquisitions: resolve the entity before the opportunity
An acquisition can create integration work, but transaction status matters. Announcement, regulatory approval and completion are different stages. Preserve the stage described by the source.
Also identify who is buying whom. A brand, operating company and parent group can have different websites and decision structures. Contacting a local subsidiary about a group-wide integration before checking the relationship can make an otherwise thoughtful message irrelevant.
A sensible research outcome may be “revisit after completion.” The presence of an event does not require immediate activation.
6. Launches: ask what changes operationally
A new product matters when it changes something your offer addresses: support languages, implementation work, distribution, compliance documentation or partner onboarding. A new color variant may not change any relevant operating condition.
Use the original product page or release, identify the intended market and distinguish a preview from general availability. Do not copy promotional claims about demand into your own factual assessment.
The best next question is often narrow: “Does the launch introduce a partner onboarding process?” If that cannot be established, keep the uncertainty rather than inventing a growth problem.
7. Tenders: verify that you can actually respond
A published supplier request can contain a concrete specification, but the right decision may be to decline. Check required certifications, geographic scope, contract scale, response date and permitted communication channels in the original notice.
Keep amendments with the opportunity. An extended deadline or changed scope can alter the decision. Avoid treating an aggregator's summary as the complete procurement instruction.
This guide does not provide procurement or legal advice. Use the applicable notice and responsible specialists for eligibility and submission decisions; the signal record is a research aid.
A copyable buying-signal record
Keep publication date, event date and date checked separate. A newly indexed page can describe an old event. A source checked today is not necessarily a fresh signal.
Use one canonical event record when several sites repeat the same announcement. Three reposts of one press release are one event, not three independent confirmations.
Worked example: a warehouse announcement
Consider the fictional company Nordlicht Components. Its official site announces a new warehouse scheduled to open in November. Your company sells inventory reporting integrations.
Observed: a new warehouse has been announced for a named location and date. Relevant hypothesis: reporting may need to work across locations. Unknown: systems, project owner, current integration partner, budget and whether the group already has a standard rollout.
The next step is to inspect current operating sites and any official implementation material. Suppose the announcement says the warehouse will use the group's existing standard system. That weakens a “new system selection” hypothesis but may leave an implementation question worth investigating.
A responsible opening, if the channel and contact are appropriate, would ask about the operational task: “Your announcement mentions the new warehouse. Is connecting its inventory reporting to existing sites part of the rollout, or is that already covered by your standard setup?” It does not assert that the company has a reporting problem.
If you cannot establish a plausible link, stop. A well-recorded dismissal saves contact research and prevents irrelevant messaging.
Prioritize with gates before scores
For a first pilot, use three decisions rather than an elaborate numerical model:
- Investigate: the account fits, the event is supported and a relevant operating question remains.
- Hold: fit is plausible, but timing, identity or relevance needs a later check.
- Dismiss: the event is stale, duplicated, contradicted or irrelevant to the offer.
Set revisit periods according to the event and your sales cycle. A tender deadline and a factory construction project should not have the same expiry rule. The period is an operating choice to test, not a universal benchmark.
If fit is unclear, return to the B2B ICP template. If evidence is unclear, use the company research prompts. Buying contact data is premature while either gate remains unresolved.
Test whether signals improve your workflow
Start with comparable accounts in one segment. Record which were prioritized by an event and which were selected by fit alone. Keep the offer, channel rules and outcome definitions consistent. If practical, allocate accounts randomly to the prioritization approaches; otherwise, label the comparison as observational.
Track reviewer time, accepted signals, stale events, irrelevant events and resulting qualified conversations. Preserve the raw counts. A higher reply rate alone can be misleading if replies mainly say the event was misunderstood.
Do not claim causation from a handful of successful messages. Signal-based selection may simply identify larger companies, better websites or accounts that were already more active. Use the pilot to find whether the extra research is worth doing, then decide whether a larger test is justified.
Where Leadbase fits
Use focused enrichment to investigate one public question about a known company and inspect the returned evidence in Activity. Keep the observation distinct from your interpretation and choose your next action after review.
This is a proposed workflow using Leadbase's documented research capabilities. It is not a claim that Leadbase continuously monitors all seven event types or supplies a proprietary buying-intent score. Source availability and research costs vary.
Continue reading: turn one uncertain event into a checkable question with AI company research prompts. Before scaling accepted accounts, use the data enrichment cost model to decide which extra fields are worth buying.
Sources and product documentation checked on 17 October 2026. The example company and scenario are fictional.
