A $4M operator hires its first AI employee.
Hour by hour, here's a 30-day install on a composite pest-control shop — Maverick Pest Control, $4M, 14 trucks, owner-operator Sarah Kim. The intake. The rubric. The first call that paid for the install. The day-30 impact. And an honest “what broke.” It's a composite, not a real customer. Every number is illustrative.
It's an 8-minute read, right here. If the math looks like it could work for you, request a Revenue Leak Audit at the bottom and we'll model it against your actual numbers.
Synthetic use-case. “Maverick Pest Control” and “Sarah Kim” are composites — not a real customer. Every dollar figure is an illustrative range, not a promised outcome. What's real: the install sequence, the intake rubric, the integration steps, the decision logic. We publish it so you can see the actual work before you ever book a call.
The intake — Maverick Pest Control
Sarah Kim runs Maverick Pest Control out of suburban Atlanta. 14 trucks, 22 employees, $4M ARR — mostly recurring quarterly contracts with a long tail of one-time call-outs. She bought the business from the founder two years ago. The last six months, it's been flat.
The intake call runs 35 minutes and produces 11 numbers. The ones that matter:
The rubric scores the four levers (Acquisition, Retention, Pricing, Recapture) and ranks each AI employee — and the revenue loop it runs — by payback × confidence. You don't hire all of them at once. You start with the leak that costs the most. Sarah's top three, in order:
- 01
AI Front Desk — Missed-Call Recovery
A 32% voicemail rate at a $340 average ticket models out to roughly $48K/yr of after-hours calls walking out the door. Highest-confidence payback — so it goes first.
- 02
Multi-Channel AR Recovery
AR sits at 61 days against an industry 38. A modeled $80K–$120K is stuck in the receivables aging. Pull it forward and it could fund the next loop.
- 03
Recurring Revenue Health Monitor
Autopay churn is silent — failed cards, expired services, billing-address moves. 14% on a $1.4M recurring base models to about $196K/yr leaking out.
Rubric output: Hire employee #1 — the AI Front Desk — and ship it in 30 days. Layer in #2 on day 31. Re-run the intake at day 90 to score what's shifted.
Install + the first captured call
Days 1–3: stack mapping. Maverick runs ServiceTitan, a Vonage business line, and QuickBooks Online. The AI Front Desk wires into the existing phone number — no port required — and pushes captured leads into ServiceTitan as new opportunities, source tagged.
Days 4–5: training the agent. Marcus, Sarah's dispatcher, sits for 90 minutes and walks the AI through the decision tree he actually uses — emergency vs. non-emergency, recurring vs. first-time, the four quoting tiers, the escalation rule for a German shepherd in the backyard.
Day 6: soft launch, after-hours only. The AI picks up 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 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, texted Sarah 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.
Tuning the loop
Two weeks of after-hours captures: 47 calls handled, 31 booked. On day 14 we sit down with Sarah and Marcus and audit every call. The wins are obvious. The losses are interesting.
Three changes after the audit:
- 01The bee/wasp differentiator — the AI kept booking wasp calls into a Friday slot, but Marcus only runs the wasp crew Tues/Wed. Fix: train the AI on the real tech-skill calendar, not the generic appointment calendar.
- 02SMS callback for hangups — 6 callers hung up in the first 15 seconds (didn't like the AI voice, or impatient). We 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.
- 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: look up ServiceTitan customer records before quoting; on a hit, route to the recurring-customer flow (apologize for the miss, reschedule, no new opportunity created).
Day 21: full 24/7 cutover. The AI now handles every inbound call outside business hours, plus daytime overflow when Marcus is on another line.
The honest failures
No 30-day report is honest without this section. Five things that went wrong — and 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 reach the crawl space, drove away. Cost: $85 of unbillable truck time. Fix: a dog/livestock/access-issue qualifier, now a required field on any exterior inspection.
The voicemail-greeting trap
Day 9. Maverick forwarded an overflow line wrong, and the AI picked up Marcus's personal cell — then introduced itself as Maverick's front desk. Marcus's golf buddy was confused. Fix: an ‘is this a Maverick-owned line?’ check on phone-line provisioning.
ServiceTitan tag collisions
Day 12. The AI created duplicate opportunity records for one caller — two calls, two records, one customer. ServiceTitan dedupe missed them because the AI used slightly different phone-number formats. Fix: enforce 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. The AI asked for clarification four times, then transcribed the address wrong. The caller hung up. Fix: a confidence-threshold fallback that routes ambiguous calls to a callback queue instead of pushing through.
The $0 quote
Day 22. The AI quoted “$0” for a service the customer wasn't eligible for under the recurring plan. They thought it was a free visit. Fix: a hard quote-floor of $89 (minimum trip charge) plus 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.
Business impact — the dollar number
30 days after the AI Front Desk went live — the numbers from ServiceTitan and the call logs:
Annualized run-rate (modeled, conservative): $40K–$64K in incremental after-hours revenue alone, off a 30-day install. The AR and Recurring Revenue loops start in month 2, projected to add another $90K–$140K over the next 90 days. The install paid back in week 1 on the Tuesday-night rodent call. Everything after that compounds. These are illustrative ranges, not a promise.
Let's model the math on your actual numbers.
A thirty-minute install-fit call. Bring your call logs, your lead sources, your last 90 days of revenue. We'll run the same rubric we ran on Maverick and tell you what the loop could pay back — even if the answer is “not yet.”
Sarah's read, day 30
We asked Sarah what she'd tell another operator weighing the install. Lightly edited:
“The Tuesday-night rodent call paid for the whole thing. Everything after that is gravy. Marcus likes that he can actually go home at 5 and the phone doesn't follow him. I like not waking up to 6 voicemails I have to triage before the trucks roll. The audit in week 2 mattered — it's not magic, it's a system that has to be tuned to how we actually run. Now that it's tuned, it just does 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 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.