How much does security
guard software cost?

The pricing unit is the real variable

Take a firm with 40 officers rotating across 12 posts. Under a per-user model it pays for roughly 40 accounts plus whatever office and client logins the vendor counts. Under a per-site model it pays for 12, regardless of whether those posts are covered by 40 officers or 90. Same company, same work, two bills that are not in the same neighbourhood. Before you compare two quotes, you have to put them in the same unit.

Per user, per month

The most common model, and the one with the most variation in what “user” means. Some vendors count officer accounts only. Others count every login — dispatchers, office admins, supervisors and the client contacts you give portal access to. CGuardPro is explicit that admins, guards, supervisors and clients all count as users at $5 each per month. That transparency cuts both ways: it is a clear number, but it means the client portal seats you hand out are billable, so plan them.

Per-user favours firms with few officers and heavy site counts, and punishes firms with high turnover — every new hire, relief officer and seasonal body lands on the invoice. Ask specifically what deactivating an account mid-month does to the bill.

Per guard (officer seats only)

A narrower version of per-user: office staff and client logins are free, only field officers are billed. It looks cheaper on the headline and often is, but confirm the definition. Whether a part-time relief officer who works six shifts a month occupies a full seat is a question with real money attached at 40+ officers.

Per site

You pay for the properties you cover. OfficerReports publishes per-site pricing — roughly $70, $65 and $60 per site per month, dropping as the site count rises. This model is predictable and it scales with what you actually invoice your clients for, which is the argument in its favour. It gets expensive fast if you run a lot of small, lightly staffed sites: a two-visit-a-week mobile patrol stop costs the same as a 24/7 post.

Per post

A close cousin of per-site, but counting staffed positions rather than addresses. A single property with a lobby post and a gate post is two posts and one site. For guarding work with 12- and 24-hour coverage this is often the most honest unit, because it tracks the thing you bill your own client for — the post, not the person standing in it, and not the turnover rate behind them.

Quote only

TrackTik and Trackforce publish no figures at all; their pricing page is a contact form. Belfry lists five tiers on its plans page with the features in each, and states only that it bills per employee per month — no number. Novagems is quote-based. This is legitimate for large deployments with real customisation, but it means several calls before a number exists, and implementation is usually priced separately. If you go down this route, ask for a total first-year figure early, not a monthly rate.

What vendors actually publish

Only a minority of this category publishes a price at all. Here is what was on the vendors’ own sites at the time of writing — figures they state themselves, not estimates:

• CGuardPro: $5 per user per month, where admins, guards, supervisors and clients all count as users, plus a one-time $299.99 implementation fee. 14-day free trial. See the pricing page.
• GuardsPro: $5, $8 and $10 per user per month by tier, or $4.25 per user per month billed annually, with a three-user minimum and a 30-day free trial.
• OfficerReports: per-site rather than per-user — approximately $70, $65 and $60 per site per month depending on volume.
• Belfry: five tiers listed by feature, priced per employee per month, with no figure published.
• TrackTik / Trackforce and Novagems: no published figures; quote-based.

Worth saying plainly, because you will find it in ten minutes anyway: CGuardPro is not automatically the cheapest option on this list. GuardsPro’s entry tier matches $5 per user per month, is lower at $4.25 on annual billing, and carries no published implementation fee. What you are comparing at that point is not the headline rate but what sits inside it — which tier your required features live in, what the client portal costs, and what the second year looks like.

A worked example — arithmetic, not a quote

The figures below are an arithmetic illustration built from CGuardPro’s published $5 per user per month and $299.99 implementation fee. It is not a quote, not a proposal, and not a comparison against any other vendor. Run the same arithmetic on whatever numbers your own shortlist gives you.

Take that firm again: 40 officers, 12 posts. Suppose four office and supervisory accounts, and six client contacts given portal access. Under a per-user model where all of those count, that is 50 users.

• 50 users × $5 = $250 per month
• $250 × 12 = $3,000 in licence for year one
• Plus the one-time implementation fee of $299.99
• First-year total: $3,299.99, or about $275 a month averaged across the year

Now change one input. Hire 20 more officers and the same firm is at 70 users, $350 a month, $4,200 a year — a 40% increase in software cost from a headcount decision, with the same 12 posts served. Under a per-site model that same hiring round would have changed nothing at all.

That sensitivity is the whole point. Run the arithmetic twice: once at today’s headcount, once at the headcount you expect in 18 months. If the two numbers are far apart under one model and flat under another, you have just learned which model fits your growth pattern. (To make the shape obvious, imagine a placeholder $50 per site — an arbitrary number, not any vendor’s price: 12 sites is $600 a month whether you staff them with 40 officers or 90.)

The total first-year cost checklist

The monthly rate is the part everyone quotes and the part that matters least in year one. Price all seven of these before you compare anything:

1. Licence. The monthly or annual subscription at your real unit count, not the demo account’s. Get the annual-billing discount in writing if one exists, along with what happens if you shrink mid-term.
2. Implementation and setup. One-time, and it varies from zero to several thousand. Ask what it buys — data migration, site and post configuration, integration work — and what it does not.
3. Training. Both the vendor’s charge and your own cost: supervisor hours, and the officer hours to get 40 people using an app they did not ask for. This line is almost never in a quote and is almost never zero.
4. Hardware. Checkpoint tags, NFC or QR media, any proprietary device, and their replacements. QR checkpoints scanned on the officer’s own phone remove most of this line; wands do not.
5. Modules billed as extras. Client portal, advanced reporting, visitor management, API access, invoicing. What you saw in the demo is not automatically in the quote. Get the included list in writing.
6. Getting your data out of the incumbent. The line nobody budgets. Exporting historical tour records, incident logs and timesheets from your current system can carry a vendor charge, a format that needs cleaning, or both — and if your contracts require you to retain that history, you cannot simply walk away from it.
7. Contract term and exit. A long minimum term is not a price, it is a risk. Establish the notice period and what happens to your data when you leave, on day one rather than in year two.

Questions to ask any vendor before you sign

• Exactly what counts as a billable unit, in writing — and are office staff and client contacts included?
• What happens to the bill when a guard leaves mid-month? Is the count a snapshot, an average, or a peak?
• Is there an implementation fee, and what specifically does it cover?
• Which of the features I just saw in the demo are in my tier, and which are add-ons?
• What is the price of the tier above mine, so I know the cost of the next thing I need?
• Is there a minimum seat count or a minimum term?
• What is the price on renewal, and is there a cap on the annual increase?
• Can I export my own tour, incident and timesheet history, in what format, and at what cost?
• Is support included at this tier, in which language and which hours?
• What is the total for the first twelve months, all lines included?

What makes the price go up later

Headcount. Under a per-user model this is automatic and usually the largest driver. Growth is good news that arrives with an invoice attached, so model it before you pick the model.

Feature gates. Tiered products are designed so that one capability you eventually need — API access, advanced analytics, a branded client portal — sits one tier above where you started. That upgrade re-prices every seat, not just the feature. Find out now which tier holds the things you will want in a year.

Add-on modules. Visitor management, asset tracking, invoicing and client portals are frequently separate line items. Each is reasonable on its own; four of them change the arithmetic.

Per-device and per-integration charges. Some products bill per phone or per tablet as well as per user, and payroll or accounting integrations can carry their own monthly fee.

Renewal. The introductory rate and the renewal rate are not always the same number. Ask for the second-year price before you sign the first year.

When a cheaper tool is the right call

Not every firm needs an operations platform, and pretending otherwise wastes your money. If you run a handful of sites with one shift pattern, no client who audits you, and no contractual requirement to produce verifiable proof of service, then a low-cost tour app or a straightforward scheduling tool will cover you. Buying capacity you never switch on is the most common way security firms overspend on software.

The calculation changes when one of these becomes true. A client starts asking for patrol evidence at contract review. A payroll dispute costs you more in argument than the annual licence. A bid requires documented tour records you cannot produce by hand. You lose a contract because the client could not see what they were paying for. At that point the software stops being an overhead line and starts being a condition of holding the work — and the honest test is whether you are already there, not whether a salesperson says you will be.

One more thing no spreadsheet captures: whether your officers will actually use it. A platform that is awkward at the post gets worked around, and then you are paying for data nobody enters. Cheap software that gets used beats expensive software that does not, every time.