Finding the Coachable Moment, Run Through Apollo
Most coaching niches aren't really about a job title — they're about a career moment. An executive coach for first-time VPs isn't selling to 'VPs of Sales'; they're selling to the person who was a director eight weeks ago and is now staring at their first board deck. A founder coach sells to the moment after the seed round closes, not to 'founders' in general. The hard part of coach outbound has never been writing the email — it's finding the two hundred people who are in that exact moment right now.
That's what makes Apollo a different kind of pairing for coaches. Apollo is a B2B contact database with title, seniority, company-stage, and job-change filters — a search engine for career moments — plus sequences to reach the people it finds. ColdRelay is the infrastructure underneath: the secondary domains, mailboxes, and dedicated IPs Apollo actually sends from. This guide covers how to wire the two together so your targeting precision isn't wasted on emails that land in spam.
Why Run Apollo on ColdRelay Infrastructure
Apollo's value to a coach is upstream of sending: the database, the filters, the saved personas, the job-change signals. Its sequences then send from whatever mailboxes you link under Settings → Mailboxes — Apollo doesn't provision domains or guarantee the deliverability of the mailboxes themselves. That's the infrastructure layer's job.
And for moment-based targeting, deliverability is the whole bet. A job-change signal has a shelf life — the window where a 'congrats on the new role' email reads as timely rather than stale is measured in weeks. If your perfectly timed email sits in a spam folder, the moment passes and the prospect is gone until their next promotion. ColdRelay mailboxes run on isolated Azure tenants with dedicated IPs, fully DNS-configured (SPF, DKIM, DMARC), live in about an hour, with 95%+ inbox placement — so the email arrives while the signal is still warm.
The pairing is additive, not competitive: Apollo is the targeting and sequencing layer, ColdRelay is the infrastructure it sends from. You keep Apollo's database, saved searches, and multi-channel sequences — you just give them mailboxes built to land inside the window that matters.
Visit Apollo →Connecting ColdRelay Mailboxes to Apollo
Provision mailboxes on ColdRelay
Pick a secondary domain adjacent to your coaching brand and provision your sending pool — ColdRelay supports 100-150 mailboxes per domain, though signal-driven coaches rarely need more than 10-25, because the list is only ever as big as the number of people currently in the moment. Everything goes live 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 via SMTP/IMAP using the credentials from the ColdRelay dashboard export. Each mailbox connects as its own linked account, so Apollo's sequences can rotate sends across the pool.
Set per-mailbox daily send limits to 2
In each linked mailbox's settings, set Apollo's per-mailbox daily send limit to 2 outbound emails. That mirrors ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup. Warmup runs continuously on ColdRelay's side as part of that budget, so there's no waiting period before your first sequence and nothing extra to configure in Apollo.
Build a saved persona around the career moment
This is where Apollo earns its place in a coach's stack. In People Search, stack the filters that define your coachable moment — for a first-time-VP coach: title contains VP, seniority is VP-level, company headcount 50-500, plus the job-change signal filtered to changes in the last 90 days. Save it as a persona and save the search; Apollo keeps surfacing fresh matches as new people step into the role, turning your niche definition into a self-refilling list.
Create the sequence and add contacts from the saved search
Build an Apollo sequence with 3-4 email steps and an optional LinkedIn step between them — at coaching volumes a profile view or connection request after email one makes the name familiar before email two arrives. Pull contacts in from the saved search on a weekly cadence rather than one big dump: the entire point of signal-based targeting is sending to this week's new VPs this week.
The Career-Moment Apollo Playbook
Define the moment, not the title
A persona that just says 'VP of Sales' targets people who've held the job for nine years and need nothing from you. The coachable version lives in the filter combination: VP-level seniority plus a job change inside 90 days plus a growth-stage company where they're likely the first person to hold the title. Spend your Apollo time engineering that intersection — every filter you add is qualification you don't have to do by hand later.
Time the send to the struggle, not the announcement
Day one of a new role, the inbox is full of congratulations and the new VP still thinks they've got this. The coachable window opens later — somewhere in the 30-90 day stretch when the first hire decision goes sideways or the first board meeting looms. Filter Apollo's job-change signal to changes 1-3 months old rather than this week's promotions, and you arrive precisely when 'I might need help with this' has become a real thought.
Congratulate the role, then name the gap
'Congrats on the new role' alone is what every recruiter and SDR in their inbox is saying. The coach version uses the congratulations as a doorway to the specific hard part: 'Congrats on stepping into the VP seat at a company growing this fast — most first-time VPs tell me the jump from running deals to running people is bigger than anyone warned them.' You're not flattering the promotion; you're showing you know what it costs. That line only works because Apollo's filters guaranteed everyone receiving it is actually in that seat.
Use Apollo's call and LinkedIn steps as presence, not pressure
Apollo sequences support email, call, and LinkedIn steps — but a coach cold-calling a new VP reads like a vendor. Use the LinkedIn step as a soft touch (a profile view or a connection note after the first email) so your face and credentials are familiar by email two, and keep the call step as a manual task you only trigger after a positive reply. The sequence's job is to make the eventual conversation feel inevitable, not extracted.
Typical Career-Moment Outbound Benchmarks (Apollo + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate on job-change-triggered sends | 5-10% | Signal-timed outreach to people in-moment runs well above static-list cold email |
| Mailboxes per coach | 10-25 | 20-50 outbound sends/day at 2 outbound per mailbox (4/day total, 2 outbound + 2 warmup) |
| Outreach window after a role change | 30-90 days | Early enough that help is welcome, late enough that the need is felt |
| Fresh matches per saved search | 20-60/week | Varies by niche breadth; the saved search refills the list as people change roles |
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 at signal-driven volumes of 10-25 mailboxes, the infrastructure line stays small.
Apollo is billed separately on its own subscription for the contact database, filters, signals, and sequences — priced per its current plans, with database access typically the part worth paying up for.
Infrastructure cost scales with mailbox count; Apollo's cost scales with plan tier and credits. For a coach, the combined stack is the cost of finding and reaching every person entering your niche's coachable moment — typically a fraction of one client engagement.
| 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 and this whole setup uses both. Apollo is the targeting and sequencing layer: the contact database, the title and job-change filters, the saved personas, the sequences. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs those sequences actually send from. Apollo finds the person in the coachable moment; ColdRelay makes sure the email reaches their inbox.
Can I just send from the mailbox Apollo links to my own domain?
You can, but you shouldn't — your primary domain carries your client threads and referral conversations, and cold sending puts that reputation at risk. Link ColdRelay mailboxes on secondary domains under Apollo's Settings → Mailboxes instead. Cold outreach runs on isolated Azure tenants with dedicated IPs, completely walled off from the domain your coaching business actually depends on.
How fresh does a job-change signal need to be before it's too stale to use?
For coaching outreach, 30-90 days after the role change is the sweet spot — past the congratulations flood, inside the stretch where the new role's hard parts have become real. Beyond about six months the 'new role' framing stops landing and you're back to ordinary cold email. Filter Apollo's job-change signal to that 1-3 month band and pull contacts into your sequence weekly so nobody enters it stale.
Do I need to wait through a warmup period before my first Apollo sequence?
No. ColdRelay mailboxes warm continuously as part of the standard send budget — 4 sends/day per mailbox, split 2 outbound + 2 warmup — so there's no waiting period before sending. Provision in about an hour, link the mailboxes in Apollo, cap each at 2 outbound/day, and your first sequence can go out the same day. Don't layer a separate warmup tool on top.