Service Radius and Drive Time: How to Price Travel Without Losing Jobs

The cost nobody puts on an invoice

Ask a mobile service business owner what a job costs to perform and you will get labor and materials. Ask what the drive cost and you will usually get a shrug and a rough guess about fuel.

Run the actual arithmetic. A technician at $28 an hour costs roughly $38 fully loaded once payroll taxes, insurance, and benefits are counted. A 45-minute drive each way is 1.5 hours, or about $57 of labor before the technician touches a tool. Add vehicle operating cost — fuel, tires, maintenance, insurance, depreciation — at a realistic all-in figure per mile, and a 35-mile round trip adds another $25 to $30.

That is $80 to $90 of cost on a job that might invoice at $220. Nearly 40 percent of the ticket consumed by getting there, and in most businesses none of it appears anywhere in the pricing.

As of August 2026, drive time is the largest unbilled cost in mobile service work, and it is the reason two companies with identical price lists can have completely different margins.

Measure before you price

You cannot price travel you have not measured. Three numbers, from your last month of completed jobs.

Average round-trip drive time per job. Not from a mapping estimate — from actual timestamps. If your technicians mark en route and arrived, you already have this. Most owners are surprised by how much larger it is than their impression.

Drive time as a share of the paid day. Total drive minutes ÷ total paid minutes. If this is above 35 percent, geography is one of your largest problems and no amount of price-list tuning will fix it. This is the inverse of technician utilization, covered in the service business KPI guide.

Cost per mile, honestly. Fuel plus maintenance plus tires plus insurance plus depreciation, divided by miles driven. Do this from real records, not from memory. It is nearly always meaningfully higher than the fuel-only number owners carry in their heads.

With those three you can price travel deliberately. Without them you are guessing, and the guess is nearly always low.

Draw the boundary in minutes, not miles

The most common service-area mistake is drawing a circle on a map. A circle assumes travel cost is symmetric in every direction, and it is not.

Real geography is anisotropic. A location 30 miles out along a highway can be a 28-minute drive. A location 12 miles away across a river with two bridges, through a downtown, or on the wrong side of a rail crossing can be 40 minutes. Radius in miles prices those identically, which is wrong in both directions — you overcharge the easy one and lose money on the hard one.

Draw the boundary by drive time. For a trade with one-to-two-hour jobs, 45 minutes each way is a common practical outer edge: beyond that, a technician spends more of the day driving than working, and the day cannot hold enough jobs to be profitable regardless of what you charge.

Then define zones inside the boundary:

• Core zone, roughly 0–20 minutes. Standard pricing, no travel adder. This is where you want most of your work.
• Extended zone, roughly 20–40 minutes. Standard pricing plus a travel component built into the quote.
• Edge zone, roughly 40–60 minutes. Higher travel component, and only accepted when the day allows or the ticket justifies it.
• Outside, beyond that. Declined and referred, cleanly and immediately.

Rush hour matters. A boundary drawn at 10 a.m. drive times is optimistic at 5 p.m. Either use a peak-hour figure or accept that the edge zone is unprofitable during rush.

Four ways to price travel

Most mobile service businesses land on zone pricing because it matches cost most closely without generating arguments. Per-mile pricing invites disputes about whose mileage figure is right. Flat charges are simple but systematically mis-price both ends of your territory.

Whichever model you pick, one rule overrides it: the travel component belongs inside the number you quote on the phone. Not disclosed afterward, not added on the invoice. A caller told "$245 all in, that includes getting there" who is charged $245 is happy. The same caller told "$195" and charged $245 is angry and often disputes the charge — a pattern covered in handling price shoppers and in the chargeback defense guide.

The clean implementation computes zone and any other surcharges server-side and returns one total, so whoever answers the phone never sees a pre-travel figure they might quote by mistake.

Enforcing the boundary at the phone

Here is where the theory usually breaks.

A caller 70 miles out describes an urgent problem at 7 p.m. Whoever is answering the phone wants to be helpful, the schedule looks light, and the job sounds like decent money. They book it. The next morning a technician burns two and a half hours of driving on a $260 job, arrives late because the first job of the day ran over, and the customer — who was told a time — leaves a review about waiting.

Every part of that sequence was well-intentioned. The failure was that the service area existed as a guideline rather than a rule.

Geography is exactly the sort of constraint software enforces better than people, because software is not tired, not sympathetic, and not optimistic about traffic. A properly configured intake layer geocodes the address at the moment it is captured, compares it against the real boundary, and refuses to quote or book beyond it — reliably, on the 8 p.m. call as much as the 9 a.m. one.

That refusal has to be graceful. The correct out-of-area response is fast, honest, and useful:

"I'm sorry — that address is outside the area we can get to reliably, and I'd rather tell you now than have you waiting on a truck that's ninety minutes away. [Referral] covers that side of town."

Callers accept a clean no far better than a slow maybe. The reputational risk in mobile service comes from accepting jobs you then serve badly, not from declining ones you cannot serve. Referrals also tend to be reciprocal — the company you send work to sends work back.

Dispatching so drive time does not compound

A well-drawn boundary can still be ruined by scheduling. Two failure patterns account for most of it.

Booking chronologically instead of geographically. Three jobs across town in a random order produce far more drive time than the same three jobs sequenced sensibly. Booking software that offers slots without any awareness of where the technician already is will build days that cannot be run on time.

Proximity-only assignment. The opposite error. Always sending the nearest technician can strand someone in a corner of the territory with nothing else nearby, so the next job is a 40-minute reposition. Good assignment weighs distance against skills, parts on the truck, and the shape of the rest of that technician's day. The multi-tech dispatch guide covers the tradeoffs.

Two practices help materially. Cluster by geography where the job type allows — grouping a zone into a half-day block rather than scattering it. And protect the emergency slot in trades where urgent work carries the best margin, because a fully booked day with no slack means the profitable emergency call goes to a competitor.

When to expand the territory

Expansion is tempting because the map looks like opportunity. It is a real decision with real arithmetic.

Expanding makes sense when:

• Your core zone is genuinely saturated and you are turning away work you could serve
• The new area has enough density to build routes rather than single stops
• You can staff it with a technician who lives or starts near it
• The average ticket in the new area supports the travel

It does not make sense when:

• Core-zone utilization is below 60 percent, which means your problem is demand, not geography
• The expansion is one large customer who will not generate neighbors
• It requires the existing crew to cross the whole territory daily

The second failure mode is common and expensive: a business takes one big account 50 minutes out, builds the schedule around it, and quietly degrades service for the dense core that generates most of the margin.

The healthier version of expansion is a second base rather than a wider circle from the existing one. The multi-location operations guide covers running separate service areas without duplicating every system, and the owner-operator scaling guide covers the earlier stage of that decision.

What the numbers should look like after

Four measurements to check a month after you set zones and enforce them.

Drive time as a share of the paid day. Should fall. If it does not, either the boundary is not being enforced or dispatch is undoing it.

Revenue per technician per day. Should rise, because the same paid hours contain more billable work.

Out-of-area declines. Should be non-zero. If you never decline anything, your boundary is decorative.

Margin by zone. The one that settles arguments. If the edge zone runs at half the margin of the core zone even with the travel component, the travel component is too low or the zone is too big.

The job costing guide covers attributing drive cost to individual jobs properly, which is what makes the zone-margin comparison possible at all.

Telling customers about travel without losing them

A well-designed travel charge still has to survive the conversation. Three phrasings decide whether it does.

Fold it into one number. "That will be $265 all in, and that includes getting a technician out to you" beats "$210 plus a $55 trip charge" even though the customer pays the same. The first is a price; the second is a price plus a complaint waiting to happen. Customers are far more sensitive to fees they perceive as added on than to the same money inside the total.

Never introduce travel after the quote. If the caller heard a number and then hears about travel, you have created the base-plus-fees pattern that produces door cancellations. The travel component belongs in the first figure spoken, which means the system doing the quoting has to know the address before it quotes — geocode first, price second.

Explain the boundary as reliability, not as policy. "We keep our area tight so we can actually hit the windows we promise" is true and lands well. "That is outside our service area" sounds bureaucratic for the same decision.

There is a fourth case worth pricing deliberately: the customer just outside the line who wants you anyway. Some of them will pay a genuine premium for it, and there is nothing wrong with a stated out-of-area rate for callers who volunteer that they want you specifically. The rule is that it is priced up front and scheduled where it does not disrupt the core territory — typically first or last job of the day, never wedged into the middle.

Where the boundary interacts with everything else

Service area is not an isolated setting. It quietly constrains four other systems, and misalignment between them is where the losses hide.

Marketing targeting. Covered below, but the short version is that advertising outside the line converts spend into declines.

Booking availability. A slot offered to an edge-zone caller has to account for the travel on both sides of it. Booking software that treats every one-hour job as one hour will produce a day that runs 40 minutes late from the second appointment onward.

Technician home base. A boundary drawn from the shop is wrong if technicians start from home. In practice a crew that takes vehicles home extends the practical territory in one direction and shrinks it in another, and pretending otherwise wastes an hour a day.

Emergency and after-hours work. The night-time boundary is usually different from the daytime one — traffic is gone, so drive times shrink, but so does the crew available. Some businesses widen the radius after hours because the roads are clear; others narrow it because one on-call technician cannot cover the far edge and return. Either is defensible; having no explicit rule is not, because the decision then gets made at 11 p.m. by whoever answers.

The point across all four: the boundary is a business rule, and business rules only work when they are enforced in the systems that make the decisions. A number written on a whiteboard in the office is not a service area. A rule the phone applies before it quotes is.

Marketing has to match the map

One last inconsistency worth closing. Many service businesses advertise a territory considerably larger than the one they can actually serve, then spend money generating calls they have to decline.

That is paid demand converted into disappointment. If your real boundary is 45 minutes, your ad targeting, service-area pages, and Google Business Profile service area should reflect roughly that, not the whole metro. The Google Business Profile guide covers setting the service area correctly, and call tracking will tell you what share of your paid calls are arriving from outside the line — a number that surprises most owners the first time they see it.

Aligning the map, the ads, the phone rules, and the price list is unglamorous work. It is also the closest thing to free margin available to a mobile service business, because every element of it costs nothing but a decision.

Want your service boundary enforced on every call, including the 8 p.m. ones? Talk to us, or see what the intake layer includes on /pricing.