Don't Add a Second Truck Until You Fix Your First One

The calls are stacking up. You're turning away work on Tuesday afternoon. Your guy is booked three weeks out and the phone keeps ringing. Every instinct you have says the answer is another truck, another tech, another set of hands on the road.

That instinct is responding to the wrong signal.

Your Lead Volume Is Not the Problem

Before I launched Reeves Electric in February 2022, I spent four months planning. Pricing model, software stack, intake script — I thought I'd mapped every variable. I had not planned for the fact that I was now the person returning the irritated 9:30pm callback from a customer whose breaker kept tripping, and I didn't yet know why those calls kept coming in the first place.

Month two, my NPS was a 4. Not 40. Four.

That wasn't a staffing problem. What I had was a systems problem wearing a volume costume. The phones were ringing, work was getting done, and something in the middle was broken in ways I couldn't see because I wasn't measuring any of it.

So I did ninety days of answering every call myself, taking notes, rebuilding the intake process from what I actually heard. By month nine, NPS was 81. Same market. Same services. No second truck. Just the first one running the way it was supposed to run.

The lesson wasn't that I was bad at my job. It was that "we're turning away work" almost never means what you think it means in the first year. It usually means the first operation isn't clean enough to see clearly yet.

What "Running Well" Actually Means

"Running well" is a set of numbers you can read on a Tuesday morning in under 20 minutes. Not a feeling.

Here's the minimum threshold I'd use.

You know your booking rate by source. Specifically — you know that calls from Google LSA booked at 38% last month and calls from organic search booked at 61%, and you know the average job value from each. You know your call-to-dispatch cycle time. You know what percentage of jobs required a callback after close, and why.

If you're not on CallRail (or something equivalent), you don't have these numbers. You have impressions. Impressions are not a system.

Every week, I sit down with my dispatcher and we listen to four calls. Two that booked, two that didn't. We tag what happened. Did the customer hang up because we quoted three weeks out? Did the price objection hold because the person on the phone stumbled through the estimate? You find things you'd never guess without listening back. Forty minutes a week. That practice did more for Truck 1's performance than any marketing spend I've run.

The reason most first trucks aren't actually running well is simple: the owner has never calculated their booking rate. They set up CallRail and stopped checking it. If you can't say what percentage of your booked revenue last quarter came from which channel at what booking rate, you don't have a system. You have a run of good luck you can't explain or protect.

Adding a Second Truck Before You're Ready Just Multiplies the Chaos

A broken intake process running across two trucks isn't twice as good. It's twice as broken, and now twice as hard to diagnose because the signal is scattered across two techs, two schedules, two sets of customer interactions.

I spent seven years at Lonestar Electrical Services, a 40-truck commercial outfit. I watched what happens when you scale before you systematize. Problems that were manageable early became structural as headcount grew — embedded in every workflow, every hire, every customer expectation by the time anyone admitted they existed.

And I think about what would have happened if I'd added a second truck in month two of Reeves Electric. I was personally taking the 9:30pm callback and I still didn't understand why those calls were coming in. A second truck would have meant more callbacks, more customers with misaligned expectations, more month-two NPS scores. The problem wasn't capacity. I just hadn't done the diagnostic work yet.

A second truck amplifies what's already there. If what's already there is chaos you're carrying in your head — that does not go better at scale.

What Happened When I Almost Hired Truck 3 Too Early

In late 2023, everything looked right on the surface. Revenue was up, lead volume was healthy, and I was turning away work whenever both trucks were already dispatched.

But I was also still personally carrying about 20 hours a week of admin — payroll, invoicing, scheduling gaps, slow-pay receivables. I hadn't hired the part-time bookkeeper yet. I hadn't hired the CSR backup.

I was reading "I'm overwhelmed" as a revenue problem. It wasn't.

What actually surfaced: during a weekly call review, my dispatcher flagged something about Truck 2. Four calls in three weeks where the customer asked about timeline and got "we'll get you on the schedule" instead of a committed window. Two of those four didn't book. We'd never noticed because we were looking at total booking rate, not per-tech breakdown. Truck 2 had a specific intake gap that had been sitting there for probably six weeks.

If I'd hired Truck 3 before catching that, I'd have onboarded a new tech into a dispatch workflow with a known problem I hadn't fixed. He'd have learned the wrong habits from day one.

What I did instead: hired the bookkeeper. Six weeks later, with clean books and 10 hours a week back, I hired a part-time CSR. Spent a month on the Truck 2 intake issue. Then evaluated Truck 3. The sequencing mattered.

Bookkeeper first. Every time. I couldn't see my actual throughput ceiling while I was drowning in payroll and receivables. The ceiling was there. I just couldn't locate it.

Your Throughput Ceiling Is the Real Number to Watch

A full phone line and a broken intake process are different problems. I've pulled call recordings that told a completely different story than the summary I got from my dispatcher. "Customer wasn't available for three weeks" turned into "we never asked what their actual timeline was." That's not a capacity problem.

The owner who tells me "we're turning away work" — I immediately want to know whether that turned-away work was actually qualified. Or is some portion of it friction in the intake call creating a false ceiling? A customer who gets a 3-week-out answer and hangs up isn't necessarily a lost lead due to capacity. Sometimes nobody offered an interim option, or nobody asked the right questions to find out what was actually urgent.

Here's the cadence I run:

Weekly numbers review — booking rate by source, average job value, callbacks, receivables aging. Takes 25 minutes. Monthly P&L close within 5 business days of month end. Quarterly planning block, 2-3 hours, just me and a spreadsheet.

If you're not running something like this on Truck 1, you won't see the throughput ceiling coming. You'll confuse a fixable system problem with a capacity problem and solve it by adding a truck.

The question isn't complicated. It's: do you actually know what Truck 1 is doing, in numbers, on a weekly basis? If no, you're not ready to add Truck 2. You're adding another thing you won't be able to measure.

What to Do Next Monday Morning Before You Post That Job Ad

Pull your last 30 days of call recordings and calculate your actual booking rate by source. If you're on CallRail, this is a two-hour exercise. If you're not on CallRail, that's the first fix — not the job ad. The $50 to $150 a month is not the question. The question is whether you can see Truck 1 clearly enough to know what you'd be replicating.

Run the admin hours math. How many hours a week are you personally on payroll, invoicing, and receivables? Multiply that by what it's actually worth to the business when you're quoting complex jobs instead. If that number exceeds the cost of a part-time bookkeeper and a part-time CSR, you know what comes before the second truck.

Sit with your dispatcher and listen to four calls from last week. Two booked, two didn't. Tag what happened. Write it down. This 40-minute exercise will tell you more about whether Truck 1 is ready than any revenue number will.

Run one month of the ops cadence before you hire. Weekly numbers, one P&L close. If you can't sustain that on a single truck for 30 consecutive days, adding a second truck adds operational noise, not operational capacity.

The second truck is not a bad idea. The second truck before you can actually read the first one — that's the move that costs you.

---

FAQ

How do I know if my first truck is actually performing well or if I'm just used to it?

You need a number, not a feeling. Pull your booking rate from last month — calls received versus jobs booked — broken out by where the call came from. If you can't produce that in under an hour, you don't have a performance baseline, you have familiarity. Do the weekly call-review exercise for four consecutive weeks: two booked calls, two unbooked calls, tagged for what happened. If you find nothing to fix, your truck is probably running well. Nobody finds nothing.

What's a realistic booking rate benchmark for a residential electrical service truck?

I don't have a clean number I'd stake anything on here. What I can tell you from Reeves Electric is that inbound calls from organic search book significantly better than inbound from LSA — the intent and trust level coming in are just different, and in my experience the gap has been material, sometimes 20-plus points depending on the month and the call sample. Track your own rate by source for 90 days before you benchmark against anything external. Your number, measured consistently, is more useful than an industry average you can't verify.

What if I have the leads but literally can't fulfill the work with one truck — isn't that a real capacity problem?

Sometimes. But before you call it a real ceiling, pull a month of calls that didn't book and categorize why. If the overwhelming majority are genuine timeline declines — customer needed someone this week, you were booked out — that's a capacity signal. If the pile is mixed: some timeline, some price objections, some where nobody ever followed up, that's a different problem and adding a truck doesn't solve it.

Should I hire the second technician before or after I have the systems documented?

After — not fully documented, because that's a project that never actually ends, but your intake script, dispatch workflow, and job-close quality check need to exist in a form a new person can be trained on. Not observed. Trained on. If the system lives entirely in your head, you're not hiring someone into a system. You're hiring someone to watch you and figure it out. That occasionally works with a great hire. It doesn't work reliably.

How long should I expect it to take to get Truck 1 genuinely dialed in before scaling?

If you're running the weekly call review, the monthly P&L close, and actively working your intake process — six to nine months to have something genuinely replicable. It took me about seven months to get from an NPS of 4 to a system I could actually write down and hand to someone. You might be faster with cleaner starting conditions. But 60 days isn't enough. You can't document what you don't yet know you're doing wrong.

What's the one metric I'd look at first to decide whether I'm ready to add a truck?

Booking rate by source, specifically whether it's been stable or improving for at least three consecutive months. Revenue going up by itself isn't the signal — revenue can rise while booking rate falls if lead volume is climbing faster than your conversion. If your booking rate has been consistent and you've already addressed the admin and scheduling drag on Truck 1, you're at a real capacity ceiling. If it's still moving around month to month, you have a systems problem. Adding a truck right now just adds more calls to a process that isn't settled yet.