How to create a profitable mobile service area

What makes a mobile service area profitable?

A profitable area produces enough contribution from paid work to cover service time, travel, mileage, parking, payment costs and overhead while meeting the owner’s income target. The exact calculation belongs to the business. Revenue alone is misleading when a high-value outer job consumes the time that could support two nearby services.

Reliability matters alongside margin. A boundary that repeatedly creates late arrivals, long empty returns or declined follow-on work is operationally weak even if individual jobs appear profitable. Define success using paid hours, total route time, direct costs, late arrival and demand density rather than maximum distance from base.

How do you map customers and demand?

Export or list recent completed customers and genuine enquiries by postcode area. Add service value, duration, travel time, parking cost and whether another nearby job followed. Plot clusters before drawing a boundary. Existing routes reveal where demand already supports efficient work and where isolated trips create empty mileage.

Include declined enquiries because they show unmet demand, but distinguish repeated clusters from one-off requests. Review by day and time as well as location. A town may support a profitable Tuesday route without being suitable for open availability every day. Protect customer privacy by using only the location detail needed for analysis.

• Completed jobs and genuine enquiries by area
• Service value and occupied appointment time
• Outbound, onward and return journey time
• Mileage, tolls and parking
• Nearby demand that could complete the route

• Count bookings by postcode district with the cluster worksheet

How do you calculate the full cost of a booking?

Count the complete route impact: preparation, service delivery, pack-down, outward or incoming travel, parking, onward travel and any empty return. Add direct vehicle and payment costs using your own records. Allocate overhead and owner time consistently. Seek accounting advice where needed; a scheduling guide cannot determine tax treatment or target margin.

Use opportunity cost carefully. If a distant service blocks a second nearby booking that normally sells, that lost capacity matters. If the diary would otherwise be empty, the decision may differ. Compare realistic alternatives rather than assuming every travel minute could have been sold. Keep the calculation reproducible so future boundary changes can be compared.

Why use a core area and outer zones?

The core area contains locations you can serve on ordinary working days at standard availability. Its journeys are familiar and demand is dense enough to create coherent sequences. Outer zones are offered on selected days, at specific times or by manual approval when grouped work makes the travel worthwhile.

This structure gives customers clear expectations while stopping scattered outer bookings from controlling the week. It also creates a safe way to test expansion. Offer a trial area day, measure take-up and complete route cost, then keep, change or remove it. Do not make the permanent boundary larger before demand proves the route.

How should prices and travel charges be considered?

Your base price, minimum job value or travel surcharge can reflect the cost of serving an area, but communication must be clear before confirmation. A surcharge may cover money costs; it does not solve a route that makes the following customer unreachable or consumes too much of the working day.

Choose distance-based travel pricing when longer road journeys are the main reason visits cost more. Choose time-based travel pricing when a short urban trip can occupy as much of the diary as a longer rural drive. Compare recent completed visits before choosing. Neither distance nor journey time captures every expense, so use the full cost calculation to decide the amounts for your charging brackets.

CalMov's Automatic travel pricing on Pro lets you choose one basis: distance in miles or journey time in minutes. Set a charge for each bracket and CalMov applies the matching travel surcharge to customer-address bookings. The pricing journey runs one way from your business base to the customer. Use complete outward and return costs to inform your bracket amounts; CalMov measures the one-way journey when applying the charge.

For an illustrative distance policy, set 0 to 6 miles at £0, 6 to 12 miles at £5, and 12 miles upwards at £10. A 9-mile journey then adds £5. Alternatively, a time policy could set 0 to 20 minutes at £0, 20 to 40 minutes at £6, and 40 minutes upwards at £12. A 28-minute journey then adds £6. These are example bracket charges, not suggested market prices or per-unit rates.

Keep the three decisions clear: where you serve, when the visit can fit and how much travel should cost. CalMov's coverage and travel time rules handle the first two; Automatic travel pricing handles the third. An applicable surcharge appears separately in the customer's booking summary and is included in the total before confirmation. Test nearby and outer addresses so the fee matches the policy you intend to offer.

What does a service-area decision example show?

A £90 job sits thirty-five minutes from the core. Service and pack-down occupy ninety minutes, the outward journey takes thirty-five and the return takes thirty-five. Before mileage and overhead, the booking consumes 160 minutes. Compare its contribution per occupied hour with a realistic nearby alternative, not the £90 headline alone.

If another £90 job can follow ten minutes away, the combined route changes materially because the long outward journey supports two services. This example explains why outer zones often work as grouped days but not random availability. Use your own prices, costs and demand probability rather than treating the numbers as a universal threshold.

How do you review and expand the boundary?

Review monthly or quarterly using accepted work, declined enquiries, paid hours, route time, direct travel cost and late arrival by area. Investigate outliers but change the boundary only when a pattern repeats. Remove or restrict locations that consistently create weak routes, even if individual customers there are valuable.

Expand one cluster at a time through a defined trial. Set the days, services and success measures in advance. After enough representative bookings, compare the route with the core. Keep the expansion only when demand, contribution and reliability meet the business’s own targets. Communicate changes early to existing customers.

• Measure contribution using complete route time.
• Track declined demand by cluster, not anecdote.
• Test outer areas on selected days first.
• Review late arrival and empty returns.
• Expand only when grouped demand repeats.

What should a monthly service-area review include?

Once a month, group accepted work, genuine declined enquiries and manual exceptions by postcode cluster. For each cluster, compare paid service value with complete route time, direct travel costs, parking, empty return and late-arrival impact. Use accounting records for actual cost decisions rather than a generic online rate.

Choose one outcome for each outer cluster: retain normal availability, restrict it to area days, test a grouped route, require manual approval or remove it. Document the reason and review it next month. A boundary becomes stronger when repeated evidence changes access predictably, not when one unusually good or bad job redraws the map.

• Accepted and declined demand by postcode cluster.
• Complete route time rather than appointment value alone.
• Direct travel, parking and payment costs from your own records.
• Late arrivals, empty returns and manual booking moves.
• One documented boundary decision to review next month.