Step Out of the Truck Without Losing Control

01

Start with the reason to leave the truck

Kevin says he started his own plumbing work in 2007, then spent more than a decade combining it with 24-hour firehouse shifts. A 2018 injury forced him to stop and showed him how rarely he had been home with his wife and young children. He left the fire service in March 2019 and made the plumbing company his full-time work.

Those dates and circumstances are Kevin's episode-time account. The useful operating question is personal but concrete: what should leaving the truck make possible? Kevin names family time and extended summer travel. Another owner may need space for health, sales, management, or succession. Write the outcome before choosing headcount or software.

Turn the reason into a constraint. Define how many field days the owner will reduce, which hours stay protected, what emergency can interrupt them, and what operating evidence must exist first. A vague wish to work less loses every argument with a full schedule; a dated transition with safety and service conditions can drive the hiring plan.

02

Define the workload before adding a truck

At recording time, Kevin says two trucks had operated for more than five years and that filling the third had been the hardest step. That does not establish the company's current staffing or prescribe three trucks for another shop. It identifies a capacity decision that should be proved with demand, not hope.

Track calls by type, booked and completed jobs, schedule delay, declined work, average labor hours, callback time, travel, after-hours load, and the owner's actual field contribution. Then model the next seat with wages, payroll costs, recruiting, licensing, truck, tools, insurance, training, supervision, marketing, working capital, and ramp time. Avoid promising that the hire will pay for itself on a fixed date.

Check South Carolina and local licensing requirements for the work and supervision involved; do not infer qualification from a podcast title. Define the new technician's scope, the jobs that require escalation, the trainer, the quality review, and the minimum demand threshold. Hiring creates capacity only when the surrounding system can feed and support the person.

03

Coach technicians to propose the next move

Kevin says he had trained technicians to lean on him by going to rescue them whenever a problem appeared. During time away, he changed the conversation: tell me how you plan to fix it, and I will confirm the plan or ask you to rethink it. That keeps a decision boundary without taking the problem back.

Build a small decision ladder. The technician handles work inside documented scope, proposes an option for unfamiliar but nonurgent conditions, and immediately escalates safety, code, property-damage, customer-vulnerability, or authorization risks. Give the field team access to current manuals, job history, photos, approved materials, price rules, and an on-call person who can actually respond.

Review calls after the job. Record the condition, options considered, chosen action, evidence, result, and whether the playbook changes. Using coaching to break the owner bottleneck adds a broader lesson: coaching works when it changes an observable decision, not when the owner attends an event and returns to the same rescue pattern.

04

Create office time before making a full exit

Kevin's near-term goal was to reduce field hours enough to spend two days a week in the office, with a full truck exit tied to another trained plumber. That staged design is stronger than disappearing from the schedule at once. It creates protected time to build the very systems the transition requires.

Give each office block an output: review callbacks, reconcile sold and completed work, inspect job files, coach one person, document a repeated exception, forecast staffing, or audit the coming schedule. If the time is absorbed by email and emergencies, the owner has changed location but is still doing reactive work inside the business.

Measure field days, owner-only decisions, after-hours interruptions, open corrective actions, and documentation completed. Move one recurring responsibility at a time, confirm the new owner can perform it, and retain a review rhythm. A full exit should be the result of proven handoffs rather than a title change.

“I can actually work on the business instead of working in the business.”

Kevin Babb, episode timestamp 07:19

05

Move calls out of the family bottleneck

Kevin says hiring a customer-service representative meant his wife no longer had to answer every incoming call and could focus on back-office work. That is an episode-time description, not a current staffing claim. It shows how an office hire can release capacity even when the founder's visible problem appears to be in the field.

Write the call flow before handing it off. Define greeting and disclosure, service area, emergency and safety routing, work the company declines, booking windows, membership or warranty lookup, pricing boundaries, reschedules, upset-customer escalation, after-hours coverage, and the record that reaches dispatch and the technician. Protect payment, address, recording, and customer data according to current requirements.

Audit a sample of calls and downstream jobs together. Did the caller understand the next step? Did the booking contain the facts the technician needed? Was an urgent condition routed correctly? Documenting a home-service business to scale can turn repeated call and dispatch misses into owned checklists rather than family memory.

06

Test time away in controlled runs

Kevin describes a two-week family trip as both relief and a stress test. A recently hired third plumber quit during the trip, while the remaining operation continued to answer calls and handle problems. That is his account of one absence; it does not prove the company can now run without him for any duration.

Test one afternoon, then one day, a weekend, and a working week. Before each run, name schedule ownership, field escalation, customer recovery, payment and purchasing limits, on-call coverage, employee absence coverage, and who can contact the owner. Keep a log of interruptions, near misses, customer effects, and decisions that stalled.

Do not judge the test only by whether revenue arrived. Review safety, callbacks, aged work, schedule changes, staff load, cash exceptions, and customer complaints. Repair one failure mode before extending the absence. Freedom built this way is a reliability exercise, not an optimistic vacation booking.

“I can leave and the company's still running.”

Kevin Babb, episode timestamp 16:20

07

Evaluate AI after designing the service

Near the end, Jim asks about AI phone answering and makes broad claims about cost, availability, human likeness, and performance. Kevin says he had not thought much about it, prefers a live person, and would need considerable persuasion. Treat Jim's claims as promotional and speculative, not verified evidence that AI performs better or is appropriate for this company.

Start with the call flow and risk categories, then compare human, answering-service, and automated options against the same test. Evaluate caller disclosure and consent, privacy, recording, accessibility, emergency language, service-area accuracy, hallucinated commitments, scheduling rules, payment handling, human escalation, outage behavior, logs, vendor access, retention, and quality review. Check current law and contracts with qualified advisers.

Pilot only low-risk scenarios with a clear escape to a person. Use representative calls, including accents, background noise, stressed customers, vague symptoms, and unsupported requests. Measure correct routing and harmful misses, not just answer rate or labor cost. A tool is useful when it improves the designed service without hiding new risk from the caller.

08

Protect freedom with routines and measures

A business does not stay independent of its owner because one technician was hired. Install routines that keep the handoffs healthy: a daily schedule and exception review, weekly callback and job-file review, monthly staffing and cash forecast, regular field coaching, and a named backup for every critical office and field responsibility.

Track owner field hours, owner-only decisions, on-call interruptions, unfilled capacity, callbacks, overdue invoices, schedule delay, and planned versus actual time away. Interpret the measures together. Fewer owner calls may be progress, or it may mean the team stopped escalating. Quality and customer evidence must accompany the freedom metric.

If broader expansion becomes the goal, building systems before franchising a service business explains why founder independence must be proven before replication. Kevin's episode ends earlier in that journey: a working owner creating enough staffing, judgment, and office structure to be present with his family without abandoning customers or the team.