Essay · 7 min read

One person, five brands — a sending-identity playbook.

A custom-domain email and sending-identity playbook for solo operators: when to bind a new domain, when an alias is enough, and when the two-domain shortcut costs more than it saves.

Every portfolio operator eventually faces the same set of decisions. A new side project needs email. Should it get its own domain? Live on an alias of an existing domain? Borrow the parent company's address? And once you have five brands across four domains, how do you decide where a new transactional email address — billing@, press@, help@ — belongs?

This piece lays out the heuristics that work in practice, ordered by how often they come up. None of these rules are sacred; the point is to name the trade-offs so you can make them deliberately instead of by default. If you're still weighing where to host all this, our survey of the best multi-domain webmail services for solo operators covers the provider side; this piece is about the architecture decisions that come after.

2026 update: the hosting decision now splits into two questions. First, whether your sensitive operator mail belongs on private email hosting for solopreneurs instead of a consumer account. Second, whether each new venture deserves a real custom-domain setup — the path covered in custom domain email with no website required, custom domain email without Google Workspace, and unlimited domain email hosting for serial entrepreneurs.

For the adjacent buying questions, see the companion guides to email hosting for micro-businesses and email management software for solopreneurs. This playbook assumes the narrower problem: one person has several brands and needs to decide which addresses deserve a first-class sending identity.

§ Rule 1: Domain or alias?

An alias is a new address on an existing domain (hello@yourdomain.comyou@yourdomain.com). A domain is a new zone entirely (hello@new-thing.com). They look similar from the outside but behave very differently in three places that matter:

  • ·Sending reputation. An alias shares its parent domain's reputation. A new domain starts fresh — which is either a feature or a cost, depending on what you're doing.
  • ·Brand perception. A letter from founder@yourdomain.com reads like 'this is a side of your existing thing'. A letter from hello@new-thing.com reads like 'this is its own thing'.
  • ·Operational cost. A new domain means more DNS records to maintain, a fresh DKIM key to rotate, a separate DMARC dashboard to watch. Aliases cost nothing additional.

Heuristic: bind a new domain when you want the brand to stand on its own or when you need reputation isolation. Use an alias when the new thing is a subdivision of an existing brand or a temporary experiment.

A domain signals permanence. An alias signals flexibility. Don't confuse the two.

§ Rule 2: When to isolate reputation.

Sending reputation is domain-scoped. A bounce storm on main.com — because your sales team sent 10,000 cold emails to a stale list — drags down every future letter from main.com, including the critical transactional ones like password resets and receipts.

This is why mature product companies split their sending into separate subdomains:

Transactional
mail.yourdomain.com — password resets, receipts, notifications. Sacrosanct.
Product marketing
news.yourdomain.com — product updates, release notes. Warm, opt-in.
Cold outreach
reach.yourdomain.com — sales prospecting. Hot, can burn.

Each subdomain has its own DKIM key, its own SPF record, its own DMARC policy, and — crucially — its own reputation pool. When the cold-outreach subdomain gets throttled, the transactional subdomain is unaffected.

For a solo operator, the version of this that matters is: if you're running a marketing experiment (Product Hunt launch, newsletter announcement, beta invite blast), and the main domain carries transactional mail that has to land, use a separate domain or subdomain for the experiment. Cheap insurance.

§ Rule 3: Addresses within a domain.

Once you've settled on a domain, the next question is which addresses live on it. Every portfolio operator eventually converges on a standard set; the art is knowing which to use when.

  1. 01yourname@ — for personal correspondence, private reach-outs, investor updates. The address your family uses.
  2. 02hello@ — the public-facing inbox. Contact form, social bios, business card. The address you'll publish.
  3. 03press@ — for press inquiries and podcast bookers. Keeps the volume separate from hello@ so press requests don't drown in generic questions.
  4. 04billing@ or accounts@ — for invoices and payment confirmations. Your CPA gets cc'd here.
  5. 05legal@ or contracts@ — for counsel, NDAs, contracts. Your attorney gets cc'd here.
  6. 06support@ — for product users (if applicable). Usually wired to a helpdesk tool.

The trap: creating too many addresses. Every address is a potential confusion (which do I write to?) and a potential leakage (which do I monitor?). Five is usually enough for a solo operator. Ten is already past the point of useful signal. And the more sensitive the inbox — legal@, billing@, contracts@ — the stronger the case for keeping that correspondence on private hosting rather than a free consumer account.

§ Rule 4: The decision tree, summarised.

When you're standing up email for a new brand, the question tree looks like this:

  1. 01Is the new thing a distinct brand or a subdivision of an existing one? Distinct → new domain. Subdivision → alias on parent.
  2. 02Does the new thing need its own sending reputation? (Cold email, bulk marketing, experimental.) Yes → new domain. No → alias is fine.
  3. 03Does the new thing have its own legal entity? (LLC, Ltd, etc.) Yes → new domain for bookkeeping clarity — the pattern laid out in email for multiple LLCs. No → alias is fine.
  4. 04Is this temporary? (30-day experiment, seasonal promotion.) Yes → alias or subdomain. No → new domain.

Three of four yesses usually mean a new domain. Three of four nos mean an alias. The ambiguous cases — two and two — go either way; lean toward aliases when in doubt because they're cheaper to reverse.

§ A note on how Folio changes the math.

Part of the reason portfolio operators historically under-use domains is that each new domain has historically meant a new Workspace seat (at $7/month) or a new Mailgun tenant. Folio's flat operator tiers remove per-mailbox charges: Solo includes three domains, Studio ten, and Holding Co. unlimited. Binding another domain within the plan limit adds no separate mailbox fee, so the decision becomes about brand and reputation rather than another seat. It's the same arithmetic behind unlimited-domain hosting for serial entrepreneurs and behind running a custom-domain setup without Google Workspace at all.

The practical effect: operators who had been squeezing five brands onto two domains for cost reasons tend to split them back out once the cost constraint is gone. The reading surface gets cleaner; the reputations properly isolate; the trade-off disappears.

§ Sources & further reading