From Founder Instinct to a Repeatable Motion
There's a moment after the seed round when outbound stops being something the founder does by feel and becomes something the company has to do on purpose. You've made your first growth hire, the board wants pipeline numbers instead of anecdotes, and the loose collection of campaigns that found your first customers needs to become a system someone else can run.
Smartlead is built for that transition: campaign-level mailbox rotation, a master inbox the new hire can own, spintax for scaling personalization, and an API with webhooks that pushes every send, open, and reply into your CRM. What it doesn't supply is the sending infrastructure underneath — the secondary domains, mailboxes, and dedicated IPs the system runs on. That's ColdRelay's half. This guide covers wiring the two together so the motion you're building is documented, measurable, and ready to scale with your pipeline targets.
Why Run Smartlead on ColdRelay Infrastructure
Smartlead is a sending and sequencing platform — it orchestrates campaigns across whatever mailboxes you connect to it. It doesn't provision domains or determine whether those mailboxes land in the inbox; that's the job of the infrastructure layer beneath it.
For a startup formalizing its outbound motion, that layer is exactly where ad-hoc setups break. Mailboxes the founder spun up by hand have inconsistent DNS, unknown reputation history, and no clear path to doubling capacity when the board signs off on a bigger pipeline number. ColdRelay replaces that with mailboxes on secondary domains, provisioned on isolated Azure tenants with dedicated IPs, SPF, DKIM, and DMARC pre-configured — live in about an hour. There's no warmup waiting period before sending, because warmup runs continuously as part of each mailbox's daily budget of 4 sends — 2 outbound + 2 warmup.
The pairing is additive, not competitive: ColdRelay is the infrastructure layer, Smartlead is the sending and sequencing layer on top. When your growth hire writes the outbound playbook doc, the infrastructure section is one line — and capacity planning becomes arithmetic instead of archaeology.
Visit Smartlead →Connecting ColdRelay Mailboxes to Smartlead
Size the mailbox pool from your pipeline target, then provision
Work backwards: if the board plan needs roughly 200 outbound sends a day, that's 100 mailboxes at 2 outbound sends each (4 sends/day total per mailbox — 2 outbound + 2 warmup). ColdRelay supports 100-150 mailboxes per domain, so a 100-mailbox pool fits on a single secondary domain with headroom. Provisioning on isolated Azure tenants with dedicated IPs takes about an hour, DNS already configured.
Export credentials and bulk-import under Email Accounts
Export the mailbox list with SMTP/IMAP credentials from the ColdRelay dashboard as a CSV, then use Smartlead's bulk CSV import under Email Accounts to connect the whole pool in one upload. No per-account manual entry — which matters when the person doing it is a one-week-old hire, not the founder who knows where everything lives.
Configure campaign-level mailbox rotation
Attach the full mailbox pool to each campaign and let Smartlead's campaign-level rotation distribute sends across it. Set each account's daily campaign limit to 2 outbound emails to mirror the ColdRelay budget, and skip Smartlead's own warmup for these accounts — ColdRelay's continuous warmup already covers it within the 4/day allocation.
Encode the founder's voice with spintax
Take the emails that actually booked your first customers and turn them into Smartlead templates with spintax variations on openers, proof points, and CTAs. This is how the founder's instinct survives the handoff: the new hire ships campaigns that sound like the messages that worked, with enough variation to keep them from looking machine-stamped.
Wire webhooks into the CRM before the first campaign ships
Use Smartlead's API and webhooks to push sends, opens, replies, and bounces into your CRM from day one, tagged by campaign. When a closed deal traces back to a specific sequence, the board update writes itself — cold email stops being the channel you believe in and becomes the channel you can prove.
The Post-Seed Smartlead Playbook
Write the playbook doc before the founder steps back
Document what the founder did by feel — target accounts, the offer framing that got replies, follow-up timing — as Smartlead campaign templates and a one-page runbook. The goal of this stage isn't more volume; it's making the motion survive a personnel change.
Use sub-accounts to split proven from experimental
Smartlead's sub-account structure isn't just for agencies. Run the proven motion in one sub-account the growth hire owns and protects, and new experiments in another — so a messaging test that flops never muddies the metrics on the campaigns paying for the hire's salary.
Report attribution, not activity
A board doesn't care how many emails went out; it cares what pipeline came back. Pipe Smartlead webhook events into the CRM and report meetings and revenue by campaign. The startups that keep outbound budget through the Series A are the ones that can show the channel's math.
Pre-plan the capacity curve
Don't scale mailboxes reactively. Map quarters to send volume: at 4 sends/day per mailbox (2 outbound + 2 warmup), each pipeline tier on the plan implies a mailbox count. Because ColdRelay provisions in about an hour and supports 100-150 mailboxes per domain, capacity additions are a calendar entry, not a project.
Typical Post-Seed Startup Benchmarks (Smartlead + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate | 2-6% | Documented founder-tested messaging holds up well through the handoff to a growth hire |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Mailbox pool at this stage | 75-150 | 150-300 outbound sends/day; fits on 1-2 ColdRelay domains at 100-150 mailboxes each |
| Time for a new hire to ship their first campaign | Under a week | ~60 minutes to provision on ColdRelay, bulk CSV import into Smartlead, templates from the playbook doc |
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, dedicated IPs, and isolated Azure tenants are included — so the cost line in your board model is a clean function of mailbox count.
Smartlead is billed separately on its own subscription for campaigns, rotation, the master inbox, and API access — priced per its current plans.
Two predictable line items: software that's roughly flat, infrastructure that scales with the capacity plan you set. That makes outbound one of the few channels where next quarter's cost is knowable before the quarter starts — exactly what a post-seed budget review wants to see.
| 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
Is ColdRelay an alternative to Smartlead?
No — they're complementary layers of one stack. Smartlead handles campaigns, mailbox rotation, the master inbox, and reporting via API and webhooks. ColdRelay provides the secondary domains, mailboxes, and dedicated IPs Smartlead sends from. You use both: ColdRelay as the infrastructure layer, Smartlead as the sending layer on top.
We've been sending from mailboxes the founder set up — do we have to start over?
You don't have to discard anything, but most teams at this stage migrate to a clean pool. Provisioning fresh mailboxes on ColdRelay takes about an hour, arrives with SPF, DKIM, and DMARC configured, and gives you known-good reputation from day one — with no warmup waiting period, since warmup runs continuously inside each mailbox's 4 sends/day budget (2 outbound + 2 warmup). Run the old accounts down in parallel if they're still performing.
How do we prove cold email ROI to our board?
Wire Smartlead's webhooks into your CRM so every send, open, and reply is tagged by campaign, then report meetings booked and pipeline created per campaign rather than raw send counts. With infrastructure cost a simple function of mailbox count on ColdRelay, you can put a real cost-per-meeting number next to paid channels in the board deck.
How should we plan mailbox capacity against pipeline targets?
Work the math backwards from the plan. Each mailbox contributes 2 outbound sends/day (4/day total including 2 warmup sends), so a target of 200 sends/day means 100 mailboxes. ColdRelay supports 100-150 mailboxes per domain and provisions in about an hour, so you can step capacity up quarter by quarter as targets rise instead of over-buying upfront.