TL;DR: A Dallas plumbing company cut 28 minutes of daily drive time per technician using a single AI agent focused on dispatch optimization. The result? 18% more jobs completed daily, $3,100/month in fuel savings, and techs who actually had time to eat lunch. Same team, same trucks - just smarter routing that considered location, skills, traffic, and job requirements in real-time. This wasn't simple, but it worked.
The radio crackles. "Carlos, can you take the water heater replacement in Fort Worth?"
Carlos glances at his GPS. He just finished a job in Plano - 45 minutes north. Fort Worth is an hour south, straight through afternoon traffic.
"Copy that," he says, because what else can he say?
He pulls onto 635, merging into the crawl. His phone buzzes. It's Marcus, another tech from the company. They're in a group chat.
Marcus: "Where you headed?"
Carlos: "Fort Worth. Water heater."
Marcus: "I'm literally 10 minutes from there. Just wrapped in Arlington."
Carlos doesn't respond. What would he say? The dispatchers are doing their best. They can't possibly track where 22 technicians are at every moment, cross-reference their certifications, check real-time traffic, and make optimal decisions in seconds.
So Carlos sits in traffic. Again. And his lunch - still in the cooler from this morning - stays there. Again.
That's field service inefficiency. Not dramatic. Not obvious. Just expensive. Every single day.
The Company Behind the Numbers
Redline Plumbing isn't some massive corporate operation. It's a family-owned residential plumbing company serving the Dallas-Fort Worth metroplex. Third generation. The kind of place where the owner knows every tech's kids’name.
Thirty-four employees total. Twenty-two technicians. Service area spanning 60+ miles from Plano to Fort Worth, Frisco to Duncanville.
The math in field services is brutal: efficiency directly equals profitability. A tech sitting in traffic isn't generating revenue. A truck burning fuel to zigzag across the metroplex is burning cash. Time wasted is money lost, and the losses compound.
Two dispatchers managed the schedule. Good people. Smart people. But they were playing an impossible game.
Here's what they were juggling:
Twenty-two techs across a massive service area
Real-time job requests coming in constantly
Each tech with different certifications and specialties
Traffic conditions that changed by the minute
Customer preferences and history
Emergency calls that disrupted everything
They did their best. Their best wasn't enough - not because they weren't talented, but because the problem was mathematically impossible for humans to solve optimally at scale.
The Real Cost of "Good Enough"
Let's talk about what "doing their best" actually looked like in practice.
The dispatchers used a system I've seen in hundreds of field service companies: they looked at who was available and assigned the next job. Proximity? Sometimes factored in. Skills match? When they remembered to check. Real-time traffic? Maybe they'd glance at Google Maps. Customer preferences? If there was time.
The result was what I call "availability-based dispatch." Not terrible. Just suboptimal in ways that add up fast.
The pattern looked like this:
A tech finishes a job in Plano. The dispatcher sees a new water heater installation request in Fort Worth. The tech is marked "available" in the system. Assignment made. Done.
Meanwhile, another tech who's been with the company for eight years (the one who can do water heaters in his sleep) just finished a simple faucet repair in Arlington, fifteen minutes from that Fort Worth job. But the dispatcher didn't see him as available yet because his ServiceTitan status hadn't updated.
So the less experienced tech gets a 90-minute round trip. The expert tech gets sent to a complex job he's less suited for. Both jobs take longer than they should.
Multiply that by 22 techs and 40-60 jobs per day.
Here's what it cost them monthly:
Over 90 minutes per tech per day in unnecessary drive time. That's windshield time, not wrench time. For a crew of 22, we're talking about 660 hours of lost labor monthly.
About 25% of their dispatches were suboptimal. Wrong tech for the job. Wrong route. Wrong sequence. Not catastrophically wrong, just... not right.
$4,200 in excess fuel costs. That's the literal gasoline being burned to drive technicians past each other on the highway.
Fifteen percent fewer jobs were completed per day than the schedule could theoretically support. The techs weren't working less hard - the routing was just inefficient enough to kill their capacity.
The owner, Mike, told me something I won't forget: "I kept thinking we needed more trucks. More techs. Turns out we just needed them in the right places."
What They'd Already Tried
This wasn't their first attempt at solving the problem.
They'd tried ServiceTitan's built-in dispatch board. Helpful for visualization, but it couldn't make optimization decisions. Just showed them where everyone was and let them drag jobs around manually.
They'd tried a standalone route optimization tool. Cost $300/month. Sounded perfect. Except it wanted them to plan the entire day's routes in the morning, then stick to that plan. Anyone who's run a field service business knows that's fantasy. Jobs run long. Emergency calls come in. Techs call in sick. The perfectly optimized 8 AM plan is worthless by 10 AM.
The routing software couldn't account for skill matching. It would route a journeyman to a simple faucet repair and send an apprentice to a complex water heater installation. Technically efficient driving. Operationally disastrous.
Mike's words: "The software was built by people who'd never actually dispatched a single truck."
So they went back to human dispatchers doing their best because imperfect humans who understood the business were better than perfect algorithms that didn't.
That's where things stood when we started talking.
The design is next. The design, the build guide, the running costs and the take-away are free to subscribers. Enter your email below and the rest of this Blueprint opens. New ones arrive every Tuesday and Friday.
