Where AV Systems Integrators Lose Margin After Commissioning - and How to Stop It

The commissioning sign-off feels like the finish line. The system is running, the handover pack is delivered, the final invoice is raised, and the project closes. But for many AV systems integrators, the weeks and months after handover are where a quiet margin drain begins. Callback visits, programming adjustments, firmware-related reconfigurations, and ad hoc user training all consume technician and programmer time - and most of it is absorbed without a purchase order, an invoice, or a formal decision to write it off. Four specific patterns account for the majority of this post-commissioning margin loss.

Callback Visits That Don't Qualify as Equipment Warranty

When a client reports a fault, the instinct is to attend site and fix it. The problem is that a significant proportion of callback visits have nothing to do with equipment failure. The display is showing no signal because an IT policy change blocked the input. The room control panel is unresponsive because the network port was repurposed. The audio system is running at the wrong output level because someone adjusted the DSP settings locally.

None of these are equipment warranty issues. But they are routinely absorbed as warranty service because there is no clear policy stating otherwise. The direct cost of sending a technician to site - loaded labor rate plus vehicle cost - runs $150 to $250 per visit (Domotz, 2024). Add the opportunity cost of a technician not billing on a new installation and the total cost per absorbed visit reaches $250 to $350.

An integrator with 25 active clients absorbing two non-warranty callbacks per client per year is giving away $12,500 to $17,500 annually with no record of doing so. The fix is a written policy in the commissioning handover pack: warranty covers equipment failure confirmed by the integrator on site; network-related, settings-related, or user-action-related faults are billable at the service rate. That distinction does not need to be adversarial - it just needs to be in writing before the first callback happens.

Programming Change Requests Categorized as Support Calls

Control system programming is one of the highest-value activities an AV systems integrator performs. At $100 to $175 per hour (QuoteAV, Feb 2026), a skilled programmer reconfiguring a control system macro, adding a new input source to a touchpanel, or adjusting a scheduled meeting room setup represents real billable work. But when a client calls to say the system "isn't working right," those change requests are frequently handled as support rather than new scope.

The pattern is familiar: the system is working exactly as specified at commissioning, but the client's requirements have changed. A department has been restructured and the room control panel needs new routing. The CEO now wants a one-button presentation mode that was not in the original brief. An IT team lead wants the video conferencing defaults changed to match a new software platform. These are change requests - they belong on a works order with a quoted price, not on a support log absorbed as overhead.

The hourly math is direct. Two hours of programmer time on a change request, unrecovered, costs $200 to $350 per incident at the full rate. Across 15 active clients generating two absorbed change requests each per year, that is $6,000 to $10,500 written off. A written threshold - any programming change not caused by equipment failure is billable at the programming rate, minimum one hour - creates the boundary and the paper trail to enforce it.

Firmware Updates That Break Existing Configurations

Manufacturer firmware updates are a consistent operational hazard in AV integration. A display manufacturer pushes a firmware update that changes HDMI handshake timing. A DSP manufacturer releases an update that resets custom filter settings. A video conferencing platform update changes the control API endpoints the control system uses to dial. In each case, the installed system stops working correctly - and the client calls to report a fault.

These situations sit in a grey area. The equipment warranty has not expired. The integrator made no error. But resolving the issue requires a programmer at $125 to $175 per hour to reconfigure, re-test, and recommission the affected elements. Without a defined policy, that cost is absorbed.

Integrators who handle this well build two things into their client terms: first, a clause stating that reconfiguration required as a result of third-party manufacturer firmware or software updates is billable; second, a firmware management log compiled at commissioning that records the current software version of every network-connected device. The second step does two things simultaneously - it creates the documented baseline that justifies the invoice, and it makes the diagnostic process faster when something breaks after an update.

End-User Training Absorbed as Post-Handover Support

AV system commissioning and user training are not the same activity. Commissioning confirms the system operates to specification. Training confirms that specific users know how to operate it correctly. The confusion between the two costs integrators measurable technician time each year.

The typical scenario: commissioning is completed with a facilities manager present. Three weeks later, the department that actually uses the room is in the space for the first time. They cannot get the video conferencing system to display correctly on the main screen, the audio is routing to the wrong zone, and nobody knows how to use the room booking integration. The integrator attends to "fix" a system that is working exactly as designed.

At $100 to $125 per hour for a field technician, three hours of absorbed user training per site visit equals $300 to $375 per incident. Across 10 such visits per year, that is $3,000 to $3,750 given away. The operational fix is a training clause in the commissioning contract: one training session of defined scope and duration is included; subsequent sessions are billable at the published training rate. Delivery of the included session is documented separately from commissioning sign-off, with a named attendee list confirming who was trained and on which system functions.

Zigaflow's works orders give integrators a structured way to raise and price post-commissioning activities before the technician leaves the office - whether that is a firmware reconfiguration, a programming change request, or a chargeable training session. Each visit creates a job cost record, and each chargeable visit generates an invoice rather than disappearing into overhead.

The Common Thread

All four of these margin leaks share the same root cause: a gap between what the commissioning sign-off covers and what the client assumes it covers. The solution is not to become adversarial with clients after handover - it is to define the boundaries in writing before handover, so both parties know what is included and what is not. An integrator running 20 active projects per year who closes each of these four gaps can realistically recover $20,000 to $35,000 in annual margin - not from winning new work, but from correctly pricing work already being done.

Related pages