Guard Management Software Pricing Explained: Per-Guard vs Per-Hour vs Per-Module

Per-guard, per-hour, per-module, or "contact us"? How guard software pricing models actually work, what drives your real cost, and how to compare offers without surprises.

Pricing is where buying guard software gets frustrating. Half the vendors won't publish a number, the ones that do use different models that don't compare cleanly, and the “cheap” option often isn't once you turn on the features you actually need. This guide explains the common pricing models, what really drives your cost, and how to compare two offers without nasty surprises after you sign.

Short answer

A flat per-guard price with everything included is the easiest to predict and compare. Be cautious with per-hour models that grow with your billable hours, per-module pricing where the real cost climbs as you switch features on, and quote-only pricing you can't compare at all.

The four pricing models

Model	How it scales	Best for	Watch out for
Per-guard (flat)	With team size	Most small & mid-size companies	Whether features are truly included
Per-hour / billable-hour	With hours worked	Large enterprise agencies	Cost balloons as guard-hours grow
Per-module (low base + add-ons)	With features enabled	Tiny ops needing only the basics	Real cost climbs as you add modules
Quote-only	Unknown until you call	—	You can't compare; pricing favors the vendor

Per-guard pricing

You pay a set amount per active guard (often with a small base fee). It's the most predictable model: your cost tracks your team size, so you can forecast it and it scales smoothly as you grow. The one thing to verify is whether every feature is included — a low per-guard rate isn't a deal if the features you need are separate add-ons.

Per-hour / billable-hour pricing

The price is tied to guard-hours — sometimes a per-hour rate, sometimes a percentage of billable hours. It's common in enterprise platforms and can make sense for very large agencies, but it has a catch: your software bill grows every time your team works more. A busy month costs you more in software, which is the opposite of what you want from a fixed operating tool.

Per-module pricing

A low entry price gets you a basic version, and capabilities — scheduling, dispatch, advanced reporting — are sold as separate modules. The sticker looks great, but the real cost is whatever you pay once you've enabled the features you actually need. Always price the configuration you'll really run, not the bare base.

Quote-only pricing

“Contact us for a quote” is the hardest to deal with. You can't compare it to anything without sitting through a sales call, and a price that's set per-deal tends to flex based on what the vendor thinks you'll pay. It isn't automatically a bad platform — but the opacity itself is a cost, in time and in negotiating position.

What actually drives your cost

Guard count — the biggest lever in most models.
Which features are included vs extra — the difference between the sticker and the real bill.
Contract length — annual lock-ins may discount the rate but cost you flexibility.
Onboarding / setup fees — sometimes a large one-time line you didn't expect.
Support tier — real support is occasionally an upsell.

Hidden costs to ask about

Before comparing prices, ask each vendor directly about: setup or onboarding fees, per-feature add-on costs, overage charges, SMS/data fees, contract auto-renewal terms, and whether exporting your own data costs anything. These are where a “cheaper” quote quietly becomes the expensive one.

How to compare two quotes fairly

Normalize everything to one number: your total monthly cost at your real guard count, with exactly the features you need turned on. A per-module base and a flat all-in price are meaningless side by side until you've added the modules. Do the math at the size you'll be in a year, not just today — the model that's cheapest at 5 guards is often not the one that's cheapest at 30.

Where PatrolWizzard fits

PatrolWizzard uses flat per-guard pricing with everything included: a $50 base that covers your first 2 guards, then $8 per additional guard — every feature in, no modules to unlock, no sales call, and a free start. The point isn't that it's always the cheapest line item; it's that the number is published, predictable, and the same whether your team works 40 hours or 400. You can see exactly what you'll pay before you talk to anyone.

Frequently asked questions

Is per-guard or per-hour pricing better? For most small and mid-size companies, per-guard is easier to predict because it tracks team size rather than hours worked. Per-hour models can make sense at enterprise scale but mean your software cost rises with a busy month.

Why do so many vendors hide their pricing? Quote-only pricing lets a vendor set the number per-deal and makes comparison harder. Published pricing is generally a sign of confidence and saves you a sales call.

How do I avoid surprise costs? Price the exact configuration you'll run — your real guard count with the features you need — and ask explicitly about setup fees, add-on modules, and contract terms before signing.