Three quotes for the same building routinely differ by a wide margin, and the difference is almost never the cameras. It is retention, licensing, cable work and what happens after handover. These are the questions that make proposals comparable.
What to ask
About the design
- What is each camera for? Ask for a written purpose per camera, naming what it must let you see. A supplier who cannot produce this has designed for coverage rather than for evidence.
- At what distance does this camera recognize a person rather than merely detect one? Ask to see sample footage from the actual model, at night, at the actual distance.
- What happens to this view when the sun is low, when it rains, when the lights are off?
About retention and storage
- How many days of footage does this quote provide, at what resolution and frame rate, on all cameras or only some?
- What does another thirty days cost? This one question exposes more about a proposal than any other, because retention is the largest cost lever and NIST treats the period as an organization-defined decision rather than a product feature.
- Where is footage stored, and who else can reach it?
About the equipment itself
- Who manufactures these cameras, and who manufactures the components inside them? If you hold federal contracts or federal grant funding this is a compliance question, not a preference: FAR 52.204-25 prohibits video surveillance equipment produced by named manufacturers for covered purposes. See the federal procurement rules.
- How is firmware updated, how often, and for how many years will updates be published for this model?
- Can each camera restrict access to its own interfaces, and can it report its own state? NIST publishes the baseline worth asking against: device identification, device configuration, data protection, logical access to interfaces, software update and cybersecurity state awareness.
About what happens afterwards
- Who administers the system after handover, and is that in this price?
- How will I know a camera has stopped recording?
- What is the response time when something fails, and is that a contractual commitment or an intention?
- If I add eight cameras in two years, what will that cost?
What to compare
Put the quotes side by side on these lines rather than on the headline figure.
- Retention days at the same resolution and frame rate across the same cameras. Quotes are frequently incomparable on this line alone.
- Total cost over five years, not purchase price. Include licenses, cloud storage, support and the maintenance contract.
- Licensing model. Perpetual or subscription, per camera or per site, and whether software updates continue if the subscription lapses.
- What is excluded. Electrical work, network switching, remedial building work, out of hours labor, and the return visit to re-aim cameras.
- Cameras that do a stated job rather than camera count. Twelve cameras with a purpose each beat twenty covering the building in general.
- Commissioning and handover. Whether the supplier will sign off view by view against the design, and what documentation you receive.
Red flags
- A camera count arrives before a site visit. Nobody can design this from a floor plan.
- Retention is not stated in days. Storage in terabytes is not an answer to the question of how long you keep footage.
- Manufacturer questions get vague answers. For a federally connected organization this alone can invalidate the purchase.
- No firmware or end of support commitment. You are buying networked devices with an unknown supported life.
- Analytics are sold on a datasheet. Accuracy depends on your scene and your lighting. Ask for a demonstration on your site, and treat any refusal as an answer.
- Nothing about who administers it. An unowned system decays one camera at a time.
- The quote is dramatically cheaper and the scope is identical. It is not identical. Look at retention and at excluded work.
How to decide
- Score against your purpose list, not against each other. Every proposal either meets each stated purpose or does not.
- Normalize the quotes. Ask each supplier to re-price at the same retention and the same license term. The ranking changes more often than not.
- Weigh the operating years. Compare over the life you expect, and decide who is administering it.
- Confirm the constraints are satisfied before price becomes the deciding factor. Prohibited equipment and unsupported firmware are disqualifying, not negotiable.
- Ask for one reference site of similar size and, if you can, look at footage rather than at the installation.
If you would rather begin from a documented view of your own building, request a free site security assessment. LABUSA will walk the site and write the purpose list that makes these comparisons possible. For what sits behind the numbers, see what drives the cost, for the technical risk questions video surveillance security and risk, and for what we install our video surveillance solutions. The ownership and review questions that outlast any purchase are in security governance and risk ownership.
Sources
- National Institute of Standards and Technology, SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations. Establishes that video retention is an organization-defined period, the basis for treating retention as a question to put to every supplier. nvlpubs.nist.gov. Accessed 18 August 2026.
- National Institute of Standards and Technology, IR 8259A, IoT Device Cybersecurity Capability Core Baseline. Establishes the six device capabilities to ask a supplier about. nvlpubs.nist.gov. Accessed 18 August 2026.
- General Services Administration, FAR 52.204-25, Prohibition on Contracting for Certain Telecommunications and Video Surveillance Services or Equipment. Establishes the prohibition on named manufacturers referred to under equipment questions. acquisition.gov. Accessed 18 August 2026.