Service & Maintenance Contracts

How It Works & Technology Overview

Post-installation service converts an installed base into recurring revenue — and into hedged risk. Every installed system has a measurable failure rate, component lifecycle, and manufacturer-warranty boundary; the agreement's job is to price that exposure deliberately. Delivery components: preventive maintenance (scheduled visits with per-system checklists — filters, firmware, testing, cleaning), remote monitoring (platform alerts from UPS/network/camera/AV systems routed into a ticket queue with defined response), reactive service (break/fix dispatches under SLA), and administrative overhead (contract management, RMA handling, reporting). The economics divide predictable cost (PMs, monitoring, updates — priceable with confidence) from unpredictable cost (failures, moves/adds/changes, user error) — the contract structure must put every unpredictable category explicitly inside or outside the fee.

Common Contract & SLA Structures

• Time & Materials: pay-per-incident at service rates; zero risk to the provider, no revenue predictability, lowest client commitment. Often with a priority-rate uplift for non-contract clients.
• Block hours: pre-purchased hours at a discount, drawn down per incident; set a monthly floor/expiration so clients can't bank hours for a month-11 drawdown.
• Flat-rate/full coverage: fixed monthly fee for a defined system inventory and service scope; the provider carries the risk, priced from the calculated annual labor burden plus a risk premium scaled to fleet age and condition.
• SLA tiers: response commitments priced by severity — e.g., business-critical (P1) 4-hour response, standard next-business-day, convenience best-effort. Response ≠ resolution; commit to what dispatch logistics can actually deliver given travel distances and tech availability. After-hours/24/7 coverage adds 20–30% to monitoring/response labor cost and needs an on-call structure behind it.
• Warranty pass-through: first-year labor often bundled with the install; the service contract begins where the project warranty ends — draw that line in the proposal.

What's Typically Included vs. Billable

Included in a typical flat agreement: scheduled PMs, remote monitoring and business-hours alert response, firmware/software updates within versions, phone/remote support, manufacturer-warranty RMA administration. Explicitly billable (or premium-priced if included): moves, adds, and changes (define what counts — one client's MACs are 2 hours a month, another's 2 hours a week), post-warranty parts and hardware failure replacement (covered parts demand a steep risk premium), user-error and training dispatches, client-side IT changes that break integrations, programming/configuration changes, and anything on inherited systems that predates a paid baseline assessment. The universal disputes are backup/DR inclusion (in IT-flavored agreements) and parts coverage — settle both explicitly in the contract, never by precedent. "While you're here" field favors executed under a maintenance ticket are the classic margin leak — change-order or decline.

What Makes It Hard (Gotchas & Failure Modes)

• Flat-rate on an aged fleet: a 10-year-old installed base under full coverage is a loss-in-waiting; price by asset age or exclude end-of-life systems.
• End-of-support inheritance: systems past manufacturer support that the client expects covered — parts don't exist, escalation lines are dead, you own the problem. Exclude or premium-price, in writing.
• Third-party footprints: competitor-built systems with no documentation, no admin passwords, no source programming — require a paid discovery/baseline assessment (line tests, config capture, defect list remediated at client expense) before any fixed rate.
• Monitoring expectation gaps: platforms alert 24/7; the contract covers business hours; the client assumes someone is watching at 2 a.m. Align the alert routing with the coverage actually sold.
• Windshield-time bleed: multi-site agreements priced on tool time while driving, parking, and security check-ins consume more hours than the repairs — geography is a pricing input.
• Deferred-maintenance boomerang: clients who skip PM windows because "everything's fine" schedule their emergency for peak hours at overtime rates; contractually tie SLA validity to completed PMs.
• Manufacturer RMA timelines vs your SLA: never tie your uptime commitment to a vendor's depot turnaround — for critical-uptime clients, mandate a client-funded spares kit for instant swaps.

Effort & Estimation Patterns

• Price from annual labor burden, not construction cost: count PM visits × checklist hours, expected dispatch volume from fleet size/age, monitoring triage load, RMA admin, and account review — then add the risk premium. Percent-of-project pricing is how underwater contracts get written.
• PM norms: AV conference room 1–2 hours per room per quarterly visit; camera systems ~10–15 minutes per camera annually (clean/focus/verify recording) plus head-end checks; fire alarm inspection (UL monitored) ~1 hour per panel + 15 minutes per device; UPS/IDF check 30–60 minutes per closet.
• Monitoring staffing: business-hours alert coverage plans 0.5–1 FTE per 50 managed clients; after-hours +20–30%.
• Response logistics: a 4-hour SLA is a dispatch-radius commitment — map tech home locations against site geography before signing.
• Contract admin: budget 2–4 hours per account per quarter for reporting, review meetings, and renewals — unpriced account management quietly erodes agreement margin.
• Annual escalators: build in rate-review/CPI clauses; multi-year flat pricing against rising labor cost is a slow leak.