Consulting Outbound, Run Through Apollo
Most consulting outbound fails before the first email is written, because the list is wrong. A pricing consultant emails companies with no pricing function. An ops consultant pitches a 12-person startup that can't fund a $40k engagement. The copy gets blamed, but the real problem is that nobody defined — in filterable terms — which companies can actually buy each practice area.
That definition problem is exactly what Apollo is for. Its B2B database lets you express a practice area as a set of filters — industry, headcount band, funding stage, title — and its signals tell you when a company is entering the window where your specialty becomes urgent. Apollo handles who and when; ColdRelay handles the layer underneath: the secondary domains, mailboxes, and dedicated IPs that Apollo's sequences actually send from. This guide covers wiring the two together, with the emphasis on the part the other consultant playbooks skip — building lists where every name on them can write the check.
Why Run Apollo on ColdRelay Infrastructure
Apollo is a database, targeting, and sequencing platform — you find prospects in it, save them as personas, and sequence them through email, call, and LinkedIn steps. What it sends those emails from is whatever mailboxes you link to it, and it doesn't provision domains or guarantee the deliverability of those mailboxes. That's the infrastructure layer's job.
Good targeting raises the stakes on that layer rather than lowering them. When you've filtered down to the 300 companies that genuinely fit your practice area, every email that lands in spam is a meaningful slice of your total addressable outreach — there's no big list to absorb the waste. With ColdRelay, you get dedicated mailboxes on isolated Azure tenants with dedicated IPs, fully DNS-configured (SPF, DKIM, DMARC) and ready in about an hour, on secondary domains that keep your client-facing address out of outbound entirely.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Apollo is the targeting and sending layer on top. You keep Apollo's database, saved personas, signals, and multichannel sequences — and give them mailboxes built to land at 95%+ inbox placement, so the precision you built into the list survives the trip to the inbox.
Visit Apollo →Setting Up Apollo on ColdRelay Infrastructure
Translate each practice area into an Apollo saved persona
Before touching infrastructure, do the targeting work. For each practice area, build an Apollo search that encodes who can buy it: industry, a headcount band wide enough to have the problem and narrow enough to afford you (say 50-500 for an ops practice), funding stage if venture money is what funds your engagements, and the two or three titles that own the budget. Save each one as a persona — 'Series B SaaS, VP Ops, 50-200 heads' — so the definition is reusable, not rebuilt from memory every quarter.
Layer hiring signals onto each persona for timing
Fit says who; signals say when. In Apollo, layer hiring filters onto each saved search for roles adjacent to your specialty — a company hiring its first RevOps manager is days from discovering it needs a RevOps consultant to bridge the gap; one posting three finance roles at once is mid-reorganization, which is when a finance-transformation consultant is relevant. Save these signal-narrowed searches separately: they're your priority queue, while the broader persona is the backlog.
Provision mailboxes on ColdRelay
Now size the infrastructure to the lists you just built, not the other way around. A consultant running two or three personas typically starts with 5-15 mailboxes on one secondary domain near the firm's name — ColdRelay supports 100-150 mailboxes per domain, so headroom isn't a concern. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC already configured, and there's no warmup waiting period before the first send.
Link the mailboxes in Apollo and set per-mailbox limits
In Apollo, go to Settings → Mailboxes and link each ColdRelay mailbox, then set each one's daily send limit to 2 outbound emails per day. That mirrors ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup, with warmup running continuously on ColdRelay's side — so don't add any warmup tooling on top; the budget already includes it.
Build one sequence per persona and launch
Create a separate Apollo sequence for each saved persona, so the copy can speak to that segment's actual situation — the email a Series B VP Ops gets should not survive being sent to a family-owned manufacturer. Mix in Apollo's call and LinkedIn steps where they fit your style, attach your linked mailboxes, and enroll the signal-matched prospects first. From day one, your limited daily sends go to the companies most likely to be in-market this month.
The Consultant Apollo Targeting Playbook
Filter for ability to buy, not just relevance
The most expensive prospects in consulting outbound are the ones who love the idea and can't fund it. Bake buying capacity into every Apollo persona: a headcount floor below which there's no budget owner for your work, a funding-stage filter if engagements only happen on raised money, an industry cut that excludes margin profiles that never pay for outside help. A company that fits your skills but fails these filters isn't a prospect — it's a future polite rejection you paid to find.
Treat hiring signals as your when, not your who
A signal doesn't make a bad-fit company good — it makes a good-fit company timely. Work the intersection: persona filters first, then hiring activity adjacent to your specialty on top. A company recruiting for roles next to your practice area is publicly admitting it has the problem and is already spending on it; your email arrives as a faster, lower-risk alternative to a six-month hire. That intersection list is small, which is exactly why it deserves your first sends of the day.
Let the 2-a-day budget enforce list discipline
Each ColdRelay mailbox sends 4 emails/day — 2 outbound + 2 warmup — so a 10-mailbox pool puts out 20 outbound emails a day, not 2,000. Treat that ceiling as the feature it is: when you only have 20 sends, you stop asking 'who else can I add?' and start asking 'who are today's 20 best-fit, best-timed companies?' Rank enrollment by signal recency within persona fit, and let yesterday's lukewarm matches wait. Scarcity at the send layer is what keeps the targeting layer honest.
Re-run saved searches weekly; prune personas quarterly
A practice-area list isn't a one-time export — companies cross your headcount floor, raise rounds, and post trigger roles every week. Re-run each saved search on a fixed weekly slot and enroll only the net-new matches, so the pipeline refills with companies that just became right. Then audit quarterly against reality: pull your last ten real engagements, check which Apollo filters they'd have matched, and tighten any persona that wouldn't have found them. Your filters should converge on your actual client base, not your aspirational one.
Typical Consultant Outbound Benchmarks (Apollo + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate on signal-matched lists | 6-10% | Persona fit plus hiring-signal timing; the broader persona backlog runs closer to 3-6% |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Share of raw industry list cut by buying-capacity filters | 60-80% | Headcount, funding-stage, and title filters remove most companies that could never fund an engagement |
| Time to first campaign | Same day | ~60 minutes to provision on ColdRelay, plus persona and sequence setup in Apollo — no warmup waiting period |
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, IPs, and isolated Azure tenants are included — and because tight targeting keeps consultant mailbox counts small, the infrastructure line stays small with them.
Apollo is billed separately on its own subscription for database access, saved personas and searches, signals, and sequencing — priced per its current plans, typically per seat with credit allowances for contact data.
Infrastructure cost scales with mailbox count; Apollo's cost scales with seats and data credits. For a consultant, the combined stack is a modest fixed cost against engagements priced in the tens of thousands — and the targeting work it enables is what stops you paying that cost to email companies that were never going to buy.
| 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 do different jobs and stack together. Apollo is where you find and define your market — the B2B database, saved personas, hiring signals, and the sequences that send email, call, and LinkedIn steps. ColdRelay provides the underlying domains, mailboxes, and dedicated IPs that those sequences send from. You use them together — infrastructure underneath, targeting and sending layer on top.
Apollo already connects to my Google Workspace — why add ColdRelay mailboxes?
Because the mailbox Apollo links under Settings → Mailboxes carries all the deliverability and reputation risk of the sending. Linking your firm's own workspace account puts the domain your clients, proposals, and invoices run on directly into cold outbound. ColdRelay mailboxes live on secondary domains, on isolated Azure tenants with dedicated IPs — so Apollo gets purpose-built sending identities and your client-facing domain carries zero outbound risk.
Do I need a warmup tool or waiting period before sequencing from ColdRelay mailboxes?
No. Every ColdRelay mailbox runs continuous warmup as part of its 4 sends/day budget — 2 outbound + 2 warmup — so mailboxes are ready to send the day they're provisioned, and the warmup never stops in the background. Just set each linked mailbox's daily send limit in Apollo to 2 outbound emails per day and skip any additional warmup tooling; layering more warmup on top adds noise, not deliverability.
If Apollo's database has millions of contacts, why am I only sending 20 emails a day?
Because for a consultant the database is for subtraction, not volume. Apollo's filters exist to cut millions of companies down to the few hundred that match a practice area and can fund an engagement — and its hiring signals cut that further to the ones likely in-market this month. At 2 outbound sends/day per mailbox, a 10-mailbox ColdRelay pool sends 20 emails a day to exactly those companies, roughly 400 a month. That's full coverage of a well-defined practice-area market at a pace each mailbox sustains indefinitely — adding mailboxes takes about an hour if a new practice area genuinely expands the market.