UK guide
Service area guide
How to create a profitable mobile service area
A service area should describe where you can deliver work reliably, not every place you would ever consider travelling. Profitability depends on your own prices and costs, so this framework uses real customer, route and operating data rather than promising one ideal radius.
Quick answer
Create a profitable mobile service area by mapping current customers and enquiries, calculating each area’s full travel and operating cost, identifying dense demand clusters and separating an everyday core from optional outer zones. Price and schedule the complete route, not an isolated appointment. Review accepted, declined and low-margin jobs regularly, and expand only when nearby demand supports reliable grouped work.
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
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.
Compare simpler options before creating many postcode prices. An area day, minimum service combination or smaller boundary may be easier for customers and the business to understand. Check consumer, tax and sector obligations relevant to your pricing and present the total payable amount clearly in the booking flow.
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.
Frequently asked questions
How large should a mobile service area be?
There is no universal radius. The boundary should include locations you can serve reliably at acceptable contribution after full route time and costs. Start with a dense core, test edge postcodes at normal travel times and add outer zones only when grouped demand supports them.
Should I use miles, postcodes or drive time?
Postcodes are easy to communicate, while drive time better reflects operational cost. Straight-line miles can hide road and access differences. Many businesses combine a customer-facing postcode list with internal journey checks, then review the exceptions using actual completed routes.
Can a travel surcharge make every area profitable?
No. A surcharge can cover some monetary cost but cannot recover a following booking made unreachable or the opportunity cost of a long empty return. Calculate the full route and customer demand. Area days or a smaller boundary may be better than charging for an inherently weak route.
How often should a service area be reviewed?
Review monthly or quarterly and after meaningful changes to prices, fuel, services, working hours or local routes. Use completed jobs and genuine declined demand. Change boundaries from repeated patterns, communicate them clearly and avoid reacting to one unusually good or bad journey.
Sources and further reading
Primary guidance used to check the privacy, accessibility or business-cost points in this article. Product features and prices should always be checked on the provider's current pages.
How CalMov helps
CalMov combines service duration, working availability and customer location to help mobile businesses offer bookable times that allow for the surrounding journeys.
See CalMov for home visit businesses