How to set up email for multiple LLCs — one operator, separate entities.

If you own more than one LLC, your accountant already keeps each entity on its own line, your bank keeps separate accounts, and the IRS treats each one as its own taxpayer. Your email is the one place those boundaries quietly collapse — a reply to the rental-property LLC goes out signed by the consulting LLC, and the corporate separation you pay a CPA to maintain leaks at the protocol level. The goal is the opposite: every entity cryptographically and reputationally distinct downstream, one human reading upstream.

There are exactly three building blocks. Picking the right one per entity is the whole game.

§ The three building blocks

Separate domain

hello@entity-two.com. Its own DNS zone, its own DKIM key, its own sending reputation. Maximum separation; the most DNS to maintain.

Alias

entity-two@your-main.com → your existing inbox. Shares the parent domain’s reputation and DKIM. Zero new setup; no real separation.

Subdomain

hello@mail.entity-two.com. Its own DKIM/SPF and a distinct reputation pool, but visibly tied to the parent. A middle option, mostly used to isolate bulk vs. transactional sending.

§ The decision tree

When a new entity needs email, ask these four questions in order:

1. 01Is it a distinct brand, or a subdivision? A distinct brand customers see on its own → separate domain. A back-office subdivision of an existing brand → alias is fine.
2. 02Does it need its own sending reputation? If it sends cold outreach, bulk marketing, or anything that could draw spam complaints, isolate it on its own domain so a problem there can’t drag down your other entities’ deliverability.
3. 03Does it have its own legal entity? A separate LLC with its own books and liability shield is the strongest case for its own domain — the mail trail then matches the corporate boundary an auditor expects. See email for multiple LLCs for the bookkeeping angle.
4. 04Is it temporary? A 90-day experiment or seasonal promotion → an alias or subdomain you can throw away beats standing up a domain you’ll unwind.

Rule of thumb: three or four ‘yes’ answers means a separate domain; three or four ‘no’ answers means an alias. The ambiguous middle leans toward aliases, because they’re cheaper to reverse. For most multi-LLC owners the answer is a separate domain per LLC — the legal-entity question alone usually settles it.

A domain signals permanence; an alias signals flexibility. The corporate veil is a domain-shaped argument.

§ What it costs: per-user vs. per-operator

The reason multi-LLC owners under-use separate domains is historically the price. Per-user suites like Google Workspace bill per mailbox, and treating each LLC as its own tenant multiplies that by the number of entities. The bill scales with the number of businesses even though there is still only one of you.

3 LLCs

Google Workspace Business Starter at $7/user/mo × 3 tenants ≈ $21/mo, plus three admin consoles.

5 LLCs

≈ $35/mo, five consoles, five bills.

Per-operator pricing

A flat single-operator plan charges for the reader, not the entity count — one subscription covers every LLC’s domain. Run the numbers on the email cost calculator.

This is the structural reason single-operator, multi-domain email exists: the cost of serving one more domain for the same human is not materially higher, so the price shouldn’t multiply. The full line-by-line is on Emcognito vs. Google Workspace.

§ When a separate domain per LLC is worth it

• ·Each LLC has its own customers, contracts, or bank relationships that should see a matching From address.
• ·An auditor or counsel may one day need to trace which entity sent a given message — per-domain DKIM makes that unambiguous.
• ·One entity does volume sending (a newsletter, a launch) and you don’t want its reputation risk touching the others.
• ·You want each entity to be able to leave cleanly — if you sell an LLC, its domain (and its mail) goes with it, with nothing entangled in your other entities.

§ When Google Workspace is still the right answer

Be honest about the trade. If any of your LLCs has employees who need shared Drive, Docs, Calendar, and Meet, Workspace’s collaboration suite is mature and worth the per-seat price for that entity. If you need enterprise admin controls — SSO, Vault/eDiscovery, per-OU policy — Workspace is built for it and a single-operator inbox is not. The per-operator model wins specifically when the operator is one human running multiple businesses, where per-user pricing charges you for seats that don’t exist.

§ Common questions

Do my LLCs really need separate email setups instead of just aliases? If a court or the IRS should see the entities as genuinely separate, sending all their mail from one DKIM key and one envelope From muddies that line. Per-entity DKIM and SPF keep the cryptographic record aligned with the entity that owns the activity.

Can one person manage email for many LLCs without many logins? Yes — that’s the point of a single-operator, multi-domain inbox: one sign-in reads every entity’s mail, while each bound domain keeps its own DKIM key and reply-From. You don’t need one Workspace tenant (and one admin console) per LLC.

What happens to an LLC’s email if I sell it? Because DNS is the boundary, you unbind that LLC’s domain and the buyer binds it to their own provider with fresh records. Nothing of theirs stays in your inbox, and nothing of yours leaves with it.

How do I move an LLC’s existing email over without downtime? It’s a per-domain DNS cutover with an overlap window so mail keeps flowing the whole time. The step-by-step is in the migration guide.

The short version: alias the subdivisions, give every real entity its own domain, and stop paying per seat for businesses that share a single reader. If you want the persona-level version of this with the morning-inbox scene, read email for multiple LLCs.