How to price travel so a job across town does not run at a loss

An hour of driving costs the same as an hour of working: the same wage, the same vehicle, the same day. What differs is that only one of them produces an invoice. A service business whose work is spread across a metropolitan area is giving away a meaningful share of its week unless the price says otherwise.

Step one: measure it before designing anything

Take two weeks of actual data. For every job, record the time leaving the previous location and the time arriving, and separately record the miles. Do not estimate. Estimates in this area are consistently low, because people remember the working and not the driving.

Two figures come out of it: average travel minutes per job, and travel as a percentage of paid hours. Those numbers determine which of the three structures below fits.

Step two: pick the structure that matches your pattern

Most small operators end up combining two: a minimum charge that makes any visit worth making, plus zones for the outer edges of the territory.

Step three: build the zone map

Draw it around drive time, not around distance and not around town boundaries. Fifteen minutes on a highway covers considerably more ground than fifteen minutes through a downtown grid, and customers understand travel time better than they understand mileage.

Three or four zones is plenty. Zone one is whatever you can reach quickly from your base with no premium. Each subsequent zone carries a stated addition. Beyond the last zone, the answer is either a quoted price case by case or a polite no.

Check the map against real conditions, including the direction and time of day. Where a river crossing, a bridge or a single congested corridor makes travel asymmetric, the map should reflect that rather than assume circles.

Step four: decide what the fee covers, and say so

The most common objection is not the amount. It is the sense that a customer is being charged twice for the same thing. Prevent it by stating what the fee covers in one line on the estimate: the travel to and from your location, which is time the crew is paid for and is not spent on your job.

Two refinements that reduce friction considerably. Waive or reduce the travel charge above a stated job size, which makes the fee obviously about short visits rather than about revenue. And group work by zone on set days, so a customer in an outer zone can be offered a lower price for being flexible about the day.

That second one converts a pricing problem into a scheduling benefit for both sides, and it is the single most effective change most route-based businesses can make.

Step five: check the local rules before publishing it

Two things to verify. Some states and cities have disclosure requirements for service call and trip fees, particularly where a charge applies whether or not work is performed, and the requirement is usually that it be disclosed before the visit is booked rather than on arrival.

And some municipalities require a local business license or registration to perform work within their limits. Where an outer zone sits across such a boundary, the annual fee is part of the cost of serving that zone, and it may be the fact that decides whether the zone is worth having at all.

What to do with the recovered time

The point of pricing travel correctly is not primarily to collect more money for driving. It is to make the true cost of a scattered route visible, so that decisions about which work to take stop being made on the assumption that every hour on the clock is equal.

Businesses that do this usually end up tightening their territory rather than raising their prices much, because once the outer zone carries its real cost, the outer zone stops looking attractive. That is the correct outcome, and it produces shorter days and better margins at the same time.