If you sell business continuity software or disaster recovery services, you know the problem: your buyers don't think about you until they already need you. And by then, they're not shopping around - they're panicking.
This creates a weird dynamic for cold email. You're reaching out to people who intellectually know they should have a plan, but emotionally believe "it won't happen to us." Your email needs to break through that denial without sounding like fearmongering. It also needs to get past multiple gatekeepers - from IT directors to ops managers to C-suite executives - all of whom have different concerns.
Here's what actually works when you're selling business continuity.
Target the Real Decision-Makers, Not Just IT
Most business continuity vendors focus their cold email on IT directors. That's a mistake. While IT has input, the actual buying decision lives somewhere else depending on company size and industry.
In mid-market companies (100-1000 employees), your primary target is the operations or facilities director - the person responsible if the office burns down or systems go down for a day. They care about continuity because downtime directly hits their OKRs.
In larger companies (1000+ employees), you're actually looking at the Chief Information Security Officer or Chief Risk Officer. These are the people who sit in compliance meetings and know exactly what regulators expect.
Build your list around these titles first: Chief Risk Officer, Chief Information Security Officer, VP of Operations, Director of Business Continuity (if they exist), Chief Compliance Officer. IT director comes third, not first.
The Opening Line That Works: Problem + Specificity
Generic openings fail here. Your prospect doesn't need another "I noticed you're in the financial services space" email. They need to immediately sense you understand a real operational problem they face.
The structure is: acknowledge a specific operational vulnerability in their industry, then connect it to a business outcome they care about.
Hi [Name], I was looking at your office locations and noticed you have 3 main sites. If one campus went down for a week due to infrastructure failure, most teams would be working from coffee shops - which usually means about 60% productivity loss on technical work. That's what we usually see with companies your size when they don't have a tested continuity plan.
This works because it:
- Shows you did actual research (specific number of locations)
- Connects downtime to a business metric they understand (productivity loss)
- Implies you've seen this problem many times (the "usually see" part)
- Doesn't assume they have a plan already
For SaaS-based business continuity tools, shift the example slightly:
Hi [Name], I was looking at your tech stack and saw you're running on AWS with a single region. Most companies we talk to don't realize how quickly a regional outage turns into a revenue problem - we usually see teams lose about 8-12 hours before they can failover if they don't have a documented plan. Have you stress-tested your recovery process lately?
The Middle Section: Proof Points From Their Industry
At this stage, your prospect is still skeptical. Prove that other companies like theirs have already solved this and that it matters.
This is where you drop a recent event or statistic specific to their industry. Don't make it up - use real incidents from the past 18 months.
For financial services companies:
- Reference the recent bank outages (SVB, Silvergate) and mention how continuity planning would have protected customer confidence
- Mention regulatory changes - FDIC or SEC guidance on business continuity now explicitly covers third-party vendor failures
For healthcare organizations:
- Point to the Scripps and Change Healthcare ransomware incidents - both involved weeks of downtime because recovery plans weren't documented
- Reference HIPAA audit trends showing more enforcement on continuity gaps
For manufacturing:
- The recent shipping delays and supply chain disruptions forced companies without backup suppliers to lose 30-50% revenue for quarters
- Insurance now requires documented recovery plans for coverage
Keep this section to 2-3 sentences maximum. You're building credibility, not writing a case study.
The Ask: Make It Absurdly Low Friction
This is critical for business continuity specifically. Your prospect is not excited to take a call about disaster scenarios. They're busy. You need to give them a reason to say yes that requires almost no commitment.
The old ask - "Can we schedule a demo?" or "Would you be open to a 20-minute call?" - fails here. That sounds like a sales call.
Instead, use a diagnostic approach:
My only ask: could you spend 3 minutes answering 4 quick questions about your current setup? I ask because most companies we work with are missing one specific thing - and I can tell you in about 30 seconds whether it applies to you. If it does, we can chat. If not, you've got a useful checklist either way.
The "4 quick questions" framing resets expectations. You're not pitching. You're diagnosing. And people will answer diagnostic questions when they won't take sales calls.
Sequence Strategy: Hit Them Multiple Times With Different Angles
Business continuity buying takes longer than most software sales - usually 60-90 days. Your first email might land when the prospect doesn't think about continuity at all. The second one hits after they had a close call (office power outage, brief system downtime). The third one reaches them right after their CFO asks about insurance coverage.
Space your emails 5-7 days apart. Change the subject line and angle for each one:
- Email 1: The operational vulnerability angle (what you read above)
- Email 2: The compliance/regulatory angle - reference a recent audit finding or regulatory update in their industry
- Email 3: The insurance angle - mention that their current policy might not cover losses if they don't have a tested plan
This approach works because you're not being repetitive - you're touching different buying centers within the same organization. The ops director cares about email 1. The compliance officer cares about email 2. The CFO notices email 3.
Response Handling: Play the Long Game
When someone responds to a business continuity email, they're usually responding to a specific concern that just surfaced. They might have had an outage. They might have heard from their auditor. They might have just seen news about an incident in their industry.
That means your first response should acknowledge the specific context they're in - don't generic-up your reply. Reference the exact problem you mentioned and ask one clarifying question about their current situation, not about your product.
This is standard B2B practice, but for business continuity vendors it's especially important because buyers have high skepticism about whether this is a real need or just sales pressure.
When to Bring in Help
Cold email for business continuity works - but it requires consistent execution. You need to build accurate lists of the right titles, customize subject lines and openings for each prospect's industry and company size, manage multi-email sequences, and handle replies thoughtfully.
If you're trying to do this while running the business - writing product updates, managing customer implementations, handling support - the campaign usually stalls after the first 20 emails. The infrastructure breaks down. Personalization gets skipped. Follow-up emails don't go out on schedule.
This is exactly what cold email business development should handle for you: building the targeted list, writing templates that actually reflect your buyer's concerns, running the sequences on schedule, and qualifying responses so you're only taking meetings that make sense. For business continuity specifically, that means handling the complexity of multiple decision-makers and the longer sales cycle without letting campaigns go cold.