Playbook · Signals

Real-Time Buying Signals: Which Ones Decay and How Fast

Marián Cabadaj By Marián Cabadaj · Published 11 September 2026 · 8 min read

Every vendor selling real-time buying signals sells you the feed. Almost none of them says how long a signal stays worth acting on, and that is the only thing the phrase real-time is claiming.

A signal is perishable. Some perish in minutes, some are still good a quarter later, and what ends them decides which is which. Treat them all as urgent and you spend the week on the slow ones, because the slow ones are still there when you get round to looking. Every figure below comes from Gartner, Harvard Business Review, The Bridge Group or Salesforce directly.

A person working at a laptop in an office with charts on the desk

What makes a buying signal real time?

Your own latency. A buying signal is any observable thing that changes the odds somebody buys, and real time describes the distance between that thing happening and you acting on it. That distance belongs to your pipeline.

Why anyone needs signals at all

Because buyers stopped raising their hands. Gartner's March 2026 sales survey, covering 646 B2B buyers between August and September 2025, found 67% say they prefer a rep-free experience, and 45% used AI during a recent purchase.

What this means for a B2B sales team: two thirds of your market will get most of the way through a purchase without talking to you. A signal is the only evidence you get that a buying task is happening at all.

First party and third party are different goods

A first-party signal happens on something you own, so you see it immediately. A third-party signal happens on somebody else's platform, so you see it after a crawl. The awkward part: the one you see fastest also decays fastest, so the only signal where speed decides anything is the one nobody sells you.

Is your real-time feed actually real time?

Probably not, and the refresh rate on the vendor's pricing page is not the number to check. A third-party signal crosses five steps before anyone acts on it, and the real-time claim covers one of them.

A close-up of a stopwatch on a dark background
  1. The event happens. Somebody posts, applies, funds or hires.
  2. The platform publishes it. Instant for a post, slower for anything syndicated.
  3. A vendor collects it. The step the word real-time usually describes.
  4. It reaches your tool. Often a batch, often overnight.
  5. A person reads it. Usually once a day, in the morning.

The last step is the one that ruins it

A feed that refreshes every fifteen minutes and gets opened once a day is a daily feed. HBR's lead response study named this cause in 2011: firms were "retrieving leads from CRM systems' databases daily rather than continuously". It is still where most of the delay sits, and it is the only step you fully control.

Which signals decay, and how fast?

All of them, at wildly different rates. Nobody publishes a measured half-life for a B2B buying signal, so the honest way to estimate one is to ask what ends it. Every signal below has something that switches it off, and that thing is the clock.

An hourglass on a wooden surface with the sand running through
SignalWhat it tells youWhat ends it
A visit to your own pricing pageSomebody is costing you up right nowThey close the tab and the session is over
A public question about the problem you solveThe problem is live and unsolved this weekThe thread gets answers and stops being read
Engagement on a competitor postAttention on the category, not intent to buyNothing ends it, which is the problem with it
A new ad campaign in the Meta Ad LibraryA go-to-market push just started and has a budgetThe campaign stops running
A job posting for the role that owns your productA gap was approved and fundedThe role gets filled
A funding roundBudget arrived and priorities are being setThe money is committed elsewhere
A new leader in the buying roleThe stack is about to be rewritten by somebody newThey inherit the stack and defend it

The one row that should change your week

Engagement on a competitor's post has nothing that ends it, which is why it feels like an endless supply and converts like a list. A signal with no expiry is an audience. Our comparison of intent providers shows the same split: the cheap volume never expires.

Does answering faster actually win anything?

On inbound, decisively. On third-party signals, much less than the people selling them imply.

A person wearing headphones working on a laptop beside a window

The evidence everyone quotes is Harvard Business Review's The Short Life of Online Sales Leads from 2011. Across 1.25 million leads at 29 B2C and 13 B2B US firms, companies contacting within an hour were nearly seven times as likely to qualify the lead as those trying even an hour later, and more than sixty times as likely as those who waited a day.

What this means for a B2B sales team: the cliff is inside the first hour, not the first day. An hourly check beats a daily by more than a daily beats a weekly, so buy frequency before volume.

The same authors audited 2,241 US companies with a test enquiry. Average response time among those answering inside a month was 42 hours, and 23% never answered.

What this means for a B2B sales team: you clear that bar with process alone. Nearly a quarter of your competitors never answer their own inbound, so an hour is a differentiator and a cheap one.

What does not transfer

That study measured people who had just filled in a form. A funding round does not go cold in an hour, and treating it as though it does produces the message every founder deletes, the one landing minutes after the announcement. Speed decides where the buyer is mid-task. Everywhere else it is a tiebreaker.

Field note: we wired a same-hour alert onto funding announcements and watched the reply rate fall below our normal cold rate. The message was faster than the news. People were still fielding congratulations and we read as automated, because we were. Moving it to day twenty, when the spending starts, fixed it.

How many signals can one person actually act on?

Far fewer than any feed will hand you, and this is the constraint that decides whether a signal programme works. Capacity sets the response window.

Four colleagues working at desks in an open-plan office seen from above

The Bridge Group's 2025 SDR Models, Motions and Metrics report, built on 351 B2B companies, puts the median SDR at 112 activities a day and 4.1 quality conversations a day.

What this means for a B2B sales team: four real conversations a day is the ceiling on how many fast-decaying signals one person converts into anything. Two hundred a week is a queue ageing faster than it is worked.

The same report puts the share of SDRs hitting quota at 60%, the lowest in its history.

What this means for a B2B sales team: a signal feed will not fix a team already missing quota. Cut the tail of slow signals first, so the fast ones get answered inside their window.

Salesforce's State of Sales 2026, a survey of 4,050 sales professionals across 22 countries, found 48% say they lack the bandwidth to do adequate cold outreach.

What this means for a B2B sales team: half the field is out of hours before a single signal arrives. Plan against how many signals you can answer inside the window.

Free tool: how many meetings your touch volume actually buys

a day
days
%
%

10 meetings a month

800 touches, 40 replies. That is 100% of the 10 meetings held a month The Bridge Group put the 2025 quota at.

%
%
$
days

$12,000 from this month

5 opportunities and 1 deals, landing around December 16, 2026. The meetings you book today are revenue one sales cycle from now, so a slow month shows up in the forecast 60 days later.

Put your own numbers in above, or open the SDR meetings calculator on its own page. What it returns is the real cap on your signal programme, whatever the feed delivers.

What should you send when a signal fires?

Something that names the signal and makes it cheap to be wrong. A signal gives you one advantage over a cold email: a reason. Hiding the reason throws it away.

A person typing on a white laptop at a desk

Three lines, in this order

  1. The signal, plainly. What you saw and where. No pretending you happened across it.
  2. The guess it leads to. One sentence on what you think it means for them.
  3. A cheap correction. A question they can answer in one word if the guess is wrong.

Teams skip the third line, and it is what separates a signal message from a confident stranger. Your guess is wrong often enough that replying has to be easy when it is. Our guide to what breaks in an automated stack covers what happens when replies outrun the people answering them.

Field note: the best version I have run named the signal in the subject line, in the plainest words available. The thing we saw, in five words. It reads as a reason to write, and nobody has ever asked how we knew.

Which numbers show the signal is working?

Four, and almost nobody measures the first, which is the whole point of buying a real-time feed.

A colleague presenting sales charts on a large screen in a meeting room
  • Median time from event to first touch. From the event's timestamp, not from when it reached your tool.
  • Share answered inside the window. Per signal type, using the windows below.
  • Reply rate by signal type. The only honest read on which source carries the programme.
  • Meetings per hundred signals. Whether to buy more of a source or switch it off.

Measure the second per type or it averages into nothing. Ninety percent on funding rounds and ten percent on pricing page visits reports as fifty, and fifty looks fine. Reply rate by type is what a scoring model should be built on, which our guide to lead scoring walks through.

Signal decay at a glance

Fastest first, which is the order to work them in.

SignalSourceDecays inRespond within
A visit to your own pricing pageFirst partyMinutesThe same hour
A public question about the problem you solveThird partyHours to daysThe same day, in the thread
Engagement on a competitor postThird partyDaysUse as context, never as a trigger
A new ad campaign in the Meta Ad LibraryThird partyWeeksTwo weeks
A job posting for the role that owns your productThird partyWeeks to monthsTwo weeks, then again on the start date
A funding roundThird partyOne to two quartersA month
A new leader in the buying roleThird partyOne to two quartersAfter their first month, not before

How Leadalf sources real-time signals

Leadalf works the third-party half of that table. It does not sit on your website and it does not watch your pricing page, which is the fastest row and the one to instrument yourself.

The differentiated point: a signal is only worth sourcing if something ends it. Every source below has an expiry built in, which is why the list stays short rather than growing into an audience.

What the workflow looks like

  • Signals in: LinkedIn, Reddit, X, the Meta Ad Library and job postings, so every line traces back to a dated event.
  • Scored against your ICP, not a keyword: volume cannot creep up by loosening a filter.
  • Delivered with the reason attached: the people behind passing signals are enriched and pushed into Instantly or HeyReach carrying the reason they qualified, which is line one above, already written.

See how the signal sourcing works end to end, or what a filtered lead costs in credits.

FAQ

What is a real-time buying signal?

It is an observable event that changes the odds somebody buys, delivered while it can still change what you do. Real time is a claim about the gap between the event and your response, and that gap belongs to your pipeline. A pricing page visit you read tomorrow is not a real-time signal, whatever captured it.

How long is a buying signal good for?

It depends on what ends it, and the range is wider than most teams assume. A pricing page session is over in minutes. A public question stops being read once the thread has answers. A job posting stays live until the role is filled. A funding round is still useful a quarter later. Reason from what ends each one.

Are third-party intent signals real time?

Rarely, and the honest ones do not claim to be. A third-party signal is published by a platform, collected by a vendor, delivered to your tool and then read by a person, and every step adds lag. An advertised refresh rate describes the collection step only. Measure the whole distance yourself, event timestamp to first touch.

Which buying signals are worth acting on first?

The fastest-decaying ones you can see, which are almost always the ones on your own property. Work them in decay order. A funding round answered a week late is still a good touch. A pricing page session answered a week late is a cold email to a stranger.

Does responding faster to a signal actually win more deals?

On inbound the evidence is strong and old. Harvard Business Review found firms contacting within an hour were nearly seven times as likely to qualify a lead as those trying an hour later. On third-party signals there is no equivalent study and the mechanism does not transfer, because a funding round does not go cold in an hour. Speed is decisive on first-party signals and a tiebreaker on the rest.

ASK AI ABOUT LEADALF