field note
Recurring revenue for security integrators: camera health
Recurring revenue for security integrators grows when monitoring finds camera work customers never report. How to package camera health as a managed service.
2026-10-25
Recurring revenue for security integrators is income the customer pays every month whether or not anything breaks, and camera health monitoring is one of the simplest recurring lines to add to an installed base. It pays a monthly fee for watching the fleet, and it turns problems the customer would never report into scheduled, billable service work.
Project revenue is the core of most integrator businesses, and it arrives in lumps. A large install fills a quarter, and the next one may not land for months. Once the warranty period ends, the installed cameras usually generate revenue only when the customer calls about something visibly broken. Most camera problems are not visible, so the customer does not call, and the work never becomes a ticket.
What monitoring finds that customers never report
A customer reports a camera when someone looks at it and sees a problem. Most camera failures do not show up that way. They show up when someone needs footage, or when an auditor asks.
| What monitoring finds | What the customer would notice | The work it creates |
|---|---|---|
| Camera offline at a low-traffic location | Nothing, until footage is needed | Service call to restore it |
| SD card failed or missing | Nothing, until the network drops and there is no local recording | Card replacement visit |
| SD card wear high (Axis) | Nothing | Card replacement on the next scheduled visit |
| Certificate expiring | Nothing, until it expires and the camera stops connecting securely | Remote renewal |
| Firmware behind or on a published vulnerability | Nothing | Remote firmware update, or a replacement quote for models past support |
| Insecure service enabled | Nothing | Remote hardening change |
| Clock drift | Nothing, until timestamps do not line up in an investigation | Remote time correction |
| Image black or frozen | Possibly, if someone watches that view | Restart, cleaning, or replacement |
| Tamper event | Possibly, if the camera was visibly moved | Inspection visit |
Every row is real work the camera needed anyway. Monitoring does not create the problems. It finds them while they are still a scheduled visit instead of an emergency, and it puts a ticket in the integrator’s queue instead of leaving the problem to surface during an incident.
On a fleet nobody has watched, the first month carries a backlog: every condition that built up since the install. That backlog is a good opening for the service conversation, because each item comes with a camera name, a location, and a reason.
Package it as a managed service
Selling camera health monitoring as a service works best when the customer can see exactly what the monthly fee covers and what is billed on top. A structure many integrators already use for other managed services:
Included in the monthly fee.
- Continuous health monitoring of every camera under contract
- Alerts classified and routed into the integrator’s ticketing system
- A response commitment for each severity, set by the integrator
- A monthly or quarterly uptime report
Remote work, included or billed by tier.
- Firmware updates in staged waves
- Password and credential rotation
- Certificate renewal
- Hardening changes, such as turning off insecure services
Billed as service calls.
- Site visits for failed hardware, SD cards, tamper inspection, and cleaning
- Replacement of cameras past vendor support, quoted separately
How the tiers are drawn is the integrator’s decision. Some fold remote work into a higher tier so the customer never sees a separate charge for a firmware update. Others keep the monitoring fee low and bill remote work by the hour. Either way, write it down. A customer who knows a firmware wave is included does not question it on the invoice, and one who knows a site visit is billed does not expect it free.
The response commitment in the first group is what makes this a managed service: the customer buys a set time to someone working the problem, on top of the alert.
The simplest way to sell it is as a line on the service contract the customer already has, bundled with the monitoring the integrator already runs. A customer who pays for alarm monitoring understands alarm monitoring for the cameras that were already installed. It lands in the same contract, the same ticket queue, and the same SLA, so there is no new vendor for the customer to evaluate.
Have the conversation with the report, not the pitch
Monitoring is easier to sell with the customer’s own fleet in front of them than with a slide. A short assessment period works well: put the cameras under monitoring, run it for a few weeks, and bring the first report to the meeting. The customer sees their own sites, their own cameras, and their own open conditions, each with a name and a reason.
The questions a customer usually asks next are the ones a managed services contract answers. Who fixes these? How fast? What happens next month? How will we know?
Customers in regulated environments have a second reason to buy. A continuous health record with dated work orders is evidence that cameras were maintained, which is what auditors, insurers, and lawyers ask for after an incident. What auditors look for is covered in what auditors actually ask about camera systems.
Doing this across 500 cameras
On one customer’s fleet, an integrator can run camera health as a service with a technician, a spreadsheet, and a quarterly walk. Across dozens of customers and thousands of cameras, the service only holds together if findings arrive as tickets, remote work happens without trucks, and the monthly report builds itself from the record.
MentatNOC is a white-label managed services toolkit for security integrators, built to sit in the service contract next to the monitoring they already sell. Each alert opens a classified ticket in the integrator’s own ticketing system, under their own SLA, naming severity, issue type, camera, and site. Dispatch knows what failed before the truck leaves the shop, the tech brings the right part when the alert calls for one, and every truck roll is a billable fix rather than an unbilled diagnostic trip. Firmware, credentials, and certificates are changed remotely in staged waves with automatic rollback, so some faults never need a truck at all.
Each customer gets a view-only uptime view under the integrator’s brand, built from the same record the integrator works from. The integrator catches outages before the customer does and calls first, which is how the proactive hero renews contracts. It monitors device health, not video. We work with integrators, and the partner program is open to integrators, distributors, and MSSPs. The live demo shows the fleet view a customer would see.