All writing
GuidesAugust 27, 20266 min read

Email Hosting for Agencies: Managing Client Domains Without the Per-Client Bill Stack (2026)

How agencies should host email across client domains: the two standard models and where their costs break, the records every client domain needs, and what to hand over when a client leaves.


Email hosting for agencies comes down to one structural choice: bill each client domain as its own per-user subscription, or run every client on one multi-domain host where you pay per person and addresses are included. A 20-person client costs $120/month at Microsoft 365 Business Basic listed pricing ($6 per user/month) or $144/month at Google Workspace Business Starter ($7.20) — the same 20 mailboxes cost $100/month on a plan priced at $60 per mailbox per year with unlimited domains. The hosting decision is also a margin decision, because the agency usually resells this line item.

Disclosure up front: we make SuperMailOS, a multi-domain email host with a plan built for agencies, so this guide is written from that side of the table. The mechanics below apply no matter who you pick.

What agency email hosting actually involves

An agency running email for its clients is doing three jobs at once: branded addresses on every client domain (hello@, billing@, the client owner's own name@), deliverability on domains whose DNS the agency often controls but the client can also touch, and access that matches how agency teams actually work — several people covering the same accounts, staff turning over, clients wanting visibility into their own mail.

The failure mode is fragmentation. Each client domain becomes its own hosting plan, its own bill, its own admin console, and its own DNS afternoon. The agency ends up running the same setup five or ten times over, and every new client adds a permanent operational cost before any margin appears.

The standard fixes are white-label forwarding or multi-tenant suites. Forwarding services market exactly this use case — one provider pitches "email forwarding designed specifically for digital agencies and consultants." Forwarding alone has a hard limit, though: mail comes in, but replies go out from somewhere else, which is a credibility and authentication problem on a paying client's domain.

Two standard models — and where their costs break

1. One suite tenant per client

Google Workspace and Microsoft 365 both support adding many domains to a single tenant — Microsoft documents a limit of 900 domains. So an agency can hold every client domain in one tenant, or one tenant per client for isolation.

The break point is pricing structure, not capability. Per-user billing multiplied by client headcount makes email a line item the agency marks up or absorbs. A 20-person client at listed Business Basic pricing is $1,440/year; at Business Starter, $1,728/year. The suite answer for bigger rosters is volume pricing, which starts to look like a resale product — that is what it is.

2. Per-person multi-domain hosting

The other model: one account holds every client domain, mail from all of them lands in managed inboxes, and billing counts people, not addresses. SuperMailOS Business works this way at $60 per mailbox per year with unlimited domains and unlimited free aliases on every one, and has an Agency plan with volume pricing for teams running 50+ mailboxes. Competitors in this category include Mailbux, which markets "unlimited email accounts at a flat monthly rate" at agencies specifically, and Forward Email's white-label forwarding for consultants. For an agency, the pricing unit is the whole game: per-person billing means the tenth client domain costs the same to host as the second.

The records every client domain needs

No matter the provider, each client domain needs its own DNS records before it can send safely:

  • MX — points the domain's incoming mail at the host's servers.
  • SPF (TXT) — lists which servers may send for the domain.
  • DKIM — cryptographic signatures proving messages were not altered in transit; one key per domain.
  • DMARC — tells receivers what to do when SPF/DKIM fail, and gets you reporting on who sends as your client.

On client domains these records live in DNS the agency usually manages — which is exactly why per-domain verification should be the host's job, not a runbook the agency maintains. SuperMailOS, for example, pulls each domain's records from the mail server's own zone, verifies them live, and blocks sending from any domain that has not passed verification; DKIM signing, DMARC reporting, and new-domain warm-up are handled on every connected domain. The general principles are in our SPF, DKIM and DMARC explainer.

Staff turnover, aliases, and continuity

Agencies have a churn problem that products don't: the person answering support@clientA.com this quarter is a different person next quarter, but the address can't change. That argues for role aliases (support@, billing@) that deliver into mailboxes owned by people, so the address outlives the staff. On per-user suites each new hire is a new line on the bill; on per-person hosts, aliases are free and the bill only moves when headcount moves.

The underlying architecture — one inbox collecting addresses from many domains — is the same setup we covered in email hosting for multiple domains.

We run that setup ourselves across the products we build — a vector conversion tool (PNG to SVG guide) and a group expense splitter (best Splitwise alternatives) — so the agency pattern above is the same consolidation we chose instead of one mail plan per product.

What to check before picking a host

  • Pricing unit. Per user, per mailbox, per domain, or flat per person? This decides your margin on every client after the first.
  • Domain limits and per-domain fees. What happens at client number 25?
  • Alias policy. Are role addresses free, or billed?
  • DNS workflow. Records from the live zone with one-click DNS for the registrars your clients use, or a copy-paste runbook per domain?
  • Isolation. Per-domain DKIM keys and per-domain reputation, so one client's deliverability problem doesn't bleed into another's.
  • Handover path. What a departing client actually takes with them (see below).

Handover: what happens when a client leaves

The agency should decide this before the first client, not during the offboarding email. The minimum viable handover: a list of every address and alias on the domain, the DNS records currently published (MX, SPF, DKIM, DMARC), and a destination for the mailboxes. On multi-domain hosts the domain is disconnected from the agency account and pointed at the new provider's records; the domain's DNS and history belong to the client either way. Any host that makes this extraction painful is a churn liability you're holding on behalf of your clients.

Frequently asked questions

Can an agency manage email for multiple client domains from one account?

Yes. Multi-domain hosts and suites both support it — Microsoft 365 up to 900 domains per tenant, and per-person hosts like SuperMailOS treat domains as unlimited on Business. Compare the pricing unit before committing, since that drives agency margin as clients add headcount.

Should each client domain get its own hosting plan?

Usually not, unless the client demands isolation. Separate plans per client mean more bills, more admin consoles, and more DNS work for the same mail. Consolidating on one multi-domain account cuts the operational cost of every client after the first.

Do I need a mailbox for every person at every client?

Only if the client actually reads mail at those addresses. Role aliases (billing@, support@) delivering into the inboxes of people who answer them cost nothing on per-person hosts, which is why per-user suites punish agency setups.

How do agencies handle email for clients when staff changes?

Keep role aliases on the client domain (support@, billing@) and route them to staff mailboxes. When someone leaves, repoint the alias — the client-facing address never changes.

Can clients keep their email if they leave the agency?

Yes, if the handover is planned. The client owns the domain and its DNS; the agency provides the record inventory and mailbox export, and the domain is pointed at the new provider. Agree on this in the engagement contract.


Running client domains on per-user billing stacks a bill under every client. SuperMailOS puts every client domain in one managed inbox — unlimited domains and free aliases on Business, with an Agency plan at volume pricing past 50 mailboxes.