Freelance Outbound, Run Through Smartlead
There's a version of freelancing that isn't solo at all: two to five independents — say a designer, a developer, and a copywriter — who keep separate clients and separate invoices but band together under one studio name to win bigger work. The collective has a real outbound problem that solo stacks don't solve: everyone needs pipeline, nobody wants to run their own infrastructure, and the studio needs to look like one company in a prospect's inbox, not five people moonlighting.
Smartlead is unusually well-shaped for this. It was built for agencies juggling multiple clients, which means it already has the machinery a collective needs — separate campaigns with their own analytics, campaign-level mailbox rotation off a shared pool, and a master inbox where every reply lands in one place. ColdRelay is the layer underneath: the studio's shared domain, the pooled mailboxes, and the dedicated IPs that all of Smartlead's campaigns actually send from. This guide covers wiring the two together as a multi-member operation on a single shared bill.
Why Run Smartlead on ColdRelay Infrastructure
Smartlead is a sending and sequencing platform — it sends from whatever mailboxes you connect to it. Its agency DNA is what makes it the right pick for a collective: client sub-accounts can keep each member's campaigns and lead lists cleanly partitioned, campaign-level mailbox rotation lets every campaign draw from one shared sending pool, and the master inbox aggregates replies across all of it. What Smartlead doesn't do is provision the domains and mailboxes themselves or guarantee their deliverability — that's the infrastructure layer's job, and for a collective it's the layer worth sharing most.
That's where ColdRelay fits. Instead of each member buying and managing their own mailboxes, the studio provisions one pool — typically 12-20 mailboxes on a single studio-branded domain (ColdRelay supports 100-150 mailboxes per domain, so one domain covers the collective with room to grow). The pool provisions 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: ColdRelay is the shared infrastructure, Smartlead is the campaign layer where each member runs their own service line on top of it. One domain reputation, one infrastructure bill split however the group agrees, and every email a prospect receives says the same studio name.
Visit Smartlead →Connecting a Shared ColdRelay Pool to Smartlead
Provision one studio pool on ColdRelay
Register a domain for the collective's shared brand — if the studio is Northbeam Studio at northbeam.studio, something like northbeamstudio.com or trynorthbeam.com keeps it coherent, with every member sending as firstname@ that domain. Provision 12-20 mailboxes on that one domain; ColdRelay supports 100-150 mailboxes per domain, so even a five-member collective fits on a single domain with headroom. Everything lands on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC already configured. One member owns the ColdRelay account; the cost is a line item the group splits.
Bulk-import the pool under Email Accounts in Smartlead
Export the mailbox credentials from the ColdRelay dashboard as a CSV, then in Smartlead go to Email Accounts and bulk-import the whole pool via SMTP/IMAP in one pass. Every member's campaigns will draw from this same set of accounts, so it only needs to be done once, by whoever administers the Smartlead workspace.
Create one campaign per member's service line
Each member gets their own Smartlead campaign — 'brand identity projects' for the designer, 'Webflow builds' for the developer, 'conversion copy retainers' for the writer. If the collective wants harder separation of lead lists and stats, give each member a Smartlead client sub-account instead and build their campaigns inside it. Either way, use campaign-level mailbox rotation to attach the shared ColdRelay pool to every campaign — capacity is communal, targeting and copy are not.
Set pool-wide limits the whole group respects
Cap each mailbox at 2 outbound emails per day in Smartlead — that mirrors ColdRelay's per-mailbox budget of 4 sends/day total, split 2 outbound + 2 warmup, with the warmup half running continuously on ColdRelay's side. The catch in a shared pool: the 2 outbound sends per mailbox are a group ceiling, not a per-member one. A 16-mailbox pool gives the collective 32 outbound sends/day in total, so agree up front how that capacity divides across campaigns and set each campaign's daily volume accordingly.
Launch, then run the master inbox as a shared switchboard
Once campaigns are live, every reply — across all members' campaigns — lands in Smartlead's master inbox. Set a simple claiming rule: replies belong to the member whose campaign generated them, and each member checks the master inbox daily to claim and answer theirs. For a collective that wants a shared scoreboard, Smartlead's API and webhooks can push campaign stats into a group dashboard or Slack channel so everyone sees whose offer is pulling its weight.
The Freelancer Collective Smartlead Playbook
Sell the studio, sign the specialist
Every email sends from the shared studio domain and opens with the studio's positioning — that's what gets a two-person prospect team to take a five-figure project seriously. But the signature and the CTA belong to the individual member whose campaign it is: 'I lead the Webflow side at Northbeam.' Prospects buy the credibility of a firm and the accountability of a named person, and this structure gives them both in one email.
Write claiming rules before the first reply arrives
The master inbox is the collective's biggest asset and its biggest fight waiting to happen. Decide in writing, before launch: replies route to the campaign owner; cross-sell replies ('do you also do branding?') go to whichever member owns that service line within 24 hours; and any reply unclaimed after a day can be answered by anyone. Collectives that skip this step end up with leads going cold inside a shared inbox while two members each assume the other has it.
Divide capacity by stated need, then audit monthly
A shared 16-mailbox pool is 32 outbound sends/day for the whole group — and the member between projects needs more of it than the member who's fully booked. Set each Smartlead campaign's daily volume to match what each member actually needs this month, then revisit at a monthly check-in using per-campaign analytics. Splitting the ColdRelay bill evenly but the capacity unevenly is fine; what kills collectives is nobody ever looking at who's using what.
Use spintax for volume lines, never for the studio voice
With multiple campaigns sending from one domain, repetitive phrasing across members' sequences compounds faster than it would for a solo sender. Use Smartlead's spintax on the mechanical lines — greetings, transition sentences, CTA phrasing — so the pool's output doesn't read as a template farm. But keep the studio's positioning line identical everywhere, on purpose: that one consistent sentence is the brand, and a prospect who gets emailed by two different members six months apart should recognize it.
Typical Freelancer Collective Benchmarks (Smartlead + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate | 3-7% | Studio positioning with a named specialist tends to out-reply generic solo outreach |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Daily outbound at collective scale | 24-40 emails | 12-20 shared mailboxes on one studio domain, divided across member campaigns |
| Time to first campaign | Same day | ~60 minutes to provision the shared pool, plus campaign setup per member in Smartlead |
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). A collective's pool of 12-20 mailboxes sits in a better tier than any member would reach alone — pooling is cheaper per mailbox than five solo setups — and DNS, dedicated IPs, and isolated Azure tenants are all included.
Smartlead is billed separately on its own subscription for campaigns, mailbox rotation, client sub-accounts, and the master inbox — priced per its current plans, and one workspace covers the whole collective.
The full stack is one infrastructure bill and one software subscription, each split across the group. Divided three to five ways, every member runs studio-grade outbound for a fraction of what their own standalone setup would cost.
| 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're complementary layers doing different jobs. Smartlead handles campaigns, mailbox rotation, sub-accounts, and replies in the master inbox. ColdRelay provides the underlying domain, mailboxes, and dedicated IPs that all of Smartlead's campaigns send from. For a collective the split is especially clean: ColdRelay is the shared infrastructure everyone chips in on, Smartlead is where each member runs their own service line on top of it.
Should each member of the collective get their own mailboxes, or share one pool?
Share one pool on one studio domain. A shared 12-20 mailbox pool reaches a better ColdRelay volume tier than five separate 3-mailbox orders, builds one consolidated domain reputation instead of five thin ones, and presents a single studio brand in every prospect's inbox. ColdRelay supports 100-150 mailboxes per domain, so one domain covers a small collective many times over. Smartlead's campaign-level rotation handles the sharing — every member's campaign draws from the same accounts.
Do we need to warm up the shared pool before launching everyone's campaigns?
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 the collective can launch all members' Smartlead campaigns the same day the pool provisions. Don't enable a separate warmup layer in Smartlead on top of it.
What happens to the shared infrastructure when a member leaves the collective?
Less than you'd fear, because the assets belong to the studio, not the person. The domain, the mailboxes, and their accumulated reputation all stay in the collective's ColdRelay account; you pause or archive the departing member's Smartlead campaign and reassign their share of the daily capacity to the remaining members. In-flight conversations from their campaign sit in the master inbox, so another member can pick them up without prospects ever emailing a dead address.