Two owners compare notes at an association meeting and one says his system is cheaper. He is quoting the license line. He is not counting the two weekends his operations manager spent rebuilding the site list, the tablets he bought for three posts, the officers who never adopted it, or the reports he still assembles by hand every Friday. Guard software cost is a stack of categories, and the license fee is the only one that arrives on an invoice — which is exactly why it is the only one anyone compares.
This article names the categories without naming a number. Pricing varies by product, by company size and by how you buy, and you should get your own quotes. What you can do here is make sure the quotes you compare are describing the same thing.
Guard software cost: the categories that appear on the invoice
The recurring license. Usually scaled by the number of people using it, sometimes by sites or posts. The first thing to nail down is who counts. Every officer? Only officers who log in? Field supervisors? Office staff? Client users reading a portal? Two products with the same headline structure can differ by a large multiple purely because of who is included, and that difference does not show up until your headcount changes.
Add-on modules. Some capabilities are bundled and some are separate lines. The distinction matters less than knowing which is which before you sign, because a module you assumed was included becomes an unbudgeted increase in month four.
Setup or onboarding fees. One-time, sometimes waived, sometimes tied to a term commitment. Ask whether waiving it changes what you can cancel.
That is the visible stack. Now the part that decides whether the project succeeds.
Implementation: the cost nobody quotes
Implementation is not the vendor’s work. It is your work, and it is paid in your people’s hours.
Somebody has to enter every client, every site, every post, every set of post orders, every officer with their certifications and their expiration dates, and every schedule pattern. Somebody has to place and label checkpoints at each site, which means walking each site. Somebody has to decide which incident types you use and what your report templates look like — and that decision is a genuine operations design exercise, not data entry, because it determines what you will be able to measure a year from now.
The honest way to budget this is in hours by role, not dollars. How many hours of your operations manager, how many of your scheduler, how many of a field supervisor per site. Then ask yourself who is covering their normal work while they do it. Companies that skip that second question end up with a half-configured system and a scheduler who is behind on callouts.
Two things reduce it materially: importing what you already have in spreadsheets rather than retyping it, and configuring one representative client site completely before touching the other forty. Do a whole site end to end, live, with real officers, and every subsequent site takes a fraction of the time because you stopped making decisions and started copying a pattern.
Training, and the cost of forgetting
Training has two audiences with very different costs.
Office staff need real training — dispatch, scheduling, reporting, permissions. It is a small group and you can do it properly.
Officers are the expensive audience, not because each one takes long, but because there are many of them, they work on shifts that never overlap, turnover means you will be training continuously forever, and any minute of training on a covered post is either overtime or an uncovered gap. A product that an officer can use with a few minutes of instruction at shift start is worth a great deal more than a product with a superior feature list and a two-hour training requirement, because the second one you will pay for repeatedly, every hire, indefinitely.
Budget the ongoing training cost, not the launch cost. The launch is a one-time hit. New-hire onboarding is a permanent line in your operating rhythm.
Hardware: less than you think, if you are careful
Guard management software mostly runs on phones. The questions that determine your hardware exposure:
- Are officers using personal devices or company devices? Personal devices cost nothing up front and create policy, reimbursement and privacy questions. Company devices are a clean policy and a purchase plus replacement cycle.
- Does the product need anything at the post itself? Checkpoint tags are inexpensive and consumable — they get painted over, torn off and weathered, so treat them as a small recurring cost rather than a one-time one.
- Does the office need anything? Usually not, beyond what you already have.
- Chargers in patrol vehicles. Trivially cheap, and the difference between a complete shift record and a dead phone at hour nine.
The trap here is not the hardware price. It is buying devices for a workflow you have not tested. Run the pilot on whatever you already have, learn what the work actually needs, and buy after.
The largest cost: a system nobody uses
This is the one that dwarfs every other category, and it never appears in any comparison.
If officers do not scan, if supervisors do not review, if reports get written from memory at the end of the week, then you are paying the license and still doing everything the old way and now maintaining a second record that contradicts the first. You have added cost and subtracted nothing. Worse, you now have a system your client believes is authoritative, which means an incomplete record is more dangerous than no record.
Adoption failure has recognizable causes and every one of them is a cost you can avoid: launching everywhere at once instead of one site, no one owning the rollout, supervisors who never open the dashboard so officers correctly conclude nobody is looking, and a system that punishes the officer with extra steps while delivering the benefit entirely to the office.
The countermeasure is to measure adoption from week one — scan completion, reports filed on shift versus after, punches made at the post versus edited later. Those numbers tell you whether you bought software or a subscription to a folder nobody opens.
The costs that are actually savings
Be fair to the other side of the ledger, and be equally rigorous about not inventing figures.
The recoverable costs are specific: the office hours currently spent chasing paper reports and assembling client summaries; the billing disputes that get resolved by producing a verified record instead of by conceding; the overtime that comes from discovering a gap after it happened rather than before; the client retention you keep because the account manager can answer a question in the meeting instead of promising to look into it.
You can measure every one of those in your own operation. Do that before the purchase, with real hours from your own timesheets, so the comparison after is yours rather than a vendor’s claim.
How to compare two quotes honestly
Build a three-year view with these rows: license, add-ons, setup fee, your implementation hours by role, launch training hours, ongoing new-hire training hours, devices and replacements, consumable checkpoint tags, and one honest estimate of what partial adoption would cost you. Fill it in for each candidate. Then compare.
The winner is frequently not the lowest license. It is the one with the smallest implementation burden and the shortest path to an officer using it correctly on their first shift, because those two categories are where the money actually goes.
If you want a straight answer on the license side, see pricing or ask about the pieces that matter for your headcount — and if scheduling is where your hours are disappearing today, start the evaluation there. Explore CGuardPro when you are ready to compare properly.