Plumbing $1.4M revenue Mid-Missouri

The $8,400/month that was hiding in voicemail.

How a six-person plumbing contractor stopped losing jobs to missed calls in the first four weeks — without hiring a receptionist, buying new software, or learning anything new.

Leak found
$8,400/mo
Across 3 line items
Time to recovery
4 wks
From audit to first dollar
Owner hours
0/wk
Ongoing management
Industry
Residential plumbing
Revenue
$1.4M annual
Team
6 techs · 1 owner
Stack
Jobber · QuickBooks

The situation

The owner — we'll call him Mike — had been running the business for eleven years. Six techs, one truck each, steady residential work in the Columbia area. Revenue was flat at $1.4M for three years running, and he'd started to notice something: he was losing jobs he used to win. Regular customers were calling the big national brand instead. New leads weren't converting like they used to.

He assumed he had a marketing problem. He didn't. He had a phone problem.

What we found

Mike's answering service kicked in after four rings. Calls between 5pm and 7am went to voicemail. Voicemails were checked once the next morning — if the dispatcher remembered. Estimates sent out on Tuesday were forgotten by Friday unless the customer called back. Nothing was nefarious. It was just the normal entropy of a small business where everyone's already doing the job of 1.5 people.

Leak Monthly cost
Missed calls after 5pm and before 7am (avg 47/mo, ~28% booking rate)
$3,200
Estimates sent and never followed up (14+ days cold, avg 11/mo)
$4,100
Rescheduled jobs drifting out of the week they were booked for
$1,100
Total monthly leak
$8,400

The worst part: Mike had suspected most of this. He just didn't have a number.

What we built

Nothing new for Mike to learn. No dashboard, no training. We worked inside the stack he already had — Jobber for scheduling, QuickBooks for money — and wrapped automation around the gaps.

1

AI after-hours answering

A voice agent picks up any call outside business hours, qualifies the job, books straight into Jobber. Hands off to a human on emergency keywords.

Built on · existing Jobber API
2

Estimate follow-up automation

Every estimate triggers a 3-touch cadence over 10 days — SMS, email, call. Customer replies cut the cadence. Closed-won auto-tags the record.

Built on · Jobber + Twilio
3

Schedule-drift alerts

Any booked job that slips past its original week pings the dispatcher with context. Most were getting buried under emergency add-ons.

Built on · internal rule engine

What happened

Week one of month two: the AI agent booked seven calls that would have gone to voicemail. Week three: two estimates from the prior month that had gone cold came back as signed jobs — both said the follow-up was the reason. By the end of month one, Mike was break-even on the retainer. Month two was pure upside.

Recovered, month two
$8,400/mo

Full leak closed by week four. Month three tracked at $9,100 recovered as the follow-up cadence matured. Owner time spent managing the build: zero.

They found $8,400 a month I didn't know I was losing. Month one I was breaking even on the retainer. Month two it was pure upside. And I didn't have to learn a single new piece of software.
"Mike" Owner · Mid-Missouri plumbing contractor · $1.4M

What's next

Mike renewed the retainer for month six. We're now looking at the owner-bottleneck column: the dozen decisions a day that only he can make. That'll be the next case study.

Names and a few identifying details have been changed. Dollar amounts, timelines, and the build are as they actually happened.
Your turn

What's your number?

One paid audit. One week. Every leak in your business, named in dollars.