An alarm company that cannot say where its jobs are is not disorganized. It is undercapitalized in a way that does not show up until someone asks for the numbers.
At the final Barnes Buchanan conference this year, Gretchen Gordon of Braveheart Sales Performance told a room of alarm and fire operators something worth pinning above the dispatch board. "Most security and fire businesses don't have a sales problem; they have a systems problem," she said, per SDM's coverage. "They are too reliant on the hero salesperson." Her data put the share of security salespeople who sell consultatively at 8 percent.
That is the whole problem in one line. Most alarm shops do not lose money because a stage is slow. They lose it because a job falls between two people and nobody owns the gap.
The short answer
Track the job as nine stages, each with one named owner and one written condition that has to be true before it moves. Then measure the drop-off at the six handoffs between them. The pipeline is not the point. The pull-through at each seam is the point, because that is where the cash is going.
Most software pitches for this category tell you the answer is one integrated platform. That is sometimes true and often premature. The chain matters more than the number of links in it.
Why "lead to invoice" is the wrong shape for an alarm job
A plumbing call is genuinely linear. Lead, quote, job, invoice, done. An alarm site is not. One address produces four distinct revenue streams that start at different times, bill on different cycles, and fail in different ways.
- The install or project. One-time, milestone-billed on anything commercial, and the only one most CRMs model.
- The monitoring RMR. Starts after the install, bills monthly forever, and is the asset a buyer is actually purchasing.
- Recurring inspection and ITM work. Annual or semi-annual, scheduled off a compliance date rather than a customer request.
- Deficiency and service repairs. Generated by number three, quoted separately, and the highest-margin work in the building.
The scale here is not marginal. Reporting on Michael Barnes of Barnes Associates in Security Business magazine put the US security alarm integrator market at about 78 billion dollars, up from 37 billion twenty years earlier, split roughly 41 billion in sales and installation against 37 billion in recurring and related revenue. Nearly half the industry's money sits in the streams a single install pipeline does not follow.
By the numbers
At his final Barnes Buchanan presentation, Barnes reported that at the end of 2025 "the average dollar in the industry statistically produced 12 cents of billable service revenue," and that the figure is trending up alongside monitoring and service margins of 51.2 percent, recovering from a decade-long slide that began at 53.9 percent in 2017. Service revenue is growing. Whether you capture it depends entirely on whether your system knows the work happened.
The nine stages, and the one thing that has to be true to leave each
Stage names are cheap. Exit conditions are what stop a job from drifting. Every row below has a single fact that must exist in writing before the job advances.
| # | Stage | Owner | Exit condition |
|---|---|---|---|
| 1 | Lead captured | Whoever answers the phone | Source recorded, site address recorded |
| 2 | Survey booked | Sales | Calendar slot confirmed with the decision maker, not the gatekeeper |
| 3 | Proposal issued | Sales | Equipment scope and monitoring term priced as two separate lines |
| 4 | Agreement signed | Sales | Signed install scope and signed monitoring agreement, both on file |
| 5 | Scheduled and staged | Ops | Material allocated to the job, panel and comms path confirmed compatible |
| 6 | Install complete | Tech | Signal test passed and logged to the central station |
| 7 | Account activated | Ops or admin | Central station account live, permit number on file, RMR start date set |
| 8 | Invoiced | Admin | Install invoice sent and first recurring cycle scheduled |
| 9 | Collected and in service loop | Admin | Cash received, next inspection date scheduled |
Stage 7 is the one almost nobody has. It is also the only stage where recurring revenue is created, which makes it the most expensive stage to skip.
The six handoffs where the money actually leaves
1. Proposal issued to signature
This is the classic leak and the one owners already know about. What they underrate is the cost of tracking it in their heads. An installer in r/accesscontrol described the failure mode precisely on a thread about what eats the week: "I'll do a quote, send it over, client says let me think about it, and then I spend the next week mentally tracking whether they're still considering or if they went with someone else."
Their fix is worth stealing. Set a reminder to follow up after three days, and if there is no reply, move on. A cutoff rule is not defeatism, it is what converts an open loop that costs attention into a closed record that costs nothing.
2. Signed to scheduled with the right scope
The gap between what sales sold and what the truck can install is a real line item. From the same thread: "Arguing with Sales, that no I can't install this thing they sold the client, because it's not compatible with the client's existing system, and why didn't they just take 5 seconds to ask me or another tech." The same commenter describes driving across town because someone changed the plan without telling the field.
The exit condition on stage 5 handles this: material allocated, panel and comms path confirmed compatible, before a truck is dispatched. A fifteen minute check that saves a return visit priced at a full day.
3. Scope change to change order
This is where install margin dies quietly. The top answer on a change order thread in r/lowvoltage is unambiguous: send an RFI outlining the scope change, get the customer to put the change in writing, send a quote for the change order, and "DO not do the work without a purchase order or an acknowledgement of the change order." Another operator adds the rule that makes it hold up later: "send an email confirming every discussion, like a recap. Anything that isn't in writing didn't happen."
Structurally, this means a change order must be its own record with its own approval state. If it is a note appended to the work order, it will be billed at the discretion of whoever assembles the invoice, which in practice means sometimes.
4. Install complete to monitoring activation
Here is the handoff unique to this trade, and the one no generic pipeline models at all. Between "the tech left the site" and "the account is billing monthly" sit three separate facts: the central station account is live, the municipal permit number is recorded, and the RMR start date is set.
Pick a single rule for when the recurring clock starts. Signal test date, install completion date, or first of the following month are all defensible. Having no rule is not, because then the start date is whatever day someone in the office happens to notice the job closed. On a 55 dollar per month residential account, a routine three week lag across 200 installs a year is roughly 5,700 dollars of monitoring revenue that was earned and never billed, and it compounds because the following month starts late too.
The permit field belongs on the site record, not the customer record. Los Angeles publishes what happens without one: a 60 dollar initial permit and 31 dollar renewal, and a false alarm schedule that charges 260 dollars for the first incident with a permit against 360 dollars without, escalating to 410 and 660 by the fourth. The city notes LAPD handles 6,000 to 7,000 alarm calls a month and over 90 percent are false. That is not a customer service footnote, it is a recurring billing and liability field that most alarm CRMs have nowhere to put.
If your permit numbers, activation dates and RMR start dates live in a spreadsheet next to your CRM, the spreadsheet is your CRM. We build custom systems that model the site, the installed system and the agreement as first-class records, so the recurring clock starts itself.
5. Inspection deficiency to quote
On the recurring side, this is where the highest-margin work is lost. A r/firealarms thread asked the question every owner should ask their own office: "if your shop wrote up 100 deficiencies last year, would anybody know how many got quoted? Or does it go to the office and then turn up on next year's report again."
The replies are the useful part. One operator was blunt about the stakes: "Inspections are a race to the bottom, deficiencies is where the profit is." Another cautioned that a sent quote is not a signed one, because "just because the office quotes a deficiency doesn't exactly equate 1 for 1 as a signed proposal from the customer." A third described a working design: inspectors raise a field quote on site, it routes to a dedicated quoting person who sends it and keeps everyone looped in, and the inspector earns a small percentage of the resulting revenue.
Only one commenter could state a number. "My deficiency pull-through % is 65-70%." That figure is worth less as a benchmark than as a demonstration. Someone in that shop measures the seam.
6. Work complete to invoice to cash
Two separate leaks wear one name. The first is unbilled work in progress, the days between the tech closing the job and the invoice going out. Vendors in this space describe the failure state openly, noting it can take days for a completed job to show up on an invoice when systems are not connected. Rev.io's own integrator page concedes that "many Integrators complete an installation without knowing if they made or lost money on the job."
The second is collection. An operator on r/lowvoltage described invoicing 125 dollar service visits, being ignored, and eventually writing them off. The most experienced reply refused the premise: "You never write it off." Their fix was a mobile card terminal to take payment on arrival, plus contract language allowing a construction lien and recovery of collection costs. Others suggested a card on file. For a business built on recurring revenue there is a cleaner lever: put customers on a service agreement so the small stuff is prepaid, and make one-off callers pay at time of service.
The four numbers that tell you where the leak is
You do not need a dashboard. You need four numbers reviewed monthly.
| Metric | Definition | What a bad number means |
|---|---|---|
| Stage pull-through | Percentage advancing across each of the six handoffs | Names the specific seam that is losing jobs |
| RMR start lag | Days from install complete to first billed day | Activation is not owned by anyone |
| Unbilled WIP age | Days from work order closed to invoice sent | The field-to-office handoff is broken |
| DSO | Days from invoice sent to cash received | Your terms and your follow-up are decorative |
Barnes named the discipline directly when flagging attrition as one of the industry's two live threats: "the better your data systems are and the more you can know in real-time how your businesses are operating, the better you will understand when certain metrics move on you."
Tip
Start with the oldest item, not the average. Sort your open work orders by the date the technician closed them and look at the top of the list every Monday. One number, thirty seconds, and it surfaces the specific job that fell in a gap rather than a statistic that hides it.
Do not automate the quote, automate the handoff
Every inspection platform sells the same promise: deficiencies convert automatically into proposals. The field has a specific and well-argued objection to this, and it is worth respecting before you buy.
Watch out
A technician on the same r/firealarms thread laid out the arithmetic. A tech writes "heat detector requires 30' scissor lift for access," the auto-quote engine ignores that clause and prices fifteen minutes to swap a detector, "now you're out 2 grand in lift rental fees and additional labour." Their second example is a heat detector at the far end of a crawlspace quoted at fifteen minutes when the crawl alone takes an hour each way. Their conclusion: a human has to review these, and the review is fast enough that the same person may as well write them.
That is the correct read. The automation you want is not the pricing, it is the routing. The system's job is to guarantee every deficiency reaches a named human within 24 hours and cannot be closed without either a sent quote or a written reason it does not warrant one. That is a workflow rule, not an AI feature, and it is the difference between 65 percent pull-through and an unknown one.
What to actually run this on
There are three honest answers, and account count decides between them more reliably than revenue does.
Spreadsheets and a shared drive. A real answer, and the trade knows it. On a fire inspection software thread the highest-voted practical reply was "Why are you paying for software. Just learn how to make neat looking excel spreadsheets," and an experienced inspector told a startup not to spend on inspection software until the fundamentals were solid. Under roughly 100 monitored accounts they are right. The failure mode is that a spreadsheet cannot enforce an exit condition, so discipline comes entirely from people.
A chain of specialist tools. This is what most working shops actually run, and it is underrated relative to the single-platform pitch. One operator described their stack in detail: Building Reports for inspections because the local AHJ requires it, ServiceTrade for scheduling and service calls, deficiencies flowing back from Building Reports into ServiceTrade as a quote, and ServiceTrade billing into QuickBooks. Their verdict: "I honestly couldn't keep up with it all without these integrated systems." Three tools, two real handoffs, one direction of data flow.
One system that models the site. Worth it when the reporting breaks rather than when the tool count annoys you. The tell is when you cannot answer a question about RMR by account, by reason code, or by contract term without opening a spreadsheet. We wrote a longer decision framework for that call in best CRM for security alarm companies, and the QuickBooks job costing guide covers what the accounting side can and cannot carry on its own.
Be skeptical of the efficiency numbers in vendor material. WorkHorse SCS, for example, claims integrating field service with accounting "typically reduces the time spent on office admin work by nearly 50% for most growing security firms," with no methodology attached. Treat that as a marketing claim, not a benchmark.
Why this is worth doing before you plan to sell
The strongest argument for tracking jobs properly is not efficiency. It is price.
Roughly 21 percent of the industry changed hands in the last four years, per Barnes at the 2026 conference, and the market has grown pickier: every deal has buyers, but the burden is on the seller to prove the company is solid. The Security Business analysis is more specific about what that proof is worth. Average transaction multiples ran from about 36 times monthly RMR for companies under 50,000 dollars of RMR to about 46 times for those above 500,000. And the line every owner should read twice: companies that can articulate their attrition rates, creation multiples, margin trends and other key performance indicators command higher multiples than better-performing companies that cannot document their results.
A better-run company that cannot prove it is run better gets paid less. The stage map is the proof.
We build custom CRM and job tracking systems for alarm dealers and low voltage contractors, modelled on the site, the installed system and the agreement rather than a generic contact and deal. If you want the four numbers above on one screen without a spreadsheet underneath, that is the build.
The 30-day install
You do not need new software to start. You need the seams named.
- Week 1. Write the nine stages on a whiteboard. Beside each, write one name and one exit condition. Argue about the exit conditions until they are unambiguous.
- Week 2. Pull every open job into the map. Expect a third of them to have no clear stage. Those are your leaks, already identified for free.
- Week 3. Instrument two numbers only: RMR start lag and unbilled WIP age. Both are countable by hand from your last twenty completed jobs.
- Week 4. Add the change order rule and the deficiency routing rule. No work without written acknowledgement. No deficiency closed without a quote or a written reason.
At day 30 you will know which handoff is worst. Only then does tool selection become a real question, because now you can ask a vendor to demonstrate the specific seam costing you money instead of watching a generic demo.
The checklist
- Every stage has one owner and one written exit condition.
- The site record, not the customer record, holds the permit number and expiry.
- The RMR start date rule is written into the monitoring agreement and applied automatically.
- Change orders are their own approvable record, never a note on a work order.
- Every deficiency reaches a named human within 24 hours and closes only with a quote or a written reason.
- The oldest unbilled work order is reviewed weekly by date, not by average.
- Stage pull-through, RMR start lag, unbilled WIP age and DSO are reported monthly.
- You can produce all four numbers for a stranger without opening a spreadsheet.
Nine stages. Six handoffs. Four numbers. The trade already knows where the work goes. The system just has to stop losing it in the gaps.