Section 1
The research: what response time does to conversion
The defining study remains The Short Life of Online Sales Leads, published in Harvard Business Review by James Oldroyd, Kristina McElheran, and David Elkington. Auditing 2,241 US companies, they found the average first response to a web-generated lead took 42 hours, 23% of companies never responded at all, and firms that responded within an hour were nearly seven times more likely to have a meaningful conversation with a decision maker than those that waited even an hour longer. The mechanism is mundane: the prospect is at their desk, problem-aware and available, for a short window after they enquire. Reach them inside that window and you get a conversation. Miss it and you are chasing someone who has moved on, often into a competitor's calendar. Interest decays by the minute, not the week. The thinking here builds on [From Lead to Booked Call: Designing the Follow-Up System That Closes](/blog/from-lead-to-booked-call-follow-up-system).
Section 2
Response time versus outcome: the decay curve
The relationship between response time and outcome is not linear, it falls off a cliff. The table below summarises the practical decay curve operators should plan around, combining the HBR findings with what we see installing LeadOS across service businesses. The headline is that the difference between five minutes and one hour is larger than the difference between one hour and one day, because the prospect's attention window closes fast. Most businesses anchor on responding within the day and feel responsible doing so. Against the actual decay curve, same-day is already deep into diminishing returns. Set your internal service-level agreement at five minutes during stated business hours, with an automated acknowledgement covering the gaps, and you will be faster than nearly every competitor your prospect contacted.
Section 3
Why service businesses respond slowly
Slowness is rarely laziness. The owner is on a client site all day. Enquiries land in a shared inbox nobody owns. The form notification goes to an email address checked twice daily. Weekend leads wait until Monday. Each delay is rational in isolation; together they produce the 42-hour average HBR measured. Goldratt's bottleneck principle frames it correctly: an hour lost at the constraint is lost for the entire system. Your marketing, your referral relationships, and your ad spend all terminate at the moment of first response, every hour of delay there devalues everything upstream. The fix is structural. You cannot willpower your way to five-minute responses while running client delivery. You need routing, notification, and automation that make the fast response the default rather than the heroic exception. For the step that usually comes next, see [Speed to Lead: Why Follow-Up Time Decides Who Wins the Client](/blog/speed-to-lead-why-follow-up-time-decides-who-wins-the-client).
Section 4
Building a five-minute response system
The system has four parts. First, instant acknowledgement: every form submission triggers an immediate, personal-sounding reply containing a calendar link, so the prospect can book before you ever touch the lead. Second, loud routing: new-lead alerts go to a phone via SMS or app push, not a quiet inbox, with a named owner per time block. Third, a first-touch script: a two-minute qualification call or message template, so responding requires no composition time. Fourth, coverage rules for nights and weekends, automation holds the lead's attention until a human is available. Gartner's research on the B2B buying journey shows buyers spend only a sliver of their time with any supplier, which makes your few minutes of contact disproportionately valuable. This stack is precisely what AutomateOS installs; a strategy call will show you your current response time and the gap. For a deeper look at this, see [Above the Fold: What Your Homepage Must Say in the First Five Seconds](/blog/above-the-fold-what-your-homepage-must-say-in-the-first-five-seconds).