Outbound as a Service Line, Built on Smartlead
There's a moment most agencies hit: a client asks, 'could you run cold email for us too?' — and the honest answer is that you've never sold it as a service. The demand is sitting inside your existing roster; what's missing is a delivery system you'd be willing to put your agency's name on. That system has two layers. Smartlead is the software layer: client sub-accounts, campaign-level mailbox rotation, a master inbox, and an API for client-facing reporting. ColdRelay is the layer underneath — the secondary domains, mailboxes, and dedicated IPs that those campaigns actually send from.
This guide is for the agency adding outbound management as a new revenue line, not the established cold email shop. It covers how to pilot the service with a single existing client inside one Smartlead sub-account, how to wire ColdRelay infrastructure into it, how to price the offering as a retainer add-on with margin you can defend — and how to turn a successful pilot into a repeatable product across the rest of your roster.
Why a New Service Line Starts at the Infrastructure Layer
When you add a service you've never delivered before, the biggest risk isn't the software — it's everything you'd otherwise have to learn the hard way: registering domains, configuring SPF, DKIM, and DMARC, sourcing IPs whose history you can't see, and discovering deliverability problems only after a paying client's campaign goes quiet. Smartlead doesn't take that on; it's a sending and sequencing platform, and it sends from whatever mailboxes you connect to it.
ColdRelay removes that entire learning curve. You order mailboxes on isolated Azure tenants with dedicated IPs — DNS (SPF, DKIM, DMARC) pre-configured, supporting 100-150 mailboxes per domain, ready in about an hour. There's no warmup waiting period before the first campaign: warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup). For a service line you're launching for the first time, that matters twice over — your pilot can start the week you sell it, and when the pilot converts the rest of your roster, fulfillment capacity is an order away rather than a months-long infrastructure project.
The pairing is additive, not competitive: ColdRelay is the infrastructure layer, Smartlead is the sending and sequencing layer on top. Smartlead gives the new service line its operating console; ColdRelay makes sure the part clients are actually paying for — emails that land — is never the thing you're improvising.
Visit Smartlead →Standing Up the Pilot: ColdRelay Into a Smartlead Sub-Account
Provision a pilot pool on ColdRelay
Pick one existing client — ideally one who has already asked about outbound — and order a small dedicated pool for them: secondary domains that echo their brand, never their primary domain. A pilot of 20-50 mailboxes fits on a single domain, since ColdRelay supports 100-150 mailboxes per domain. The pool provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC pre-configured — small enough to be low-stakes, real enough to prove the service.
Create the client sub-account in Smartlead
In Smartlead, create a client sub-account for the pilot client under your agency account. Even with one client, start with the sub-account structure rather than running their campaign in your main workspace — the pilot is also a dress rehearsal for the operating model you'll use when client two and three sign on.
Bulk-import the pool under Email Accounts
Export the mailbox credentials from the ColdRelay dashboard as CSV, then in the client's sub-account use Email Accounts → bulk import via CSV over SMTP/IMAP. The export matches the column layout Smartlead's importer expects, so the whole pilot pool connects in one upload — no per-mailbox manual setup eating into your pilot margin.
Set limits, enable rotation, and write the sequence with spintax
Cap each mailbox's daily campaign limit in Smartlead at 2 outbound emails, mirroring ColdRelay's per-mailbox budget of 4 sends/day total — 2 outbound + 2 warmup, with warmup running continuously on ColdRelay's side (don't double-warm in Smartlead). Build the client's campaign, attach the full pool with campaign-level mailbox rotation, and use Smartlead's spintax support to vary phrasing across sends so a 30-mailbox pool doesn't broadcast 30 identical emails.
Set up the master inbox and client reporting before launch
Decide reply ownership on day one: replies land in Smartlead's master inbox, and someone on your team triages them daily — forwarding qualified conversations to the client within hours. Then wire Smartlead's API and webhooks into a simple branded report (sends, replies, positive replies, meetings). For a new service line, the report is the deliverable the client renews on; build it before the first send, not after the first month.
The Outbound-as-a-Service Launch Playbook
Sell the pilot to a client you already have
Your first outbound client shouldn't come from outbound — it should come from your roster. An existing client already trusts your work, tolerates the small adjustments of a first delivery, and gives you a referenceable result in their vertical. Frame it explicitly as a pilot: defined scope, defined duration, a clear review date. You're not pretending to be a ten-year cold email shop; you're extending a relationship that already works.
Price it as a retainer add-on, with the math done in advance
Because ColdRelay prices per mailbox and Smartlead is a flat subscription, the cost side of the new service is fully knowable before you quote it. Work the capacity arithmetic first — at 2 outbound sends/day per mailbox (of the 4/day total, 2 being warmup), a 50-mailbox pool delivers roughly 3,000 outbound emails a month — then set the add-on retainer against that capacity plus your management time. Quote a monthly add-on, not a per-lead price: per-lead pricing on a service you're delivering for the first time is a margin gamble you don't need to take.
Sell capacity and conversations, not a lead quota
The fastest way to kill a new service line is overpromising its output in month one. Scope the pilot deliverable as what you control — mailboxes live, sends delivered, replies triaged and handed over fast — and report results (positive replies, meetings) as outcomes the pilot is measuring, not numbers you guaranteed. With 95%+ inbox placement on ColdRelay infrastructure, the delivery side holds up its end; let list quality and offer strength reveal themselves in the data before you commit to quotas in the renewal.
Turn the pilot into a product before client two signs
The week the pilot proves out, write down everything as a runbook: the pool size you ordered, the sub-account setup, the CSV import, the limit settings, the sequence skeleton, the report template. The goal is that the second client's setup is an execution day, not a second invention — order the pool in the morning (it provisions in about an hour), and have campaigns ready in their sub-account by the afternoon. The agencies that make outbound a real revenue line are the ones where infrastructure and setup are a checklist, and only the strategy is bespoke.
Typical Benchmarks for an Agency's First Outbound Offering (Smartlead + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup, warmup running continuously |
| Pilot pool size | 20-50 mailboxes | Fits on one domain (ColdRelay supports 100-150 per domain); big enough to generate real data in a 60-90 day pilot |
| Time from pilot signed to first send | Same week | ~60 minutes to provision on ColdRelay; list building and sequence writing are the long pole, not infrastructure |
| Setup time for client #2 onward | Half a day | With a written runbook: order the pool, create the sub-account, bulk-import, clone the sequence skeleton |
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 — and the tiering works in a launching agency's favor: the pilot starts small, and as more clients adopt the add-on, your total mailbox count climbs into better tiers even though each client's pool stays separate.
Smartlead is billed separately on its own subscription, covering client sub-accounts, campaign-level rotation, the master inbox, spintax, and API/webhook access — priced per its current plans.
For a new service line, the key property is that both costs are known before you sell: infrastructure scales with mailbox count, software is a predictable subscription. That makes the add-on retainer a margin calculation you can do at the proposal stage — and a number you can defend at the renewal.
| 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. Smartlead is the sending and sequencing software: client sub-accounts, campaign-level mailbox rotation, the master inbox, spintax, and the API your client reporting runs on. ColdRelay is the infrastructure underneath: the secondary domains, mailboxes, and dedicated IPs each sub-account sends from. An agency offering outbound as a service uses both — one is the console, the other is the capacity.
We've never run cold email as a service. Can we realistically offer this?
Yes — provided you don't try to own the infrastructure problem yourself. The genuinely hard part of delivering outbound for a client is deliverability: domains, DNS, IP reputation, warmup. ColdRelay handles all of it — provisioning on isolated Azure tenants with dedicated IPs in about an hour, SPF, DKIM, and DMARC pre-configured, warmup running continuously within each mailbox's 4 sends/day budget (2 outbound + 2 warmup). What's left is what agencies are already good at: positioning, copy, list strategy, and managing the client relationship.
How should we price the outbound add-on for clients?
As a flat monthly retainer add-on, scoped to capacity. Both of your costs are predictable — ColdRelay bills per mailbox with volume tiers, Smartlead is a subscription — so you can compute the pilot's delivery cost before quoting and layer your management fee on top. Avoid per-lead pricing in the first engagements: until you've seen how a client's vertical and list quality convert, a per-lead price is a guess wearing a contract.
What's the risk to the client — or to our agency — if the pilot doesn't work?
Contained, by design. The pilot runs on its own ColdRelay pool — dedicated secondary domains, dedicated IPs, an isolated Azure tenant — so the client's primary domain and your agency's own domain are never exposed to outbound reputation risk. If the offer or list doesn't convert, you've spent a small monthly infrastructure cost and learned it on real data; if a pool ever degrades, a fresh one provisions in about an hour. The downside is a line item, not a reputation event.