White-labelling an outbound stack turns an agency from a service with a tool cost into a product with a service attached. The economics are genuinely good. The reason most attempts stall is not margin, it is that reselling software means inheriting the support burden of software, and that cost never appears in the spreadsheet that justified the decision.
Here is both halves.
Where the margin comes from
Not from marking up seats. Clients can price-check seats. The margin comes from three places they cannot:
- Infrastructure at your volume, sold at theirs. Mailboxes bought at $0.80 to $2.50 and delivered as part of a managed programme. A client buying 20 mailboxes alone pays retail and still has to warm them.
- The setup nobody wants to do. Domains, DNS, authentication, warmup schedules and placement testing are two weeks of specialist work per client. That is the single most billable thing in the stack.
- Bundling. The client is buying meetings, not mailboxes. Once the invoice reads “outbound programme” rather than a line-item tool bill, the comparison to a software price disappears.
Client isolation is the whole product
This is the part that decides whether the business is viable, and it is technical rather than commercial.
| Must be isolated | Why |
|---|---|
| Domains and mailboxes | One client’s bad list must not touch another client’s sending reputation. This is the risk that ends agencies |
| Workspaces and data | Client A must never be able to see that client B exists. Also a contractual requirement in most engagements |
| Suppression lists | Per client, always. A shared suppression list leaks your client roster |
| Login and branding | If they log in and see a vendor’s logo, you are a reseller rather than the provider |
| Billing | Your invoice, your pricing, your terms. Any vendor billing visible to the client destroys the margin |
The reputational point deserves emphasis: on a shared setup, one client who uploads a purchased list can damage placement for every other client on those domains. Per-client domains are not tidiness, they are the thing you are actually selling.
What to charge
Three models work, in rough order of how well they hold up.
Managed programme, monthly retainer. The strongest. You own strategy, copy, infrastructure and reporting; the client owns the sales calls. Price on the value of meetings, not on tool cost. This is where most of the margin is.
Software plus onboarding. A monthly platform fee under your brand, with a one-off setup charge covering domains, authentication and warmup. Lower revenue per client, far better scaling, and the setup fee is what makes it profitable.
Per-meeting or per-lead. Attractive to clients and dangerous to you: you carry the full risk of their offer, their ICP and their close rate. Only take it where you have run the same motion in the same market before.
One rule regardless of model: charge for setup. Free setup means a two-week specialist project delivered before a single invoice, and it is the most common reason white-label agencies run out of cash while growing.
The costs that decide whether this works
Support becomes yours. When a client’s mailbox stops sending, they ask you, not the vendor. Budget real hours for it and set response expectations in the contract.
Onboarding is a fixed cost per client. Domains registered, DNS records, warmup, placement testing, then copy. Two weeks before results, every time. Price it or template it, ideally both.
Churn follows results with a lag. Outbound takes six to eight weeks to show whether it works, so your first honest churn signal arrives in month three. Do not build a cost base on month-one revenue.
Deliverability is now your liability. A client whose campaigns land in spam blames you regardless of whose list it was. This is why isolation and placement testing per client domain are operational requirements rather than nice extras.
Sequencing it
- Run it as a service for three or four clients first. You cannot template an onboarding you have never done.
- Standardise the setup into a checklist with named DNS steps and a warmup schedule. This is your actual product.
- Then add your branding and hand clients a login. Reporting they can see themselves removes a recurring support conversation.
- Keep per-client infrastructure separate from day one. Retrofitting isolation after a shared-domain incident is not really possible.
Next: scaling the delivery side, running outreach for many clients, or what the infrastructure actually costs at volume.
Frequently asked questions
Is white-labelling a cold email stack profitable?
Yes, but not from marking up seats. The margin comes from infrastructure bought at your volume, the two weeks of setup work per client that nobody wants to do, and bundling the whole thing as an outbound programme rather than a tool bill.
What has to be isolated per client?
Domains and mailboxes, workspaces and data, suppression lists, login branding and billing. The domain isolation matters most: one client’s bad list must not be able to damage another client’s sending reputation.
What should I charge?
A managed monthly retainer priced on the value of meetings holds up best. Software plus a one-off onboarding fee scales better. Per-meeting pricing transfers all of the client’s ICP and close-rate risk to you.
Should I offer free setup?
No. Setup is two weeks of specialist work per client, and giving it away is the most common reason white-label agencies run short of cash while growing.
What is the hidden cost?
Support. Once your logo is on it, every mailbox problem is your problem rather than the vendor’s. Budget real hours and set response expectations in the contract.