Security Operations
Security Company Recurring Revenue: How to Track Renewals and Stop Quiet Attrition
A security company can add customers every month and still shrink. The reason is attrition that nobody sees until the revenue report comes in.
Recurring monthly revenue (RMR) is the most valuable thing a security dealer owns. It is also the easiest thing to lose slowly. A card expires, a contract term ends without a conversation, a customer moves, a callback goes badly. Each one is small. Together they decide what the business is worth. This article covers how to track recurring revenue at the account level, run renewals on a calendar instead of by memory, and tie the whole thing back to the field work that causes it.
What is recurring revenue management for a security company?
Recurring revenue management is the practice of tracking, protecting, and growing the monthly revenue that comes from monitoring and service contracts. It covers the contract, the billing, the renewal, the service history, and the reason a customer stays or leaves.
It is different from sales and different from accounting. Sales brings an account in. Accounting records what was billed and collected. Recurring revenue management asks a third question: which accounts are healthy, which are at risk, and what should someone do about it this week?
Four terms are worth fixing early:
- RMR: recurring monthly revenue from monitoring, service plans, and similar contracts.
- Attrition (or churn): accounts that cancel or do not renew, usually tracked as a share of the base over a period.
- Cost to serve: what it costs to keep one account, including service visits, truck rolls, and support time.
- Renewal window: the stretch of time before a term ends in which you can still change the outcome.
[Assumption] Terminology varies by dealer and monitoring platform. Define each term in writing before you report on it, so two people reading the same dashboard mean the same thing.
Why does recurring revenue quietly leak?
Most security companies do not lose accounts in one dramatic event. They lose them across five quiet gaps.
The contract term nobody is watching. A term ends, auto-renewal rules vary by contract and by state, and the account either rolls over unnoticed or lapses unnoticed. Either way, no one made a decision. [Assumption] Renewal and notice rules differ by jurisdiction and contract language. Confirm them with your own counsel.
Service history that never reaches the renewal conversation. A customer with three callbacks in a year is a different renewal from a customer with none. If the person making the call cannot see the tickets, they have the same script for both.
Billing problems that look like cancellations. Failed payments, wrong amounts, and billing set up on the wrong date all create friction. Some of that friction ends the account.
Installs that never convert cleanly. The recurring revenue starts at the install. If the signed agreement, the equipment list, and the billing setup do not match, you start the relationship with a correction. This is the handoff covered in our guide to home security business software.
Cost that nobody attaches to the account. An account that pays a modest monthly amount and generates a callback every quarter may be worth less than it looks. Without cost to serve, every account looks equally good.
What should you track on every recurring account?
Pick a fixed set of fields and make them mandatory. Six is enough to start.
| Field | What it answers | Where it usually hides |
|---|---|---|
| Monthly recurring amount | What does this account pay? | Billing system or monitoring platform |
| Contract start, term, and end date | When can we lose or keep it? | Signed PDF in a folder |
| Equipment and service scope | What did we promise to maintain? | Install paperwork, technician notes |
| Service history | How often do we visit, and why? | Ticket system, phone notes |
| Cost to serve | Is the account profitable? | Spread across payroll, vehicles, parts |
| Renewal status and owner | Who is handling it, and where is it? | Someone's inbox or memory |
If you can fill all six for an account in under two minutes, you have recurring revenue management. If you cannot, you have recurring revenue reporting, which tells you what happened after it is too late to act.
How do you build a renewal calendar that works?
A renewal calendar is a list of every account sorted by term end date, with a person assigned to each one. The goal is to remove surprises.
Step 1: Export every active contract with its end date. If end dates live in PDFs, this is the hard part. Do it once and accept that it takes time.
Step 2: Sort by end date and group into windows. Use 120 days, 60 days, and 30 days out. [Assumption] These windows are a starting point. Match them to your contract notice requirements.
Step 3: Score each account before anyone calls it. Look at service history, open tickets, and payment status. Sort accounts into healthy, watch, and at risk.
Step 4: Assign an owner and a first action. Healthy accounts get a confirmation. Watch accounts get a check-in call. At-risk accounts get a conversation that starts with the problem, not the renewal.
Step 5: Log the outcome and the reason. Renewed, renewed with changes, cancelled, or lapsed. Always record why. Without reasons, attrition is a number and not a lesson.
Step 6: Review weekly. Monthly is too slow. By the time a monthly review sees an at-risk account, the window has often closed.
Which metrics tell you the truth about recurring revenue?
Start with these six. Calculate them yourself from your own data.
- Gross attrition by month: accounts or RMR lost, before counting new sales. Tracking both counts and dollars shows whether you are losing small accounts or large ones.
- Renewal rate by cohort: renewals as a share of accounts that reached term end. Group by install year or sales channel.
- Attrition by reason: moved, price, service quality, competitor, payment failure, unknown. Watch the size of "unknown." It measures how well your team logs outcomes.
- Service calls per account per year: a leading indicator. Rising calls often come before cancellations. [Assumption] This relationship should be tested on your own data.
- Cost to serve by contract type: reveals which plans earn their keep.
- Time from install to first correct bill: a measure of how clean your handoff from install to billing is.
This article does not cite an industry benchmark for any of these. Benchmarks vary widely by market, customer mix, and how each company defines the terms. Your own trend is a better guide than someone else's average. If you want an outside reference, look for a named, dated report from a security industry trade association or your monitoring platform, and read how they define attrition before comparing.
Where spreadsheets and disconnected tools fail
Recurring revenue depends on several systems staying in step. They rarely do.
- Contract end dates in a spreadsheet. The spreadsheet is accurate on the day it is built and decays from there. No one is alerted when a date gets close.
- Service history in a separate ticket system. The person managing renewals cannot see it without asking someone.
- Billing in a third place. Payment failures show up as billing alerts, not as account risk.
- Commissions in a workbook. Security sales pay is often tied to contract value and term, so a cancelled account touches payroll. If no one connects the two, the company pays for sales it did not keep.
Each tool works on its own terms. The risk sits between them. For the broader argument, see our piece on the hidden risk of manual field service workflows.
What does a good recurring revenue process look like in practice?
Take an account with a three-year term ending in 90 days. The renewal calendar flags it. The owner opens the record and sees two callbacks in the last year, both for the same sensor, and one open ticket from last week. The first call is not a renewal pitch. It is a call to close the open ticket and confirm the fix. The renewal conversation happens after.
Now take the same account without a shared record. The renewal call goes out on a script. The customer brings up the sensor. The rep has no idea what they mean.
The difference is not skill. It is whether the information was in front of the person making the call.
How does this apply across verticals?
Recurring revenue logic reaches beyond security.
Home automation and security. The model described here fits most directly: monitoring and service agreements, long terms, and a service history that predicts renewals.
Solar and renewable energy. Recurring revenue is less common, but post-install service and maintenance agreements follow the same pattern when a company offers them.
Pest control. Recurring service plans are the core business. Pest control is a newer vertical for Core365, so ask for references from pest customers. The retention topic gets its own article in this series.
Roofing. Roofing is the newest vertical and is mostly project-based. Maintenance agreements are the closest parallel, if offered.
Where does Core365 fit?
Core365 is an operations platform for field service companies, not a monitoring platform and not a general ledger. This section describes only what the Core365 site says, and it points out where the site is silent.
One platform for the security operation. The Home Automation and Security page describes a single platform for certifications, equipment management, and service contracts, and says it removes the silos between canvassers, technicians, schedulers, and the billing team. These are vendor claims to validate in a demo.
Service records. Service365 is described as centralizing customer records, project documentation, tickets, schedules, and field activity in one system. This is the service history your renewal owner needs to see. The page does not describe contract terms or renewal dates as fields.
Customer communication. Contact365 describes unified customer communication across text, voice, and digital messaging, with centralized interaction history. The page also mentions a forthcoming Customer Connect portal. Forthcoming means not yet available. Ask for the current status.
Contracts and signed documents. DocuVault365 describes converting PDFs into signable documents, secure document storage, and contract workflow queues with status dashboards. That addresses the signed agreement that otherwise sits in a folder.
Receivables. Finance365 describes receivables dashboards that show funding activity and revenue flow. The page states it is explicitly not a general ledger system. It does not describe recurring billing, invoicing, or collections. If recurring billing is central to your evaluation, ask directly.
Commissions. Commissions365 describes custom plan structures, tiered rates, bonuses, and performance-based adjustments. The page does not mention recurring commissions, chargebacks, or clawbacks. If your sales pay is tied to contract term, ask how that is handled.
Reporting. Analytics365 describes cross-department dashboards and trend tracking. The page does not mention retention, attrition, or RMR reporting.
What the site does not say. The site does not describe a renewal calendar, RMR tracking, an attrition report, or a connection to an alarm monitoring platform. The Integrations page names tools for solar design, communication, monitoring (SolarEdge, for solar systems), funding, HR, and AI, but names no alarm monitoring platform or payment processor, and says the integration list is not exhaustive. [Assumption] These may exist or be on a roadmap. Ask for them by name in a demo and ask to see them working.
Published figures such as "15+ hours saved weekly" are vendor claims, not verified results.
Key takeaways
- Recurring revenue is lost in small steps: unwatched term dates, missing service history, billing friction, messy installs, and unmeasured cost to serve.
- Track six fields on every account and make them mandatory.
- Build a renewal calendar that looks 120, 60, and 30 days out, with a named owner for each account.
- Score accounts before calling them, using service history and payment status.
- Log the reason for every cancellation and watch how large the "unknown" bucket is.
- Calculate your own metrics. Do not borrow an outside average without checking its definition.
- Ask any vendor, including Core365, how it handles renewal dates, RMR reporting, recurring billing, and your monitoring platform. Ask to see each one working.
- Core365 is an operations platform for field service. It is not a monitoring platform and not a general ledger.