After-hours window, mapped before it ships
For 2-person service shops

Roughly 1 in 3 enquiries land between 6 pm and 9 am— a 24/7 AI agent is what catches the after-hours thread the founder wakes to.

On a typical 2-person service shop, roughly one in three service enquiries lands after the founder has closed for the day — between 6 pm and 9 am on a weekday, plus most of the weekend. A meaningful share of those after-hours threads carry purchase intent (close-to-purchase pricing and availability questions, not browsing). Stack the morning-handoff gap on top, and the worked-loss arithmetic rolls up to ~€4,500/month on a 2-person service shop — the same envelope the /slow-reply, /missed-questions, and /process-breakdown pillars each describes from a different angle. Skip the morning handoff and the email lands in a flat queue; ship the 24/7 agent and the visitor wakes up to a thread that already moved forward.

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

After-hours share
~1 in 3 enquiries
Built around
A custom map
Mode
24/7 AI, morning handoff
~€4,500/month after-hours worked loss
300 enquiries · €60 lead value

Leak on the line

~€4,500/month

of service-avoidable loss sitting inside the after-hours window on a 2-person service shop — ~1 in 3 enquiries land between 6 pm and 9 am on a weekday, plus most of the weekend, and a meaningful share carry purchase intent. The morning-handoff fallback lands the full transcript in the owner's inbox by 9 am; the thread the visitor expected a reply on at 11 pm the night before is the conversion that walked without it. 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.

After-hours share
~1 in 3
Morning handoff
by 9 am
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 the after-hours window — each one buys back a slice of the morning.

After-hours loss on a 2-person service shop is not a single problem. It is four leaks at once — the after-hours share itself, the late-night intent that compounds on top of it, the morning-handoff fallback the team opens to, 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, /missed-questions, and /process-breakdown pillars each describes from a different angle.

01
After-hours share — the 6 pm to 9 am weekday + weekend window that compounds every other leak
Roughly one in three service enquiries on a 2-person shop lands after the founder has closed for the day — 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 same ~1-in-3 share is the spine of the /slow-reply, /missed-questions, and /process-breakdown pillars, because compounding it against the other leaks is what produces the ~€4,500/month worked-loss envelope. The map sizes the overlap against the working calendar; the build closes the after-hours window on the visitor's clock, not the team's.
02
Late-night intent — the meaningful share of after-hours threads carry purchase intent, not browsing
A meaningful share of those after-hours threads carry purchase intent — close-to-purchase pricing/availability questions, not browsing. The visitor who messages at 11 pm to ask if a slot is still open next week is signalling readiness to buy; the thread that arrives Sunday night and waits until Tuesday morning for a human reply is the conversion that walked. The map sizes the after-hours intent against the helpdesk + CRM the team already keeps; the build installs the 24/7 agent that catches the thread on arrival, the same way the /slow-reply pillar catches the five-minute reply inside business hours.
03
Morning handoff — the full transcript landed in the owner’s inbox by 9 am, not a flat after-hours queue
The 24/7 agent's job at 6 am is not to reply to every thread — it's to escalate the ones that need a human, with the full transcript in the owner's inbox by 9 am. The team opens the morning with the thread already context-loaded: who messaged, what they wanted, which FAQ was answered, which thread needs a real reply. The escalation path is the same one the /process-breakdown pillar wires to the silent-drop map — a sorted queue instead of a flat inbox, with the after-hours thread pinned to the top because that's what the visitor expected a reply on at 11 pm the night before.
04
Worked dollar-loss — the ~€4,500/month the after-hours map recovers before the bot ships
Take a 2-person service shop with 300 service enquiries a month, a 25-percentage-point conversion gap between threads answered inside five minutes and threads that wait hours / until morning, and a €60 average lead value. Apply the Oldroyd / Lead Response Management floor that a reply inside five minutes qualifies at a radically higher rate than a reply hours later. The lost threads the after-hours window leaks — 300 × 25% — is 75 lost conversations/month, × €60 average lead value = €4,500/month. The arithmetic is spelled out one section below; substitute your own enquiries/mo and lead value to rerun against your operation.

The arithmetic, with assumptions spelled out

How a 2-person service shop arrives at the ~€4,500/month after-hours leak.

Take a 2-person service shop with 300 service enquiries a month and a €60 average lead value. Apply the after-hours share (~1 in 3) and the late-night intent on top — a meaningful share of those threads carry purchase intent rather than browsing. 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 / next-morning bucket. The lost threads the after-hours window leaves behind — 300 × 25% — is 75 lost conversations/month, × €60 average lead value = €4,500/month sitting inside the after-hours 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) 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
After-hours share
~1 in 3
Reply floor
< 5 min

Worked loss

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

Picking up where the after-hours map leaves off

The 24/7 agent catches a different leak on every pillar — but the morning handoff is shared.

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 missed questions walks the FAQ-coverage version of the same leak; the SMS-side version lives on cart recovery; how this stacks up against off-the-shelf tools lives on compare. The engagement shape on the pricing page covers how the build runs once the map is in hand — and the process breakdown pillar covers the four-finding map that decides which leak to tackle first.

FAQ

The questions a 2-person shop asks once they've read the four findings.

Quick answers about the after-hours share, the late-night-intent thread, the ~€4,500/month worked loss, and how the 24/7 AI agent + morning-handoff handoff actually work. If yours isn't here, send it directly to hatchloom-5@polsia.app.

One mapping call away

Tell us how your operation closes at 6 pm. The after-hours 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 how much of the ~€4,500/month after-hours 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.

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.