field note
How to grow a security integration business
Growing a security integration business means adding service revenue to project work. Where growth comes from: the installed base, service contracts, refresh.
2026-10-25
A security integration business grows most predictably when it adds service revenue on top of project work, so that every finished install becomes a customer who pays every month instead of a job that ends. Projects still matter. They are how the installed base gets built. But a business that only sells projects has to win its revenue again every quarter.
Most integrators know this and still struggle to act on it, because service revenue needs things project work does not: contracts that define the service, a way to know when something breaks before the customer calls, and reports that show the customer what they are paying for. This post maps where the growth actually comes from and what has to exist to capture it.
Project revenue and service revenue
The two kinds of revenue behave differently, and a growing business needs both.
| Project revenue | Service revenue | |
|---|---|---|
| Timing | Lumpy, tied to wins and construction schedules | Monthly, predictable |
| Sales effort | Won again for every job, often against competitors | Won once, then renewed |
| Margin pressure | Bid against other integrators on hardware and labor | Priced on the service, not the parts |
| What it builds | The installed base | The relationship that brings the next project |
Service revenue also changes what the business is worth. Buyers of integration businesses generally value contracted recurring revenue more than a project backlog, because it continues after the sale.
Five places growth comes from
Each of these is a different motion with a different first step.
1. Attach service to every new install. The easiest service customer to sign is one whose system you are about to hand over. Make a maintenance agreement part of every proposal, priced as its own line, so the customer decides on it at the same time they decide on the install.
2. Convert the installed base. Every customer whose warranty has expired is a service prospect. Many of them have never been asked. Start with the largest systems and the customers who called most often last year. The model is laid out in recurring revenue for security integrators.
3. Take over neglected accounts. Customers who are unhappy with their current integrator’s service are looking for someone who will answer. A takeover brings an installed base, a list of problems that becomes the first quote, and a customer who already decided to switch.
4. Sell refresh and compliance projects from data. Cameras past their manufacturer’s end of support, hardware covered by NDAA Section 889, and cameras that fail every month are all projects. When they come from the customer’s own monitoring record, they get approved more often than a cold proposal.
5. Charge for the first look. A paid assessment replaces the free site survey. The customer pays for a findings report, and the findings become the next project.
What has to exist first
Service revenue falls apart if the operations behind it are improvised. Before selling agreements at scale, an integrator needs four things.
- A written agreement that defines scope, response by severity, included and billed work, and exclusions.
- A response commitment the team can meet. Alerts have to arrive classified and land in the ticketing system the service desk already uses, with the SLA the integrator set. The structure is in how integrators set a surveillance system SLA.
- A way to fix it on the first trip. Firmware, credentials, and certificates handled remotely, and trucks sent with a diagnosis and the right part. Covered in truck rolls that fix it.
- Reports the customer reads. Uptime by site and camera, open conditions, and work completed, sent on a schedule.
What to measure
Track a few numbers monthly. The targets are the integrator’s to set. What matters is that they move in the right direction.
- Share of revenue from service. The clearest single signal that the business is becoming less lumpy.
- Accounts under agreement, as a share of all active customers.
- Renewal rate on agreements that reached the end of their term.
- Truck rolls per hundred cameras, and the share fixed on the first visit.
- Projects sourced from the installed base, such as refreshes and expansions that started from a service report.
Doing this across 500 cameras
An integrator with a handful of service customers can run them from a spreadsheet and memory. Once agreements cover dozens of customers and thousands of cameras, service only holds together if monitoring, alerting, remote work, and reporting run the same way for every account.
MentatNOC is a white-label managed services toolkit for security integrators. Add it to service contracts and bundle it with the monitoring services already on the price sheet: alarm monitoring for the cameras you already installed. It watches every Axis, Bosch, and Hanwha camera under management, and each alert opens a classified ticket in the integrator’s own ticketing system, under the integrator’s own SLA, naming the condition, the camera, and the site. Dispatch knows what failed before the truck leaves the shop, the tech brings the right part when the alert calls for one, and the integrator bills for every truck roll instead of eating diagnostic trips. Firmware, credentials, and certificates change remotely in staged waves with automatic rollback, so some faults never need a truck.
Each customer gets a view-only uptime view under the integrator’s brand, and the integrator catches outages before the customer does, which makes them the one who calls first. 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 views a customer would see.