RevOps
Price the pipeline you lose every minute you wait to follow up.
- Category
- RevOps
- Signup
- None
- Your data
- Stays in your browser
- Also in
- Claude, via MCP
How much revenue does slow lead response cost?
Estimate conversion at your current response time, subtract it from conversion at a fast target, and multiply the gap by lead volume and deal value. This calculator models conversion decaying as e^(−minutes ÷ 21). At 600 leads a month, 45 minutes versus 5 minutes costs about 61 deals a month at a 12% fast-response conversion rate.
Waiting 45 minutes instead of 5 costs about $245,129/month. Speed-to-lead decays fast, instant routing and auto-assignment usually recover most of this.
Models the well-documented steep drop in contact/qualification odds within the first minutes. Actual decay varies by channel and offer.
About this calculator
Speed-to-lead isn't a soft best practice, it follows a fairly steep decay curve: contact and qualification odds fall fast in the first several minutes after a lead comes in and keep falling, more slowly, after that. This calculator applies an exponential decay model to your own volume and deal value, so the case for faster routing lands in dollars, not a generic "respond within five minutes" rule.
How to use it
- Enter inbound leads per month.
- Enter your current average response time and a target response time (5 minutes is the commonly cited fast-routing benchmark).
- Enter the lead-to-deal conversion rate you achieve at that target speed, and average deal value.
- Read conversion at your current (slower) speed, the relative conversion lost to the delay, and the deals and revenue that costs you monthly and annually.
Methodology
The model uses an exponential decay function, e^(–minutes ÷ 21), calibrated so conversion odds are near their peak around 5 minutes and drop off steeply as minutes pass. This shape reflects the well-documented pattern that contact and qualification odds fall off sharply in the first tens of minutes, not linearly over hours.
Conversion at your current response time is calculated by scaling your stated target-speed conversion rate by the ratio of decay at your current time to decay at your target time: convAtTarget × (decay(current) ÷ decay(target)).
Lost conversion points is the difference between target-speed and current-speed conversion. That percentage-point gap, applied to your monthly lead volume, gives lost deals; lost deals × deal value gives lost revenue, shown monthly and annualized.
The 21-minute decay constant is a modeling assumption representing the commonly observed steep early drop-off, not a measurement of your specific funnel. Actual decay shape varies by channel, offer type and lead intent, treat the dollar figure as directionally right rather than exact.
The decay model behind speed-to-lead cost
Decay(m) = e^(−m ÷ 21) Conversion now = Conversion at target × Decay(current minutes) ÷ Decay(target minutes) Lost conversion points = Conversion at target − Conversion now Deals lost per month = Leads per month × Lost conversion points ÷ 100 Revenue lost per month = Deals lost × Deal value
- m
- Minutes from the lead arriving to the first real attempt to contact them.
- 21
- The decay constant in minutes. It is a modelling assumption that produces a steep early drop, not a measured value.
- Conversion at target
- Lead-to-deal rate you achieve, or expect, when you respond at the target speed.
- Relative conversion lost
- Lost points ÷ conversion at target. The share of your fast-response conversion that the delay removes.
The curve is steep by design. With a 21-minute constant, each extra 21 minutes multiplies conversion by about 0.37. Compared with the best-known study, it is aggressive: HBR found firms that tried to contact a lead within an hour were nearly seven times as likely to qualify it as firms that waited even an hour longer, while this model gives a much larger gap over the same hour. Treat the output as an upper estimate for high-intent leads, and run a lower-loss scenario too.
Worked example: 600 inbound leads a month, 45-minute average response
A B2B services firm gets 600 inbound demo and enquiry leads a month. Leads sit in a shared inbox before being assigned, so the average first call is 45 minutes after the form fill. When reps call within 5 minutes, about 12% of leads become deals. The average deal is ₹40,000.
- Decay at 45 minutes = e^(−45 ÷ 21) = 0.1173.
- Decay at 5 minutes = e^(−5 ÷ 21) = 0.7881.
- Conversion now = 12% × 0.1173 ÷ 0.7881 = 1.79%.
- Lost conversion points = 12% − 1.79% = 10.21 points, which is 85% of the fast-response conversion.
- Deals lost = 600 × 10.21% = 61.3 deals a month.
- Revenue lost = 61.3 × ₹40,000 = ₹24.5 lakh a month.
- Sensitivity: cutting response to 15 minutes instead of 5 still leaves 4.55 points lost, about 27 deals or ₹10.9 lakh a month.
The model says most of the loss happens in the first half hour, so the fix is structural rather than motivational: automatic assignment on form submission, an instant alert to the owner and a fallback rep when the owner is unavailable. Because the curve is steep, check the result against your own data: compare conversion for leads called within 5 minutes with those called after an hour. The pipeline velocity calculator shows what recovered deals do to monthly revenue.
Lead response findings from the Harvard Business Review study
| Finding | Figure |
|---|---|
| US companies audited | 2,241 |
| Responded to a web lead within one hour | 37% |
| Never responded | 23% |
| Average response time | 42 hours |
| Likelihood of qualifying the lead if contact was attempted within an hour, vs waiting even an hour longer | Nearly 7 times |
What is a good lead response time?
For inbound demo requests and enquiries, the practical target is minutes, not hours. The HBR study above set the bar at one hour and found most companies missed it. Five minutes is the common operating target because it can only be met with automatic routing, which is the real point.
Use three numbers to judge your process:
- Median time to first attempt, not the average, because a few overnight leads distort the average.
- Share of leads touched within 5 minutes during working hours.
- Share of leads never contacted, which HBR found was 23% of companies in its audit.
If you cannot report these from your CRM today, that is the first fix.
Speed-to-lead in India vs the US
Indian buyers often fill several vendor forms in one sitting and expect a phone call or WhatsApp message, so the first vendor to reach them frequently sets the comparison. Phone and WhatsApp follow-up need their own routing: missed-call numbers, IVR and WhatsApp inboxes should create a CRM record and an owner, or the lead never enters the response-time report. Account for working hours: a lead at 9 pm is not "late" until the next morning's first slot. See HubSpot round robin lead routing for a setup that works with Indian sales teams.
US teams more often route through SDRs, so the delay hides in the handover from marketing to SDR. Measure time from form submission to first SDR attempt, not to assignment. Calling and texting rules also matter: consent requirements under US telemarketing law affect automated dialling and SMS, so check them before automating outreach. The SDR capacity planner shows whether you have enough people to respond fast at your volume.
Common speed-to-lead mistakes
- Measuring time to assignment instead of time to the first real contact attempt.
- Reporting the average, which a few weekend leads can inflate, instead of the median during working hours.
- Treating every lead source the same. Demo requests decay faster than ebook downloads.
- Routing to an owner who is on leave or has left, with no fallback rule.
- Entering conversion at current speed in the "target speed" field, which shrinks the modelled loss.
- Fixing speed without fixing the first conversation. A fast call that asks no qualifying questions wastes the advantage.
Sources
- The Short Life of Online Sales Leads, Harvard Business Review. Accessed 2026-10-19.
Go deeper
FAQ
Because the steepest part of the decay curve happens within the first 30-60 minutes, most of the conversion damage from slow response is already done well before a lead has waited a full business day. Modeling in minutes keeps that early, fast-moving decay visible instead of averaging it away.
Five minutes is a widely cited benchmark for inbound web leads because it captures the buyer while intent is still fresh. If your current process routes through manual assignment or a shared inbox, your realistic current time is likely much higher than five minutes, enter your honest current average, not an aspirational one.
No, high-intent channels like demo requests and pricing-page form fills decay fastest since the buyer is actively comparing options in the moment. Lower-intent channels like content downloads or webinar signups decay more slowly, if most of your volume is low-intent, the dollar impact here will run lower than the model suggests.
Speed-to-lead is the time between a prospect submitting a form, call or message and your team's first attempt to contact them. It is usually measured in minutes for inbound leads.
No. It is a modelling choice that produces the steep early drop seen in response-time studies. The HBR study is the evidence that early response matters; it does not give a decay constant. Calibrate against your own CRM data where you can.
Respond automatically at night with a useful message and a booking link, then call at the start of the next working day. Count response time from the start of working hours if you do not staff evenings.
Record the create date and the timestamp of the first logged call, email or message by the owner, then report the difference. Most CRMs can calculate this with a date property and a workflow or a built-in first-activity field.
Numbers looking off?
If the model says one thing and the pipeline says another, that gap is usually where the revenue is. A 30-minute call finds it.
It starts with a 30-minute call. Pick a time below.