Reply speed, mapped before it is built
For service small businesses

Inside five minutes the enquiry still converts.An hour later, it has already left.

The Lead Response Management study holds across verticals: a reply inside five minutes is the floor at which most enquiries still convert. A reply four hours later has lost the timing — the visitor is already messaging the next shop on the list. An instant, same-minute automated acknowledgement, paired with a human-shaped handoff, is the difference between an enquiry staying on your inbox and an enquiry going cold. Hatchloom maps the leak on your operation, then ships the four response-time levers — instant reply, after-hours coverage, fallback routing, follow-up — that close it.

Source note · Oldroyd / Lead Response Management (the 5-minute response-window study) insidesales.com.

Floor
5-min reply
Built around
A custom map
Mode
Instant AI, human handoff
€4,500/month worked-loss example
300 enquiries · €60 lead value

Leak on the line

~€4,500/month

of service-avoidable loss sitting inside a one-person service shop's inbox when replies stretch from five minutes to four hours — recoverable, once the four response-time levers are 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.

Speed floor
5 min
After-hours share
~1 in 3
If unaddressed
€4.5K/mo

Worked example, not a guarantee. The arithmetic and the underlying assumptions live one section below.

The four response-time levers

Four dials on a one-person operation — each one buys back a slice of the day.

Slow replies on a service-SMB inbox are not a single problem. They are four leaks at once — the enquiry that sat a minute too long for a human to read, the after-hours thread that arrived when the team was off, the hand-wave handoff that ate the morning, and the bumped follow-up that landed tomorrow instead of today. The map finds them; the build closes them.

01
Instant reply — the same-minute automated acknowledgement, before a human reads the thread
The enquiry sits in the inbox for the same minute your team is on a different screen. Inside that minute, an automated reply lands in the visitor's thread — short, on-message, and acknowledging the question without trying to close it. The visitor stops shopping the next shop on the list. The team opens the thread with real context, not a cold intake form to triage. The five-minute floor isn't met by humans — it's met by an automation that doesn't sleep.
02
After-hours coverage — the 6 pm to 9 am window where a slow reply becomes a lost enquiry
Roughly a third of the enquiries a service SMB sees in a week arrive outside the founder's working hours — between 6 pm and 9 am on a weekday, plus most of the weekend. The bot answers the question from a written playbook, and routes anything it can't handle to a morning bump for the team. The conversion physics are identical at every size; a short-staffed shop feels them more sharply, but the fix is the same.
03
Fallback routing — the escalation that does not eat the morning
When the bot can't answer, the enquiry is captured with the full transcript, classified, and routed to the inbox or Slack channel that should pick it up — refund to billing, complaint to the founder, bespoke quote to the sales thread. The team opens the next morning with a sorted queue instead of a flat inbox. Without it, your day starts with forty minutes of triage before the actual work begins.
04
Follow-up — the bumped thread that lands at 9 am, not at 9 am tomorrow
The bot's tracked threads don't go cold overnight — they bump at 9 am local with a 'we have your request, the team will reply today' note. The enquiry that arrived at 11 pm lands at the top of the morning queue in the team's queue, not buried under six hours of fresh lead traffic. The same bot writes back into the helpdesk, CRM, or carrier you already pay for — so follow-up never means a parallel system your team has to learn.

The arithmetic, with assumptions spelled out

How a service SMB arrives at the ~€4,500/month worked loss.

Take a one-person service shop with roughly 300 service enquiries a month and a €60 average lead value. Apply the Oldroyd / Lead Response Management finding that a reply inside five minutes qualifies at a radically higher rate than a reply hours later — concretely, a 25-percentage-point conversion gap between the five-minute bucket and the four-hour bucket. That puts the lost enquiries that fell out of the slower bucket at 300 × 25% — 75 lost conversations/month, × €60 average lead value = €4,500/month sitting inside the inbox the bottleneck reply is leaving behind. 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 one- and two-person shops.

Source · Oldroyd / Lead Response Management (the 5-minute response-window study) insidesales.com. Worked example, not a guarantee — substitute your own enquiries/mo and lead value to rerun.

Sample inputs

Monthly enquiries
300
Avg lead value
€60
Conversion gap
~25 pts
Reply floor
< 5 min

Worked loss

300 × 25% × €60 ≈ €4,500/month

Picking up where the reply-speed map leaves off

The map decides which lever to pull first. The build is what phones it home.

The four levers on this page are the same four the bot uses on a real engagement — and the same four the mapping call decides between during week one. The sibling pillar on cart recovery walks the parallel track for Shopify-style checkouts; the engagement shape on the pricing page covers how the build runs once the map is in hand.

FAQ

The questions a service SMB asks once they've read the four levers.

Quick answers about the 5-minute window, the €4,500 figure, the four lever names, and what the mapping call actually delivers. If yours isn't here, send it directly to hatchloom-5@polsia.app.

One mapping call away

Tell us how your inbox answers. The reply-speed map comes from there.

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 which of the four levers is the biggest leak on a two-person shop — and whether the engagement fits. See how the engagement runs on the landing page.

Start a mapping call

Replies in one business day, usually faster.