Stack-Intelligence Outbound for IT Services, Run Through Apollo
Most MSP prospecting starts with who a company is — industry, headcount, zip code. Apollo lets you start with what a company runs. Its technographic filters expose the stack behind the firmographics: the firm still on on-prem Exchange, the office running a competitor's RMM agent, the 80-seat company on Microsoft 365 with none of the security add-ons attached. Each of those is not just a contact record — it's a reason to write.
Apollo supplies the intelligence and the sequencing; it doesn't supply the sending infrastructure. The displacement emails those signals justify still need domains, mailboxes, and IPs underneath them — and that's ColdRelay: dedicated mailboxes on isolated Azure tenants with dedicated IPs, provisioned in about an hour. This guide covers wiring the two together and building campaigns where the targeting itself is the personalization: every prospect on the list got there because their stack said they should.
Why Run Apollo on ColdRelay Infrastructure
Apollo bundles three layers an MSP needs — a B2B contact database with title, industry, technographic, and signal filters; saved personas and searches that keep target lists fresh; and sequences that mix email, call, and LinkedIn steps. What it doesn't bundle is the infrastructure layer: Apollo sends from whatever mailboxes you link under Settings → Mailboxes, and it doesn't provision domains or guarantee those mailboxes deliver.
That's where ColdRelay fits. Instead of buying workspace seats and configuring DNS by hand, you order dedicated mailboxes on isolated Azure tenants with dedicated IPs, fully DNS-configured (SPF, DKIM, DMARC) and ready in about an hour. Link them in Apollo and every sequence sends from infrastructure built to land.
The pairing matters most when your targeting is this precise. A technographic search might surface only 120 companies in your market running end-of-life server infrastructure — a list that specific is too valuable to lose 20% of to spam folders. At 95%+ inbox placement, ColdRelay makes sure the email that says "I noticed what you're running" actually arrives at the company you noticed. ColdRelay is the infrastructure, Apollo is the intelligence and sending layer on top — additive, not competitive.
Visit Apollo →Connecting ColdRelay Mailboxes to Apollo
Provision mailboxes on ColdRelay
Pick secondary domains related to but separate from your primary firm domain — client tickets and invoices live on the main one, so it never touches outbound. ColdRelay supports 100-150 mailboxes per domain; stack-intelligence campaigns run narrow and deep, so most firms start with 15-40 mailboxes on one or two domains. 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
In Apollo, go to Settings → Mailboxes and connect each ColdRelay mailbox via SMTP/IMAP using the credentials exported from the ColdRelay dashboard. Each mailbox links as its own sender, so Apollo can distribute sequence emails across the full pool.
Set per-mailbox daily send limits to the ColdRelay budget
In each linked mailbox's settings, cap the daily send limit at 2 outbound emails per day to mirror ColdRelay's per-mailbox budget — 4 sends/day total per mailbox, split 2 outbound + 2 warmup. ColdRelay's warmup runs continuously inside that budget, so there's no separate warmup period before your first sequence and nothing extra to configure in Apollo.
Build saved searches around displacement signals
This is the step that makes the Apollo pairing different. Build a saved search per displacement scenario: companies whose technology filters show aging on-prem infrastructure, accounts running a competitor MSP's toolset, Microsoft 365 shops with no security add-ons detected, and companies with an open sysadmin or IT-support job posting in your service area. Save the matching decision-maker titles as personas so each search refreshes with new matches automatically.
Create one sequence per scenario and launch
In Apollo, build a separate sequence for each saved search — the copy has to match the signal that put the prospect on the list, so one generic sequence defeats the targeting. Mix email steps with call and LinkedIn tasks for the higher-value accounts, enroll each search's contacts into its matching sequence, and let Apollo rotate sends across your ColdRelay mailboxes.
The Stack-Intelligence Apollo Playbook for IT Services
Target stacks, not titles
Every MSP in your market is filtering Apollo by "office manager, 20-200 employees, within 50 miles." Almost none are filtering by what those companies actually run. Build your lists from the technology signal first — end-of-support server OS, on-prem Exchange, a competitor's remote-monitoring agent — and let firmographics narrow second. A 100-company list where every entry has a documented reason to switch outperforms a 1,000-company list of businesses that merely fit a profile, and it spends far less of a finite local TAM.
Treat the sysadmin job posting as a buying trigger
Apollo's hiring signals surface the single best MSP trigger there is: a 30-person company posting for a sysadmin or IT support role. That posting says the pain is real and budgeted — but one hire can't cover patching, security, after-hours response, and vacations. Sequence these companies within days of the posting going live with a direct comparison: the fully-loaded cost of the hire against a managed contract that never calls in sick. You're not interrupting; you're answering a question they're already spending money on.
Write the opener around what the filter found
Stack-intelligence targeting earns you an opener no generic campaign can use: name the situation that put them on the list. "Most firms we talk to still running on-prem Exchange are weighing the migration this year — has that hit your roadmap?" reads like relevance, not surveillance. Two rules keep it working: phrase the signal as a question, because technographic data is probabilistic and being confidently wrong kills the thread; and never name the data source — the prospect should feel understood, not scanned.
Measure scenarios against each other, then feed the winner
Because each displacement scenario runs as its own Apollo sequence, you get something most MSP outbound never produces: a per-signal conversion table. After a quarter you'll know whether end-of-life infrastructure, the co-managed security gap, competitor displacement, or hiring triggers books the most assessments in your market. Retire the weakest scenario, widen the saved search on the strongest, and add ColdRelay mailboxes only when the winning scenario's list outgrows your daily send capacity — growth driven by evidence, not enthusiasm.
Typical Stack-Intelligence Benchmarks (Apollo + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate on signal-targeted sequences | 4-8% | Stack and hiring-signal lists run well above generic firmographic campaigns |
| Hiring-signal sequences vs. cold firmographic lists | 2-3x replies | An open sysadmin posting is budgeted pain; speed to first touch matters |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Time to first sequence | Same day | ~60 minutes to provision, plus saved-search 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). DNS, dedicated IPs, and isolated Azure tenants are included — and because signal-based lists are narrow by design, a 15-40 mailbox footprint covers most stack-intelligence motions.
Apollo is billed separately on its own subscription for the contact database, technographic and signal filters, saved personas, and sequences — priced per its current plans, typically per user with credit allowances.
Infrastructure cost scales with mailbox count; Apollo's cost scales with seats and data credits. The two stack cleanly — one bill for the intelligence and sequencing, one for the sending capacity underneath it — and the narrow-list approach keeps both lean.
| 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 of one stack. Apollo is the intelligence and sending software: the contact database, technographic and hiring-signal filters, saved personas and searches, and sequences with email, call, and LinkedIn steps. ColdRelay is the infrastructure underneath: the secondary domains, dedicated mailboxes, and dedicated IPs that Apollo's email steps actually send from. You link ColdRelay mailboxes under Apollo's Settings → Mailboxes and run both together.
Apollo already includes everything else — why add infrastructure?
Because Apollo sends from the mailboxes you link to it; it doesn't provision domains, configure SPF, DKIM, and DMARC, or isolate your outbound reputation from the domain your clients open tickets on. ColdRelay handles that layer: dedicated mailboxes on isolated Azure tenants with dedicated IPs, ready in about an hour, kept completely separate from your primary firm domain. The more precise your Apollo targeting, the more each send is worth — and the more it matters that it lands.
Are technographic signals reliable enough to build campaigns on?
Reliable enough to target with, not reliable enough to assert with. Technology detection is probabilistic — a company flagged as running on-prem Exchange usually is, but not always. The playbook handles this: use the signal to decide who gets the email, then phrase the signal as a question in the copy rather than a claim. A prospect who's already migrated simply says so; a prospect who hasn't hears the most relevant cold email they'll get this year.
Do I need a warmup period before launching my first Apollo sequence?
No separate warmup period. ColdRelay mailboxes warm continuously — 2 warmup sends/day per mailbox as part of the 4/day total budget, alongside 2 outbound — so you can provision in the morning, link the mailboxes in Apollo, and launch your first displacement sequence the same day. Warmup keeps running in the background for the life of each mailbox.