Designing a “standard spec” CCTV package range (good/better/best) that speeds up quoting Part 1

If you’re quoting CCTV regularly, you’ll know the pain: every enquiry feels like a mini-design project, even when 80% of sites are basically the same. You ask the same questions, build the same kit list, re-type the same assumptions, then tweak it all again because the client says “what’s the cheaper option?” or “can we make it a bit better?”
A good/better/best package range fixes that. Not by turning security into a “one-size-fits-all” box, but by giving you a repeatable standard spec that gets you from inquiry to quote fast—without killing your margins or leaving you exposed when the job turns out to be harder than expected.
And if you ever need a simple, non-alarmist reason why CCTV is still a priority for a lot of UK sites: police-recorded shoplifting offences rose to 519,381 in the year ending September 2025 (a 5% increase year-on-year). That kind of pressure makes clients want quick answers—and you want a quoting system that can keep up.
Below is a practical way to build your package range so it’s easy to sell, easy to install, and easy to scale.
1) Start with the real goal: faster quoting without cutting corners
A package range should do 4 things:
Reduce decisions you have to make on every quote (codec, PoE, drive sizes, camera grades, cabling standards).
Standardise assumptions (labour, access, containment, commissioning) so you don’t underquote.
Create upgrade paths (so “better” and “best” feel like sensible steps, not random add-ons).
Keep stock and support simple (you don’t want 15 camera models across your “standard” jobs).
If you’re buying through a trade supplier like FVS CCTV, you can align your packages to product categories you can reorder quickly, which helps you keep installs consistent.
2) Define your “standard site types” (so packages don’t get messy)
Don’t build packages around brand names or model numbers first. Build them around site patterns you see every week.
A simple approach is 3 “most common” site types:
Small commercial: 4–8 cameras, short runs, basic coverage (entrance, till, yard, rear door).
Medium site: 8–16 cameras, mixed internal/external, need better night footage.
Higher risk or higher value: perimeter + entrances + key assets, desire for deterrence, audio, analytics, longer retention.
Your packages should fit these patterns with minimal change. When something falls outside the pattern, you use an add-on menu (we’ll cover that).
3) Choose the “fixed decisions” that you never want to debate again
This is where you win time back. Pick defaults and lock them in:
Recording and compression
Standardise on H.265 where possible (more storage-efficient than older formats).
Decide your baseline retention target (example: 14–30 days depending on sector).
Standardise remote access method and handover approach.
You can build your NVR options around a core category like IP CCTV NVRs so the recorder choice is never a long debate.
Cameras
Standardise your camera families by “grade”:
Good = solid, general-purpose coverage.
Better = improved low-light + clarity for identification.
Best = strongest night performance + deterrence/analytics options.
Keep camera selection anchored to a category like IP CCTV Cameras so you’re not reinventing the wheel every quote.
Networking and power
If you’re IP (which most new installs are), decide the default powering method:
PoE from NVR for small jobs, PoE switch for anything bigger or with longer runs.
A dedicated category like POE Switches makes it easy to keep your BOM consistent.
Accessories and finishing
Pick a standard list for mounts, junction boxes, glands, labels, and so on—then treat anything beyond that as a priced extra. Your “default accessories basket” can sit under a category like Camera & NVR Accessories.
4) Build the package matrix (the part that speeds everything up)
You want a matrix you can paste straight into a proposal. Here’s a practical structure that clients understand and installers can deliver.
Good: “Coverage and evidence”
Best for: small offices, low-risk units, basic perimeter/entrance coverage.
Standard spec idea
Cameras: 2–4MP IP cameras (general-purpose fixed lens)
Night: IR night vision (baseline)
Recording: H.265 NVR sized to camera count
Retention: 14 days target (adjustable)
Remote access: app + secure credentials handover
PoE: NVR PoE (small systems) or small PoE switch as needed
Handover: camera views named, basic playback demo, admin password set
This package is your “quick quote” winner. It’s not bargain-basement. It’s just the least complex package you’ll happily stand behind.
Better: “Identification where it matters”
Best for: retail, mixed indoor/outdoor, areas where you’ll actually need faces/plates (depending on angle).
Standard spec idea
Cameras: 4–8MP mix (use higher resolution where distance matters)
Night: better low-light performance (less blur, more usable detail)
Recording: stronger NVR, higher throughput, sensible drive sizing
Retention: 30 days target (common request in the real world)
PoE: switch-led PoE for stability and expansion
Add practical upgrades: better lenses for choke points, improved positioning, signage
If you want a clean “better night” offering without changing everything, you can anchor a variant around higher low-light camera ranges such as COLOURVISION where appropriate.
Best: “Deterrence + intelligence”
Best for: higher-value sites, yards, compounds, repeated incidents, or clients who want prevention—not just footage.
Standard spec idea
Cameras: higher-performance cameras in key locations (entrances, perimeter lines, assets)
Night: colour-at-night options in priority zones
Deterrence: active warning lights/audio where suitable
Analytics: line crossing, intrusion zones, people/vehicle classification where supported
Recording: higher channel NVR headroom + smarter storage planning
Resilience: UPS option, better segregation of CCTV network
Handover: documented system map + user roles + maintenance plan option
This is where Active Deterrence Cameras can become your “hero” differentiator—because it’s something clients can understand instantly: “it doesn’t just record; it pushes back.”
5) Standardise your pricing structure (so you stop re-quoting from scratch)
A good/better/best range works best when your pricing is built from repeatable blocks:
A) Base system price (by camera count band)
Example bands you can use internally:
4 cameras
8 cameras
12 cameras
16 cameras
Each band has a fixed “kit + labour” baseline with your standard assumptions.
B) Add-on menu (priced extras)
This is where you protect margin and avoid scope creep. Common add-ons:
Extra camera (fixed price per unit)
Longer retention (drive upgrade cost)
Out-of-hours working
Long cable runs / containment
Access equipment (MEWP/scissor lift)
UPS / resilience
Extra monitors
Remote viewing setup for multiple users
Documentation pack / O&M pack
When you quote, you give the client 1 clear package price, then list extras as optional or required based on site reality.
Use an internal checklist to decide what’s “included by default” and what triggers an add-on.
6) Lock your “assumptions” into every quote (this is where installers make money)
If you only do 1 thing after reading this, do this: put your assumptions in writing, every time.
Your packages should include standard assumptions like:
1 x recorder location agreed and accessible
Standard working hours
Standard cable routes (no major builders work)
Power and network availability at agreed points
Reasonable access to camera positions (ladders/tower; no MEWP unless stated)
Client responsible for permissions (landlord, wayleaves, etc.)
Signage responsibility and GDPR responsibilities clarified
That last part matters. Clients don’t always know what they need to do. If you’re dealing with commercial CCTV, you’ll often end up answering compliance questions—so it helps to have a reference point for regulated environments. Even if you’re not in that world every day, having a page like NDAA Compliant CCTV Solutions in the UK
