A camera installation ends when the invoice is paid. A video service begins when someone has to keep accounts working, answer access calls, investigate outages and explain what the customer is paying for next month.
That is the commercial opportunity in selling remote video under your own name. It is also the point where an installer stops reselling equipment and starts operating a service. The recurring charge only works when billing, support, account administration, escalation and site dependencies have named owners.
The recurring service is an operating model
Branded remote viewing sounds like a product feature. For the customer, it is a continuing promise: the cameras remain reachable, authorised people can sign in, alerts or recordings remain available, and somebody knows what happens when access fails.
Those promises create work across five areas:
- Billing: someone creates the charge, collects it, handles failed payments and explains what the subscription includes.
- Account administration: someone creates users, removes former employees, manages permissions and maintains the relationship between the customer, sites and devices.
- Technical support: someone handles password problems, browser access, mobile access, recorder connectivity and device changes.
- Escalation: someone decides whether a fault belongs to the camera, recorder, local network, Internet connection, viewing service or installation.
- Site dependencies: someone confirms that the installed system can support the promised workflow and keeps the prerequisites documented.
An installer can assign all five responsibilities to itself, share them with a platform provider or leave specific work with the customer. The decision must appear in the service description and the handover process. A recurring charge without an operating model turns every unclear boundary into an argument.
The customer relationship is shaped by those boundaries, which is why the next step is to define what the installer is actually promising.
Brand ownership changes the customer’s expectation
When the service appears under the installer’s name, the customer sees one accountable relationship. The camera manufacturer, recorder maker and connectivity provider can still be involved behind the scenes, but the customer needs a clear route for access problems and service questions.
That does not mean the installer must perform every task. It means the installer must explain who performs each task and how the customer reaches that person. The distinction matters because technical ownership and customer-facing ownership are separate decisions.
A useful service description answers these questions in plain language:
- What does the monthly service provide: live viewing, recorded video, user administration, alerts or a defined combination?
- Who creates and removes users?
- Who changes permissions when the customer changes staff?
- Who investigates a site that has lost its connection?
- Who pays for replacement hardware, additional installation work or an Internet service change?
- What happens when the customer wants another site, camera or user?
- Which requests are included remotely, and which require a billable visit?
Why Your Client Calls You, Not the Camera Brand explores the customer-facing relationship around the installed system. Here, the practical consequence is simple: a branded service needs a named route from the customer’s problem to its resolution.
Once the relationship is defined, the installer can discover whether the existing site is capable of supporting it.
The site has dependencies that belong in the sale
Remote video is not created by changing a logo. The recorder, server software, network path, accounts and time configuration all affect whether the customer receives the experience being sold.
Avigilon’s documented cloud-connection workflow, for example, requires Internet access, a supported Unity Server version, the Unity Video Web Endpoint Service, minimum system requirements and correctly configured time settings. The workflow also includes registering the organisation and granting users access through the service’s administration process. Avigilon’s connection documentation describes those requirements for its own system; they are a concrete example of the dependencies an installer needs to verify rather than a universal checklist for every CCTV platform.
Before offering a recurring service at an existing site, record:
- the recorder or video-management product and supported software version;
- the route from the site to the viewing service;
- the service or endpoint required to publish access;
- the customer’s administrator and user-approval process;
- the time configuration used by the recorder and cameras;
- the account credentials and recovery ownership;
- the work required if the existing system cannot meet the promised access path.
This discovery step protects the recurring service from a common commercial mistake: pricing the visible feature while leaving the site remediation outside the agreement. Existing systems bring their own constraints, which is why the existing-CCTV browser problem deserves its own technical and commercial treatment.
The site audit identifies the work. The contract must then identify who pays for it.
Price the responsibility before pricing the subscription
No credible market-wide monthly price, installer margin or support allowance can be applied to every branded video service. The charge has to come from the selected platform’s actual meter, the support scope, the connectivity arrangement and the margin the installer requires.
Build the price from explicit inputs:
- Platform cost: identify what the provider bills for the chosen service, account, site, device, stream, storage or other unit. Record the billing unit and the date checked.
- Connectivity responsibility: state whether the customer supplies the Internet connection and who investigates it when the site becomes unreachable.
- Support scope: define the requests included in the service and the work that becomes a separate charge.
- On-site work: separate remote administration from visits, replacements, rewiring, network changes and recorder upgrades.
- Risk allowance: use the installer’s own measured support records after launch rather than a claimed industry average.
- Commercial margin: add the amount required for the responsibilities the installer has accepted, then test the result against the customer’s expected value.
The provider’s price is only one input. A lower platform charge does not create a viable service if the installer accepts unlimited troubleshooting, unclear outage ownership and unpaid site visits. A higher platform charge can still be workable when the service boundaries are precise and the customer understands what is included.
Put price-change terms in the agreement. The customer needs to know whether a provider change passes through to the subscription, how much notice applies and what happens if the service can no longer be offered on the agreed terms. Do not promise price stability that the platform contract does not provide.
The price model becomes defensible when every recurring cost and responsibility has an owner. The sourcing decision should test those owners before a platform is selected.
Build, Buy or Deploy: Confirm the operating model
The installer-facing decision is narrower than a product team’s infrastructure decision. The question is which option gives the installer clear control over branding, accounts, support, media-path responsibility and price-change terms without creating an unpriced operating burden.
Build on open source
Building on open-source components gives the installer responsibility for the assembled service. That includes the customer-facing administration, deployment, upgrades, security work, monitoring, media path, recording choices and support route. It suits an organisation that has the engineering and operations capacity to maintain those responsibilities over the life of the customer relationship.
The installer should not choose this route because the individual components are available without a licence fee. The relevant calculation includes implementation, maintenance, incident response, security updates and the work required to turn components into a repeatable customer service.
Buy a cloud API
A cloud API can reduce the infrastructure the installer operates, but it does not automatically settle the customer-facing model. Confirm whether the API supports the required branding, account hierarchy, user administration, recording controls, support escalation and billing arrangement.
Also confirm what remains on the customer site. The cloud service cannot remove a recorder limitation, an unsuitable network path or an unclear local administrator. Ask where media travels, who controls recording processing and storage, and which provider terms can change the installer’s cost base.
Deploy a commercial platform
A commercial platform can provide a defined administration model and a partner route, but the installer still needs to read the operating terms. Confirm the allowed brand presentation, account ownership, renewal process, support boundary, escalation path, media-path responsibility and notice for price changes.
The white-label infrastructure decision guide covers the wider product-team choice between building, buying and embedding. For an installer, the decision should end with a written responsibility matrix and a customer-facing price model.
Samvyo is one option to evaluate when an installer needs OEM and white-label depth alongside embeddable SDKs and a managed-service option. It is based on SFU architecture, and it can support customer control over the media path, TURN and recording processing and storage. It is a poor fit when the installer wants a simple equipment resale with no continuing service responsibility, or when the chosen CCTV system cannot be connected through a supported integration path.
Select the platform only after the responsibility matrix, site prerequisites and price-change terms are written down. That keeps the recurring service attached to work the installer can actually deliver.
Turn the handover into a service launch
The handover is where a one-off installation becomes a continuing service. Give the customer the account owner, user-management process, escalation route, connectivity responsibility and list of billable site work. Record the system dependencies that were verified and the conditions that would require a new survey.
Train the customer’s administrator to perform the actions they own. Then test the support path with a controlled access change, a user removal and a documented connectivity escalation. The test is valuable because it exposes responsibility gaps before a real employee loses access or a remote site disappears from view.
The Handover Call: What CCTV Customers Ring Their Installer About First follows the customer questions that surface after installation. Those questions should feed the service description, the onboarding checklist and the support boundary.
Once the first customers are live, measure the support work using the installer’s own records. Track the request type, site dependency, owner, resolution path and whether the work was included or billable. That evidence lets the installer revise the service without pretending that an unsupported market average describes its operation.
Bottom Line
Recurring revenue for CCTV installers comes from taking responsibility for a continuing video service. A monthly label on an installation invoice is only the visible part. The service becomes viable when billing, accounts, support, escalation, site dependencies and price-change exposure are assigned before the customer is enrolled.
Sell under the installer’s name only when the platform and contract make those responsibilities visible. If the installer cannot explain who owns the next failure, it is not ready to promise the recurring service.
What's Next
After the service model is clear, the next commercial problem is deciding what a customer means when they ask for an AI alert. What Your Customer Means by AI Alerts, and What You Can Deliver Today separates detection, delivery and response so the installer can describe the deliverable precisely.
FAQs
How can CCTV installers create recurring revenue?
CCTV installers can create recurring revenue by packaging an ongoing video service around remote viewing, account administration, support and agreed site responsibilities. The price should be built from the selected platform’s actual billing unit, the connectivity arrangement, the included support scope and the installer’s required margin.
Should an installer sell remote video under its own name?
An installer should sell under its own name when it can assign billing, account administration, support and escalation clearly. The installer should use a different commercial model when it wants to resell equipment without accepting continuing responsibility for the service.
What should a CCTV installer ask before offering a cloud video service?
Ask which recorder and software versions are supported, what site connectivity is required, who administers accounts, where media and recordings are handled, which support requests are included and who pays for on-site remediation. Confirm the provider’s price-change terms before presenting a recurring price to the customer.
What costs should be included in a recurring CCTV subscription?
Include the platform’s stated charge, the agreed support work and the responsibilities the installer accepts for account administration, escalation and site dependencies. Keep visits, hardware replacement, network changes and other excluded work separate when they are outside the recurring scope.
Can an installer use Samvyo for a white-label video service?
Samvyo is one platform option for an installer evaluating embeddable SDKs, OEM and white-label depth, and a managed-service model. It is based on SFU architecture and supports customer control over the media path, TURN and recording processing and storage, but the installer still has to verify the CCTV integration path and define its own customer support responsibilities.
What is the biggest risk in selling branded remote video?
The biggest risk is accepting a customer-facing promise without assigning the work behind it. An installer should document who owns access, user changes, connectivity faults, platform escalation, recording questions, price changes and on-site work before the recurring service begins.