You know your gross margin on parts. You know your labor rate. But do you know how much of your technician’s day is windshield time versus wrench time?

Most trades business owners I work with can tell me their hourly rate down to the dollar. They can’t tell me which zip codes or job types are bleeding profit through drive time. The P&L shows a healthy margin. The calendar shows full schedules. But when you map actual profitability by service area or job size, the picture changes fast.

A typical HVAC company running four trucks might have one technician driving 90 minutes round-trip for a $400 service call while another covers three calls in the same time window. The first call looks profitable on paper. It isn’t. The owner doesn’t see it because drive time lives in a gray zone between dispatch notes and payroll hours.

This isn’t about squeezing technicians. It’s about seeing the real cost structure of your business so you can route smarter, price better, and stop subsidizing low-margin work with the profit from good jobs.

Why Drive Time Is Invisible in Most Trades Businesses

Drive time doesn’t show up as a line item. It’s baked into labor hours, fuel costs, and the opportunity cost of jobs you didn’t take because the truck was on the road.

Your dispatch board shows job start times. Your invoices show labor hours on-site. The gap between those two numbers is where profit leaks. A plumber who’s on the clock for eight hours but only billing five is spending three hours driving, waiting for parts, or dealing with dispatch friction.

Most owners track this in their head or rely on end-of-day truck sheets that get filed and forgotten. You might know that the north side of town is a pain. You don’t know it’s costing you $1,800 a week in unbilled drive time because no one is aggregating those sheets and mapping them to job margin.

The businesses that do track drive time are usually doing it manually. Technicians log miles in a notebook or a spreadsheet. Someone in the office keys it into QuickBooks once a week. By the time you see the data it’s two weeks old and you’re already committed to next week’s schedule.

You can’t optimize what you can’t measure in real time. And you can’t measure it in real time if tracking depends on a human remembering to write it down after a ten-hour day.

What Good Drive Time Tracking Actually Looks Like

Automatic capture is the baseline. GPS pings when the truck leaves the shop and when it arrives on-site. No driver input. The system knows the route, the time, and the mileage. It writes it to the job record before the technician opens the door.

That data needs to connect to job costing immediately. Drive time isn’t useful as a standalone metric. You need it attached to the job so you can see total cost: parts, labor hours on-site, labor hours in transit, fuel, and margin. One electrical contractor I know realized his most requested service, panel upgrades in a neighboring county, was break-even after drive time. He raised the rate 18% and lost zero customers.

The second piece is route optimization that learns. Static routing tools give you the shortest path between five stops. AI-powered routing looks at traffic patterns, job duration variance, and time-of-day constraints. It knows that a service call in the industrial park takes 90 minutes on average but the same call in a residential neighborhood takes two hours because access is harder. It builds that into the route and the time estimate.

The third piece is exception alerting. If a job that should take 30 minutes of drive time is running 50, you want to know while the truck is still on the road. Maybe there’s an accident. Maybe the address was wrong. Maybe the technician took a detour. Real-time tracking lets you reroute or communicate with the customer before the delay becomes a service failure.

All of this rolls up into reporting that shows profit by service area, by job type, and by technician. You start to see patterns. The small residential calls in the outer suburbs don’t pencil. The commercial maintenance contracts in the core are gold. You adjust pricing, routing, and marketing accordingly.

The Manual Workflow That’s Costing You $50K to $200K a Year

Here’s what it looks like without automation.

Technician finishes a job. Writes the end time on a paper ticket or keys it into a mobile app. Drives to the next job. Forgets to log the start of the drive. Arrives on-site, logs the arrival time, realizes he forgot the drive start, estimates it.

End of the day he’s got five jobs on the sheet. Three have accurate times. Two are guesses. He turns in the sheet. Office admin keys the hours into the job costing module. She doesn’t have context on which hours are drive and which are on-site, so it all goes into labor.

Owner reviews job profitability at the end of the month. Sees that labor as a percent of revenue is creeping up. Doesn’t know if it’s inefficiency, longer jobs, or drive time. Decides to push technicians to close more calls per day. Technicians feel the pressure, start rushing jobs, quality slips, callbacks increase.

Meanwhile, dispatch is still routing by whoever answers the phone first and which truck is theoretically closest. No one is looking at drive time as a cost to minimize. No one is clustering jobs geographically. The schedule is a game of Tetris played with phone calls and gut feel.

This is how a business doing $3 million in revenue can have $120,000 in unbilled drive time and not see it. It’s not fraud. It’s not laziness. It’s just invisible in the workflow.

How AI Agents Close the Loop

An AI agent doesn’t forget to log the drive. It doesn’t estimate. It doesn’t wait for end-of-day reconciliation.

The 24/7 Dispatch Voice Agent answers the call, qualifies the job, and checks drive time to the address before it even offers a time slot. If the customer is 40 minutes from the nearest available truck and it’s a non-emergency call, the agent offers a slot when a truck will already be in that area. The customer gets a faster arrival window. You get a route that doesn’t burn an hour of windshield time.

Once the job is booked, the system tracks the truck from dispatch to arrival. It logs drive time automatically and writes it to the job cost record in real time. The technician never touches it. The office never keys it in. It’s just there.

If the route is running long, the agent texts the next customer with an updated ETA. If the delay is significant, it offers to reschedule. The customer doesn’t sit around waiting. You don’t eat the cost of a wasted trip if they’re not home.

After the job, the Review and Reactivation Agent asks for feedback and logs the total job time, including drive. That data feeds back into route optimization. The system learns that jobs in a certain neighborhood take longer than the map suggests. Next time it books a call there, it pads the estimate and routes accordingly.

The Estimate Follow-Up Agent tracks whether the job converted and at what margin. If high-drive-time jobs are converting at lower rates, that’s a signal. Maybe the price isn’t covering the cost. Maybe customers in that area are price-shopping harder. You adjust.

All of this happens without anyone in your business doing additional work. The agent is tracking, logging, learning, and optimizing in the background. You see the output in a dashboard that shows profit per job, per route, per service area.

What You Learn When You Can See the Numbers

One roofing company I worked with thought their residential re-roof business was their profit center. When we mapped drive time and job duration, they realized their commercial flat-roof maintenance contracts were twice as profitable per labor hour. The residential jobs looked good on revenue. They didn’t look good on margin after you factored in two-hour round trips to subdivisions with no other work nearby.

They didn’t kill the residential business. They raised the minimum job size for outer-area work and focused marketing on the commercial segment. Revenue stayed flat. Profit went up 22% in six months.

Another electrical contractor discovered that his most experienced technician was spending 30% more time driving than the rest of the crew. Turned out dispatch was sending him to all the difficult jobs because he was the best troubleshooter. Made sense from a service quality perspective. Didn’t make sense from a cost perspective. They rebalanced the dispatch logic to cluster his jobs geographically and sent a less experienced tech with him on the tricky calls. Drive time dropped. Mentorship improved. Win on both sides.

A plumbing business found that their after-hours emergency calls were profitable despite premium rates, but their next-day follow-ups to those same customers were loss leaders. The truck was already out there for the emergency. The follow-up required a separate trip. They started offering a discount if the customer could bundle the follow-up work into the emergency visit. Conversion rate on add-on work doubled. Drive cost per job dropped.

You can’t make these decisions without the data. And you can’t get the data without automatic tracking that connects drive time to job-level profitability.

The Omni Audit for Trades Businesses

We built the AI audit for trades businesses to show you exactly where drive time and dispatch friction are hiding profit in your operation.

It’s a 60-minute working session. No deck. No discovery theater. We connect to your dispatch tool, your job costing system, and your call logs. We pull 90 days of data and run it through the same models that power the agents.

You get three outputs. First, a dollar estimate of what drive time and routing inefficiency is costing you, broken out by service area and job type. Second, a map of your highest-profit routes and your break-even or loss zones. Third, a build plan for the agents that will track, optimize, and report on this automatically.

Most trades businesses we audit are losing $50,000 to $200,000 a year in drive time and dispatch overhead. The audit shows you where it’s happening and what it would take to capture it. Book a 60-min Omni Audit and we’ll map it for your business.

If you’re also dealing with after-hours calls going to voicemail and losing another $20,000 to $60,000 in missed emergency work, grab the After-Hours Call Recovery Plan for Trades. It’s a one-page worksheet that shows you how to calculate the cost of missed calls and what an always-on voice agent recovers.

Why This Matters More as You Scale

When you’re running two trucks, you can probably route them in your head. You know the territory. You know the customers. You can feel when a job is too far out to be worth it.

At six trucks, you’ve lost that visibility. Dispatch is a full-time job. You’re relying on your dispatcher’s judgment and whatever routing tool you’ve bolted onto your dispatch software. Drive time is a guess.

At ten trucks, you’re flying blind. You’ve got technicians sitting in traffic, jobs running late, customers calling to ask where the truck is, and no real-time way to see what’s happening or fix it on the fly.

The businesses that scale profitably past $5 million are the ones that instrument this early. They know their cost per mile, their cost per job, and their profit per service area. They route with data, not gut feel. They price based on total delivered cost, not just parts and on-site labor.

AI agents make that possible without adding headcount. You don’t need a logistics manager. You don’t need a data analyst. You need a system that tracks, learns, and optimizes automatically. That’s what Omni does.

What Happens After the Audit

If the numbers make sense, we build the agents. Typical build time is two to four weeks depending on how many systems we’re connecting and how much workflow we’re automating.

The dispatch voice agent goes live first. It starts answering calls, booking jobs, and logging drive time immediately. You’ll see the data start to populate in your dashboard within days.

Route optimization layers in next. The system starts suggesting better routes based on real drive time data. Your dispatcher can accept or override the suggestions. Over the first month, the system learns your preferences and the suggestions get better.

After 30 days, you’ve got enough data to run the first profitability report by service area. That’s when you start making pricing and marketing decisions based on what the numbers show, not what you thought was true.

Most businesses recover the cost of the build in 90 to 120 days just from better routing and fewer missed calls. The long-term value is in the compounding effect of better data. You stop taking unprofitable work. You double down on high-margin segments. You route smarter every week.

If you want to see what that looks like for your business, book my Omni Audit and we’ll map it. Bring your dispatch data and your job costing reports. We’ll show you where the profit is hiding.

For more on how AI agents work across the trades business workflow, explore the Omni Ops suite and our broader library of guides and insights on automation for field service businesses. If you’re earlier in the research process, the EDNA blog covers the full range of AI use cases we’re seeing across verticals.