Filling a Cohort, Run Through Smartlead
If you sell a cohort-based program — a 12-week group program, a quarterly mastermind, a leadership intensive with a fixed start date — your outbound doesn't run at a steady hum. It runs in waves. Six weeks of quiet list-building, then a compressed enrollment window where every day of sending matters, then nothing until the next cohort. That rhythm is the opposite of the always-on, drip-style outreach most cold email advice assumes.
Smartlead is built for exactly this kind of campaign-driven sending: wave campaigns with mailbox rotation, spintax to keep higher-volume sends sounding human, and a master inbox to triage replies when enrollment week gets loud. ColdRelay is the infrastructure underneath — the secondary domains, mailboxes, and dedicated IPs Smartlead actually sends from. This guide covers how to wire the two together around a launch calendar, not a perpetual sequence.
Why Run Smartlead on ColdRelay Infrastructure
Smartlead is a sending and sequencing platform — it sends from whatever mailboxes you connect to it. It doesn't provision the domains or guarantee the deliverability of the mailboxes themselves; that's the infrastructure layer's job.
For launch-driven coaches, the infrastructure timing matters as much as the infrastructure quality. A cohort launch can't wait on a multi-week domain warmup — if your start date is six weeks out, your sending capacity has to be real on day one of the enrollment push. ColdRelay mailboxes provision on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC pre-configured, and 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). You hit 95%+ inbox placement during the window when it actually counts.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Smartlead is the sender on top. You keep Smartlead's campaign scheduling, mailbox rotation, and master inbox — you just give it mailboxes built to land, provisioned on your launch calendar instead of someone else's.
Visit Smartlead →Connecting ColdRelay Mailboxes to Smartlead Before a Launch
Provision mailboxes 6 weeks before cohort start
Work backwards from your start date: enrollment closes the week before, the outreach wave runs the 4-5 weeks before that, so infrastructure goes live at T-minus-6. Pick a secondary domain themed to the program rather than just your name — if the program is The Operator Accelerator, something like operatoraccelerator.io. ColdRelay supports 100-150 mailboxes per domain; a coach filling a 20-30 seat cohort typically provisions 25-50 mailboxes, all live on isolated Azure tenants with dedicated IPs in about an hour.
Bulk-import the mailboxes into Smartlead
Export the mailbox CSV with SMTP/IMAP credentials from the ColdRelay dashboard, then in Smartlead go to Email Accounts and use the bulk CSV import. All 25-50 mailboxes connect in one upload, each as its own sending account, ready for campaign-level rotation.
Cap each mailbox at 2 outbound/day and skip double-warmup
In each account's settings, set the daily campaign limit to 2 outbound emails to mirror ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup. ColdRelay's warmup runs continuously on its side, so leave Smartlead's warmup off and spend the full Smartlead budget on enrollment outreach.
Build the wave as stacked campaigns, not one drip
Create separate Smartlead campaigns for each segment of your list (see the playbook below) and attach the full mailbox pool to each — Smartlead's campaign-level mailbox rotation spreads sends across every account so no single mailbox carries the launch. Schedule the campaigns to open in sequence across the enrollment window: warm segments first, cold segments behind them.
Write spintax variants before the window opens
At 50-100 sends/day toward one program, identical copy starts looking like a blast — to prospects and to filters. Use Smartlead's spintax support to write 3-4 rotating variants of your opener, your proof line, and your CTA before launch week, so every send reads like a one-off note even at full wave volume. Once the window opens you won't have time to write; you'll be in the inbox.
The Cohort-Launch Smartlead Playbook
Segment the list by warmth, not just fit
A launch list has three temperatures: people who know you (past discovery calls, webinar attendees, lapsed clients), people one degree away (referral names, community members), and true cold. Run each as its own Smartlead campaign with copy matched to the relationship — a warm 'doors open for the spring cohort' note reads insulting as a cold pitch, and a cold intro wastes a warm lead. Same ColdRelay mailbox pool underneath, three very different conversations on top.
Anchor every email to the cohort date
A fixed start date is the one honest deadline in cold email — use it. Sequence your Smartlead steps around the calendar: 'spring cohort opens in 3 weeks' early in the wave, 'enrollment closes Friday, 4 seats left' at the end. Real scarcity converts where manufactured urgency gets deleted, and it only works if the wave timing and the copy agree.
Triage the master inbox like enrollment depends on it
During launch week, replies arrive faster than you can give each one a considered answer. Work Smartlead's master inbox in two passes: a morning triage that sorts replies into now (asked about price, dates, or fit — answer within the hour), soon (interested but vague — same day), and next cohort (timing objections — tag and park). A hot reply that waits two days during a closing window is a lost seat, and the parked list becomes the warm segment of your next launch.
Let the infrastructure go quiet between cohorts — on purpose
Between launches you don't need 50 mailboxes' worth of outbound, and forcing volume to 'keep things active' just burns your list. Drop to a handful of mailboxes running a light nurture wave to the next-cohort tags while ColdRelay's continuous warmup keeps every mailbox healthy inside the standard 4/day budget (2 outbound + 2 warmup). When the next launch window opens, the full pool is warm and ready — no re-ramp, no rebuilding.
Typical Cohort-Launch Benchmarks (Smartlead + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate during launch window | 3-7% | Warm and one-degree segments pull the average up; true cold runs lower |
| Mailboxes per launch | 25-50 | 50-100 outbound sends/day at 2 outbound per mailbox (4/day total, 2 outbound + 2 warmup) |
| Outreach window before cohort start | 4-6 weeks | Provision at T-minus-6; close enrollment the week before kickoff |
| Time from provisioning to first send | Same day | ~60 minutes to provision, no warmup waiting period before sending |
What It Costs: Smartlead + 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 because cohort sending is seasonal, a 25-50 mailbox pool stays a small line item next to a single program seat.
Smartlead is billed separately on its own subscription for campaign scheduling, mailbox rotation, spintax, and the master inbox — priced per its current plans.
Infrastructure cost scales with mailbox count; Smartlead's cost scales with plan features. One full cohort seat typically covers the entire stack for a year — one bill for sending capacity, one for the sending software.
| 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; Smartlead handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Does ColdRelay replace Smartlead?
No. They do different jobs and stack together. Smartlead handles the campaign layer — wave scheduling, mailbox rotation, spintax, and reply triage in the master inbox. ColdRelay provides the layer underneath: the secondary domains, mailboxes, and dedicated IPs Smartlead sends from. Every setup in this guide uses both.
Can I really provision sending infrastructure 6 weeks before a launch and be ready in time?
Yes — that's the point of the timeline. ColdRelay mailboxes go live in about an hour with SPF, DKIM, and DMARC pre-configured, and there's no warmup waiting period: warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup). Provisioning at T-minus-6 actually leaves you slack; the constraint is writing your segments and spintax variants, not the infrastructure.
How many mailboxes do I need to fill a 20-30 person cohort?
Most cohort coaches run 25-50 mailboxes per launch. At 2 outbound sends/day per mailbox, that's 50-100 sends/day — enough to work a 1,500-3,000 person launch list through a multi-step sequence inside a 4-5 week window. If your list is bigger or your window shorter, add mailboxes on ColdRelay; a single domain supports 100-150 of them.
What do I do with the mailboxes between cohorts?
Keep them — don't deprovision and rebuild every launch. ColdRelay's continuous warmup keeps each mailbox healthy within the standard 4/day budget even when your outbound drops to a trickle, so the pool stays ready. Many coaches run a light between-cohort nurture to prospects tagged 'next cohort' in Smartlead, which turns last launch's timing objections into this launch's warm segment.