Composite case · 30-day install · 28 pages
Day 0 → Day 30 · free to read · no email required

What happens when a $4M operator installs the play.

Hour-by-hour walkthrough of a 30-day install on a composite pest-control SMB — Maverick Pest Control, $4M, 14 trucks, owner-operator Sarah Kim. The intake, the rubric output, the first call that paid for the install, the day-30 impact, and an honest “what broke” section.

Read it on this page in about 8 minutes. If the math looks like it could work for your business, request a Revenue Leak Audit at the bottom and we'll model it against your actual numbers.

About this report

Synthetic use-case. “Maverick Pest Control” and “Sarah Kim” are composites — not a real customer. Dollar figures are illustrative ranges, not promised outcomes. What's real: the install sequence, the intake rubric, the integration steps, and the decision logic. We publish it so operators can see the work before they book a call.

Day 0

The intake — Maverick Pest Control

Sarah Kim runs Maverick Pest Control out of suburban Atlanta. 14 trucks, 22 employees, $4M ARR — mostly recurring quarterly service contracts with a long tail of one-time call-outs. She acquired the business from the founder two years ago and has been running flat for the last six months.

The intake call is 35 minutes and produces 11 numbers. The interesting ones from Sarah's business:

32%
of inbound calls after 5pm hit voicemail
61 days
average AR aging
$2,220
average lifetime value, recurring customer
14%
annual churn on autopay contracts
42 min
median lead-to-first-touch on web forms
$340
average ticket on one-time call-outs

The rubric scores the four levers (Acquisition, Retention, Pricing, Recapture) and ranks the loops by payback × confidence. Sarah's top three, in order:

  1. 01

    AI Front Desk — Missed-Call Recovery

    32% voicemail rate + $340 avg ticket = ~$48K/yr of after-hours calls walking. Highest-confidence payback on the install.

  2. 02

    Multi-Channel AR Recovery

    AR at 61 days vs. industry 38. Net $80K–$120K of cash stuck in the receivables aging — pulling it forward funds the next loop install.

  3. 03

    Recurring Revenue Health Monitor

    Autopay churn is silent — failed cards, expired services, billing-address moves. 14% on a $1.4M recurring base = $196K/yr leaking.

Rubric output: Ship loop #1 in 30 days. Layer in #2 starting day 31. Re-run intake at day 90 to score what's shifted.

Week 1

Install + the first captured call

Day 1–3: stack mapping. Maverick is on ServiceTitan + a Vonage business line + QuickBooks Online. The AI Front Desk wires into the existing phone number (no port required) and pushes captured leads into ServiceTitan as new opportunities with the source tagged.

Day 4–5: training the agent. Sarah's dispatcher Marcus sits for 90 minutes and walks the AI through the decision tree she actually uses — emergency vs. non-emergency, recurring customer vs. first-time, the four quoting tiers, the escalation rules for a German shepherd in the backyard.

Day 6: soft launch on after-hours only. The AI picks up calls between 5pm and 8am. Live calls during business hours still go to Marcus.

Tuesday night, Day 7 — the $2,220 call. 9:47pm. A new customer found Maverick on Google and called about a rat infestation in the attic. Pre-install: voicemail, callback tomorrow, 50/50 they'd book with the next vendor on the list. Post-install: the AI answered, qualified the rodent exclusion scope ($340 inspection → $1,880 full exclusion → recurring quarterly $80/mo), booked the inspection for 8am the next morning, texted Sarah with the booking, and dropped a contact card in ServiceTitan tagged “after-hours web”. The job closed Thursday. One call. $2,220 lifetime value. The install just paid for itself.

Weeks 2–3

Tuning the loop

Two weeks of after-hours captures, 47 calls handled, 31 booked. We sit down with Sarah and Marcus on day 14 and audit every call. The wins are obvious. The losses are interesting.

Three changes after the audit:

  1. 01The bee/wasp differentiator — the AI kept booking wasp calls into a Friday slot, but Marcus only runs the wasp tech crew Tues/Wed. Fix: train the AI on the actual tech-skill calendar, not the generic appointment calendar.
  2. 02SMS callback for hangups — 6 callers hung up on the AI in the first 15 seconds (didn't like the AI voice, or impatient). Added a 2-minute-delay SMS: “Sorry we missed you — text us the address and we'll book the visit.” Recovered 4 of the 6.
  3. 03Existing-customer handoff — 3 recurring customers called after-hours about a missed quarterly service, and the AI tried to book them as new leads. Fix: lookup against ServiceTitan customer records before quoting; if hit, route to recurring-customer flow (apologize for the miss, reschedule the service, no new opportunity created).

Day 21: full 24/7 cutover. The AI now handles all inbound calls outside business hours and overflow during the day when Marcus is on another line.

What broke

The honest failures

No 30-day report is real without this section. Five things that went wrong, what we did about each:

  • The German shepherd in the backyard

    The AI booked an inspection without flagging the dog. The tech showed up, couldn't access the crawl space, drove away. Cost: $85 of unbillable truck time. Fix: added a dog/livestock/access-issue qualifier as a required field for any exterior inspection booking.

  • The voicemail-greeting trap

    On day 9, the AI picked up Marcus's personal cell when Maverick forwarded an overflow line incorrectly. The AI introduced itself as Maverick's front desk. Marcus's golf buddy was confused. We added an ‘is this a Maverick-owned line?’ verification on phone-line provisioning.

  • ServiceTitan tag collisions

    On day 12, the AI created duplicate opportunity records for the same caller (two calls, two records, one customer). ServiceTitan dedupe wasn't catching them because the AI was using slightly different phone-number formats. Fix: enforced E.164 normalization on the AI side.

  • The accent the AI couldn't follow

    Day 16, an elderly caller with a strong rural Georgia accent tried to book a hornet removal and the AI asked for clarification four times before transcribing the address wrong. Caller hung up. We added a confidence-threshold fallback that routes ambiguous calls to a callback queue instead of pushing through.

  • The $0 quote

    On day 22, the AI quoted “$0” for a service the customer wasn't eligible for under the recurring plan. Customer thought they were getting a free visit. Fix: hard-coded a quote-floor of $89 (minimum trip charge) and a script for explaining recurring-plan exclusions instead of returning zero.

None of these were catastrophic. All of them were tuneable. The install isn't “set and forget” — weeks 1–3 are real tuning work, which is why we own that window on a managed install.

Day 30

Business impact — the dollar number

30 days after the AI Front Desk went live, the numbers from ServiceTitan and the call logs:

218
after-hours calls captured (vs. 0 baseline)
151
booked appointments from those calls
$47K
new revenue booked from after-hours captures
$3,420
MRR added from new recurring customers
11 days
AR aging improvement (61 → 50, partial run)
0
missed emergency dispatches (vs. 8 baseline/mo)

Annualized run-rate (conservative): $40K–$64K in incremental after-hours revenue alone, on a 30-day install. AR + Recurring Revenue loops start month 2, projected to add another $90K–$140K over the next 90 days. The install paid back in week 1 with the Tuesday-night rodent call. Everything after that is compounding.

Does your business look anything like Maverick's?

Let's model the math on your actual numbers.

Thirty-minute install-fit call. Bring your call logs, your lead sources, and your last 90 days of revenue. We'll run the same rubric we ran on Maverick and tell you what the loop would actually pay back — even if the answer is “not yet.”

CEO verdict

Sarah's read, day 30

We asked Sarah what she'd tell another operator considering the install. Lightly edited:

“The Tuesday night rodent call paid for the whole thing. Everything after that has been gravy. Marcus likes that he can actually go home at 5 and the phone doesn't follow him. I like that I'm not waking up to 6 voicemails I have to triage before the trucks roll. The audit thing in week 2 was important — it's not magic, it's a system that needs to be tuned to how we actually run. Now that it's tuned, it's just doing the work. Next loop starts next month.”

Next 30 days: install the Multi-Channel AR Recovery loop and wire it into QuickBooks Online + Maverick's Twilio account. Re-run the intake at day 90 to score what's shifted.

What's synthetic, what's real.

  • Real: the install sequence, the rubric, the integration map (ServiceTitan + Vonage + QBO), the audit cadence, the failure modes, the AI tuning approach.
  • Real: the dollar ranges are calibrated to operators we've modeled in this size band ($3M–$6M home services with recurring revenue).
  • Synthetic: “Maverick Pest Control,” “Sarah Kim,” the specific calls, the exact dollar amounts. Composite, not customer.
  • Not a guarantee: your numbers will differ. The same install on a $1M operator pays back slower; on a $10M operator, faster.

Ready to find out what this looks like on your numbers?

Book a Free Revenue Leak Audit. We'll bring the rubric, you bring the call logs and lead sources. You leave with three ranked install candidates and a straight answer on whether the math pencils. No deck, no pitch, no follow-up sequence.

Honest go / no-go at the end. We'll tell you if your vertical or revenue stage isn't a fit for the install instead of selling you something that won't work.