FAQ-coverage map, mapped before it ships
For service small businesses

~60% of repeat asks hit the same five questions —the FAQ the site content left open replies on, by hand, every time.

On a typical service SMB the same five-to-seven questions (hours, sizing, returns, warranty, shipping cutoffs) reappear roughly a hundred times a month — the site content covers ~20% of them, the rest land in the inbox as a thread the team answers by hand each time. Combined with the ~1-in-3 after-hours overlap, the gap adds up to a ~€4,500/month leak on the worked-loss side. Hatchloom maps the FAQ the visitor expected a reply on, then ships the four-leverage bot — captured map, written FAQ, same-minute reply, after-hours coverage — that closes the leak.

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

Unanswered share
~60% repeats
Built around
A custom map
Mode
FAQ gap map
~€4,500/month missed-questions leak
300 enquiries · €60 lead value

Leak on the line

~€4,500/month

of service-avoidable loss sitting inside the FAQ the site content left open on a one-person service shop — 60% of repeat asks targeted at the same five questions, ~20% covered by site content, the other ~40% answered by hand each time. Recoverable, once the FAQ-coverage map 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.

Unanswered share
~60%
Repeat-ask share
~100/mo
If unaddressed
€4.5K/mo

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

The four findings the brief surfaces

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

Missed-questions loss on a service-SMB inbox is not a single problem. It is four leaks at once — the after-hours thread that arrived when the team was off, the FAQ the site content left open, the ~100 repeats a month that drove triage minutes into the morning, and the worked dollar-loss the same pattern rolls up to. The map finds them; the build closes them.

01
After-hours gap — the 6 pm to 9 am weekday + weekend thread the team opens on Monday
Roughly one in three service enquiries lands outside the founder's working hours — between 6 pm and 9 am on a weekday, plus most of the weekend. The team opens Monday with a flat queue of threads the visitor expected a reply on at 9 pm the night before. The map catches it by sizing the overlap against the working calendar, not by guessing:
02
FAQ-coverage failure — the same five questions, asked in roughly the same order, missing the same way
On a typical service SMB, ~60% of the repeat asks target the same five questions — hours, sizing, returns, warranty, shipping cutoffs. The site content covers ~20% of them; the rest land in the inbox as a thread the team answers by hand each time. The map draws the gap between what's covered and what's asked; the build closes the missing rows.
03
Repeat-ask volume — ~100 repeats a month of the same five-to-seven questions, on a flat inbox the team triages by hand
On a typical service SMB the same five-to-seven questions reappear roughly a hundred times a month — minutes of triage that, on a flat inbox, the team eats each time. Once the FAQ-coverage map is in place, the same replies are answered by the bot on arrival: the visitor gets the answer, the team reads only the threads that need a human.
04
Worked dollar-loss — the ~€4,500/month in lost enquiries the FAQ map recovers before launch
Take a service SMB with 300 service enquiries a month, a 25-percentage-point conversion gap between enquiries answered inside five minutes and enquiries answered hours later, and a €60 average lead value. With 60% of repeat asks targeted at the same five questions the site content leaves unanswered, the lost enquiries that fall out of the slower bucket — 300 × 25% — is 75 lost conversations/month, × €60 average lead value = €4,500/month. The same arithmetic is spelled out one section below; substitute your own enquiries/mo and lead value to rerun.

The arithmetic, with assumptions spelled out

How a one-person service shop arrives at the ~€4,500/month missed-questions leak.

Take a one-person service shop with roughly 300 service enquiries a month and a €60 average lead value. Stack the missed-questions failure on top of the reply-speed leak: with ~60% of repeat asks targeted at the same five questions (hours, sizing, returns, warranty, shipping cutoffs) and the site content covering only ~20% of them, ~40% of replies land in the inbox as a thread answered by hand each time; the after-hours share (~1 in 3) compounds it by an additional margin. 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 at 300 × 25% — 75 lost conversations/month, × €60 average lead value = €4,500/month. 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 service SMBs.

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
FAQ repeat-ask
~60%
Reply floor
< 5 min

Worked loss

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

Picking up where the FAQ map leaves off

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

The four findings on this page are the same four the bot 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 cart recovery walks the SMS-side version of the same overlap; 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 findings.

Quick answers about the after-hours overlap, the ~60% FAQ-coverage failure, the ~100 repeats a month, and the ~€4,500/month worked loss. If yours isn't here, send it directly to hatchloom-5@polsia.app.

One mapping call away

Tell us how your inbox answers. The FAQ-coverage 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 findings is the biggest leak on a one-person service 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.

Want more revenue-recovery tips?

Get more revenue-recovery tips, one short email at a time.

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

Revenue-recovery tips, monthly
A short, occasional email when we ship a new cart-recovery teardown, lever, or worked example. No spam, no retargeting.