Multi-site AV rollouts: why the second site is where the margin disappears

By the third or fourth site, a multi-site AV rollout loses money for a specific reason: the contract is one document, but the delivery is dozens of separate problems. The quote was priced assuming that each location is a copy of the last - same design, same BOM, same labor hours. It is not. Ceilings differ, cable routes change, equipment substitutions accumulate, and on-site decisions that were absorbed without documentation at site one get absorbed again at site two and three. Each location drains a portion of the profit the integrator assumed was already locked in when the program contract was signed.

The Single-Quote Trap in a Multi-Site Program

Most AV integrators win a multi-site rollout by quoting it as a volume deal. The client gets consistent pricing and technology across all locations; the integrator gets scale and a substantial contract value. The logic is sound on paper: standardize the design, replicate the BOM, reduce per-site labor cost through repetition. Site 10 should cost less to deliver than site 1.

The flaw in that logic is that the quote treats all sites as interchangeable. A single BOM. A single per-site labor estimate. One site survey, conducted at the pilot location, used as the template for all subsequent locations. If site 1 is the design anchor, sites 2 through 15 are assumed to be variations of the same room. Assumption is not a site survey.

According to PMI's Pulse of the Profession, 43% of projects exceed their original budget, with an average overrun of 27%. For AV integrators running a multi-site rollout without per-site cost visibility, that overrun compounds rather than self-corrects. Each location absorbs cost that was never assigned to it, and the program average stays healthy long enough to disguise the problem until closeout.

Three Points Where Each Site Bleeds

On a multi-site rollout, margin disappears through three specific failure points that interact with each other as the program progresses.

The first is the survey cost that was never priced. Responsible multi-site AV project delivery requires a site survey at every location before hardware is ordered - not just at the pilot. That survey costs technician time, travel, and a structured deviation review before any procurement decision is made. When the rollout is quoted as a single program job, per-site survey costs are either omitted from the estimate or allocated to the pilot only. By site 5, the cumulative survey cost that was never priced is already eroding the per-site margin target.

The second is kit variation. The standard BOM is the starting point at every location; it is rarely the ending point. A ceiling at one site is four inches lower than the design assumed. A column blocks the standard display mounting position at another. A cable route that worked cleanly at sites 1 and 2 is obstructed by existing infrastructure at site 3, adding an unplanned half-day of labor. Each deviation triggers a substitution, an additional purchase order, or an unscheduled return visit. None of these generate a change order when the integrator is treating the program as one job - they are absorbed as "getting on with it."

The third is uncontrolled change. AVIXA's AV Industry Outlook and Trends Analysis consistently identifies labor planning and project cost control as among the top operational challenges for AV integrators globally, and labor represents 30 to 40% of an AV project's total cost. When each site visit generates informal adaptations - an extra display to match what was installed at the previous location, an additional cable run because the local IT team provisioned network access in a different room position - those hours are never logged against a site-specific budget. They dissolve into the program record and make the overall cost picture look acceptable until the labor tally is done at closeout.

Why the Program Contract Makes This Structurally Worse

A program contract is commercially rational. It gives the client a fixed price for multiple locations, simplifies procurement, and demonstrates the integrator's confidence in the design standard. But it creates a specific operational problem: it removes the natural financial checkpoint that a per-site structure would provide.

On a traditional single-site AV job, the integrator quotes the work, wins it, opens a job record, procures against that record, and closes the job with an invoice. Every cost sits against the job. Every deviation from the quoted scope is visible against the same record. The project manager can see, at any point, whether the job is on track.

On a program rollout where all sites live inside one contract and one job record, that visibility disappears. Costs are aggregated. The project manager sees total program spend against total program revenue. Site 6 may have cost 18% more than its per-site allocation, but that fact is invisible inside the combined record. The program average can appear healthy while individual sites are each contributing a small loss.

The Fix: One Contract, One Job Per Site

The structural correction is to set up a separate job record for each site at the point when the rollout is sold - not at the point when the site is surveyed, and not as an administrative tidy-up after problems emerge. Each site record carries its own BOM, its own labor estimate, its own survey cost allocation, and its own cost log. The client contract remains a single commercial document. The program pricing still reflects the volume relationship. But every procurement decision, every deviation from the standard design, and every informal on-site change is captured against the specific location that generated it.

Zigaflow's project tracking feature supports this structure by giving integrators visibility across all active sites in a program simultaneously, each as a distinct job record, with its own costs, purchase orders, and invoice milestones. When site 4 starts running over on labor, that variance is visible in real time against site 4's budget - not dissolved into a program average that appears healthy because sites 1 through 3 came in under target.

This approach changes what the project manager can act on. A 15% labor overrun at one location becomes a flagged issue that can be investigated, discussed with the client, and potentially billed as a change order before the installation team moves to the next site. The integrators who protect margin across a program in the audio-visual sector are the ones who impose this discipline at the start, when every site is still identical in theory, before the real world makes each one different.

The multi-site AV rollout is one of the strongest commercial opportunities in the integration market. It is also one of the most reliable ways to book significant revenue and discover at closeout that a third of the sites were unprofitable. The difference between those two outcomes is not the quality of the work. It is whether the program was structured so that each site's cost could be seen, managed, and, where necessary, billed for independently.

Sources

• AV Project Budget Tracking: Prevent Overruns & Protect MarginXTEN-AV · accessed 2026-10-05
• Nationwide AV Rollout Process: Design to Punch-List GuideITS (Intech Solutions) · accessed 2026-10-05
• Best practices for improving multi-site project managementSiteOwl · accessed 2026-10-05
• Where AV System Integrators Lose MarginZigaflow · accessed 2026-10-05
• How to Conduct a Proper Site Survey (and Avoid Problems Later)AVIXA · accessed 2026-10-05