Recruiting BD, Powered by Apollo's Database
For a solo or boutique recruiter, the edge isn't volume — it's knowing which companies are hiring before the competition does. That's what Apollo's B2B database is for: filtering for companies with open job postings, fresh funding rounds, or headcount growth, then pulling the hiring managers behind those signals into a sequence.
Apollo handles the data and the sending workflow. ColdRelay is the layer underneath — the secondary domains, mailboxes, and dedicated IPs Apollo actually sends from. This guide covers how independent recruiters wire the two together: building signal-driven searches in Apollo, sequencing hiring managers for business development, sourcing passive candidates by title and skills, and keeping all of it off your primary domain.
Why Run Apollo on ColdRelay Infrastructure
Apollo gives recruiters two things most desks pay separate vendors for: a B2B contact database with hiring and intent signals, and a sequencing engine to act on them. What it doesn't provide is the sending infrastructure itself — Apollo sends from whatever mailboxes you link under Settings → Mailboxes, and the deliverability of those mailboxes is your problem, not Apollo's.
That's the gap ColdRelay fills. Instead of running BD outreach from your personal recruiting domain — the same one your candidate submissions and offer-stage emails depend on — you provision dedicated mailboxes on isolated Azure tenants with dedicated IPs, fully DNS-configured (SPF, DKIM, DMARC) and ready in about an hour. Link those to Apollo and your sequences send from infrastructure built to land, while your real domain stays clean.
The pairing is strictly additive: Apollo is the data and sending layer, ColdRelay is the infrastructure beneath it. You keep Apollo's filters, signals, and sequences — you just give them mailboxes that won't burn your reputation.
Visit Apollo →Connecting ColdRelay Mailboxes to Apollo
Provision mailboxes on ColdRelay
Pick one or two secondary domains adjacent to your recruiting brand. ColdRelay supports 100-150 mailboxes per domain, but a solo or boutique desk usually starts much smaller — 10-30 mailboxes covers most independent BD volume. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC pre-configured.
Link the mailboxes in Apollo
In Apollo, go to Settings → Mailboxes and link each ColdRelay mailbox as a sending account. Set each mailbox's daily sending limit to 2 outbound emails per day — that mirrors ColdRelay's per-mailbox budget of 4 sends/day total, split 2 outbound + 2 warmup. ColdRelay's warmup runs continuously on its own, so there's no warmup waiting period before your first sequence.
Build signal-driven saved searches
Create saved searches and personas in Apollo for your niche: filter companies by active job postings in your specialty, recent funding rounds, or headcount growth, then layer on the buyer persona — VP Engineering, Head of Talent, hiring manager titles. Save a separate search for passive candidate sourcing using title, skills, and tenure filters.
Create sequences with email and call steps
Build an Apollo sequence for the BD motion: two or three email steps referencing the specific signal that surfaced the company (the open req, the raise), with a call step between touches — boutique recruiters win on the phone, and Apollo's dialer slots into the sequence natively. Attach your linked ColdRelay mailboxes so sends rotate across them.
Enroll prospects and let the signals refresh
Enroll contacts from your saved searches into the sequence. Because the searches are saved, Apollo keeps surfacing new companies as they trigger your filters — new postings, new rounds — so the top of your BD funnel refills weekly without re-researching. Add ColdRelay mailboxes whenever you need more daily capacity.
The Boutique Recruiter Apollo Playbook
Sequence the signal, not the title
A hiring manager with three open reqs and a fresh Series B is a different email than a cold title match. Reference the specific trigger in step one — Apollo's job posting and intent filters exist so your opener can prove you did the work.
Run BD and candidate sourcing as separate personas
Keep two saved personas in Apollo: hiring-side buyers (talent leaders, line managers at growing companies) and passive candidates (title, skills, and tenure filters). Different searches, different sequences, same ColdRelay mailbox pool underneath.
Keep placements on your real domain
Candidate submissions, interview scheduling, and offer-stage email go from your primary domain. Everything cold — BD sequences and passive-candidate first touches — runs from ColdRelay secondary domains, so a deliverability dip never costs you a placement.
Use call steps to punch above your size
A boutique desk can't out-send an agency, but it can out-touch one. Put a call step after the second email in every Apollo BD sequence — replies that start on the phone close faster, and the email did the warm-up.
Typical Boutique Recruiter Benchmarks (Apollo + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared provider pools |
| BD reply rate (signal-led) | 3-6% | Referencing the open req or funding round in step one lifts replies meaningfully |
| Passive candidate reply rate | 5-9% | Tight title/skills filters and a specific role beat generic recruiter intros |
| 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, plus saved searches and sequence setup in Apollo |
What It Costs: Apollo + ColdRelay
Billed per mailbox per month, with volume tiers that drop as mailbox count rises (see the table below). DNS, dedicated IPs, and isolated Azure tenants are included — a boutique desk's starting footprint of 10-30 mailboxes stays modest.
Apollo is a separate subscription covering the contact database, signals, and sequencing — priced per its current plans, typically per seat.
Solo recruiters keep both bills small: a single Apollo seat for data and sequencing, plus a small ColdRelay mailbox pool for sending. Capacity scales by adding mailboxes, not by re-platforming.
| 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 compete with Apollo?
No — they're complementary layers. Apollo provides the B2B database, hiring signals, and sequencing; ColdRelay provides the domains, mailboxes, and dedicated IPs Apollo sends from. Recruiters use both together: Apollo decides who to email, ColdRelay makes sure it lands.
How many mailboxes does a solo recruiter actually need?
At 2 outbound sends/day per mailbox (4/day total including 2 warmup sends), 10 mailboxes is 20 outbound emails a day — enough for a tightly targeted BD motion. Boutique desks running BD plus passive candidate sourcing often land at 20-40 mailboxes, far below the 100-150 a single domain supports.
Do I need to wait for a warmup period before sending from Apollo?
No. ColdRelay mailboxes arrive with warmup running continuously — 2 warmup sends/day per mailbox as part of the 4/day budget — and DNS (SPF, DKIM, DMARC) pre-configured. You can link them under Apollo's Settings → Mailboxes and start sequencing the same day, in about an hour from provisioning.
Should candidate sourcing and BD outreach come from the same mailboxes?
At boutique volume it's workable, but separating them is cleaner: use distinct ColdRelay domains (or at least distinct mailbox groups) per motion so a deliverability issue on one never touches the other. Either way, keep both motions off the primary domain you use for submissions and offers.