Use case
- Read
- 4 min
- Updated
- 14 Oct 2026
- Sections
- 7
Use case
Email for agencies running client domains
Every client domain in one inbox and on one bill, priced per person, with free role addresses, and a checklist for the day a client leaves.
4 min read · 14 Oct 2026 · 7 sections
On this page 7 sections
- What does email for an agency with client domains cost?
- How do you onboard a client’s domain?
- How do role addresses survive staff changes?
- What happens to a client’s email when they leave?
- Is there a plan for larger agencies?
- When is SuperMailOS the wrong fit for an agency?
- Questions
- Do we need a separate plan for each client?
- Can each client domain have its own hello@ and support@?
- Who sets up a client's DNS?
- Does a new client domain need warming up?
- What happens when a client leaves?
An agency has one email setup per client, and usually one more for itself. SuperMailOS puts every client domain in one workspace on one bill: Business covers unlimited domains at $5–$6 a person a month, role addresses like press@ and jobs@ are free aliases on every domain, and each domain gets its own DNS records, DKIM signature and DMARC reports. You pay for the people who read mail, not for the addresses clients’ customers write to.
What does email for an agency with client domains cost?
For 6 people, 12 domains, 40 role addresses, about 150 emails sent a day, billed yearly, cheapest first (US dollars before tax, competitor prices from each provider’s own pages):
| Provider | Plan | A year |
|---|---|---|
| Purelymail | Simple pricing | $10 |
| Migadu | Standard | $290 |
| SuperMailOS | Business | $360 |
| Google Workspace | Business Starter | $504 |
| Microsoft 365 | Business Basic | $504 |
| Proton | Workspace Standard | $935.28 |
| Zoho Mail | Mail Lite / Mail Premium | Not priced |
| Fastmail | Standard or Professional | Not priced |
SuperMailOS isn’t the cheapest line here: Purelymail and Migadu cost less. What $360 a year buys is every client’s mail in one threaded inbox, per-person pricing that doesn’t move when a busy client sends more, and the DNS and DMARC work done for each domain. The email cost calculator runs the same numbers for your own team.
How do you onboard a client’s domain?
- Add the domain. If its DNS is on Cloudflare, DigitalOcean, Linode, Vultr, Hetzner DNS or Spaceship, connect it once and the records are written for you. Anywhere else, you get the exact records to paste.
- Let the records check out. MX, SPF, DKIM and DMARC are generated from the mail server’s own zone and checked live; the domain can’t send until they pass.
- Create the people and the addresses. A mailbox for each person who reads mail; free aliases for every role address.
- Bring the old mail across, then switch. Copy existing mail over IMAP first and point MX at us last, so nothing falls between providers (migration guide).
How do role addresses survive staff changes?
A role address is an alias pointing at a mailbox, so when the account manager on a client changes, you repoint the alias and the address clients’ customers know stays the same. For an address several people work from, a shared mailbox like support@ counts as one mailbox, and giving teammates access to read, send or manage it costs nothing extra.
What happens to a client’s email when they leave?
A hand-off checklist that keeps the client in control of their own domain:
- Confirm who owns the domain and DNS logins. Ideally the client did all along.
- Export their mailboxes and hand them over, or let their new provider copy them over IMAP.
- Point MX and SPF at the new provider, and replace our DKIM record with theirs.
- Change the DMARC report address. Domains here send DMARC reports to dmarc@supermailos.com so they appear in the dashboard; the client should point theirs somewhere they own.
- Remove the domain from your workspace once mail flows to the new provider. Your other client domains carry on unchanged.
Is there a plan for larger agencies?
Yes: from 50 mailboxes there’s an Agency plan with volume pricing. It’s on the pricing page; write to us to set it up.
When is SuperMailOS the wrong fit for an agency?
- The client should own the account. If a client wants its own admin and its own bill, set it up in its own workspace, or its own provider.
- You run campaigns for clients. Newsletters and cold outreach need a sending platform; business mailboxes, ours included, aren’t built for it.
- The client lives in a suite. A team in Google Workspace or Microsoft 365 gets documents and calls with its mail; moving only the mail may cost more than it saves.
Questions
Do we need a separate plan for each client?
No. Every client domain sits in one workspace on one bill. Pro covers up to 3 domains; Business covers unlimited domains, so a growing client list never changes the plan.
Can each client domain have its own hello@ and support@?
Yes. Role addresses are free aliases on every domain, as many as you need, each delivering into whichever mailbox should answer it.
Who sets up a client's DNS?
If the client's DNS is on Cloudflare, DigitalOcean, Linode, Vultr, Hetzner DNS or Spaceship, you connect it once and the records are written for you; the access token is used once and never stored. Anywhere else you get the exact records to paste, and each one is checked live before the domain can send.
Does a new client domain need warming up?
Sending on a new domain is ramped up gradually, starting with a small daily cap that grows until it's lifted. How fast depends on the domain's age: a domain registered days before it joins ramps more slowly than an established one.
What happens when a client leaves?
Export their mailboxes, point their domain's MX and SPF at the new provider, change the DMARC report address to one they own, then remove the domain from your workspace. Your other client domains carry on unchanged.