Targeting Intelligence Is the Security Vendor's Real Edge
Most cold email advice for cybersecurity companies obsesses over getting past filters and writing for skeptical buyers. Fair enough — but the highest-leverage decision happens before a single word is written: who gets the email at all. A security product is only relevant to companies running the stack it protects, facing the compliance regime it satisfies, or hitting the maturity moment where they finally staff security seriously. Apollo is where that targeting happens — its B2B database layers technology filters, industry and headcount combos, and hiring signals into lists that are relevant by construction.
What Apollo doesn't provide is the infrastructure those emails send from. The mailboxes linked under Settings → Mailboxes are whatever you bring — and if that's your corporate domain on a shared tenant, the most precisely targeted list in the world still dies in quarantine. This guide covers the pairing: building security-specific targeting in Apollo with technographics, compliance proxies, and hiring signals, and sending it all from ColdRelay mailboxes built to land.
Why Run Apollo on ColdRelay Infrastructure
Apollo bundles the contact database, list filters, and sequencing into one platform — but it sends from mailboxes you link yourself. It doesn't provision domains, configure DNS, or carry the deliverability of the sending identities. That gap matters double for security vendors: your targeting may be precise enough to find the 400 companies that genuinely need you this quarter, but those 400 companies sit behind the strictest gateways in B2B, and a poorly provisioned mailbox wastes every one of those rare, qualified shots.
ColdRelay is the layer underneath. You provision dedicated mailboxes on isolated Azure tenants with dedicated IPs, with SPF, DKIM, and DMARC pre-configured — ready in about an hour, with no warmup period before sending. ColdRelay supports 100-150 mailboxes per domain, so a serious sending pool fits on a couple of secondary domains, fully separate from the corporate domain your customers trust.
The pairing is additive, not competitive: Apollo is the data and sequencing layer — who to email and in what order — and ColdRelay is the infrastructure layer — the domains, mailboxes, and dedicated IPs the sequences send from. Precision targeting deserves delivery that matches it.
Visit Apollo →Connecting ColdRelay Mailboxes to Apollo
Provision mailboxes on ColdRelay
Choose secondary domains adjacent to your brand but separate from your primary corporate domain. ColdRelay supports 100-150 mailboxes per domain; security vendors running a signal-driven motion typically start with 20-50 mailboxes on 1-2 domains, since precise lists need fewer sends than spray-and-pray. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC already configured.
Link the mailboxes in Apollo under Settings → Mailboxes
In Apollo, go to Settings → Mailboxes and link each ColdRelay mailbox so sequences can send from the pool. Linked mailboxes become available as sending accounts across your sequences, and Apollo attributes replies and meetings back to the right sender.
Set per-mailbox daily send limits to 2
In each linked mailbox's settings, cap the daily send limit at 2 outbound emails. That mirrors ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup. ColdRelay's warmup runs continuously as part of that budget, so the mailboxes are sequence-ready the day they're linked; the cap just keeps Apollo from spending reputation faster than the infrastructure is designed for.
Build saved personas and technographic searches
This is where the security-specific work happens. In Apollo's search, stack technology filters (companies running the platforms your product protects, or a competitor's tool you displace), industry × headcount combos that proxy compliance exposure, and job-posting signals like open security engineer or first-CISO roles. Save each combination as a saved persona and saved search so new matches flow in continuously instead of being a one-time list pull.
Build multi-channel sequences and launch
Create Apollo sequences that mix email, call, and LinkedIn steps — security buyers who ignore a cold email often pick up when the prior touches established context. Attach the linked ColdRelay mailbox pool to the email steps and enroll contacts from your saved searches. At 2 outbound sends/day per mailbox, 30 mailboxes covers 60 highly targeted sends a day — more than enough to work a signal-driven list properly.
The Cybersecurity Apollo Playbook
Filter by the stack you protect — or the tool you displace
Apollo's technology filters show you which companies run the platforms your product secures and which run a competitor you displace. A cloud security vendor filters for companies on the cloud platforms it covers; an endpoint vendor filters for installed competitors approaching renewal-shaped pain. The email that opens with the prospect's actual stack isn't pattern-matched as a blast — because it isn't one.
Use industry × headcount as a compliance-exposure proxy
Compliance pressure is rarely a filterable field, but its proxies are. A healthcare company past 50 employees has HIPAA exposure outgrowing its ad-hoc controls; financial services firms carry regulatory obligations at any size; a company selling into enterprise is getting hammered with vendor security questionnaires. Build Apollo segments from these industry-and-headcount combos and let the copy name the obligation the segment implies.
Treat security hires as maturity-moment triggers
A company posting its first CISO role or a cluster of security engineer openings is publicly announcing a budget, a mandate, and a gap — the exact moment a security vendor wants to arrive. Save Apollo searches on those hiring signals and enroll new matches as they appear; a first-CISO email that acknowledges the new leader's mandate lands very differently than a pitch sent the quarter before anyone owned the problem.
Let precision set the volume, not the other way around
At 2 outbound sends/day per mailbox (4/day total with warmup), capacity is deliberately scarce — so spend it like it's scarce. Rank your saved searches by signal strength: stack-match plus hiring signal outranks stack-match alone, which outranks industry-proxy alone. Enroll the strongest tier first and let weaker tiers wait for capacity, rather than diluting a tight list to fill mailbox quota.
Typical Cybersecurity Outbound Benchmarks (Apollo + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs, isolated tenants, and pre-configured SPF/DKIM/DMARC — non-negotiable when the recipients run the gateways |
| Reply rate, technographic-matched lists | 2-4% | Stack-specific relevance roughly doubles what generic title-based security lists produce (1-2%) |
| Reply lift on hiring-signal triggers | 2-3x | First-CISO and security-engineer-posting segments vs. untriggered sends to the same company profile |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Time to first sequence | Same day | ~60 minutes to provision on ColdRelay, plus linking mailboxes and building saved searches in Apollo |
What It Costs: Apollo + ColdRelay
You pay per mailbox per month for the infrastructure, with volume tiers that drop as you scale (see the table below). Dedicated IPs, isolated Azure tenants, and pre-configured DNS are included.
Apollo is billed separately on its own per-seat subscription covering the contact database, filters, saved searches, and sequencing — priced per its current plans.
Infrastructure cost scales with mailbox count; Apollo cost scales with seats and data credits. A signal-driven security motion keeps both lean — precise lists need fewer mailboxes than volume plays, and the volume tiers reward you as the pool grows with pipeline.
| Mailboxes | ColdRelay price / mailbox / month |
|---|---|
| 1–199 | $1.00 |
| 200–999 | $0.85 |
| 1,000–4,999 | $0.70 |
| 5,000+ | $0.55 |
Each mailbox sends 4 emails per day — 2 outbound to prospects + 2 warmup. ColdRelay provisions mailboxes on isolated Azure tenants with dedicated IPs; Apollo handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Does ColdRelay replace Apollo?
No — they're complementary layers and you use them together. Apollo is the data and sequencing layer: the contact database, technographic and signal filters, saved personas, and multi-channel sequences. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs those sequences send from. Neither does the other's job.
Apollo's database has millions of contacts — shouldn't we send at higher volume?
The database is big; your real market isn't. Once you stack technology filters, compliance-proxy segments, and hiring signals, a security vendor's genuinely qualified list is usually hundreds of companies per quarter, not tens of thousands. Each ColdRelay mailbox sends 4 emails/day total — 2 outbound + 2 warmup — and that budget fits a precise list naturally. To scale capacity, add mailboxes; ColdRelay supports 100-150 per domain.
Do ColdRelay mailboxes need a warmup period before Apollo sequences can start?
No separate warmup period. Warmup runs continuously as part of each mailbox's 4 sends/day budget — 2 outbound + 2 warmup — so mailboxes are sequence-ready the day you link them under Settings → Mailboxes. Set Apollo's per-mailbox daily send limit to 2 and launch the same day you provision.
How reliable are technographic and hiring-signal filters for security targeting?
Reliable enough to rank on, not to bet blindly on — technology data lags real stacks, and a job posting can be backfill rather than a new mandate. Treat the signals as prioritization, not gospel: enroll the strongest combinations first, verify the trigger in your first line where you can, and let reply data tell you which saved searches actually convert. Even imperfect signals beat title-only lists by a wide margin for this audience.