Buying signals definition

Most lists of buying signals are written from the seller's wish list. This page starts from what can actually be observed about a company from outside, groups it into five sources, and then deals with the part most guides skip: a team that tracks too many signals ends up acting on almost none of them.

What is a buying signal?

A buying signal is a dated, observable change at a company that makes a purchase more likely soon. It has to be visible from outside, tied to one named company, and recent. A new head of finance, a won tender, a job ad for a first data engineer, a new office: each tells you that something at the company is moving and that people there are about to make decisions.

A signal is not a qualification. Forrester's Kahnke notes that signals age quickly and do not replace qualification: a company can show every sign of change and still not fit your product. The signal answers 'why now'. Your ideal customer profile answers 'why them'. You need both before you write.

Which types of buying signals exist?

Signals come from five sources. They differ in how precise the date is, how many sellers see them, and how directly they point at a purchase. Registry events carry the most precise dates. News is seen by everyone at once.

Examples, not a complete list. Each source splits into many subtypes.

Job ads deserve a second look. An ad that states why the company is hiring, such as building a function from scratch or replacing a system, names the project and implies the budget in one line. Few public events sit closer to a buying decision.

Research backs both halves of the argument. Forrester's list of the biggest intent data mistakes stresses that signals age quickly and do not replace qualification. Gartner found in 2025 that 61% of B2B buyers prefer a rep-free buying experience, which leaves little room for outreach without a clear reason. Elias's window of dissatisfaction supplies the timing logic, as an author's thesis rather than a measured result.

How many signals can a team actually act on?

Fewer than most teams expect. Leadspicker's observation from customer setups is that a small team receives 10 to 20 signals a day and works through barely one of them. The constraint is not signal quality. It is capacity: a signal nobody acts on while it is still current is worth nothing.

So the useful question is not which signals exist, but how many the team can handle. Work it backwards:

1. Measure capacity. Count how many signalled accounts the team can research and write to each day, with a proper first sentence for each.
2. Track that many signal types, not more. Start with the two or three closest to your product's buying moment.
3. Filter by fit first. Accept signals only from accounts that already match your ideal customer profile.
4. Review monthly. Drop a signal type that produces replies nobody can use. Add one only when the team has time to spare.

Tracking everything produces noise. A short list of signal types worked every day beats a long list that piles up unread.

How fast does a signal go stale?

Most signals lose their value within days to weeks, and being early matters more than the exact day. Craig Elias, who built a sales method around trigger events, argues that the first vendor to reach a buyer inside the 'window of dissatisfaction' after a change usually wins. That is an author's thesis, not measured data, but it explains why a late signal is worth little.

Windows differ by type:

• Short: funding announcements and news mentions. Every vendor sees them on the same day.
• Medium: a new executive. The window stays open while they are still forming plans and reviewing vendors.
• Longer: a job ad tied to a project, such as a migration. The project runs for months and the ad stays live until the role is filled.

In practice that rules out a weekly export into a spreadsheet. Signals should reach the team on the day they happen, in the tools it already uses.

How does a signal turn into a message?

A signal becomes a message when it answers three questions: who to write to, why now, and with what. The event gives you 'why now'. 'Who' is harder: Gartner's 2025 research puts B2B buying groups at five to 16 people, so a signal is only useful if it also points at the right one. 'With what' is the offer connected to the change.

1. Read the event. What changed, and what problem does that create or expose?
2. Pick the person. The new executive, the hiring manager behind the ad, or the owner of the budget that just moved.
3. Open with the event. 'Saw you are hiring your first data engineer' is a reason. 'I hope you are well' is not.
4. Offer one thing. A single, specific next step tied to the change.

The weak point in most setups is the gap between the alert and the message. A signal that arrives as a news link still needs someone to find the company, the person and the contact details. A signal that arrives as a task with all of that attached can be worked in minutes.

Frequently asked questions

Which buying signals are worth tracking?

The ones closest to your product's buying moment, from accounts that already fit your ideal customer profile. For most B2B teams that means two or three types to start, such as a new executive in the buying role, a job ad for the function you serve, or a won contract. Add more only when the team has capacity to spare.

How many signals can a small team act on?

Usually only a handful a day. Teams that track many signal types receive far more than they can research, and the unworked ones expire. Set the number of tracked types by the team's daily capacity, not by what the data feed can deliver.

How fast does a buying signal go stale?

Within days for news and funding announcements, which every vendor sees at once. Job ads tied to a project stay useful longer, because the project runs for months. In every case the first relevant message inside the window has the advantage.