Surveillance companies have a particular cold email problem: your prospects are paranoid by nature. They don't trust unsolicited contact. They're used to being pitched. And they have actual security concerns about who they're talking to - which makes getting a response feel impossible.
Add in the fact that security decision makers are often buried three levels deep in bureaucracy, and you've got a real problem. Generic cold email tactics don't work here. You need specificity, credibility, and a clear understanding of what actually matters to the people who spec surveillance systems.
Who You're Actually Trying to Reach
Most surveillance companies waste time emailing the wrong person. They hit IT directors or facilities managers who don't own the budget. The people who actually make these decisions are:
- Chief Security Officer (CSO) or VP of Security - owns the overall security strategy and budget
- Director of Physical Security - manages cameras, access control, monitoring centers
- Loss Prevention Manager (retail/hospitality) - owns shrinkage reduction and incident response
- Facilities Director (manufacturing/industrial) - responsible for site safety and monitoring infrastructure
The CSO or Director of Physical Security is your target 80% of the time. They think about risk, compliance, incident response, and coverage gaps. They don't care about frame rates or codec specs - they care about whether the system catches what matters and integrates with their existing infrastructure.
The Opening Line That Actually Works
Your first line needs to prove you understand their specific problem, not surveillance in general. Generic opens like "we help companies improve security" get deleted. Specific ones about their actual gaps get responses.
The framework: Name a specific compliance gap, coverage area, or response problem that relates to their industry or facility type.
We worked with [similar company type] last year on their warehouse monitoring - specifically on getting incident alerts to the right person within 30 seconds instead of 5+ minutes. Wondering if that's something you're dealing with?
This works because it's not about your product. It's about a concrete problem they actually think about. If they're managing a large facility, response time to incidents matters. If they're retail, shrinkage and incident documentation matter. Name the actual problem first.
The Research Piece That Gets You In
Security decision makers are skeptical of anyone who hasn't done basic homework. One reference to something specific about their operation - a recent incident, a facility expansion, a known compliance requirement - signals you're not a spray-and-pray operation.
For surveillance, your research should focus on three areas:
- Recent news about the company - mergers, new locations, expansion plans, incidents
- Industry-specific compliance changes - new regulations affecting their sector
- Known vulnerabilities in their current setup - old technology, known gaps you can find through basic research
If they just opened a new warehouse, your angle is different than if they're dealing with a compliance audit. A retail chain handling theft losses has different priorities than a healthcare facility managing access control after a data breach.
Find one piece of public information - a press release, a compliance update, a facility announcement - and reference it specifically in your email. Not vaguely. Specifically enough that they can't claim it applies to everyone.
Email Structure That Gets Responses
Your surveillance company email should follow this structure:
- Subject line: Reference the specific problem or outcome, not your company
- Open: 1-2 sentences stating a specific gap or challenge they likely face
- Social proof: 1-2 sentences about someone similar you've worked with (or a known challenge in their industry)
- The ask: Very small - 15-minute call to explore one specific thing
- Close: Your name, title, phone number - nothing fancy
Total email length: 75-100 words. Security people read fast and have low tolerance for fluff.
Subject: Response time on your warehouse incidents? Hi [Name], I worked with a 200k+ sq ft logistics operation last quarter - their incident response time was 6-8 minutes because alerts weren't routing to the right person. They fixed it in about 30 days. Not sure if you're dealing with that, but worth a quick conversation if you are. Do you have 15 minutes sometime this week? [Your name] [Your title] [Direct phone]
Notice what's missing: your company name in the body, any feature talk, any urgency language, any value proposition fluff. Just a problem, a quick proof point, and a tiny ask.
Targeting and List Building
Your list quality determines everything. For surveillance, you need:
- Facilities over 50k sq ft (typically has formal security operations)
- Industries with high compliance requirements (healthcare, financial services, government, manufacturing)
- Companies with known security incidents or recent expansion
- Operations with multiple locations (CSOs exist at this scale)
Skip small businesses with one location and a facilities manager who wears five hats. Skip companies in low-security industries. Your response rate lives and dies on list quality here.
Use ZoomInfo or Apollo to filter for companies by facility size and industry. Cross-reference with news alerts for recent security incidents or expansion announcements. Companies dealing with active security challenges will respond at 2-3x the rate of cold prospects.
The Follow-up Sequence That Matters
Security people are busy and skeptical. Your follow-up needs to add value, not just repeat yourself.
- Email 1 (Day 0): The initial hook
- Email 2 (Day 3): New angle - reference a different problem or compliance issue relevant to their industry
- Email 3 (Day 6): Social proof from their specific vertical or problem type
- Email 4 (Day 10): Final touch - very short, gives them an out gracefully
Stop at four. If they're not interested by then, they're not interested. Most surveillance deals that close come from the first or second email anyway - your job is just to stay visible long enough to catch them at the right moment.
What Actually Converts to Meetings
Security decision makers take meetings when you've proven three things: (1) you understand their specific problem, not surveillance in general; (2) you've worked with someone similar; (3) you're not going to waste their time.
Expect a 3-5% response rate from a solid, targeted list. Expect about half of responses to convert to actual meetings. That's normal for this space. You're not missing something if it's not higher - security buyers are just more skeptical and slower to move than most B2B buyers.
The companies that actually book meetings are the ones that treat each email like they're talking to one specific person, not firing from a template at a thousand prospects.
Where Most Surveillance Companies Fail
Most surveillance companies either go too technical (talking about camera specs and codec support) or too generic (talking about "comprehensive security solutions"). The middle ground - talking about specific outcomes their team cares about - is where responses happen.
They also target too wide. Emailing every facility manager in a database wastes time. Your list should be ruthlessly specific: large facilities, high-security industries, companies with known gaps. Quality over volume, every time.
Finally, they give up too fast. This type of cold email typically takes 60-90 days to generate consistent meetings. Most surveillance companies run three weeks of campaigns, see a 2% response rate, and kill it. The companies seeing real pipeline run for at least 90 days, refine based on what's working, and let it compound.
Building This at Scale
Running cold email for surveillance means managing list quality, copy testing, follow-up sequences, and infrastructure simultaneously. If you know the framework above, you can build this yourself - but the gap between knowing it and actually running it at scale is real.
The difference between "I understand cold email for surveillance" and "we're consistently booking 5-10 security decision maker meetings per month" is execution - the research, list building, infrastructure, and campaign management that has to stay running cleanly in the background. That's where most surveillance companies either get stuck or spend 20+ hours a week on admin work instead of selling.