Headcount-Trigger Prospecting, Run Through Apollo
Group benefits doesn't sell on a steady drumbeat — it sells at thresholds. The 38-person company that ignored every benefits email becomes a live opportunity the quarter it hires its way toward 50 full-time employees and ACA applicable-large-employer obligations. The 80-person company that doubled headcount in a year has almost certainly outgrown the broker who set up its plan at 25. The buying moment isn't a date on a calendar; it's a line on a headcount chart — and the broker who emails while the company is crossing it gets the conversation before anyone else knows to ask.
Apollo is the tool that can actually see those lines being crossed: a B2B database with employee-count bands, headcount-growth filters, and hiring signals, plus the title filters to find the HR or finance person who owns the decision. ColdRelay is the infrastructure underneath — the secondary domains, mailboxes, and dedicated IPs that Apollo's sequences actually send from, so the agency domain carrying binders and claims correspondence never appears in a prospecting email. This guide covers how to wire the two into a trigger-event machine.
Why Run Apollo on ColdRelay Infrastructure
Apollo's edge for a broker is upstream of the send: it's the database and the filters. You can save a search for companies in your territory sitting at 40-49 employees with headcount up 20%+ year over year, layer on active hiring signals, and have Apollo surface the new companies matching it every week — then push the right contacts straight into a sequence. No other part of the broker stack watches the market for threshold-crossers like that.
What Apollo doesn't do is provision the mailboxes those sequences send from. It links whatever accounts you connect under Settings → Mailboxes, and the deliverability of those accounts is the infrastructure layer's problem. That's where ColdRelay fits: dedicated mailboxes on isolated Azure tenants with dedicated IPs, SPF, DKIM, and DMARC pre-configured, ready in about an hour. There's no upfront warmup period before sending — warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup) — and placement holds at 95%+.
The pairing is additive, not competitive: Apollo is the data and sequencing layer that finds companies the moment they cross a headcount line, and ColdRelay is the infrastructure layer that makes sure the email about it actually lands. A perfect trigger wasted on a spam-foldered send is worse than no trigger at all.
Visit Apollo →Connecting ColdRelay Mailboxes to Apollo
Provision mailboxes on ColdRelay
Trigger-event volume is lower than blast volume but the sends are precious, so size the pool to the signal flow. ColdRelay supports 100-150 mailboxes per domain on isolated Azure tenants with dedicated IPs; benefits-focused brokerages typically start with 20-60 mailboxes on one secondary domain — never the agency domain. Everything provisions in about an hour with SPF, DKIM, and DMARC already configured.
Link the mailboxes under Settings → Mailboxes
In Apollo, go to Settings → Mailboxes and link each ColdRelay mailbox using the SMTP/IMAP credentials from the ColdRelay dashboard export. Each mailbox links as its own sending account, so Apollo can distribute sequence sends across the pool instead of hammering one address.
Set per-mailbox daily send limits to 2
In each linked mailbox's settings, set Apollo's per-mailbox daily send limit to 2 outbound emails. That mirrors ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup — with ColdRelay running the warmup half continuously in the background. Don't add another warmup layer on top.
Build the threshold searches and personas
In Apollo's database, create saved searches keyed to the thresholds that trigger a benefits purchase: employee-count bands like 40-49 and 45-55, headcount growth over the past 6-12 months, and active hiring signals, all scoped to your territory and target industries. Then build saved personas for the buyer — HR manager and people-ops titles at companies over ~75 employees, founder/CEO/CFO titles below that — so one click turns a matching company into the right contact.
Create the trigger sequence and launch
Build an Apollo sequence that opens with 2-3 threshold-specific emails, then adds a call task and a LinkedIn step for accounts that engage. Enroll contacts from your saved searches, re-run the searches weekly to catch newly matching companies, and work replies same-day — a company crossing 50 employees is talking to someone about benefits this quarter, and the only question is whether it's you.
The Insurance Broker Apollo Playbook
Prospect the threshold, not the renewal date
Renewal-date outreach fights every other broker over the same X-date window. Threshold outreach has the field nearly to itself: a company at 46 employees and hiring is weeks from ACA applicable-large-employer territory, and most of its leadership doesn't know what changes at 50. Apollo's employee-count bands and headcount-growth filters are the only practical way to maintain a live list of those companies — saved searches at 40-49 and 45-55 employees, re-run weekly, are the core asset of this motion.
Treat hiring signals as the early warning, headcount as confirmation
Database headcount lags reality — the company that posted eight job openings last month will cross the line before any directory updates. Layer Apollo's hiring signals on top of the count filters so you catch growers while they're growing: a 42-person firm with active postings across multiple departments is a better prospect today than a 51-person firm that crossed quietly a year ago and already solved the problem.
Match the persona to the company's size, not a fixed title list
The benefits buyer changes as the company grows, and a single title filter misses half the market. Below roughly 75 employees there's usually no HR leader — the founder, CEO, or CFO owns the decision. Above it, an HR manager or people-ops lead runs the evaluation with finance approving. Build two Apollo personas and route each saved search to the right one, so the 45-person company hears from you at the founder's inbox and the 120-person company at the HR director's.
Lead with the fact of the threshold, never a quote
The trigger gives you a first line no renewal-window email can match: it's about their company, not your agency. 'You're on track to cross 50 full-time employees — a few compliance and plan obligations kick in at that line' earns the reply because it's useful before it's a pitch. Stay compliance-aware: never promise savings percentages or imply premiums in cold copy, and let the licensed conversation happen on the call task Apollo surfaces after the reply.
Typical Insurance Outbound Benchmarks (Apollo + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate on trigger-matched sends | 3-6% | Threshold and hiring-signal triggers outperform static-list outreach; the relevance is built into the targeting |
| New threshold-crossers per weekly search re-run | 10-40 companies | Varies with territory size; Apollo saved searches surface newly matching accounts each cycle |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Time to first campaign | Same day | ~60 minutes to provision on ColdRelay, plus search and sequence setup 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). DNS, dedicated IPs, and isolated Azure tenants are included — and since ColdRelay supports 100-150 mailboxes per domain, even a scaled-up trigger operation fits on one or two secondary domains.
Apollo is billed separately on its own subscription for the contact database, filters and signals, saved searches, personas, and sequences — priced per its current plans.
The economics suit a precision motion: Apollo's bill buys the signal — knowing which companies are crossing a threshold this week — and the infrastructure bill scales with the mailbox pool at per-mailbox rates that drop in higher tiers. Because trigger volume is targeted rather than sprayed, most brokerages run this play on a smaller pool than a volume blast would need.
| 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
Is ColdRelay an alternative to Apollo?
No — they're complementary layers, not competitors. Apollo is the data and sequencing layer: the contact database, headcount and hiring-signal filters, saved searches, personas, and sequences with email, call, and LinkedIn steps. ColdRelay is the infrastructure layer underneath — the secondary domains, mailboxes, and dedicated IPs that Apollo's sequences send from. The trigger-event motion uses both together.
Why does the 50-employee mark matter so much for benefits prospecting?
At 50 full-time employees (including full-time equivalents), a US company generally becomes an applicable large employer under the ACA, with employer-shared-responsibility obligations it didn't have at 49. Plenty of founders running 45-person companies don't know that's coming — which is exactly why a broker who reaches out while they're crossing the line, with a plain explanation rather than a pitch, tends to get the meeting. Apollo's employee-count bands and growth filters are how you find those companies before the threshold, not after.
Apollo links our existing mailboxes — why not just connect the agency's own accounts?
Because your agency domain carries certificates of insurance, binders, and claims correspondence that absolutely cannot afford a damaged sending reputation. Cold prospecting volume belongs on separate infrastructure: ColdRelay mailboxes on secondary domains, isolated Azure tenants, and dedicated IPs, linked into Apollo under Settings → Mailboxes. The agency domain never appears in a sequence, so a prospecting campaign can't put a claims email in a spam folder.
Do new ColdRelay mailboxes need a warmup period before Apollo can start sequencing?
No waiting period. Each mailbox sends 4 emails/day total — 2 outbound + 2 warmup — with warmup running continuously as part of that budget rather than as an upfront phase. Mailboxes provision in about an hour with SPF, DKIM, and DMARC pre-configured, so the same afternoon your saved searches surface a batch of threshold-crossers, the sequence reaching them can already be live. Just set Apollo's per-mailbox daily send limit to 2 and leave the warmup to ColdRelay.