How far should your service area be? A profit-first way to decide

For a self-employed tradesperson, how far should your service area be? a profit-first way to decide is about protecting paid hours rather than sounding polished in messages.

The Sunday dated 17 May 2026 falls in a period when family plans, weather swings or tax deadlines change how quickly customers decide.

During this week, details such as postcode rings on a map, a travel cutoff by minutes not miles and separate pricing for edge-of-area jobs change time, price and customer expectation in practical ways.

That is why this post treats this approach as a fixed operating rule for W06, not as something to improvise after the van door closes.

Start this process with a clear gate: decide what has to be confirmed before you commit, then use the same rule whether the enquiry came by call, text or website form.

Make postcode rings on a map visible in your first message for W06, so the customer sees it as normal information rather than a late extra demand.

Treat a travel cutoff by minutes not miles as a planning filter on jobs linked to this workflow, because it can alter the route, the van stock or the amount of protected time you need.

For the week of 17 May 2026, split the admin on this setup into three parts: immediate reply, end-of-day diary check and one review of open quotes.

Where photos or measurements are missing on this method, ask for them before pricing so that your number reflects the real job rather than a hopeful guess.

The usual mistake with this plan is trying to be helpful by leaving too much open, then finding that the customer heard certainty where you only meant possibility.

Another common slip on this approach is pricing around postcode rings on a map too casually, which can look fine on paper but collapse once the job overruns by half an hour.

Many sole traders also forget how much a travel cutoff by minutes not miles affects the whole week of 17 May 2026, not just one slot, especially when traffic or school runs distort the route.

A quieter error on this process happens when separate pricing for edge-of-area jobs gets mentioned verbally but never written down, leaving you with no clean reference when the customer remembers it differently.

If you skip discipline on this workflow, a decent enquiry can turn into a low-margin tangle that steals time from better work already booked for W06.

Assume this setup adds 28 extra minutes to each of 8 jobs in a month because one key point was not pinned down at the start.

The arithmetic for this method is 8 jobs x 28 minutes = 224 minutes, which is 3.7 hours of lost working time.

If your chargeable rate on that kind of work is £51 an hour, 3.7 hours costs about £190.

Add £16 for one extra materials run, parking hit or fuel-heavy detour created by this plan, and the monthly cost becomes roughly £206.

• Review your last three enquiries connected to this approach and mark where the missing detail first showed up.
• Write one standard line for postcode rings on a map so you can send it without changing the wording every time.
• Check next week's diary for jobs that may be affected by a travel cutoff by minutes not miles and move them before the route becomes messy.
• Decide today how you will handle separate pricing for edge-of-area jobs on future jobs and add that rule to the quote or confirmation message.
• Chase any open this process enquiry from W06 where the next step is still unclear to both sides.

This is with me and I can move it forward. W06. Before I confirm this workflow, send the full address, the best access window and a note on postcode rings on a map. Add photos that show this setup clearly. Tell me whether a travel cutoff by minutes not miles or separate pricing for edge-of-area jobs will change timing, and I will reply with the next step, a workable slot and the right price basis.