The call comes in at 5:40 on a Friday. Sump pump died, finished basement, water still running. The address is 44 miles out, past the edge of the area you drew on a map three years ago for reasons nobody remembers. Your crew is 20 minutes from wrapping the day. The office manager looks at you and asks the only question that matters: do we take it?
A gut-feel answer is hard to review later. The solution is not automatically a bigger radius or a smaller one. It is a written rule, built zone by zone, that anyone answering the phone can apply at 5:40 on a Friday without inventing the criteria during the call.
A service-area strategy is a written, ZIP-level rule set that tells your office which leads to accept, which to accept only under specific conditions, and which to refer out, based on expected contribution after lead cost and travel. It is an operating document, not a marketing setting, and it belongs beside the procedures your dispatcher already uses.
What a service-area strategy decides
The strategy answers four questions for each ZIP code, and only these four:
- Accept or not. Does a lead from this ZIP get a scheduled visit, or a referral?
- At what price. Does work from this ZIP carry a travel adjustment, or does it price like a core-zone job?
- Under what conditions. Is the zone open only for emergency mitigation, only for planned installs, or only when a crew has slack capacity?
- For how long. What date does the decision get reviewed, and what numbers would change it?
Notice what is missing: nothing about how far you can drive. The question is whether the expected work at the end of that drive pays for the windshield time, the vehicle cost, the people in the truck, and the capacity you can no longer use closer to base.
ZIP codes are often more practical than county lines or "about 30 minutes out" because they can be attached consistently to lead, job, and mileage records. Use a different geographic unit if your systems report it more reliably; the point is to compare the same small areas each month.
The three stages every lead passes through
Before you can price a lead, you have to agree on when a lead counts. Use three stages and track them separately, because each one has its own cost and its own drop-off.
Contact stage
The phone rang, the form came in, or the lead vendor delivered. Cost here is what you paid for the lead plus intake labor — the minutes someone spent answering or calling back. Some inquiries end here because the trade, location, or requested work does not fit. Your service-area math still has to absorb that acquisition and intake cost.
Qualification stage
Someone confirmed the requested service fits what you offer and the property sits in a zone you are currently accepting. Cost here is more intake time and whatever review your written process requires. This is also where the service-area rule first does real work: a lead from a paused zone gets a clear disposition before anyone schedules a truck.
Authorization stage
The customer signed the applicable work authorization or approved the estimate. From here the job consumes travel, crew hours, and equipment, and may produce gross profit. For the formulas below, use an end-to-end authorization rate: authorized jobs divided by all received leads in that ZIP cohort. Track qualified-to-authorized conversion separately for sales review, but do not substitute it for the end-to-end rate when valuing every lead you purchased or received.
Write the stage definitions on one page and make the office log every lead into one of them. If your records cannot say how many May leads from 43119 reached authorization, no formula in this article will save you, because you will be feeding it guesses.
Round-trip miles and loaded crew time
Travel cost has two parts, and shops routinely count one and forget the other.
Miles. Round-trip miles from your shop or from the crew's previous stop, times a cost per mile that covers fuel, wear, and insurance. Pick a number from your own fuel and maintenance records; do not borrow one.
Loaded crew hours. Round-trip drive hours, times the number of people in the truck, times each person's loaded hourly rate — wage plus payroll burden, benefits, and insurance. Two technicians riding to a far job are not free just because nobody clocked a task during the drive.
In words: travel cost per round trip equals (round-trip miles × cost per mile) plus (round-trip drive hours × technicians in the truck × loaded hourly rate).
Example, with numbers chosen for illustration and not as benchmarks: 46 round-trip miles at $0.70 per mile is $32.20. At an average 55 mph, the total round-trip drive is 46 ÷ 55 = 0.84 hours. Two technicians at a loaded $42 per hour cost 0.84 × 2 × $42 = $70.56 using the rounded time. Using the unrounded time, total travel cost is about $102.45. If your route, vehicle, or crew differs, your number will differ — that is the point of running your own figures.
One more field worth logging: drive time at the hour the job actually happens. A 46-mile run at 2:00 p.m. and the same run at 5:15 p.m. are different jobs. If your far-zone leads cluster at rush hour, your loaded hours are worse than the mileage suggests.
Expected gross profit per lead
Now convert closes into expectations. Three formulas, each in plain words:
- Gross profit per job = average collected job revenue × (1 − direct cost share). Define direct cost with your accountant and apply that policy consistently; do not mix unlike definitions across ZIP cohorts.
- Expected gross profit per received lead = gross profit per job × end-to-end authorization rate. If half of all received leads in the example become authorized jobs, a $2,976 gross-profit job produces $1,488 of expected gross profit per received lead before travel.
- Total cost per received lead = lead cost + intake labor + expected travel cost per received lead. In the simplified example below, one modeled trip is assigned to each authorized job, so expected travel equals trip cost × end-to-end authorization rate.
Subtract the third from the second and you get expected net gross profit per lead — the single figure that decides whether a ZIP earns its place on the map. Compare it against a floor you set deliberately: the minimum net figure a lead must clear to stay in the accepted list. Shops set different floors depending on backlog and overhead, so there is no universal number; there is only yours, written down.
The Service Area Break-even Calculator walks through mileage, drive time, crew size, expected job contribution, authorization rate, and lead cost separately. Keeping time and mileage as separate inputs is more reliable than forcing both into one per-mile assumption.
A worked example: three ZIP cohorts
Here is a complete example for a two-tech crew doing both emergency mitigation and planned waterproofing installs. Every number below is an illustration of the method, not a benchmark or a recommendation.
Shared assumptions (examples): lead cost $95; intake labor 30 minutes at a loaded $24 per hour, so $12 per lead; cost per mile $0.70; average speed 55 mph; two technicians at a loaded $42 per hour.
Mitigation job: average collected job revenue $4,800, direct cost share 38%, so gross profit per job = 4,800 × 0.62 = $2,976. End-to-end authorization rate 50%. Expected gross profit per received lead = $1,488.
Small install job: average collected job revenue $1,900, direct cost share 55%, gross profit per job = 1,900 × 0.45 = $855. End-to-end authorization rate 35%. Expected gross profit per received lead = 855 × 0.35 = $299.25.
Set an example net floor of $170 per lead. That floor is invented for this example, not recommended. Now run three cohorts:
| Cohort / example ZIPs | Round-trip miles | Travel cost per round trip | Net per mitigation lead | Net per small-install lead | Verdict |
|---|---|---|---|---|---|
| Core ZIP cohort | 18 | $40.09 | $1,361 | $178 | Keep both lines open |
| Extended ZIP cohort | 46 | $102.45 | $1,330 | $156 | Keep mitigation; test small installs against the $170 example floor |
| Long-haul ZIP cohort | 88 | $196.00 | $1,283 | $124 | Keep mitigation; pause small installs |
Here is one row worked end to end so you can check the method. Extended cohort, mitigation line: 46 round-trip miles at 55 mph is 0.836 drive hours; loaded crew cost = 0.836 × 2 × $42 = $70.25; mileage = 46 × $0.70 = $32.20; travel per authorized job = $102.45. Weighted by the example 50% end-to-end authorization rate, travel per received lead = $51.23. Total cost per received lead = $95 + $12 + $51.23 = $158.23. Net = $1,488 − $158.23 = $1,329.77, which rounds to the table's $1,330.
Within this invented example, the mitigation line remains above the example floor while the small-install line falls below it as distance increases. That is not proof that a real long-haul mitigation call should be accepted; capacity, response commitments, job mix, and actual costs still matter. It does show why the same ZIP may carry a different rule for each service line.
Also notice what the table cannot tell you: whether your crews had the hours to spare. That is the next section.
Urgency, capacity, and when distance bends
The math above assumes the truck can go. Two conditions bend that assumption.
Urgency. A distant commitment can affect the response window you offer other callers. Before adding distance, use the Lead Response Opportunity Calculator with your own pipeline numbers, then compare that modeled opportunity with what the far ZIP contributes. If a distant service is conditional on spare capacity, say so in the dispatch rule rather than deciding differently on every call.
Capacity. A planned waterproofing or drainage job may block another appointment even when its measured drive time is modest. Record the calendar effect as well as the mileage. Compare the far job's expected contribution with the alternative work that the same crew time could support closer to base. If the far job only works when the calendar has room, write that condition into the rule.
Capacity rules are also where you protect the customers who fund the whole map. If accepting a distant job routinely pushes a core-zone callback to next week, the distant ZIP is borrowing from the ZIPs that pay your rent. The monthly review below is where that shows up in numbers.
The monthly keep / test / pause review
A service-area strategy is a hypothesis until the data comes back. Review it once a month, same day, same worksheet. Pull these fields per ZIP:
- Leads received, split by stage reached: contact, qualified, authorized
- Authorization rate and average gross profit per closed job
- Round-trip miles actually driven (from job records, not the map estimate)
- Drive hours and loaded crew hours consumed
- Response time on emergency calls, measured from first contact to on-site
- Net expected gross profit per lead, computed with the formulas above
- Verdict, effective date, and the condition attached to it
Then apply three verdicts:
- Keep — the cohort has enough records for your chosen evidence threshold, expected contribution cleared your floor, and the zone did not break a capacity or response commitment. The ZIP stays on the accepted list under its current conditions.
- Test — the ZIP is new, the sample is too thin for your evidence threshold, or the result sits near the floor. Keep accepting under a written condition and a dated review point.
- Pause — the cohort repeatedly missed the written floor or accepting it broke a more important capacity commitment. Move the ZIP to your documented non-acceptance or referral procedure and identify what material change would justify another test.
Track the verdict history. A ZIP that cycles keep → pause → keep every quarter is usually telling you the floor is wrong, or that one large job is propping up a weak average. The small-shop restoration KPI guide covers the surrounding numbers — close rate, average job size, revenue per crew hour — that keep this review honest.
Google Business Profile settings are a different decision
Keep the operating decision and the profile settings in separate lanes. Your service-area strategy decides where crews go and why. Your Google Business Profile service-area settings describe where you actually serve customers, and the settings should follow the operating decision — never the reverse. Do not widen the profile to chase visibility in a ZIP your own worksheet just paused.
Google's own service-area guidance and its guidelines for representing a business are the references here, and both change over time: check the live pages rather than copying a distance limit or field count from an article, including this one. The durable principles are to represent the areas you genuinely serve, accurately, and to keep the profile consistent with reality. Google's documentation addresses eligibility and representation, not rankings — no setting guarantees placement.
For the non-profile pieces of being findable — citations, reviews, photos of real work — the local marketing foundation checklist pairs with this strategy: the checklist covers how you appear, this article covers where you appear.
Questions owners ask
- Should I just accept everything within an hour's drive?
- You can drive it; the question is what it nets. Run the ZIP through the formulas. If a far job only makes sense when the calendar is open, write that condition into the rule instead of leaving it to whoever answers the phone.
- Do I really count the office manager's time in lead cost?
- Yes. Intake minutes are a real cost per lead, same as the lead fee. If intake takes 30 minutes at a loaded $24 per hour, that is $12 against every lead whether it closes or not.
- One big job made a weak ZIP look great last month. Now what?
- That is a thin sample, not a verdict. Keep the ZIP in test status, note the condition, and require a second month of data before promoting it to keep. The verdict history exists precisely for this.
- ZIP codes or county lines?
- Use the smallest geographic unit that your lead, job, and travel systems all record consistently. That is often a ZIP code, but a dense ZIP may still need a drive-time or neighborhood condition. Consistent records matter more than the boundary label.
Sources and operating boundaries
- Google Business Profile service-area guidance — current principles for representing the areas you serve. Check the live page for present-day limits and fields rather than relying on any stated here.
- Google guidelines for representing a business — accuracy and eligibility expectations for profile content. These address representation, not ranking outcomes.
This article covers business operations — pricing a service area, reviewing it, and recording the decisions. It does not replace qualified professionals on the subjects it deliberately leaves alone: technical diagnoses of water problems, safety clearance for entry into affected structures, accounting treatment of costs and burden, and any legal or insurance questions about the work you accept. Those belong with the licensed and credentialed people who carry them. WaterProStack is a resource for contractors, not a restoration firm, an insurer, or an emergency service.