In this article
Build your contractor service area strategy around work the right estimator, technician or crew can cover profitably. A radius around the office cannot tell you whether a property fits the travel, scheduling and job rules that make it worth accepting.
Build the map from actual operating conditions. Separate job types, test representative addresses, identify route barriers, and give intake staff a written rule for each ZIP. Keep that decision separate from a provider’s territory language. A contractor can have a sensible internal service area without receiving a reserved territory, and a commercially available ZIP can still be a poor operational fit.
theBuildd publishes this guide and sells residential home-improvement leads. The framework below is an operating template, not a promise of demand, contact, project fit, sold work or return on investment in any ZIP.
A contractor service area strategy needs four coverage layers
One company-wide radius hides who travels, where that person starts and what happens after the first visit. Use four coverage layers instead. They may overlap, but they do not have to be identical.
| Coverage layer | Decision it controls | Origin to test | Constraint to record |
|---|---|---|---|
| Lead intake | Whether the office may accept and work the inquiry | Office workflow, not a vehicle location | Trade, job family, property location, current capacity and required unknowns |
| Estimating | Whether the company will send someone to assess or quote | Estimator’s actual start point or prior appointment | Visit length, arrival window, return trip and proposal workload |
| Technician or service | Whether a service vehicle can cover the call | Shop, technician home base or preceding job, as applicable | Parts access, vehicle, licensing, urgency and the next scheduled stop |
| Production | Whether the company can deliver the work | Yard, supplier, crew base or active project | Crew hours, equipment movement, deliveries, parking, access and project duration |
This is a planning model, not an industry standard. Its value is that it stops an easy estimating trip from standing in for the production burden. A salesperson might reach an address comfortably while a multi-person crew, trailer or repeated material run makes the same property impractical.
Job type matters too. Housecall Pro’s current service-area guide treats service type, farthest-point travel and exceptions as inputs to the area decision. Housecall Pro is a software vendor, so that page is not evidence for a universal limit. It does support the narrower point that a working service area needs operating conditions, not just a line on a map.
Keep lead-buying coverage separate from territory terms
Three maps can describe the same contractor, and each answers a different question:
| Map or rule | What it means | What it does not prove |
|---|---|---|
| Internal lead-buying area | The ZIP and job combinations your office is prepared to evaluate | That every address or project in the ZIP fits |
| Provider territory | The provider’s written rules for availability, distribution, reservation and change | That your crews can cover the work profitably |
| Public service area | The places presented to customers on a profile or website | That a lead provider supplies those places or that capacity is available today |
Read the provider’s territory language on its own terms. The guide to exclusive lead territories owns that commercial decision, including the questions to ask about reservations and changes. This page owns the contractor’s internal acceptance map.
Do not use a Google Business Profile limit as a lead-buying benchmark. Google’s current Business Profile service-area guidance, checked 26 September 2026, says businesses can enter cities, postal codes or other areas, cannot edit a service area as a radius, and should keep the overall area within about two hours of driving time from the base. Those are rules and guidance for that public profile. They do not say that two hours is economically sensible for your estimator or crew.
The practical test is simple: if marketing, provider settings and operations contain different area lists, name each list. Do not let staff assume that an address shown publicly is automatically approved for a bought lead.
Map travel time from real crew origins, not a circle
A ZIP is useful for intake because it is easy to record and match. It is not a reliable proxy for one uniform trip. The US Census Bureau explains that ZIP Code Tabulation Areas are generalized areal representations of point-based USPS ZIP Codes. It also notes that ZCTAs can be noncontiguous. That is enough reason to test addresses rather than treating a ZIP-shaped map as proof of accessibility.
Build a travel sample in this order:
- Name the origin for each role. Use the places an estimator or crew actually starts, which may include a shop, yard, employee base, supplier or prior job. Do not default to the registered office when nobody begins there.
- Select representative destinations. Test more than the nearest edge. Include locations in different parts of the ZIP and addresses near any boundary, bridge, mountain route, ferry, toll crossing, restricted road or dense parking area that affects field work.
- Use relevant time windows. An estimator leaving between appointments and a production crew moving before a workday do not face the same conditions. Record the time window that matches the task rather than the fastest result available when the map is built.
- Measure the whole movement. Include the inbound trip, return or next stop, likely supply movement, and any repeat visits the job type normally requires. The first visit is only one part of the field burden.
- Preserve the result and its date. Store the origin, destination, job type, time window, travel duration, distance, known barrier and date checked. That makes a later review reproducible.
You can do the sampling manually with a mapping tool or automate a larger set. Google Maps Platform documents that its Compute Route Matrix method calculates distance and duration for multiple origins and destinations. That capability can organize the test, but the output is still an input to your decision. It does not know your crew, job economics, parking burden or current schedule.
Do not turn the sample into a false promise. A route result is an estimate under selected conditions, not a guarantee of future arrival time.
Build a job-type matrix before accepting a ZIP
The same ZIP can fit one type of work and fail another. Replace the single yes-or-no service radius with one row for each job family that materially changes field effort.
| Job-family input | Question to answer | Write this in the rule |
|---|---|---|
| Initial visit | Does this work require an in-person diagnosis, measurement or estimate before a proposal? | Required role, expected visit pattern and accepted origin |
| Production pattern | Is the work one visit, several visits, recurring service or a continuous project? | Number and type of field movements used in the coverage decision |
| People and equipment | Which crew, vehicle, trailer, tools or licensed role must reach the site? | Actual resource constraint, not “crew available” |
| Materials | Does the route depend on a yard, supplier, delivery zone or return trip? | Supply origin and any delivery or access restriction |
| Site conditions | Can parking, building access, permits, road limits or community rules change the burden? | Known condition and who verifies it |
| Capacity | Can the company accept this work during the relevant production window? | Capacity owner and the rule for temporary closure |
| Economics | What minimum scope makes the full field burden acceptable? | Contractor-set threshold and evidence required at intake |
Keep thresholds in company terms that an intake person can verify. “Large job” is not a rule. A named job family, minimum scope indicator or required manager review is.
The home-improvement trade directory shows the residential categories theBuildd serves generally, but it does not set a radius for any contractor. Your licensing, equipment, team, project mix and local geography control the operational map.
Set the minimum job threshold from your own economics
Extra travel may be acceptable for one project and wasteful for another. There is no honest universal project-value or drive-time threshold. Build yours from completed-job records and current capacity.
Start with the contribution available before the extra field burden:
Collected job revenue - job-variable labor - materials - subcontractors - job-specific fees = contribution before added travel
Then estimate the added field burden for the ZIP and job family. Include paid travel time, vehicle expense, tolls or parking, repeat visits, supply movement and the capacity displaced by that movement. Keep acquisition cost separate so you can see whether the problem is geography, the lead source or both.
Use the calculation as a decision test:
- Is the minimum accepted scope observable early enough for intake to apply it?
- Does the threshold cover the full visit pattern, not only the first estimate?
- Are you using collected revenue and actual job-variable costs rather than an optimistic proposal amount?
- Does the company still accept the work when the schedule is full and the distant job displaces a closer one?
- Who may approve an exception, and what evidence must that person record?
The cost per booked job guide covers acquisition and downstream outcome economics in more detail. This service-area rule should use those company-owned figures without pretending that one source cost reveals whether a distant project is worth producing.
Classify every ZIP as core, conditional or excluded
Turn the analysis into three intake classes. A map that only the owner understands is not yet an operating rule.
| Class | Default intake action | Required documentation | Typical reason |
|---|---|---|---|
| Core | Accept for the listed job families, subject to ordinary qualification and capacity | ZIP, accepted job families, valid origins and review date | Representative trips and production pattern fit the current rule |
| Conditional | Hold or accept only when written conditions are confirmed | Condition, evidence field, decision owner and exception outcome | Only certain scopes, schedules, property types or crew configurations fit |
| Excluded | Decline or route outside the paid-lead program | Exclusion reason, effective date and review owner | Travel, access, licensing, project mix or current capacity fails the rule |
Do not force an unknown request into the nearest category. If job type, property location or scope is unclear, route it to a named reviewer. Record the original homeowner-reported request separately from facts the contractor later verifies.
Geographic acceptance also is not qualification. A property can be inside a core ZIP while the project itself is outside scope. Use the separate guide to what counts as a qualified lead when defining that later stage.
A usable conditional rule reads like this:
Accept
[ZIP]for[job family]when[observable condition]is confirmed. Otherwise send it to[role]before promising a visit. Record[required evidence]and the decision reason.
Replace every bracket. If staff still need to interpret words such as “nearby,” “big enough” or “probably,” the rule is unfinished.
Review ZIP cohorts without blaming the map for every loss
Review geography at the ZIP-and-job-family level, but keep stages separate. A homeowner who never answered, an out-of-scope project, an estimator who could not make the trip and a proposal that was not accepted are different outcomes.
| Review field | What it helps diagnose | Do not conclude automatically |
|---|---|---|
| Delivered inquiries | Whether the source supplied records in the agreed coverage | That the homeowner was contacted or the project fit |
| Two-way contacts | Whether a qualification conversation occurred | That the ZIP is operationally suitable |
| In-scope projects | Whether contacted requests met the written job criteria | That travel and production economics work |
| Site visits or estimates | Whether the field step occurred | That the work sold or the trip was efficient |
| Proposals and sold work | Whether suitable opportunities moved through sales | That geography caused every win or loss |
| Collected revenue and job-variable cost | What the completed work contributed | That acquisition or travel was the only cause |
| Actual travel and repeat visits | Whether the planning assumptions held | That one unusual project represents the ZIP |
| Exceptions | Which rules staff overrode and why | That an exception should become the default |
Set the review cadence and minimum evidence standard before looking at the results. The right sample depends on your volume and decision risk, so this guide does not invent a universal number. Preserve small cohorts as inconclusive rather than forcing a confident verdict.
Remove or narrow a ZIP when repeated evidence shows an operational mismatch the company cannot correct. Expand only when the proposed job families, field resources, thresholds and intake rule have all been tested. A good project in a new area is a reason to investigate, not proof that every future lead there fits.
What ZIP coverage means when buying from theBuildd
theBuildd serves US residential home-improvement contractors under coverage agreed by trade and ZIP. That agreement controls where a lead may be supplied. It does not replace your property-level and project-level acceptance rule.
| Stage | theBuildd’s stated role | Contractor-owned decision |
|---|---|---|
| Coverage setup | Confirm current availability for the agreed trade and ZIPs | Submit only ZIP and job combinations the team can evaluate responsibly |
| Delivery | Send the lead by text and email within 10 minutes | Monitor both channels, assign an owner and preserve the receipt time |
| Distribution | There is one buyer per lead through theBuildd. The homeowner may still seek other quotes independently. | Do not describe one-buyer delivery as a promise that no other contractor can compete |
| Qualification | No provider-run qualification is promised | Verify property, project, scope, service area, timing and other written criteria |
| Operational fit | Deliver under the agreed coverage | Decide whether the actual address, job family, capacity and field burden fit |
| Remedy | Replace, rather than refund, bad leads when the written criteria are met | Preserve the evidence required by the current terms |
theBuildd does not commit to demand or lead volume in each ZIP, homeowner contact, project fit, an appointment, a sold job or return on investment. Current plans are month to month, with 10 days’ written notice before the next billing date. Review current pricing and terms before treating an offer detail as fixed.
Use this service-area worksheet before you add ZIPs
Complete one row for each candidate ZIP and job family. Do not combine job types when they use different origins, crews or visit patterns.
| Worksheet field | Entry |
|---|---|
| ZIP and job family | [One specific combination] |
| Intake class | [Core, conditional or excluded] |
| Estimator origin and sampled destinations | [Actual origin; representative addresses] |
| Crew or technician origin and sampled destinations | [Actual origin; representative addresses] |
| Relevant time windows | [When each movement normally occurs] |
| Full visit pattern | [Estimate, production, return, supply and repeat movements] |
| Barriers and access conditions | [Traffic pattern, bridge, toll, parking, ferry, road or site constraint] |
| Accepted scope and threshold | [Observable project condition based on company economics] |
| Capacity rule | [Who can pause or reopen acceptance] |
| Exception owner | [Named role and required evidence] |
| Review evidence | [Stage outcomes, actual travel, job costs and exceptions] |
| Decision date and next review | [Dates and accountable owner] |
The finished worksheet should let an intake employee answer three questions without improvising: is the ZIP accepted, does this job family fit, and who decides an exception? If it cannot, narrow the rule before adding paid volume.
Bring a service-area rule, not just a ZIP list
Share your trade, candidate ZIPs, accepted job types and contractor-owned qualification process. We will confirm current theBuildd coverage and whether the one-buyer lead model fits.