Demos are designed to go well. The presenter knows the shortcuts, the sample data is clean, and nothing is on fire. That is not dishonest — it is a demo. The useful guard software vendor questions are the ones a good demo cannot answer for you, because they are about what happens in month fourteen when the person who sold it to you has moved on, the officer who loved it has quit, and a client is asking for two years of reports by Friday.
What follows is organized by the thing you are actually trying to learn, not by feature category. Judge the answers on specificity. “Yes, absolutely” is not an answer. A vendor showing you the screen where the thing happens is an answer.
Guard software vendor questions about support
You will need support at 3 a.m., and that is the problem. Security operations run continuously. Software vendors mostly do not. That gap is where the frustration lives.
- What hours is support staffed, in my time zone, and what happens outside them? Get the actual hours, not “we’re always here for our customers.”
- What is the difference between a normal issue and an urgent one, and who decides? If a dispatcher cannot see the board mid-shift, that is not a ticket in a queue.
- How do I reach support — and is there a path that does not require a supervisor to fill out a web form at 2 a.m.?
- When a field officer has a problem on their phone, who do they call? In most operations the right answer is your own supervisor, not the vendor. So the follow-up matters: what tools does my supervisor have to fix an officer’s problem without escalating?
- Do I have a named contact after onboarding, or does my relationship end when implementation does?
That last one predicts more of year two than any feature. Plenty of products are pleasant to buy and lonely to own.
Questions about your data, asked bluntly
Everything you record becomes evidence you may need years later, in a billing dispute, a claim, or a client’s own investigation.
- Show me the export, in the demo, right now. Not a description. Ask them to export a month of reports while you watch.
- Does the export include attachments — incident photos, signatures, scan records — or only text?
- Can I export whenever I want, myself, without asking anyone and without a fee?
- How long is history retained, and can I set that myself? Retention obligations vary by client contract, by state and by jurisdiction, and nothing here is legal advice — but you need to know whether the product can meet whatever your counsel tells you to meet.
- Who inside your company can see my records, under what circumstances, and is that access logged?
- If I cancel, walk me through the steps and the timeline.
A vendor comfortable with all six is a vendor who expects you to stay for reasons other than difficulty leaving.
Questions about the field, where the product actually lives
Office demos happen on good connections. Officers do not work on good connections.
- What exactly works with no signal? Get it item by item: clocking in, scanning a checkpoint, writing a report, attaching a photo, the panic button. The honest answer includes something that does not work offline — anything real-time cannot. A vendor who claims everything works offline is describing a product that does not exist.
- What happens to work captured offline? Does it sync automatically, does the officer have to remember to do something, and what does the officer see so they know it went through?
- What does the timestamp say — when the officer did it, or when it synced? This is a real question with a real consequence. If a tour scan in a basement stamps as 03:40 because that is when the phone found signal, your client will see a gap that did not happen.
- What happens if the officer’s phone dies mid-shift? Can a supervisor close out the shift, and does the record show that it was closed by someone else?
- How much battery does a twelve-hour shift cost? Ask how the app decides when to record position. “Every few seconds, always” and “when the officer moves” are very different products.
- Can an officer edit something after the fact, and does the record show it was edited, by whom and when? For anything you might hand to a client or a claims adjuster, the answer needs to be that edits are visible.
Questions about how it fits your operation, not the demo’s
Every product demos on a simple operation. Yours is not simple.
- Show me a twelve-hour post with a callout replacement mid-shift. Watch how many steps it takes.
- Show me an officer covering two client sites in one shift. This breaks more products than any other scenario.
- Show me an overnight shift that crosses midnight, and show me the timesheet it produces. Then ask what happens on the daylight-saving change.
- How do post orders reach the officer, and what happens when a client changes them at 5 p.m. on a Friday?
- What can my client see, and how much control do I have over what they see? Client visibility is a selling advantage and a liability at the same time.
- How do permissions work? Can a field supervisor see only their own sites? Can a branch manager see only their branch?
Questions about implementation, before it becomes your weekend
- Who does the setup work, and how many hours of my staff does it take? A vendor who has done this before can describe the shape of it. One who cannot has not.
- Can we import what we have, or does someone retype every site and officer?
- How long until my first client site is running live with real officers, not test data?
- How much training does an officer need on their first shift? Then ask to see it — hand the phone to someone in the room who has never seen it.
- What does new-hire onboarding look like six months from now? With turnover, this is a permanent cost, not a launch cost.
Questions about the future you are buying into
- How often do updates ship, and how do I find out what changed? Both extremes are warnings: a product that changes constantly disrupts a trained workforce, and a product that has not changed in a long time is being maintained rather than developed.
- How do customers influence what gets built? Ask for a concrete example of something they built because a customer asked.
- What does the product deliberately not do? The best answer you can hear. A vendor with a clear boundary has a strategy. A vendor who says the product does everything either misunderstood the question or is guessing.
- What does pricing look like as I grow? Add fifty officers, add a branch, add a large client. Know the shape now, at the pricing conversation, not at renewal.
Answers that should make you slow down
Not deal-breakers, but slow down and dig: a demo the presenter will not let you drive; “we can build that for you” offered too readily, which frequently means a custom version only you will have and only they can maintain; an export that requires a support ticket; vagueness about offline behavior; a reference list of customers who do not resemble your operation; and a price that only holds if you sign this month.
The single best question
Ask for two references: one company similar to yours in size and service mix, and one that has been on the product for at least a couple of years. Then ask those references one question — what surprised you after the first six months? Everything real about a vendor lives in that answer.
If you want to put these questions to us, start with pricing or read how daily activity reports are captured in the field, then get in touch.