On a typical 2-person service shop, a meaningful share of inbound web leads are never contacted by a human at all — the form lands, the team is on a different screen, the lead ages past the hour, and the visitor has already bought elsewhere. The ones that do get a reply decay sharply between a 5-minute acknowledgement and a 4-hour wait: the lead-to-call curve is steep, and the cliff is what produces the ~€4,500/month worked-loss envelope the mapped journey + 24/7 AI agent recovers. Hatchloom maps the lead-to-call window on your operation, then ships the agent that holds the five-minute line — same-minute acknowledgement inside business hours, after-hours reply from a written playbook, and the warm thread escalated to the owner with full context by morning.
Source note · Oldroyd / Lead Response Management (the 5-minute response-window study; the lead-to-call decay curve the /slow-reply, /after-hours, /process- breakdown, /missed-questions, /booking-recovery, and /cart-recovery pillars each walk from a different angle) insidesales.com.
Leak on the line
~€4,500/month
of service-avoidable loss sitting inside the lead-to-call window on a 2-person service shop — a meaningful share of inbound web leads never get a human reply at all, the ones that do decay sharply between a 5-minute acknowledgement and a 4-hour wait, and the 24/7 agent catches the rest on the visitor’s clock with a written-playbook reply or a morning escalation that lands the full transcript in the owner’s inbox by 9 am. Recoverable, once the mapped journey + 24/7 AI agent is running against your operation instead of a generic template. The assumptions are spelled out below; a critic can rerun the math against your own enquiry volume and lead value.
Worked example, not a guarantee. The arithmetic and the underlying assumptions live one section below.
The four findings the brief surfaces
Speed-to-lead loss on a 2-person service shop is not a single problem. It is four leaks at once — the lead-to-call decay curve the same LRM study walks, the five- minute floor the cluster rests on, the share of inbound leads never contacted by a human at all, and the worked dollar-loss the same pattern rolls up to. The map finds them; the build closes them, with the same 24/7 AI agent the /slow-reply, /after-hours, /missed-questions, /booking-recovery, /process-breakdown, and /cart-recovery pillars each describes from a different angle.
The arithmetic, with assumptions spelled out
Take a 2-person service shop with 300 service enquiries a month and a €60 average lead value. Apply the Lead Response Management finding that a reply inside five minutes qualifies at a radically higher rate than a reply four hours later — concretely, a 25-percentage-point conversion gap between the five-minute bucket and the four-hour / never-contacted bucket. The lead-to-call decay curve the LRM study walks shows the cliff sitting between five minutes and thirty minutes; the share of inbound leads never contacted by a human at all stacks on top. The lost enquiries that fell out of the slower / never-contacted bucket — 300 × 25% — is 75 lost conversations/month, × €60 average lead value = €4,500/month sitting inside the speed-to-lead leak a mapped journey + 24/7 AI agent closes. Real shops skew higher once the enquiry volume grows or the lead value climbs; the rounded €4,500/month figure on the hero sits inside the same envelope across most 1- and 2-person service SMBs.
Source · Oldroyd / Lead Response Management (the 5-minute response-window study + the lead-to-call decay curve) insidesales.com. Worked example, not a guarantee — substitute your own enquiries/mo and lead value to rerun.
Sample inputs
Worked loss
300 × 25% × €60 ≈ €4,500/month
Picking up where the speed-to-lead map leaves off
The four findings on this page are the same four the 24/7 agent covers on a real engagement — and the same four the mapping call decides between during week one. The sibling pillar on slow reply walks the same five-minute / after-hours track for reply times; the parallel on after-hours walks the 6 pm to 9 am window that compounds on top; the FAQ-coverage version of the same leak lives on missed questions; how the same envelope lands on a Shopify-style checkout lives on cart recovery; the quote- and booking-form version of the leak is on booking recovery; the silent-drop map that names which handoff is leaking lands on process breakdown. The engagement shape on the pricing page covers how the build runs once the map is in hand.
FAQ
Quick answers about the lead-to-call decay curve, the 5-minute floor, the share of inbound leads never contacted by a human, and how the 24/7 agent + morning handoff actually keep the lead-to-call window open. If yours isn't here, send it directly to hatchloom-5@polsia.app.
One mapping call away
No sales deck, no demo under NDA. Send us the shape of your operation, the helpdesk and CRM you already pay for, and a window for a 30-minute call. We'll tell you in plain English how much of the ~€4,500/month speed-to-lead leak the 24/7 agent is positioned to close on a 2-person service shop — and whether the engagement fits. See how the engagement runs on the landing page.
Replies in one business day, usually faster.
Want more revenue-recovery tips?
A short email when we ship a new teardown, a new lever, or a new worked example. No marketing drip, no sales sequence. Unsubscribe in one click.
Tips, one short email at a time