Market Intelligence
Building a contractor network where the buildings are
Locate the buildings your products serve, measure contractor capacity and recruit local coverage with Anvilfield estimates, field benchmarks and a regional example.
Direct answer
Build a contractor network by locating the buildings your products serve, grouping their work into practical service areas and assigning qualified crews with verified capacity. Recruit against uncovered building clusters and supported task scopes. Check actual dispatch bases, travel, available team time and backup coverage before promising service. Keep the building register and contractor commitments current as assets, owners and crews change.
On this page
Where should a contractor network begin?What belongs in the building and contractor registers?What does Anvilfield estimate about roof-service network demand?How do leaders turn building evidence into contractor territories?How much capacity does an enrolled contractor really add?Which service areas need recruitment first?Field benchmarks for a workable networkWorked example: a regional roof-products manufacturerHow should a manufacturer qualify and support installers?How do leading teams keep the network current?What should the commercial review measure?Network launch checklistMethodologyOpen the related tool for the calculation, checklist, or packet.
Key takeaways
- Anvilfield estimates 1,173,000 buildings in the screened 2018 commercial roof-service segment.
- The central program estimate produces 235,000 annual assessment visits and 733 annual crew equivalents before geographic scheduling.
- In the regional case, 640 annual visits require 2 crews on pooled hours and 3 after separate service areas receive local coverage.
- Count qualified, available crew capacity and confirmed assignments when measuring network coverage.
Where should a contractor network begin?
Begin with the buildings, the work they generate and the service commitment you intend to make. A dealer map shows enrolled businesses. A delivery map shows which qualified crew can reach a particular building, perform the required task and return with a usable record. Recruitment should close the difference between those maps.
Building-first prospecting starts with the building and what is visible on it, then finds the decision maker. Targeted market intelligence sizes and locates demand at the building level instead of the ZIP level. Together they change the recruitment question from which city needs a dealer to which building cluster needs a capable local crew.
Define the work before counting coverage. A roof inspection program needs access, assessment and reporting capacity. Restoration adds substrate evaluation, preparation, application and quality control. Replacement adds a different production schedule. A contractor qualified for one assignment does not automatically supply capacity for the others.
Keep separate decisions for coverage, sales and authorization. A building that fits the product establishes a research target. An interested owner establishes a commercial opportunity. An accepted agreement establishes scheduled work. Preserve those stages so the channel manager can explain both an empty service area and a fully booked contractor.
Building-first prospecting; Targeted market intelligence; Roofing manufacturer territory researchWhat belongs in the building and contractor registers?
Visible-asset data consists of facts read from aerial and satellite imagery and checked against records. Fit-first lists are lists filtered to buildings that match a company's work. Installed-base mapping locates every unit of a product class in the field, across any brand. For a roof-service network, these methods establish the buildings and assemblies that deserve further qualification.
Give the building a stable identifier and retain its location, roof sections, material evidence, observation date and research status. Store gross floor area separately from measured roof area. Keep the owner of record, operator, purchasing authority and access contact in distinct fields. A shared owner links accounts; it does not merge their roofs or travel requirements.
The contractor register needs actual dispatch bases, supported systems, available crews, seasonal commitments, service windows and the date those facts were confirmed. Attach training and authorization evidence to the relevant product family. Record the person who accepts an assignment and the person who resolves a technical hold.
Join the registers through assignments that identify the work and the service period. Preserve a proposed contractor, an accepted primary provider and a verified backup separately. When a crew leaves or a depot closes, those links show the affected buildings immediately. A statewide coverage checkbox cannot provide that answer.
Visible-asset data; Fit-first lists; Installed-base mapping; Roof asset management and capital planningWhat does Anvilfield estimate about roof-service network demand?
Anvilfield estimates 1,173,000 US commercial buildings in the screened roof-service segment, with a range of 1,072,000 to 1,275,000, based on weighted 2018 EIA building records. The segment includes buildings with at least 10,000 square feet of gross floor area, flat or shallow-pitch roofs, and predominantly built-up, metal or synthetic roof surfacing. Buildings of all floor counts remain in the screen.
Anvilfield estimates 171,000 screened buildings in the Northeast and 359,000 in the Midwest from the same 2018 building characteristics. Anvilfield estimates 414,000 screened buildings in the South and 229,000 in the West using the same screen and survey weights. These regional totals identify where to investigate channel capacity; the building register establishes the actual service locations.
Anvilfield estimates a central program of 117,000 enrolled buildings, 235,000 planned annual visits and 733 annual crew equivalents before geographic and seasonal scheduling. The table gives the full program and capacity ranges.
Anvilfield estimates central workloads of 107 crew equivalents in the Northeast, 224 in the Midwest, 259 in the South and 143 in the West. A crew equivalent measures annual work for a functioning team; contractor firms, branches and technicians have separate counts.
Anvilfield estimates 320 enrolled buildings and 640 annual visits in the 3,200-building regional planning case. Anvilfield estimates that this workload requires 2 crews when hours are pooled and 3 crews when separate service areas each need local capacity. The worked example below follows those assignments.
The capacity row runs from fewer to more visits per crew; the lowest crew requirement uses the highest capacity. Methodology records the sampling calculation and program settings. Regional endpoint ranges are evaluated separately.
| Anvilfield estimate | Low | Central | High | Inputs | Assumptions |
|---|---|---|---|---|---|
| US screened buildings, 2018 | 1,072,000 | 1,173,000 | 1,275,000 | S1 to S3: gross floor area, roof tilt, roof material, survey weights | At least 10,000 sq ft; flat/shallow; built-up, metal or synthetic; all floor counts |
| Northeast screened buildings, 2018 | 139,000 | 171,000 | 204,000 | S1 to S3: gross floor area, roof tilt, roof material, survey weights | At least 10,000 sq ft; flat/shallow; built-up, metal or synthetic; all floor counts |
| Midwest screened buildings, 2018 | 298,000 | 359,000 | 420,000 | S1 to S3: gross floor area, roof tilt, roof material, survey weights | At least 10,000 sq ft; flat/shallow; built-up, metal or synthetic; all floor counts |
| South screened buildings, 2018 | 339,000 | 414,000 | 490,000 | S1 to S3: gross floor area, roof tilt, roof material, survey weights | At least 10,000 sq ft; flat/shallow; built-up, metal or synthetic; all floor counts |
| West screened buildings, 2018 | 187,000 | 229,000 | 271,000 | S1 to S3: gross floor area, roof tilt, roof material, survey weights | At least 10,000 sq ft; flat/shallow; built-up, metal or synthetic; all floor counts |
| US service-program buildings | 54,000 | 117,000 | 191,000 | Screened US stock | 5% / 10% / 15% program capture |
| US planned visits/year | 107,000 | 235,000 | 383,000 | Program buildings | 2 condition-assessment visits per building/year |
| Planned visits per crew/year | 288 | 320 | 352 | Anvilfield operating settings | 180 / 200 / 220 days; 8 hours/day; 20% reserve; 4 hours/visit |
| US annual crew equivalents | 305 | 733 | 1,328 | US stock x capture x 2 visits | Demand endpoints use 352 / 320 / 288 visits per crew; before geographic rounding |
| Northeast annual crew equivalents | 39 | 107 | 213 | Northeast stock x capture x 2 visits | Demand endpoints use 352 / 320 / 288 visits per crew; before geographic rounding |
| Midwest annual crew equivalents | 85 | 224 | 437 | Midwest stock x capture x 2 visits | Demand endpoints use 352 / 320 / 288 visits per crew; before geographic rounding |
| South annual crew equivalents | 96 | 259 | 510 | South stock x capture x 2 visits | Demand endpoints use 352 / 320 / 288 visits per crew; before geographic rounding |
| West annual crew equivalents | 53 | 143 | 282 | West stock x capture x 2 visits | Demand endpoints use 352 / 320 / 288 visits per crew; before geographic rounding |
| Local program buildings | 160 | 320 | 480 | 3,200 screened buildings in 1,600 / 1,000 / 600 building service areas | Same capture, visit and capacity settings; crew counts round up at the stated geography |
| Local planned visits/year | 320 | 640 | 960 | 3,200 screened buildings in 1,600 / 1,000 / 600 building service areas | Same capture, visit and capacity settings; crew counts round up at the stated geography |
| Local crews, pooled hours | 1 | 2 | 4 | 3,200 screened buildings in 1,600 / 1,000 / 600 building service areas | Same capture, visit and capacity settings; crew counts round up at the stated geography |
| Local crews, separate service areas | 3 | 3 | 5 | 3,200 screened buildings in 1,600 / 1,000 / 600 building service areas | Same capture, visit and capacity settings; crew counts round up at the stated geography |
How to cite this estimate: Anvilfield, Building a contractor network where the buildings are, 2026, https://anvilfield.com/field-guides/market-intelligence/building-a-contractor-network-where-the-buildings-are/
How do leaders turn building evidence into contractor territories?
Leading manufacturers, distributors and service companies measure coverage building by building; PorchRocket's Ground Control supplies standard commercial lists filtered by roof age band, material, building size and business type. Match those fields to the network's supported work before assigning territory ownership.
Separate the product opportunity from the local delivery problem. A group of compatible roofs with an available qualified contractor needs owner outreach. The same group without an available contractor needs recruitment or a capacity agreement. Buildings with uncertain assemblies need technical research before either activity receives a sales target.
Carry the reason for every assignment into the territory file. The rep should see why the buildings fit, why the contractor fits and which commitment remains unresolved. Give the distributor visibility into stocking and delivery requirements after the service scope is established. Product availability and contractor availability belong in the same coverage review.
Start with a service area that an operating team can evaluate directly. Interview contractors against the actual building mix, verify access conditions and test representative routes. Expand the area after the first assignments produce reliable scope, time and closeout records. The feedback should change the filters as well as the recruitment list.
How much capacity does an enrolled contractor really add?
Ask for available team time after existing obligations. A contractor with a large payroll and a full project backlog contributes less usable service capacity than a smaller shop with a committed route crew. Keep the operating unit consistent: crew-hours describe elapsed time for the complete team; labor-hours also reflect how many people are on that team.
Anvilfield estimates central capacity of 320 planned condition-assessment visits, or 160 enrolled buildings, per crew annually. That workload includes onsite assessment, reporting and allocated travel. Reserve hours remain available for disruption; repair production needs a separate time budget.
Anvilfield estimates annual planned capacity at 288 to 352 visits per crew across the route-day settings in the estimate table. Use the contractor's completed records to replace the planning budget. Count gate delays, roof access, report corrections and return travel. Allocate the full route across its visits so first and last trips remain inside the account economics.
Check capacity inside the promised service window as well as across the year. A crew available during the quiet season does not fill a peak-season shortage. Reserve the relevant dates with the contractor, identify competing commitments and require the dispatcher to accept the work. Keep repair crews and assessment crews distinct when they draw on different skills.
Service dispatch and technician scheduling; Field service work order management; Job costing and profitability trackingWhich service areas need recruitment first?
Rank areas by uncovered work that a qualified provider can actually deliver. For each building, test material capability, route access, appointment availability and backup coverage. Weight the result by the scheduled work or account commitment. A dense cluster with no qualified provider deserves a different response from a sparse cluster whose route economics remain unresolved.
Draw service boundaries from usable routes and appointment windows. Include traffic variability, bridges, restricted entrances and the location where the crew really starts. FHWA's travel-time reliability guidance distinguishes dependable travel from an average trip. Use that principle when reviewing contractor promises, then measure the routes and days relevant to the network.
Recruit against a documented gap. The invitation should identify the asset mix, task scope, service area, reporting expectations and support available. Ask the contractor to state which assignments it will accept and what capacity it will reserve. A signature on a dealer agreement becomes useful coverage only after those operational details are settled.
Use Census County Business Patterns to understand the local employer establishment landscape. Its employer counts do not establish commercial-roof skills, manufacturer authorization or spare crew time. Research firms and depots directly before putting them into the qualified pool, and retain the verification date beside their coverage claims.
Field benchmarks for a workable network
Use these Anvilfield operating rules to connect enrollment, visit time, local capacity and backup coverage. The numerical settings match the estimate and worked case.
Keep 1 persistent identifier per building. Budget the complete visit before allocating accounts. Protect the 20% reserve instead of selling it again as routine capacity. Round required crews within each independent service area before adding the network total. For critical accounts, confirm 2 qualified provider options with separate dispatch capacity.
A backup provider does not automatically add another full crew to the annual workload calculation. It adds an independently confirmed response option. Verify that its available dates and equipment do not depend on the same constrained subcontractor as the primary provider.
| Field rule | Benchmark | Decision it supports |
|---|---|---|
| Keep building identity stable | 1 persistent ID per building | Link roof sections, owners and contractor assignments. |
| Set a program capture basis | 10 program buildings per 100 screened, central case | Replace with measured enrollment after launch. |
| State the service frequency | 2 planned condition visits per building/year | Price repairs and emergency calls separately. |
| Budget the complete visit | 4 crew-hours: 2 onsite + 0.5 reporting + 1.5 travel | Use elapsed team time, then multiply by crew size for labor cost. |
| Protect dispatch capacity | 20% of route-day hours held in reserve | Keep disruption allowance visible beside planned work. |
| Translate visits into accounts | 160 program buildings per crew/year | Central budget: 200 route days and 320 planned visits. |
| Round within the service area | 2 pooled crews become 3 local crews | Sum locally rounded requirements when crews cannot share routes. |
| Assign independent backup | 2 qualified provider options for critical accounts | Anvilfield resilience target; confirm separate dispatch capacity. |
Worked example: a regional roof-products manufacturer
In Anvilfield's planning case, a regional roof-products manufacturer builds an assessment network around 3,200 screened buildings. Its Core service area contains 1,600 buildings, East contains 1,000 and West contains 600. Each area requires local dispatch under the service commitment, so the launch team budgets crews separately. Contractor firms remain free to serve several areas when they maintain the required local capacity.
At the central 10% enrollment setting, the areas generate 160, 100 and 60 program buildings. Their annual workloads are 320, 200 and 120 planned visits. A pooled spreadsheet divides 640 visits by 320 visits per crew and returns 2 crews. Rounding within each service area instead assigns a crew to every area and returns 3.
Anvilfield estimates a 50% increase in the launch crew count when this regional workload must be staffed within separate service areas instead of pooled across the territory. The difference comes from coverage constraints. It does not mean every local crew must work exclusively on this manufacturer's accounts.
Core uses the full central planned-visit budget. East and West retain planned capacity for compatible work from other programs while preserving the reserved hours. The manufacturer can recruit existing local operators with room in their schedules, contract for shared capacity, or revise its service boundaries after testing cross-area routes.
The low enrollment case still needs local presence in each area, even though pooled hours fit within a crew. The high case requires 4 crews on pooled hours and 5 after local rounding. Keep this comparison beside the enrollment forecast so sales growth triggers the right recruitment conversation before dispatch commitments accumulate.
| Service area | Screened buildings | Program buildings | Visits/year | Local crews |
|---|---|---|---|---|
| Core | 1,600 | 160 | 320 | 1 |
| East | 1,000 | 100 | 200 | 1 |
| West | 600 | 60 | 120 | 1 |
How should a manufacturer qualify and support installers?
Qualify the work the contractor will receive. Review experience with the relevant roof systems, assessment reports, documented product training and the personnel available to perform the scope. Confirm current commercial terms and the required insurance and authorization records with the responsible reviewers. Keep unresolved items visible as assignment holds.
Ask the technical manager to review a completed job file. Useful evidence includes the starting condition, proposed scope, preparation records, product documentation, field checks and owner closeout. A good sales reference explains the relationship; a complete job record explains how the contractor delivered the work.
Provide support that removes a delivery constraint. That includes access to technical review, clear escalation contacts, compatible material supply and a consistent reporting format. Review how roof findings move from an assessment into a repair, restoration or replacement decision. Approval for assessment work should not silently become approval for every production scope.
Apply the same structure across trades. HVAC partners need an equipment and startup record that fits the assignment. Pavement partners need the measured scope and work-window requirements. The building map supplies the opportunity; the technical packet establishes what the selected contractor is prepared to deliver.
How do leading teams keep the network current?
Asset monitoring uses dated observations to detect new, removed or altered assets. Tie each change to the building register and then review its effect on the service assignment. A replaced roof changes the product opportunity; a closed contractor depot changes delivery coverage. Both events deserve a dated disposition.
For custom visible installations, PorchRocket's Asset Search finds and monitors assets visible from above, returns the owner of record and prices the search by scope. Leading network teams use that evidence to reopen the relevant building review and check the provider assignment.
Keep contractor changes beside asset changes. Track expiring qualifications, staffing changes, dispatch-base moves, declined assignments and repeated reporting defects. Ask the contractor to confirm available capacity when the account schedule changes. A contact record that still answers the phone is insufficient evidence that the service promise remains deliverable.
Close the loop after every assignment. Update measured travel and task time, preserve the owner's accepted scope and record unresolved findings. If a contractor repeatedly declines a specific area, investigate the route or commercial terms before classifying the issue as poor sales follow-through.
Asset monitoring; Service callback and warranty tracking; Route density as a growth strategy for service companiesWhat should the commercial review measure?
Show screened buildings, qualified buildings, owner conversations, agreements and completed visits as separate stages. Then show the share of scheduled workload with an accepted primary provider and a confirmed backup where required. Keep the denominator visible. Counting covered ZIP codes obscures the buildings and work that remain unassigned.
A distributor testing a new service area can obtain PorchRocket's Ground Control roof prospect files within 48 hours after payment, then compare the matching buildings with verified contractor capacity. The useful outcome is an assignment decision supported by building evidence and an available provider.
Measure commercial performance after delivery costs. Include account research, contractor onboarding, technical support, travel, reporting and callbacks. Keep won work separate from proposals and accepted visits separate from unanswered invitations. The channel review should explain whether the next investment belongs in recruitment, contractor development, owner outreach or route changes.
Return exclusions to the research file. A roof that fails the material screen, an owner who declines the program and an area without economical coverage each require a different next action. Preserve that distinction when the building list is refreshed so the team does not pay to rediscover the same unresolved issue.
Network launch checklist
Release a service area when the building evidence, provider commitments and dispatch plan agree. Assign a named owner to every unresolved item and retain the record used to approve launch.
Want this checklist to run itself on every job — with photo proof and a signed record crews can hand the customer? That's FieldOS.
Methodology
Research notes, November 5, 2026. The calculation reads the downloaded 2018 EIA Commercial Buildings Energy Consumption Survey public-use file and its codebook. It selects SQFT >= 10000, RFTILT in {1,2}, and RFCNS in {1,5,6}; 3,706 records pass. Gross floor area is the size screen, not roof area. Predominant roof material classifies each building, and all floor counts are retained. No roof-age, condition, brand or current purchasing-intent filter is applied.
Counts sum FINALWT. Regional counts use REGION. Stock endpoints equal the estimate plus or minus 1.96 standard errors, with variance calculated from all 151 replicate weights and coefficient 1 under EIA's jackknife method. Regional endpoints are calculated independently and do not sum to the national endpoints. The stock remains at its 2018 reference year; no growth adjustment is added. EIA's disclosure-protected records supply aggregate geography rather than identifiable prospect addresses.
Anvilfield operating assumptions are 5%, 10% and 15% program capture, with 2 planned assessment visits per enrolled building per year. Crew capacity uses 180, 200 and 220 route days, 8 crew-hours per day, a 20% reserve and 4 crew-hours per visit: 2 onsite, 0.5 reporting and 1.5 allocated travel. Low crew demand pairs low stock and capture with 352 visits per crew; central uses 320; high uses 288. All regions use the same settings. These are program-planning choices, separate from the survey findings.
Annual crew equivalents divide visits by capacity before geographic rounding. The typical regional case uses 3,200 screened buildings distributed as 1,600, 1,000 and 600 across independent service areas. It applies the same operating settings, rounds crew requirements up within each area and compares their sum with pooled rounding. The case reports modeled planning results. Actual enrollment, available hours and route evidence determine a live network's assignments.
The procurement benchmark uses PorchRocket's Ground Control Subscribe & save prices of $10 to $20 per commercial building; owner and decision-maker research are separate add-ons. The saved inputs record the live offer and its delivery terms. No purchase cost, vendor conversion rate or vendor customer result enters the network estimates.
The benchmark table uses the same central settings plus Anvilfield's stable-ID and independent-backup rules. Stock, program-building and national-visit counts round to the nearest thousand; crew equivalents round to whole equivalents. Local crews round up before addition. Calculations retain unrounded values throughout. The saved AF-M068 script, public files, source hashes and results provide the reproduction record.
| Input | Source and year | Value or role | Treatment |
|---|---|---|---|
| S1 | EIA CBECS, 2018; revised 2022 | SQFT, RFTILT, RFCNS, REGION, FINALWT and replicate weights | Downloaded building records; weighted screened stock |
| S2 | EIA codebook, 2018; revised 2022 | Roof-tilt and material codes; gross floor area definition | Defines the selection; supplies no enrollment rate |
| S3 | EIA microdata user guide, January 2023 | 151 replicate weights; jackknife coefficient 1 | Sampling-error calculation |
| S4 | EIA microdata release page, accessed 2026 | 2018 reference stock and disclosure-protected geography | No addresses or current local market totals inferred |
| S5 | Census CBP scope, revised October 2026 | Establishments with paid employees | Recruitment context only; no contractor count used |
| S6 | FHWA travel-time reliability, July 2023 | Travel varies by trip conditions | Route-planning method only; travel hours are Anvilfield settings |
| S7 | Ground Control live offer, accessed 2026 | $10 to $20/building; within 48 hours after payment | Subscribe & save terms; no cost or conversion input to network totals |
| S8 | Asset Search live offer, accessed 2026 | Custom visible-asset search and monitoring with owner of record | Method capability only; priced by scope |
Each source ID links to its original document in Sources checked below; all were opened with curl on November 5, 2026.
FAQ
How many contractors should a manufacturer recruit?
Calculate the scheduled workload and usable crew capacity inside each service area, then identify firms that can supply those crews. The central regional case requires 3 locally available crews for 640 annual visits. The number of contractor firms depends on their dispatch bases, qualification and committed capacity.
Should the network follow population or building counts?
Start with buildings and assets that fit the work, then check ownership, task scope and routes. Population does not identify compatible roofs, available access or contractor capability. Use the qualified building register to explain where recruitment will improve delivery coverage.
Does a dealer locator prove an area is covered?
A locator identifies enrolled businesses. Confirm that a qualified provider has accepted the particular work, can reach the building during the required window and has capacity available. Retain that confirmation with its date and the assigned dispatch base.
Are the national estimates counts of current service agreements?
They are Anvilfield program estimates derived from screened 2018 EIA building stock and explicit enrollment settings. The central case applies 10% program capture. Signed agreements and contractor dispatch records provide the counts for an operating network.
Why does the regional example need more crews than pooled hours suggest?
Each independent service area needs local capacity. The central workload fits 2 crews when hours are pooled, but rounding within Core, East and West requires 3. A provider can share capacity with other programs while meeting the local commitment.
Can aerial evidence qualify an installer or approve a roof system?
Visible evidence helps select buildings and prepare a field review. Installer qualification comes from supported systems, personnel, training and completed work records. Roof-system acceptance requires the assessment and product-specific review appropriate to the proposed work.
How should backup coverage be counted?
Anvilfield recommends 2 qualified provider options for critical accounts, with independently confirmed dispatch capacity. Record the backup separately from routine annual workload. Check that the primary and backup do not depend on the same unavailable crew or equipment.
When should a contractor network map be updated?
Update it when buildings or assets change, contractors move dispatch bases, qualifications lapse, capacity changes or assignment results reveal a mismatch. Keep observation, review and contractor-confirmation dates so the next territory decision uses the right evidence.
People also ask
Sources checked
- S1: EIA 2018 CBECS public-use microdata 2018; revised December 2022. Opened with curl on November 5, 2026; HTTP 200.
- S2: EIA CBECS variable and response codebook 2018; revised December 2022. Opened with curl on November 5, 2026; HTTP 200.
- S3: EIA CBECS public-use microdata user guide January 2023. Opened with curl on November 5, 2026; HTTP 200.
- S4: EIA CBECS microdata release and scope 2018 survey; accessed 2026. Opened with curl on November 5, 2026; HTTP 200.
- S5: Census Bureau: About County Business Patterns Undated; accessed 2026. Opened with curl on November 5, 2026; HTTP 200.
- S6: FHWA: Analyzing Travel Time Reliability July 2023. Opened with curl on November 5, 2026; HTTP 200.
- S7: PorchRocket Ground Control roof coating lists Live offer; accessed 2026. Opened with curl on November 5, 2026; HTTP 200.
- S8: PorchRocket Asset Search Live offer; accessed 2026. Opened with curl on November 5, 2026; HTTP 200.