Your technicians are on the road four hours a day. You’re paying them for every minute. The question isn’t whether they’re working hard — it’s whether the routes you’re giving them make any sense.

Most trades business owners I talk to know drive time is expensive. What surprises them is how much it compounds. A crew that spends 90 extra minutes per day in the truck isn’t just burning fuel. They’re missing a billable call, arriving late to the next job, and clocking overtime because the last stop ran into the evening. Over a year, that pattern costs you between $50,000 and $200,000 in lost margin.

The fix isn’t working harder. It’s tracking drive time automatically and using AI to optimize routes before the truck leaves the yard.

Why Drive Time Bleeds Profit Faster Than You Think

Drive time feels like overhead. It’s not on the invoice, so it’s easy to treat it as a fixed cost. But it’s not fixed. It’s a variable you control, and right now most trades businesses are flying blind.

Here’s what happens when you don’t track it. Your dispatcher books jobs in the order they come in. A plumber finishes a water heater replacement in the north suburbs at 10 a.m., then drives 40 minutes south for a drain snake, then back north for a 2 p.m. furnace tune-up. The route makes sense on paper because each job was available. But the tech spent two hours in the truck for six hours of billable work.

Multiply that across three crews, five days a week. You’re paying for 30 hours of drive time that could’ve been 18 if the jobs were sequenced differently. That’s 12 hours a week, 600 hours a year. At a loaded labor rate of $75 per hour, you just found $45,000 sitting in traffic.

And that’s before you count the calls you didn’t get to. When a crew is stuck in the truck, they can’t take the next job. The customer calls a competitor. You lose the sale and the chance to upsell maintenance or a replacement. For a typical HVAC or plumbing business doing $3 million in revenue, we usually see two to four missed calls per week that could’ve been captured with better routing. Each one is worth $800 to $2,500 depending on the job type.

The other cost is overtime. When the day starts late because the first stop was 45 minutes away, the last stop bleeds into hour nine or ten. You’re paying time-and-a-half for work that should’ve fit in a regular shift. Overtime alone can add $15,000 to $30,000 per crew per year if routing is consistently inefficient.

What Manual Tracking Misses

Some owners try to solve this with a spreadsheet. They ask techs to log start and stop times for each job, then calculate drive time at the end of the week. It’s better than nothing, but it doesn’t work.

First, the data is always late. By the time you see that Tuesday’s route was a disaster, the week is over. You can’t fix it retroactively, and you’re not going to remember the details when you plan next Tuesday.

Second, techs don’t log accurately. They’re focused on the work, not the admin. They round times, forget to hit the timer, or batch-enter everything at the end of the day. The log says 22 minutes of drive time when it was really 38. Your analysis is built on guesses.

Third, even if the data is perfect, you still have to interpret it. Which routes are inefficient? Is the problem the sequence, the distance, or the time of day? Should you move the 2 p.m. call to Thursday, or swap it with the 10 a.m.? A spreadsheet can’t answer that. You’re left eyeballing a list of addresses and making your best guess.

The result is that most owners know drive time is a problem but don’t have a system to fix it. They tell the dispatcher to “try to keep jobs close together,” which helps on good days and falls apart the moment the schedule gets tight.

How AI Route Optimization Works in Practice

AI route optimization isn’t magic. It’s math applied to your real schedule, and it runs every time a new job comes in.

Here’s what it looks like. A customer calls at 9 a.m. with a leaking water heater. Your 24/7 Dispatch Voice Agent answers, qualifies the job, and checks availability. Instead of booking the first open slot, the system looks at where each crew will be throughout the day, calculates drive time from their current or next location, and assigns the job to the tech who can get there fastest without disrupting the rest of the route.

If Crew A is finishing a furnace install two miles away at 10:30 a.m., they get the call. Crew B is 15 miles away and booked solid until 3 p.m., so they’re out. The system doesn’t just look at the clock. It looks at the map, the traffic patterns for that time of day, and the duration of each job already on the schedule.

Once the job is assigned, the route recalculates. If adding the water heater means the 2 p.m. call is now on the way instead of a backtrack, the system adjusts. If it creates a conflict, it flags it for your dispatcher to review. The tech gets an updated route on their phone with turn-by-turn directions and the new sequence. No phone tag, no confusion.

The same logic runs overnight. Before the first truck leaves in the morning, the system sorts every job by location, time window, and priority. Emergency calls stay first. Scheduled maintenance gets slotted into the gaps. The result is a route that minimizes total drive time across all crews, not just one truck at a time.

One electrical contractor I work with cut average daily drive time from 3.2 hours per tech to 2.1 hours using this approach. That’s 5.5 hours per crew per week, which let them add one extra service call per day without hiring. Over a year, that’s 250 additional billable calls. At an average ticket of $850, that’s $212,000 in new revenue from the same labor pool.

Automatic Time Tracking That Actually Tells You Something

The other half of this is tracking what’s actually happening, not what you planned. AI route optimization gives you the best route on paper. Automatic time tracking tells you whether the crew followed it and where the plan broke down.

Modern tracking doesn’t rely on the tech remembering to start a timer. It uses GPS to log when the truck arrives at a job site, when it leaves, and how long the drive took. The system knows the route it suggested and the route the crew actually took. If they deviated, you see it.

This matters because the biggest drive time leaks aren’t the routes you planned poorly. They’re the stops you didn’t plan for. The tech swings by the supply house because the part you ordered wasn’t in stock. They grab lunch on the way to the next call. They take a scenic route because the highway was jammed and they didn’t check traffic. Each detour adds 10 to 20 minutes, and none of it shows up in your schedule.

Automatic tracking surfaces these patterns. You’ll see that Crew B stops at the same supply house three times a week, which means your parts ordering process is broken. You’ll see that the route through downtown always takes 15 minutes longer than the system estimated, so you adjust the buffer. You’ll see that one tech consistently takes longer to drive between jobs than the others, which is either a performance issue or a signal that they’re getting stuck with the hardest routes.

The AI audit for trades businesses we run includes a drive time analysis. We pull four weeks of job data, map every route, and calculate how much time was spent driving versus working. For most businesses, the number is 25% to 35% of the total labor hours. The best-run operations get it down to 18% to 22%. That gap is where the money is.

The Dispatch Problem You Didn’t Know You Had

Here’s the part that catches people off guard. Even if you optimize routes and track drive time perfectly, you still lose money if your dispatch process is manual.

The problem is reaction time. A customer calls at 11 a.m. with a burst pipe. It’s an emergency, so it jumps the queue. Your dispatcher has to figure out which crew can get there fastest, call them to confirm, rearrange the rest of their day, and call the other customers to let them know their appointment moved. That takes 15 to 20 minutes if everything goes smoothly. The customer is waiting. The crew is waiting. The clock is running.

By the time the tech is dispatched, it’s 11:20 a.m. They finish their current job, drive to the new site, and arrive at 12:10 p.m. Total response time: 70 minutes. The customer is frustrated, the water damage is worse, and you’re eating the cost of an expedited repair that could’ve been contained if you’d arrived 30 minutes earlier.

Now run the same scenario with a 24/7 Dispatch Voice Agent. The customer calls at 11 a.m. The agent answers immediately, qualifies the job, checks crew locations, and assigns it to the closest available tech in under two minutes. The crew gets a notification, sees the updated route, and starts driving. They arrive at 11:35 a.m. Response time: 35 minutes. The customer is happy, the damage is minimal, and you just saved the cost of a drywall repair.

This isn’t a hypothetical. It’s the difference between a system that thinks in seconds and a human who has to juggle six things at once. The agent doesn’t get distracted, doesn’t make mistakes, and doesn’t need to ask someone else for approval. It just executes.

The same logic applies to non-emergency dispatch. When a new job comes in, the agent books it into the optimal slot without waiting for your dispatcher to finish the call they’re on. Your dispatcher’s job shifts from routing every call to handling exceptions and customer escalations. That frees up 15 to 20 hours per week of admin time, which is either a part-time salary you don’t have to pay or an owner who gets their evenings back.

What Happens When You Track Drive Time at Scale

Once you have automatic tracking and AI routing in place, the data starts to tell you things you couldn’t see before.

You’ll notice that certain zip codes always take longer to reach than the map suggests. Maybe it’s traffic, maybe it’s parking, maybe it’s gated communities where the tech has to wait for access. Whatever it is, you now know to add a buffer or avoid booking back-to-back calls in that area.

You’ll see which job types consistently run long and throw off the rest of the day. If every water heater replacement is scheduled for 90 minutes but actually takes two hours, your routes are built on bad assumptions. You adjust the estimate, and suddenly the afternoon stops falling apart.

You’ll identify which techs are efficient and which ones aren’t. If one crew consistently completes the same route 30 minutes faster than another, that’s either a training opportunity or a signal that you’re assigning jobs unevenly. Either way, you can fix it.

The businesses that do this well use the data to run a weekly routing review. Every Monday, they look at last week’s drive time by crew, by day, and by job type. They identify the three biggest inefficiencies and adjust the dispatch rules for the current week. It takes 20 minutes, and it compounds. After a quarter, drive time is down 15% to 20%, and the schedule is predictable enough that customers stop calling to ask when the tech will arrive.

If you want a practical starting point for tightening up dispatch and follow-up workflows, the After-Hours Call Recovery Plan walks through how to capture the calls that come in when your team is off the clock. It’s a natural complement to route optimization, because the fastest route doesn’t matter if you’re missing half the inbound leads.

Why This Matters More Than Adding Another Truck

Most trades business owners solve capacity problems by hiring. You’re booked solid, customers are waiting, so you add a truck and a crew. It works for a while, then you hit the same wall six months later.

The problem is that hiring doesn’t fix inefficiency. It scales it. If your current crews are spending 30% of their day in the truck, the new crew will too. You just added $150,000 in labor cost to capture $180,000 in new revenue. The margin is thin, and you’re back to being capacity-constrained as soon as demand ticks up.

Route optimization flips that equation. Instead of adding a truck, you get 10% to 15% more capacity from the crews you already have. That’s the equivalent of half a crew for zero incremental labor cost. You can take more calls, shorten lead times, and improve customer satisfaction without hiring, onboarding, or buying another vehicle.

The math is straightforward. A three-truck operation doing $3 million in revenue typically has $900,000 to $1.1 million in direct labor and drive time. If you cut drive time by 20%, you free up $180,000 to $220,000 in capacity. That’s not revenue. That’s capacity you can sell. At a 50% gross margin, that’s $90,000 to $110,000 in additional profit, or the equivalent of adding $450,000 to $550,000 in top-line revenue without increasing fixed costs.

You can see why this matters more than most of the marketing or sales tactics trades businesses spend money on. It’s not about generating more leads. It’s about fulfilling the demand you already have without leaving money in the truck.

What an Omni Audit Uncovers

When we run an Omni Audit, drive time is one of the first things we measure. We don’t need access to your dispatch system or your techs’ phones. We just need four weeks of completed job data: addresses, start times, end times, and crew assignments.

From that, we can map every route, calculate actual drive time, and compare it to the optimal route for the same set of jobs. The gap between the two is your leakage. For most trades businesses, it’s 60 to 90 minutes per crew per day. That’s $30,000 to $70,000 per crew per year in recoverable capacity.

We also identify the dispatch patterns that create the problem. Are you batching jobs by time instead of location? Are emergency calls disrupting the whole day because you don’t have a buffer? Are certain customers always scheduled at times that force a long drive? The audit flags the top three patterns and shows you what fixing them would look like.

The output isn’t a slide deck. It’s three things: a capacity map that shows where your crews are spending their time, a leakage estimate with the dollar impact, and a priority list of the workflows we’d automate first. You walk out of the call knowing exactly how much money is sitting in drive time and what it would take to capture it.

Book a 60-min Omni Audit and we’ll run the analysis live. No prep required on your end.

Building the System That Runs Itself

The long-term play isn’t just optimizing routes. It’s building a dispatch system that doesn’t need you to think about routes at all.

That means the AI handles inbound calls, qualifies jobs, assigns them to the optimal crew, and updates the route automatically. The Estimate Follow-Up Agent tracks every quote you send and follows up on day two, day five, and day 14 until the customer books or declines. The Review and Reactivation Agent asks for a review the day after every completed job and reactivates past customers when it’s time for their next service.

Your dispatcher’s job becomes exception handling. They step in when a job runs long, when a customer has a special request, or when a crew calls in sick. The system handles everything else.

This is what we mean when we talk about Omni for trades businesses. It’s not one tool. It’s a connected system where the agents handle the repetitive work and surface the decisions that actually need a human. Route optimization is one piece. Dispatch automation is another. Follow-up and reactivation are two more. Together, they turn a business that runs on your constant attention into one that runs on process.

The businesses that make this shift don’t grow by grinding harder. They grow because they have the capacity to say yes to more work without burning out their team or their owner. Drive time drops, billable hours go up, and the schedule becomes predictable enough that you can actually plan your week instead of reacting to it.

If you want to see what that looks like for your business, book my Omni Audit. We’ll map your current state, quantify the leakage, and show you the two or three automations that would have the biggest impact. Sixty minutes, three outputs, no deck. See Omni for trades businesses and decide if it makes sense for you.