Your Software Stack Was Built for a Bigger Shop Than Yours

When I was at Lonestar Electrical Services, a 40-truck commercial outfit in Austin, we had a guy named Derek whose entire job was the software. Not dispatch, not estimating — the software. He maintained the workflows, trained new hires on the platform, and sat in a conference room once a quarter with the vendor's customer success team. Derek was good at his job. Derek cost the company somewhere north of $65,000 a year plus benefits.

When I launched Reeves Electric in February 2022, I was Derek. I was also the dispatcher, the CSR, the bookkeeper, and the person answering the irritated 9:30pm call from the customer whose breaker kept tripping. Two trucks. A software stack I'd spec'd off Facebook group recommendations. A very steep learning curve headed directly at my face.

That's the story most small shops don't tell themselves before they buy the tools the big guys use.

---

The Tool Doesn't Know You Have Five Trucks

Enterprise-grade field service software is built around assumptions. Dedicated dispatchers. Office admins. A person whose job is to own the CRM. A GM who reviews the reporting dashboards. These aren't features the platform is selling you — they're the infrastructure the platform assumes you already have. The way a 240-volt tool assumes you have a 240-volt outlet.

Most small shops adopt software the same way they'd buy a tool off a job site. Someone in a Facebook group said it worked. They didn't ask what that shop had underneath it. Didn't ask how many people were maintaining the workflow. Didn't ask whether the guy recommending it had a full-time dispatcher or was running dispatch from his truck on a 5-inch phone screen between service calls.

The problem isn't that the big platforms are bad. ServiceTitan and FieldEdge are serious tools. The problem is that what you're paying for assumes headcount you don't have. Permission structures built for an ops manager reviewing his billing coordinator's work become pure overhead when you are both of those people. The dispatch board designed for three dispatchers on split shifts is friction, not value, when you're doing dispatch in a browser tab between estimates.

At Lonestar, Derek existed because the software required a Derek. At Reeves Electric in 2022, I became a bad Derek on top of everything else I was already doing badly.

---

What the Wrong Stack Actually Costs You

The subscription fee is visible. It shows up on the bank statement, it's a line in the P&L, you can argue about whether it's worth it. The real cost is invisible and significantly larger.

Here's what it looks like in practice. You spend configuration hours — not setup once, but the ongoing maintenance of a system with more moving parts than your operation can reliably run. Someone half-builds an automation in month two. It mostly works. It breaks in month five when the platform updates something. Now nobody touches it. That's before you get to the integrations nobody's maintaining, and the opportunity cost underneath all of it.

I've said this before and I'll keep saying it: 80% of small-shop revenue leakage happens in the first call. The call that doesn't book. The intake that sends the wrong signal. The dispatcher who doesn't ask the right diagnostic question. Every hour you spend in a settings menu configuring a customer portal that your customers will never actually use is an hour you're not spending listening to the calls that didn't book.

That's not a small number. That's your business running slower because your tool is.

---

The Stack That Actually Fits a Five-Truck Residential Shop

Here's what I run, and what I'd recommend to a shop doing $800K to $2M in residential service.

Jobber at the core. I'd push you toward Jobber over Service Fusion for a shop this size. It's opinionated, it's fast to learn, and it does the core job — booking, dispatch, invoicing, payment collection — without requiring a Derek to maintain it. It won't impress a VC. It'll run your shop.

CallRail for tracking. Every marketing channel gets a number. Google ads, LSA, truck wraps, your website, whatever referral source you're running. Every call gets recorded and transcribed. This costs $50 to $150 a month. It is, dollar for dollar, the highest-impact spend in my budget.

Once a week I sit with my dispatcher and we listen to four calls: two that booked, two that didn't. We've done that since late 2022. That practice is what moved our booking rate from 41% to 68% through 2023. Not a platform upgrade. Not a new marketing channel. Listening to our own calls.

Zapier for the glue, but only when you can write down on paper exactly what you want to automate and a human is currently doing it manually. Not speculatively. Not because the platform supports it. When you can say: "Every time X happens, Y needs to happen, and right now someone's doing that by hand."

QuickBooks Online for accounting. NiceJob or Podium for review management — pick one, both work, stop agonizing. That's the stack.

The ceiling on it is higher than people expect before they go looking for something bigger. I've talked to shops at trade events running $3M on Jobber. The platform isn't what's holding them back. Their process is. Their hiring is. Their pricing is. Software doesn't fix those things; it just makes them move faster.

---

You're Not Ready for That Tool Yet, and That's Fine

There's real pressure in contractor communities to "professionalize" the operation. Get on the enterprise platform. Build the infrastructure. Look like the shop you want to be in five years. I felt it when I launched.

But buying ahead of your process maturity doesn't accelerate growth. It creates confusion. Here's the failure mode. A shop buys a platform for its automation features. Setup is complex, busy season hits, they go live on booking and invoicing and leave the automation unbuilt. Six months later they're using 15% of the platform while paying for 100% of it. The parts they're using work fine. The parts they're not using are the entire reason they bought it over the cheaper option.

I've heard this from people at trade events and from people who message me after I write about this stuff. The pattern is consistent. Shop buys ahead of process maturity. Configuration stalls. They run on the cheap features of an expensive tool for 18 months and then either finally configure it or switch.

When someone with 22 trucks tells you their ServiceTitan setup is incredible, they're telling you the truth. They're also describing a setup that required 18 months of configuration, an internal champion, and at least one full-time person to maintain it. That's the honest context for the recommendation. What worked at truck 20 is not the right call at truck 5.

---

What Actually Broke When I Tried to Run Lonestar's Playbook

Month two at Reeves Electric, my NPS was a 4. The electrical work was fine. The techs were good.

The problem was intake — and the software I'd chosen assumed a CSR existed to run it. I was the CSR. I was also the dispatcher and the tech on calls I couldn't hand off. The platform surfaced the wrong information at the wrong time to a two-truck operation with no back office, and I didn't have the hours to fix the configuration because I was also answering phones until 9:30 at night.

So I stopped trying to fix the software and started trying to understand the actual problem. Ninety days, I answered every call myself. Took notes. Tagged the calls that booked and the calls that didn't and looked for the pattern.

The problem wasn't the platform. It was the workflow. The platform was making a broken workflow move faster.

Once I understood what the intake actually needed to do, I could configure the tools to support it. Before that, I was configuring tools in search of a process I hadn't defined yet. No platform fixes that. By month nine, NPS was 81. Not because I switched software. Because I rebuilt the intake.

---

Before You Touch the Settings Menu

If your stack feels wrong, do these things before you buy anything else.

Pull last month's software spend, line by line. Every subscription, every add-on. Next to each one, write the name of the person at the shop whose job it is to own that tool — not who has the login, but who maintains the workflow, reviews the output, and notices when something breaks. If the answer is "nobody" or "me, when I get around to it," that tool is overhead until further notice.

Spend one week listening to four calls. Two that booked, two that didn't. If you don't have CallRail yet, check whether your VoIP system has recording built in — most do. If not, your smartphone will handle it. Write down what happened in the first 90 seconds of each call. The problem you find is almost never "we need a better platform." It's "we need a better intake script and a way to track whether it's working."

Sequence the complexity. Get booking and invoicing clean in whatever core tool you have right now. Make that part work without manual workarounds. Then layer CallRail once you have a baseline to measure against. Then build Zapier automations — only for specific manual tasks you can name out loud that a human is doing repeatedly every week. Add complexity when you can name the exact problem it solves.

The shops that scale without chaos aren't the ones that bought the biggest platform earliest. They're the ones that knew what their process was before they asked software to run it.

---

FAQ

What's the difference between Jobber and ServiceTitan, and when does it actually make sense to move up?

Jobber does the core job without much overhead. ServiceTitan requires scale to get value from — the permission structures, the reporting layers, the dispatch board all assume headcount a 5-truck shop doesn't have. The move makes sense when you have a dedicated dispatcher who isn't doing anything else, a dedicated office admin who isn't doing anything else, and someone with time to own the platform configuration. Below that staffing level, you're paying for features you can't operate.

I'm already on a bigger platform and switching feels more expensive than staying. How do I think about that?

Sometimes staying is right. If you've done 60% of the configuration and you're using the core features, switching creates real migration cost — data export, retraining, two weeks of chaos minimum. The question to answer honestly: how many hours a week are you spending maintaining this platform that a simpler tool wouldn't require? At Reeves Electric I can quantify that now because I track it. If you can't quantify it, start there before you decide anything.

How do I know if I'm too small for the software I bought, versus just needing to finish the setup?

One question: do you have a person whose job includes maintaining this — not as a side task, but as an actual part of their role? If no, and setup has been "almost done" for more than 90 days, you're not going to finish it. The platform assumes infrastructure you don't have. Using 15% of a platform for 12 months is a signal, not a phase.

Is there a truck count where the bigger platforms start to make sense?

Think staffing, not revenue. When you have a full-time dispatcher, a full-time CSR or office admin, and someone — even part-time — who can own the platform configuration, you can absorb a more complex tool. In residential service, that staffing level tends to show up around 10 to 12 trucks. If the owner is still running calls, that number probably goes up.

What's the actual risk of staying on a simple stack if I want to grow to 10 or 15 trucks?

The genuine risk: reporting gets harder, some workflow automations won't be available, multi-crew dispatch gets messy. What doesn't happen is a sudden wall. The bottlenecks become visible before they become catastrophic. When you can name specific things your current stack can't do that you actually need — not theoretically need, actually need — that's when to evaluate moving.

How do I handle integrations between simple tools?

The weak point is usually data moving between your core platform, QuickBooks, and something else when the native integration is flaky. Zapier and Make solve most of this for well-defined, one-directional tasks. If the integration is complex enough that Zapier can't handle it cleanly, that's a signal your process needs to be simpler, not that you need a bigger platform. Figure out the workflow first. Then see if the integration problem still exists.