Managing Corporate AV Call-Off Work: Rate Cards, Scope Control, and Billing Discipline for AV Systems Integrators

An AV integrator who wins a long-term corporate account faces a different operational problem than one running a series of one-off projects. The commercial model shifts. Instead of pricing each job from scratch, the business operates against a rate card agreed months earlier. Instead of a clear project end date, work arrives as a stream of call-off instructions - some routine, some substantial, most somewhere in between. The challenge is not landing the account. It is building the operational discipline to extract the margin the rate card was supposed to deliver.

Data from ISE 2026 shows that integration firms are increasingly using managed service arrangements to break free from the traditional seven-year rip-and-replace cycle and instead build ongoing relationships with corporate clients. That transition changes the revenue model - but it also changes the operational model, and integrators who treat a managed account the same way they treat a project account will lose money on it.

What a Corporate Call-Off Arrangement Looks Like

A corporate call-off arrangement typically begins with a master service agreement (MSA), sometimes called a framework agreement, between the integrator and the client. The MSA sets out the commercial terms - rate card, payment terms, notice periods, liability limits, and performance obligations. It does not commit the client to any specific volume of work. Instead, it establishes the conditions under which individual call-off instructions will be placed.

A call-off instruction is a request for a defined piece of work under the MSA. It might be a single boardroom upgrade, a multi-room conferencing rollout across a new floor, or a reactive install to support a business change. Some call-offs arrive as a formal statement of work. Others arrive as an email from the facilities manager or IT director. Either way, the integrator is expected to scope the work, confirm it falls within (or outside) the rate card, resource it, execute it, and invoice it - all within whatever turnaround time the MSA specifies.

The key structural difference from project work is that commercial and operational decisions happen much faster. In a project environment, the integrator prices the job, agrees the contract, and mobilizes. In a call-off environment, the rate card has already set the commercial framework - the integrator's job is to scope correctly, execute efficiently, and bill accurately against terms that were agreed before the instruction arrived.

Building the Rate Card Right

The rate card is the commercial backbone of any managed AV account. Get it wrong at the start and every call-off that follows erodes margin. Get it right and the account becomes one of the most predictable revenue streams in the business.

A well-structured AV rate card organizes labor into distinct categories. System design and pre-installation engineering sit separately from installation labor, which sits separately from commissioning and testing, which sits separately from post-installation support. Each category carries a different cost base. A senior systems designer charges out at a different rate than a second-fix installer. Combining them into a single "day rate" and pricing to the middle leaves money behind on design-heavy call-offs and loses money on installation-heavy ones.

Equipment is another area where integrators undervalue the rate card. Corporate clients understand that hardware costs vary with the market. Most MSAs include a mechanism for equipment pricing - either a percentage margin above trade cost, a named-brand price list with an agreed uplift, or a hybrid approach. Integrators who try to hold equipment pricing flat over a multi-year MSA will find that supply chain fluctuations quickly compress margins on orders placed after an initial favorable procurement period.

The third area where rate cards fall short is project management. Coordinating a four-room boardroom rollout across a live corporate campus involves site access scheduling, liaison with the client's facilities and IT teams, equipment storage and logistics, and commissioning coordination. That coordination cost is real. If the rate card does not include a project management line - or if it bundles project management into the labor rate without separating it out - that cost gets absorbed rather than recovered.

Scope Control on Call-Off Work

Scope creep is a known problem on project work. On managed accounts, it is structurally worse - because the client does not experience individual call-offs as commercial decisions. They experience them as operational requests to the integrator they already have a contract with.

The practical consequence is that scope additions on call-off work tend to arrive informally. A facilities manager sends an email asking for "one more screen in the breakout area while the team is on site." The installation crew, three hours into the day, adds it to the job. It gets captured on the day sheet. It may or may not get invoiced, depending on whether the project coordinator notices it when closing out the call-off record.

Effective scope control on managed accounts requires two things. First, a written scope sign-off process for every call-off instruction. Even routine requests should go through a brief confirmation step - the integrator confirms scope, confirms that the work is within the rate card or will require a supplement, and gets approval before mobilizing. This takes minutes on small jobs. It prevents significant disputes on larger ones.

Second, a clear definition - in the MSA itself - of what is within rate and what triggers a new quotation. Common categories to define explicitly include: work that requires structural modifications to the installation environment, work involving manufacturer-specific programming or code changes beyond standard configuration, out-of-hours or expedited delivery, and supply of equipment not previously specified in any works schedule. If the MSA does not define these boundaries, the client's natural assumption is that everything falls within rate. And that assumption is usually wrong.

Billing and Revenue Recognition Under a Call-Off Model

Billing on managed accounts is one of the most common places integrators lose revenue they have genuinely earned. The mechanisms are different from project billing, and integrators who apply project billing habits to managed accounts typically end up with aged work that either gets written off or disputed.

Project billing is usually milestone-based: deposit, stage payment on installation, final payment on sign-off. Call-off billing is different. Individual call-offs may be too small for a multi-stage payment schedule. The volume of instructions may make it impractical to close each one individually before invoicing. And the MSA may specify a billing cycle - monthly or quarterly - that does not align with how individual call-offs are completed.

The most effective approach for most managed AV accounts is a consolidated billing cycle with individual call-off records to support it. All call-offs completed within the billing period - whether two or twenty - are consolidated onto a single invoice that references each call-off instruction by number. The supporting records (scope confirmation, day sheets, commissioning sign-off) are attached or available on request. This gives the client the transparency they need to approve payment and gives the integrator a clean, auditable billing trail.

Revenue recognition is a separate consideration for integrators who carry call-off work across accounting periods. A call-off instruction received in month three but completed in month four needs to be recognized in the correct period. Accrued revenue treatment applies where work has been delivered but not yet invoiced. If the business does not capture this consistently, monthly accounts will understate revenue during active periods and overstate it when billing catches up.

Reporting, Performance, and Renewal Discipline

An MSA does not renew itself. Corporate accounts that generate regular call-off work do so because the integrator performs against the agreed terms - response times, quality, on-time completion, and accurate billing. Integrators who cannot demonstrate that performance clearly at renewal time are negotiating from a weaker position than the account justifies.

Most MSAs include a performance reporting obligation, even if it is loosely defined. At minimum, the integrator should be able to report on: call-off volumes by period, average response and completion times against the agreed service level agreement, any call-offs that required a scope supplement and the commercial outcome of each, and any snags or defects raised and how they were resolved.

If the operational system captures this data as a byproduct of running the work - rather than requiring separate reporting effort - the integrator can produce a performance summary in minutes. If it requires manual collation from day sheets, emails, and a separate billing record, the report will either not be produced or will be produced too infrequently to be useful.

The renewal conversation is also where operational performance data becomes commercial leverage. An integrator who can show that average call-off response time is 1.4 days against a two-day SLA, that 97% of call-offs were completed on first mobilization, and that billing accuracy is strong (no disputed invoices in twelve months), has a defensible case for a rate card uplift at renewal. An integrator who cannot quantify their own performance is conceding that ground to the client, whose primary interest at renewal is in holding rates flat or securing a reduction.

How Zigaflow Supports Managed Account Operations

Running a managed AV account requires the same operational foundation as project work - quoting, job management, purchasing, invoicing - but applied across a higher volume of smaller, faster-moving pieces of work. The overhead of creating a separate record for every call-off, linking it to the correct MSA rate card, confirming scope, and then closing it out ready for consolidated billing adds up quickly if it is handled across disconnected systems.

Zigaflow gives AV integrators a single platform to manage call-off instructions from receipt through to invoiced completion. Each call-off can be raised as a job against the parent account, priced from the agreed rate card, resourced, and tracked to completion. Invoices draw from the closed job records, making consolidated billing straightforward and the audit trail transparent. For integrators working on multiple concurrent corporate accounts, project tracking gives visibility across all active call-offs at once.

For integrators moving from one-off project work to managed account operations, the discipline is about using the same system for both - and not defaulting to email and spreadsheets for smaller call-offs on the assumption that the overhead does not justify the record.

Building an Account Worth Renewing

A corporate AV call-off account is worth more than the sum of its individual call-offs if it is run correctly. The rate card sets the commercial framework. Scope control protects the margin on individual instructions. Billing discipline ensures that earned revenue is collected. Reporting demonstrates performance that justifies renewal.

The integrators who lose managed accounts between the first and second term usually lose them operationally, not commercially. The rate card was reasonable. The technical quality was fine. What was missing was the discipline to capture, bill, and account for everything that had been delivered - consistently, across every call-off, every billing cycle, and every quarter. Build the operational model before winning the account, and it will support the account rather than struggle to keep up with it.