Freelance Outbound, Run Through Apollo
The quiet killer of most freelance outreach isn't the copy — it's the list. A solo designer or writer can't justify an enterprise data subscription, so they end up scraping directories, guessing email patterns, and emailing people who changed jobs a year ago. At agency volume, bad data is a tax; at 10-20 sends a day, it's fatal, because every wasted send is a meaningful slice of your entire pipeline.
Apollo changes that math. Its free and low-cost tiers put a real B2B contact database — with title filters, industry filters, and buying signals like active job postings — in the hands of someone spending freelancer money, plus sequences to send from. ColdRelay is the infrastructure underneath: the secondary domain, the small mailbox pool, and the dedicated IPs that Apollo's sequences actually send from. This guide covers wiring the two together so that the few emails you send each day go to the right person, at the right company, in the right week.
Why Run Apollo on ColdRelay Infrastructure
Apollo solves the half of outbound that solo operators usually can't afford to solve: knowing who to email. Saved personas turn 'marketing managers at 10-50 person ecommerce brands' into a reusable filter, saved searches resurface fresh matches every week, and signal filters surface companies that just posted job openings — which, for a freelancer, is a flashing sign that budget and urgency exist right now. Its sequences then send email, call, and LinkedIn steps from whatever mailboxes you link to it.
What Apollo doesn't do is provision those mailboxes or guarantee their deliverability — it sends from the accounts you connect under Settings → Mailboxes, and the quality of those accounts is the infrastructure layer's job. That's where ColdRelay fits. A freelancer needs a modest pool — typically 5-10 mailboxes on one secondary domain (ColdRelay supports 100-150 mailboxes per domain, so headroom is never the constraint). They provision on isolated Azure tenants with dedicated IPs, fully DNS-configured (SPF, DKIM, DMARC), ready in about an hour, with no warmup waiting period — warmup runs continuously as part of each mailbox's daily budget.
The pairing is additive, not competitive: Apollo is the data and sequencing layer, ColdRelay is the infrastructure it sends from. Together they fix both ends of the small-volume problem — the data tells you which 20 people deserve today's sends, and the infrastructure makes sure those 20 emails actually reach an inbox.
Visit Apollo →Connecting ColdRelay Mailboxes to Apollo
Provision a small mailbox pool on ColdRelay
Pick one secondary domain adjacent to your brand — if clients know you at janedoe.dev, something like janedoework.com keeps the connection obvious without exposing the address your contracts run through. Order 5-10 mailboxes; ColdRelay supports 100-150 per domain, but a signal-driven solo pipeline doesn't need more. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC already configured.
Link the mailboxes in Apollo under Settings → Mailboxes
From the ColdRelay dashboard, grab each mailbox's SMTP/IMAP credentials and add them in Apollo under Settings → Mailboxes. With a 5-10 mailbox pool this is a few minutes of work, and once linked, Apollo's sequences can rotate sends across all of them.
Set per-mailbox daily send limits to match the budget
Apollo lets you cap sending per linked mailbox — set each one's daily send limit to 2 outbound emails to mirror ColdRelay's per-mailbox budget of 4 sends/day total, split 2 outbound + 2 warmup. ColdRelay runs the warmup half continuously in the background, so Apollo only ever needs to handle the outbound half.
Build a saved persona and a signal-filtered search
In Apollo's search, define your ideal client with title and industry filters — say, heads of marketing at 11-50 person B2B SaaS companies — and save it as a persona. Then layer on a buying signal: filter for companies with active job postings in your discipline. A company hiring for a content team needs a writer this month, not someday; save the search so the freshest matches are waiting every time you open it.
Build a sequence and launch
Create an Apollo sequence with mixed steps: a signal-referencing cold email, a LinkedIn touch a few days later, a short follow-up email, and an optional call task for the warmest threads. Enroll contacts from your saved search, attach your linked ColdRelay mailboxes, and launch. With 5 mailboxes you have 10 outbound sends/day — exactly enough to cover the genuinely signal-qualified prospects Apollo surfaces each day.
The Freelancer Apollo Playbook
Save the persona once, prospect in minutes forever
The biggest hidden cost of solo outbound isn't sending — it's the hours lost rebuilding lists from scratch every time a project ends. Build your title and industry filters once, save them as an Apollo persona, and let saved searches surface new matches on their own. List-building collapses from an afternoon of scraping into a ten-minute weekly review, which is the difference between outreach that survives busy months and outreach that doesn't.
Treat hiring signals as project triggers
A job posting is the loudest buying signal a freelancer can get. A company hiring a content marketer has a content problem today and a 6-8 week empty seat while they recruit — exactly the gap a freelancer fills. Filter your Apollo searches by active job postings in your discipline and lead the email with it: 'Saw you're hiring a content lead — I can carry the editorial calendar while you search, or instead of a full-time hire.' You're not interrupting; you're answering a need they just announced.
At 20 sends a day, every bounce is 5% of your pipeline
Big senders absorb bad data; you can't. One bounce out of 20 daily sends is 5% of your entire day's output, and a handful of them starts denting the domain reputation your whole pipeline rides on. So work a small-batch habit: pull contacts from Apollo in batches of 50, check the email confidence indicators, drop catch-all addresses unless the signal is exceptional, and run the batch through a verifier before enrollment. Twenty verified, signal-qualified contacts beat two hundred raw exports every single week.
Let the email carry the ask — use the other steps for presence
Apollo sequences support email, call, and LinkedIn steps, and the temptation is to fire everything at once. At solo scale, restraint wins: the cold email makes the one concrete ask, a LinkedIn connection a few days later puts a face and portfolio behind the name, and a call task exists only for prospects who replied warm. Three light touches across two weeks feels like a professional who noticed their hiring post — five aggressive ones feels like a bot, and you don't have the volume to burn goodwill.
Typical Freelancer Outbound Benchmarks (Apollo + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate | 3-8% | Signal-timed outreach to hiring companies out-replies generic persona blasts |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Bounce rate target | Under 2% | Verified small batches and pruned catch-alls — non-negotiable at low volume |
| Time to first campaign | Same day | ~60 minutes to provision on ColdRelay, plus persona 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). At a 5-10 mailbox pool, this stays a small, predictable line item, and DNS, dedicated IPs, and isolated Azure tenants are all included.
Apollo is billed separately on its own plans for the contact database, saved personas and searches, signal filters, and sequences — and its free and entry tiers are generous enough that many freelancers run real pipeline before ever upgrading.
The full stack is one small infrastructure bill plus a database subscription that starts near zero — enterprise-grade contact data and deliverability at a price a solo operator can actually defend on a slow month.
| 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 doing different jobs. Apollo provides the contact database, saved personas, signal filters, and the sequences that send email, call, and LinkedIn steps. ColdRelay provides the underlying domain, mailboxes, and dedicated IPs that those sequences send from. You use them together: Apollo decides who gets the email, ColdRelay makes sure it lands.
Why not just link my regular freelance email to Apollo?
Because that address is your business — your client threads, invoices, and contracts all depend on its reputation, and Apollo will send from whatever mailbox you link under Settings → Mailboxes. ColdRelay puts outbound on a separate secondary domain with dedicated IPs on isolated Azure tenants, so even an underperforming sequence can't touch the inbox your livelihood runs through.
Do I need to warm up the mailboxes before launching my first Apollo sequence?
No waiting period. ColdRelay mailboxes warm continuously — 2 warmup sends/day per mailbox run in the background as part of the 4/day budget (2 outbound + 2 warmup) — so you can link them in Apollo and launch a sequence the same day you provision. Just set each mailbox's daily send limit in Apollo to the 2 outbound sends and leave the warmup half to ColdRelay.
Is Apollo's data accurate enough to rely on at freelancer volume?
It's the strongest database a freelancer can get at this price, but no database is perfect — which matters more at 10-20 sends/day than at 1,000. Work in small verified batches: favor contacts with high email-confidence indicators, skip catch-all addresses unless the buying signal is strong, and verify each batch before enrolling it in a sequence. That habit keeps bounces under 2% and protects the ColdRelay domain reputation every send depends on.