Agency Prospecting on Budget Signals, Run Through Apollo
Most agency cold email fails for a reason that has nothing to do with copy: the prospect has no open budget the week the email arrives. A company that just closed a Series A, or just hired its first VP of Marketing, is in a completely different buying state than the same company six months earlier — and Apollo is the rare prospecting database that lets you filter for exactly those moments. Funding events, new leadership, job changes: the signals that precede an agency engagement are all queryable.
The stack splits into two layers. Apollo is where the targeting and sequencing live — the B2B database, signal filters, saved personas, and multichannel sequences. ColdRelay is the layer underneath: the secondary domains, mailboxes, and dedicated IPs those sequences actually send from. This guide covers how an agency wires the two together to run a signal-based motion — where the trigger for every email is a budget event, not a list refresh.
Why Signal-Based Prospecting Needs Its Own Infrastructure Layer
Apollo's edge for agencies is timing. Its database lets you filter companies by recent funding rounds, surface accounts that just hired into a marketing leadership role, and track job changes among people who bought from agencies before. But a signal has a shelf life — a funding announcement is a warm doorway for weeks, not quarters — and Apollo doesn't provision the mailboxes that have to be ready the day the signal fires. It links and sends from whatever mailboxes you connect; domains, DNS, and IP reputation are the infrastructure layer's job.
That's where ColdRelay fits. You provision mailboxes on isolated Azure tenants with dedicated IPs, with DNS (SPF, DKIM, DMARC) pre-configured, ready in about an hour — and critically for a timing-driven motion, there's no warmup waiting period before sending. Warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup), so infrastructure is never the reason you missed a signal's window. Your agency's own domain — the one carrying proposals and client threads — stays completely out of the blast radius.
The pairing is additive, not competitive: ColdRelay is the infrastructure layer, Apollo is the prospecting and sequencing layer on top. Apollo tells you who just got budget; ColdRelay makes sure the email about it actually lands.
Visit Apollo →Wiring ColdRelay Mailboxes Into Apollo's Signal Workflow
Provision the sending pool on ColdRelay
Order secondary domains adjacent to your agency's name — never the primary domain your clients email. ColdRelay supports 100-150 mailboxes per domain, so a typical signal-based pool of 20-60 mailboxes fits on one or two domains. 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 under Settings → Mailboxes
In Apollo, go to Settings → Mailboxes and connect each ColdRelay mailbox via SMTP/IMAP using the credentials exported from the ColdRelay dashboard. Once linked, Apollo can rotate sequence sends across the full pool instead of leaning on one or two accounts.
Set per-mailbox daily send limits to 2
Use Apollo's per-mailbox daily send limit to cap each linked mailbox at 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. Don't allocate that warmup budget to extra outbound; the split is what keeps placement at 95%+.
Build saved searches around budget signals, one per service line
In Apollo, create a saved persona and saved search for each service line, keyed to the signal that opens budget for it: companies with a funding round in the last 90 days for brand and web work, accounts that hired a VP or Head of Marketing in the last 60 days for content and demand gen retainers, leadership changes at companies in your strongest vertical for positioning work. Saved searches refresh as new companies trip the filters — your prospect list rebuilds itself daily.
Create signal-specific sequences with email, call, and LinkedIn steps
Build one Apollo sequence per saved search, with the signal written into step one — the email opens on the funding round or the new hire, not on your agency. Use Apollo's multichannel steps to compound the touch: an email referencing the announcement, a LinkedIn connection a day later, a call task for anyone who opens twice. New matches from the saved search flow into the matching sequence, and sends rotate across the ColdRelay pool.
The Signal-Based Agency Playbook on Apollo
Treat a funding round as a budget event, not a news item
A company that just raised has new money, new growth targets, and usually no agency bench to hit them with — and Apollo's funding filters surface these companies the week the round is announced. The pitch isn't congratulations; it's the specific thing freshly funded companies at that stage need from an agency in your lane: a site that matches the new positioning, a content engine before the next raise. Reference the round in one clause and spend the rest of the email on what comes next for them.
Catch the new VP of Marketing inside their first 90 days
A newly hired marketing leader is the single best agency buyer in B2B: they have a mandate to show results fast, an inherited team with gaps, and a honeymoon window to bring in outside help. Apollo's job-change and new-hire filters find them; your sequence should speak to the first-90-days agenda — quick wins, an audit framing, a project scoped to land before their first board review. Six months later the same person is a cold prospect again; the saved search keeps you arriving on time.
Map each service line to its own signal, persona, and saved search
Generic agency outreach dies because every service is pitched to everyone. In Apollo, give each service line its own triangle: a signal that opens budget for it, a persona who owns that budget, and a saved search that joins the two. Funding round → founder or CEO → brand and web. New marketing leader → that hire directly → retainers and demand gen. Leadership change in your best vertical → the incoming executive → repositioning work. Each triangle gets its own sequence, so reply data tells you which signal-service pairing actually pulls.
Size the daily signal flow to the pool, not the other way around
Signal-based prospecting is a drip, not a blast — your saved searches might surface 20-50 genuinely qualified new companies a day across all service lines, not thousands. That cadence fits the infrastructure math cleanly: each ColdRelay mailbox contributes 2 outbound sends/day (of its 4/day total, the other 2 being warmup), so a 30-mailbox pool covers 60 signal-triggered sends a day with sequencing depth to spare. If your searches start surfacing more signal than the pool can reach while the window is fresh, that's the cue to add mailboxes — demand-driven scaling instead of speculative volume.
Typical Signal-Based Agency Benchmarks (Apollo + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate on signal-timed outreach | 5-9% | Emails referencing a funding round or new hire within its window; the same offer on a static list typically runs 2-3% |
| Usable window after a budget signal | 30-90 days | Funding rounds stay warm roughly a quarter; a new marketing hire's openness to agencies peaks inside the first 90 days |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup, warmup running continuously |
| Time from signal fired to first email out | Same day | Saved searches surface new matches daily; infrastructure provisions in ~60 minutes, so the pool is never the bottleneck |
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 because a signal-based motion runs on daily drip volume rather than mass blasts, agencies typically start with a smaller pool than list-blasting shops and grow it only when signal flow outpaces capacity.
Apollo is billed separately on its own subscription, covering the B2B database, signal and intent filters, saved personas and searches, and multichannel sequences — priced per its current plans.
The combined cost maps neatly to the motion: Apollo's subscription buys the signals and the sequencing, ColdRelay's per-mailbox pricing buys exactly the sending capacity your daily signal flow needs. One engagement won from a well-timed funding-round email typically covers both line items for the year.
| 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 prospecting and sequencing layer: the contact database, funding and job-change filters, saved personas, and email-call-LinkedIn sequences. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs that Apollo's sequences send from. An agency running a signal-based motion uses both — Apollo to find the moment, ColdRelay to make sure the email about it lands.
Why not just send from the mailboxes we already have connected in Apollo?
Because those are usually mailboxes on your agency's primary domain — the one carrying proposals, invoices, and live client threads. Cold outreach volume puts that domain's reputation at risk, and a deliverability problem there hurts every client relationship at once. ColdRelay provisions secondary domains on isolated Azure tenants with dedicated IPs, so the signal-based motion runs at full speed while your primary domain stays untouched. You link the ColdRelay mailboxes under Settings → Mailboxes in Apollo and sequence from those instead.
How many mailboxes does a signal-based motion actually need?
Work backwards from your daily signal flow, not from a volume target. Each mailbox contributes 2 outbound sends/day of its 4/day total (the other 2 are warmup), so if your Apollo saved searches surface 25-30 qualified new companies a day across your service lines, a 30-40 mailbox pool covers first touches plus follow-up steps comfortably. That's a deliberately smaller starting pool than blast-style outbound — the signals do the qualifying, so you need precision capacity, not raw tonnage. Scale when fresh signals start aging out before you can reach them.
A funding round just hit our saved search — do new mailboxes need warmup before we can act on it?
No waiting period. ColdRelay mailboxes provision in about an hour with SPF, DKIM, and DMARC pre-configured, and warmup runs continuously as part of the standard budget — 4 sends/day per mailbox, split 2 outbound + 2 warmup — rather than as an upfront quarantine. That matters for a timing-driven motion: a signal with a 30-90 day shelf life shouldn't lose its first weeks to infrastructure. Set Apollo's per-mailbox daily limit to the 2 outbound sends and the pool is ready the same day it's ordered.