Skip to content
From the blog

Buying signal timing windows

A buying signal timing window is how long a signal stays worth acting on before the response drops off. The range runs from minutes for a demo request to months for an open role: the same message that lands on day 3 reads as scraping on day 40. Every major window is below, with sources.

By Rahul Bageria, co-founder · Updated August 2026 · 9 min read

The windows

How long each buying signal stays warm

Six signals cover most of what an early-stage team acts on. The table is the short answer; the reasoning and sources follow. The full motion lives in our signal-based selling guide.

Signal Window Check cadence What kills it
Inbound hand-raiser (demo request, form fill) Minutes. Same session, same hour. Real-time alert to phone or Slack Waiting until tomorrow: the average firm takes 42 hours (HBR, 2011).
Job change or past champion Best inside 30 days. Treat 90 as the expiry. Daily, 15 minutes Day 90: the stack is audited, the shortlist formed.
New executive hire Same 90-day family, freshest in the first weeks. Daily, same 15 minutes The stack audit ending, and discovery calls with it.
Funding round Weeks 2 to 6 for most sellers; weeks 4 to 12 via the hires the money pays for. Daily digest (Crunchbase email) The day-1 congrats wave, or a stale congrats past week 12.
Hiring signal (open role) While the role is open: time-to-hire averages 44 days, plus ramp. Weekly, 30 to 60 minutes The hire being made, which starts a new-hire clock.
Topic intent (Bombora-style) Weekly by construction: scores compute once a week. Weekly, in the same review Treating a weekly batch score like a fire alarm.

Sources: UserGems' Buying Signals Benchmark Report (2024, 2.28 million opportunities; checked August 2026); Harvard Business Review, The Short Life of Online Sales Leads (March 2011); RevenueHero's audit of 1,000 B2B sales teams (2024); the Josh Bersin Company with AMS (2023); Bombora Company Surge documentation (checked August 2026). Funding windows have no public conversion-by-week dataset; those rows are how we run the motion.


The framework

Every signal has a clock, but not the same clock

Event signals decay by attention, state signals decay by need. That one distinction sets the right speed for everything you track, so we gave it a name.

Definition

An event clock counts down from a datable moment every competitor can see: a round, a move, a launch. A state clock runs while a standing pressure stays unsolved: an open role, a growing team.

Event clocks
  • Funding rounds, job changes, launches, leadership news
  • The window is set by inbox noise, not by the buyer
  • Too early drowns in the congrats wave; too late meets a formed shortlist
  • Rewards speed and a sharp first line
State clocks
  • Open roles, headcount growth, a stack gap nobody has fixed
  • A standing pressure few are watching; warm while the problem is unsolved
  • Too early costs nothing; too late, the hire is made
  • Rewards relevance and patience

No clock starts at the press release either: a round closes weeks before the announcement. The clock starts when the buyer's situation changes, not when you find out.

Speed wins when everyone saw the signal. Relevance wins when nobody else did.


The worked clock

One clock, drawn out: the job change

The job change is the sharpest event clock in the set, so here is its whole life. Every event signal follows this shape.

Days 1 to 30 · The opening

The warm month

The new role is unformed and the stack is under audit. UserGems' 2024 benchmark data shows new executives converting 2.5x higher in their first three months than after a year.

Days 31 to 90 · Narrowing

The audit closes

Priorities firm up and the shortlist forms. You can still enter, but the first line has to name the mandate, not the move.

Past day 90 · Absorbed

The window has shut

The new leader has settled into the existing stack. Sales Navigator's job-change filter reaches back exactly 90 days; the market drew the line there too.

The point

The clock is the buyer settling in, not your CRM reminder. Past day 90 your note needs a second, fresher reason to exist, which is what stacking is for.


The math

Signal-by-signal timing math

Every window here comes from a named dataset or is labeled as practice. Where no measured number exists, we say so.

Five clocks, sourced
Job changes

30 days is the prize, 90 the expiry

UserGems' 2024 benchmark data has new executives converting 2.5x higher in their first three months than after a year, and new leaders audit the stack early. See job changes and champion tracking.

Funding

Weeks 2 to 6, then change the angle

No conversion-by-week dataset exists for funding outreach; these are the windows we run. Week 1 is founder-to-founder territory only. Past week 12, open on the plan, not the money. Details in funding rounds.

Hand-raisers

Minutes, the only one

A demo request is the only signal measured in minutes; the receipts are in the next section. Identified visitors have no published conversion-by-delay data, so same-day-to-72-hours is practice, not law. See website intent.

Hiring

While the role is open, plus ramp

The Josh Bersin Company with AMS measured time-to-hire at 44 days across 250,000 hires, 67 or more in specialist fields like energy, and the pain outlives the offer letter through ramp. Setups in hiring signals.

Launches, M&A

Labeled as logic, not data

No published windows exist here. A launch is strongest as a reference in its first two weeks. An acquisition is the opposite of urgent: skip the announcement spike, revisit at 90 to 180 days. See product launches and M&A signals.


The receipts

What the famous speed stats actually say

The famous 21x stat is real, 19 years old, and about phone calls to web form fills. All three parts matter before you rebuild your process around it.

How the stat gets sold

"Leads go cold in 5 minutes. Respond instantly to every signal or lose the deal."

  • Treats 2007 phone-call data as a law of all outreach
  • Stretches an inbound finding onto outbound signals
  • Sells urgency tooling on a 19-year-old dataset
What the study measured

"Phone callbacks to web form fills at six companies in 2007: contact odds 100x higher and qualification odds 21x higher at 5 minutes versus 30."

  • Inbound hand-raisers only, contacted by phone
  • Measured contact and qualification odds, not revenue
  • Directionally still right, because most firms stay slow
Three studies, one direction
1
2007

The origin study

Dr James Oldroyd's Lead Response Management study, distributed by InsideSales: phone callbacks to web form fills at six companies. It measured contact and qualification odds, not revenue, and it predates the phone in your buyer's pocket.

2
2011

The audit that stuck

Harvard Business Review audited 2,241 US firms with a test lead: 37% responded within an hour, 23% never did, and the average response ran 42 hours. Within-the-hour firms qualified leads at nearly seven times the rate of those an hour slower.

3
2024

The modern rerun

RevenueHero reran the audit across 1,000 B2B sales teams: 63.5% never responded at all, and the average response passed 29 hours. The bar has not moved in 13 years; it may have dropped.

Answering within the hour beats most of the market, because the average competitor takes more than a day. None of it transplants onto outbound, where nobody raised a hand.

Want your signals worked on the right clock, by the two of us?

Book a Fit Check

Stack it

When signals stack, clocks reset

Freshness is not strength. A weak signal that fired an hour ago loses to a strong signal from six weeks ago, and stacking is how you enter late without pretending to be early.

Don't

Apologize for being late

Congrats on the Series A back in March! Is now a better time to connect?

  • Six weeks past the congrats wave
  • The only reason offered is stale
  • Reads as a scraped list
Do

Reset the clock with the second signal

You raised in March and just brought in a RevOps lead. Is pipeline coverage on their plate yet?

  • The new hire is this week's reason
  • Stacks two honest observations
  • Answerable in one line

The combinations that work are in the signal stacking play.


The ops

Running timing windows as a two-person team

You do not need real-time monitoring; you need the right cadence per clock, and only one tier is real-time.

The three tiers
Only one tier is an interrupt
Minutes
Hand-raisers only. Form fills and replies page you on phone or Slack. Nothing else earns an interrupt.
Daily, 15 minutes
Job changes, funding news, identified visitors. A Sales Navigator saved search, a Crunchbase digest, a visitor alert channel.
Weekly, 30 to 60 minutes
Job posts, topic intent, headcount trends. Bombora refreshes weekly, so a daily check reads the same numbers twice.
Key takeaways
4 points
  • 1 Automate detection; a human decides who gets a message.
  • 2 Coverage beats breadth: three families reliably, not eight sometimes.
  • 3 Start free: saved searches, alerts, digests, a careers-page check.
  • 4 Upgrade tooling when list volume demands it, not ambition.

Weekly intent mechanics live in the intent data signal.


Failure modes

The five timing failure modes

Nearly every timing mistake is one of five patterns, and the clock model catches all of them.

The stale congrats

A "congrats on the round" note six weeks late signals scraping, not attention. Late on an event signal means changing the angle: open on the plan, not the money.

False urgency

One anonymous website visit is not a timer, and a topic surge is a weekly batch statistic, not a fire alarm. The full list is in when signals mislead.

Over-rotation on speed

Fast and generic loses to slower and specific. The day-1 funding wave is speed without relevance, and the sharper line a day later wins.

Waiting for the perfect stack

The inverse failure: hoarding signals, waiting for three to line up while the event clock runs out. Enter on one strong signal; stacking is for re-entering late.

!
Caution

The announcement is not the event

Funding rounds are announced weeks after they close, so by press day the inside clock has already run. And anything you can see before the press cycle, a hiring spike, a quiet executive arrival, reads as surveillance the moment you name it.

Do this instead
Use pre-announcement signals to time the send, never as the first line.

FAQ

Questions founders ask

How quickly should you respond to an inbound lead?
Within the hour, and ideally within minutes of the form fill. The 2007 InsideSales study found calling a web lead inside 5 minutes made contact 100x more likely than at 30 minutes, and the bar is still low: HBR's 2011 audit measured a 42-hour average response, and RevenueHero's 2024 audit found 63% of 1,000+ B2B firms never responded at all. Answering the same hour beats most of the market.
How long is a job change a good sales trigger?
Treat the first 30 days as the prize and 90 days as the expiry. UserGems' 2024 benchmark data shows new executives converting 2.5x higher in their first three months than after a year, and Sales Navigator's job-change filter reaches back exactly 90 days. Past that point the new leader has settled into the existing stack and the warm edge is gone.
Should I email a company right after they raise funding?
Not on announcement day, and not with congratulations. Week 1 is a wall of congrats notes, so we work weeks 2 to 6, after the noise clears and while plans are still forming. Week 1 only makes sense founder to founder, with a specific thesis about where the money will go.
Do buying signals expire?
Event signals expire, state signals persist. A funding round or a job change is news that every competitor sees at once, so its value decays in weeks. An open role or a growing team is a standing pressure, and it stays warm for as long as the underlying problem is unsolved.
How often should I check intent data?
Weekly. Bombora computes Company Surge scores once a week on the standard tier, measuring a 3-week window against a 12-week baseline, so checking daily just rereads the same numbers. Put intent in a weekly review block and spend the daily minutes on job changes and funding news instead.
What is speed to lead, and does it apply to outbound?
Speed to lead is the time between an inbound lead raising their hand and your first response. The evidence behind it comes from phone callbacks to web form fills, so it is an inbound concept. Outbound signals run on windows of days to weeks, where relevance beats raw speed.
Rahul Bageria, co-founder of Real Good GTM
About the author
Rahul Bageria

Co-founder of Real Good GTM. He has been the first business hire and Chief of Staff at seed-stage B2B startups, building outbound pipeline before any playbook existed. This post comes from running signal-based outbound on these clocks every week, where the difference between day 3 and day 40 shows up directly in the reply rate.

Connect on LinkedIn

Keep going

Put the windows to work

The deep pages behind the two clocks that come up most, plus the play for entering late.

Want your outbound running on the right clocks?

Book a fit check. We'll look at which signals your market actually emits, set the cadence tiers a two-person team can hold, and tell you straight if outbound is not the right motion for you yet.

Book a Fit Check

No hard sell. No fake numbers. Real good work speaks for itself.