Signal-Driven Agency Outbound, Run Through Apollo
Most agency outbound fails on timing, not targeting. The company that fits your ICP perfectly but signed with a competitor last quarter isn't a prospect — and the company that looked dormant six months ago just raised a Series A and is suddenly the best lead on your list. The agencies winning with cold email aren't emailing better companies; they're emailing the same companies at the moment something changed.
Apollo is built to catch those moments: its B2B database layers funding, hiring, and headcount signals over title and industry filters, and saved searches surface fresh matches into your pipeline every week. ColdRelay is the layer underneath — the secondary domains, mailboxes, and dedicated IPs Apollo actually sends from. This guide covers wiring the two together into a system where the prospects find you weekly, and the email lands when it matters.
Why Run Apollo on ColdRelay Infrastructure
Apollo solves the hardest part of signal-driven prospecting — knowing who to email and when. Its database tells you which companies just raised, which ones just hired their first VP of Marketing, and which ones are posting marketing roles faster than any team could reasonably onboard. What Apollo doesn't do is provision the sending infrastructure: it sends sequences through 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. You order mailboxes on isolated Azure tenants with dedicated IPs — SPF, DKIM, and DMARC pre-configured — and they're live in about an hour. ColdRelay supports 100-150 mailboxes per domain, so a full signal-driven pool usually fits on one or two secondary domains, keeping your agency's primary domain out of outbound entirely.
The pairing is additive, not competitive: Apollo is the data, sequencing, and sending layer; ColdRelay is the infrastructure it sends through. A funding-signal email that lands in spam is worth exactly as much as no signal at all — which is why the infrastructure layer is where the whole timing advantage either survives or dies.
Visit Apollo →Connecting ColdRelay Mailboxes to Apollo
Provision the signal pool on ColdRelay
Order your mailboxes on one or two secondary domains close to your agency brand. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC pre-configured — and because warmup runs continuously as part of each mailbox's send budget, there's no waiting period before your first signal batch goes out. ColdRelay supports 100-150 mailboxes per domain, so the pool has room to grow without new domains.
Link the mailboxes in Apollo
In Apollo, go to Settings → Mailboxes and link each ColdRelay mailbox so Apollo can rotate sequence sends across the pool. Set each mailbox's daily send limit to 2 outbound emails per day — matching ColdRelay's per-mailbox budget of 4 sends/day total, split 2 outbound + 2 warmup. Warmup stays on ColdRelay's side; Apollo only spends the outbound half.
Build three saved searches, one per budget signal
Create separate saved searches in Apollo for the three signals that predict agency budget: companies that raised funding in the last 90 days, companies whose first senior marketing hire (CMO, VP Marketing, Head of Growth) started in the last 6 months, and companies with multiple open marketing roles posted recently. Saved searches refresh as new companies match, so each one becomes a self-restocking prospect feed — check them weekly and pull the fresh matches into your pipeline.
Save personas that point at the budget owner
Use Apollo's saved personas to route each signal to the person who actually controls agency spend at that stage. For seed and Series A companies with no marketing leader yet, that's the founder or CEO. Once a CMO or VP Marketing shows up in the org, the founder stops being the buyer — persona-match to the new marketing leader instead. Title filters do this automatically once the personas are saved; you stop guessing who signs.
Build one sequence per signal, then add call and LinkedIn steps
Create a distinct Apollo sequence for each saved search — the funding email, the new-leader email, and the hiring-surge email open completely differently, so they can't share copy. Use Apollo's multi-step sequences to layer a LinkedIn connection touch and a call task between email steps: a prospect who just raised is being emailed by everyone, and the agencies that show up on a second channel are the ones that get the meeting.
The Agency Signal Playbook for Apollo
Open with the trigger, not the pitch
A signal-driven email earns its reply in the first line by proving you know why now: 'Congrats on the Series A — most teams at your stage burn the first two quarters figuring out paid acquisition the hard way.' The signal is the personalization; everything after it is just the offer. If the email would still make sense sent to a company that didn't raise, didn't hire, and isn't hiring, it's not a signal email — it's a cold blast wearing a costume.
Route by stage: founder before the CMO exists, CMO after
The budget owner changes as the company grows, and emailing the wrong one wastes the signal. Pre-marketing-hire, pitch the founder on outcomes — pipeline, CAC, launch velocity — because they're buying a result they can't yet produce in-house. Post-hire, pitch the new CMO on leverage: they inherited goals bigger than their team, and an agency is how they hit quarter one numbers without waiting on headcount. Apollo's title filters split the same account list into both motions automatically.
Treat a marketing hiring surge as a capacity pitch, not a threat
Agencies often skip companies that are visibly hiring marketers, assuming the budget is going to headcount. It's the opposite signal: a company posting three marketing roles at once has committed budget to growth and is months away from having the team to spend it. The pitch writes itself — 'you'll have the team by Q4; we can run paid and lifecycle until they're ramped.' Apollo's open-roles signal finds these companies the week the postings go up, which is exactly when the gap is most painful.
Work the weekly refresh like a standing meeting
Signals decay — a funding announcement is crowded by week three, and a new CMO stops taking intro calls once their vendor stack is set. Put a fixed weekly slot on the calendar to open each saved search, pull the new matches, persona-check them, and push them into the matching sequence the same day. Because ColdRelay warmup runs continuously inside each mailbox's 4 sends/day budget (2 outbound + 2 warmup), the pool is always ready for the week's batch — the only bottleneck allowed in this system is how fast you process the list, never whether the infrastructure can send.
Typical Signal-Driven Agency Benchmarks (Apollo + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate (signal-triggered sequences) | 5-9% | Funding and new-hire triggers roughly double untargeted agency outbound; the signal does the personalization |
| Useful signal window | 2-6 weeks | Funding signals crowd fastest; new-leader and hiring-surge signals stay warm longer |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Time to first signal batch | Same day | ~60 minutes to provision on ColdRelay, plus saved searches and sequences 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 — a fixed line item that stays flat whether a given week's saved searches surface ten new signals or a hundred.
Apollo is billed separately on its own subscription for the database, saved searches, personas, sequences, and credits — priced per its current plans.
Infrastructure cost scales with mailbox count; Apollo's cost scales with seats and credit usage. For a signal-driven motion the math is unusually clean: Apollo tells you exactly which companies just got budget, and the infrastructure cost of reaching them is a known monthly number.
| 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, not competitors. Apollo is the data and sending layer: the contact database, signal filters, saved searches, personas, and sequences. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs that Apollo's sequences actually send from. You use both together — Apollo decides who gets the email and when, ColdRelay makes sure it lands.
Apollo already sends email — why do I need separate mailboxes?
Apollo sends through mailboxes you link under Settings → Mailboxes; it doesn't provision domains or carry their sending reputation. Linking your agency's primary-domain inboxes puts your real domain's reputation behind every cold send. ColdRelay mailboxes give Apollo dedicated sending infrastructure instead — secondary domains on isolated Azure tenants with dedicated IPs, SPF, DKIM, and DMARC pre-configured, live in about an hour — so signal-driven outbound never touches the domain on your proposals.
Which Apollo signals actually predict agency budget?
Three, in practice: a funding round in the last 90 days (new capital, growth mandate, no time to build in-house), a first senior marketing hire in the last 6 months (a new leader with goals bigger than their team), and multiple open marketing roles posted at once (budget committed, capacity months away). Each maps to a different buyer and a different pitch, which is why they belong in separate saved searches and separate sequences rather than one merged list.
How many mailboxes do we need if prospect volume changes week to week?
Size the pool to your busiest realistic week, not the average — signal flow is lumpy, and a funding-announcement wave you can't email inside the window is pipeline lost for good. At 2 outbound sends/day per mailbox (of the 4/day total, with 2 warmup), 25 mailboxes handles about 350 outbound sends a week, comfortable headroom for most agencies' signal volume. Scaling up later takes about an hour on ColdRelay, and with 100-150 mailboxes supported per domain, growth rarely requires new domains.