For the holding-company-of-one

The parent entity.
Every brand beneath it.

A holding-company-of-one is one operator wearing four hats — the parent LLC, the agency, the Shopify brand, the SaaS. Folio keeps the corporate boundary intact (separate DKIM keys, separate SPF/DMARC posture, separate signatures) while collapsing the reading surface to a single inbox. Your accountant still sees four entities; you only sit in one editor.

You set up the holding company a few years ago. Underneath it sits an agency, a micro-SaaS, a Shopify brand, and the LLC that owns the intellectual property. Each has its own bank account, its own K-1, and — crucially — its own email domain.

Folio is the inbox for the one person who reads mail for all of them. Four domains, four DKIM signatures, four margin colours, one price.

Updated 11 May 2026 (2026-05-11)

Start free — no cardSee the price

Android app live on Google Play

I · The problem with running several LLCs from one head

Bookkeeping is per entity. Your inbox isn't.

Your accountant tracks each entity separately. The bank tracks each entity separately. The IRS definitely tracks each entity separately. The one place where the entities collapse into a single blob is your email — where the holdco's wire confirmation, the agency's client retainer, and the Shopify brand's support ticket all land on the same From line.

The standard workaround is one Workspace seat per entity. $7/month × four LLCs is $336/year, plus four separate admin consoles, four sets of billing, four places where you have to remember to turn 2FA on.

The actual requirement is simpler: identities stay separate in the ways that matter (reputation, signature, reply From), and consolidated in the ways that help (reading surface, sign-in, price).

Your holding company's structure exists for a reason. Your inbox should respect it — not flatten it into one From.

II · A Monday at the parent company

Four entities, one reader's morning.

Not a screenshot — a live render in the same editorial design system the app uses. Each row's stripe is the domain the letter was sent to. Hover (or read quickly, by eye): which self is each one addressed to?

III · How the reading changes

Identities as visible as they are on the cap table.

Each entity you bind becomes a first-class identity: its own colour stripe, its own DKIM signature, its own reply-From behaviour. Your bookkeeping structure is reflected in your reading surface — every letter is already filed in your head by the time you've read the subject.

  • ·
    One subscription across all entities. You are one reader; you pay for one seat. The holdco and every brand underneath it sit on a single Holding Co. plan — $29/mo billed annually (or $39/mo) for unlimited domains — never one seat per entity.
  • ·
    Separate sending reputations. The agency's reputation, the Shopify brand's reputation, and the holdco's reputation are isolated. A bounce problem on one entity's list can't leak onto another's.
  • ·
    Compliance-clean replies. When procurement writes to the holdco's legal@ address, the reply goes out from the holdco's legal@ — not some agency alias. DKIM-signed by the holdco's key.
  • ·
    No admin-console proliferation. One Stripe billing portal, one sign-in, one sidebar. You aren't juggling four Workspace admin URLs on five computers.

IV · Pieces your CPA and counsel will ask about

Boringly reliable, entity by entity.

When your CPA or general counsel asks how your email holds up under audit, these are the answers.

Per-entity DKIM
Each LLC's domain has its own RSA-2048 DKIM key. Signatures are entity-scoped; an auditor tracing a disputed email can verify which key signed it.
Data segregation
Messages are stored per identity. Retention policies (30-day trash) apply uniformly; no cross-entity bleed.
PITR backup
DynamoDB point-in-time recovery is enabled. Accidental deletes are recoverable to the second, within the retention window.
Magic-link auth
No password to rotate, no 2FA to manage across four tenants. Sign-in is a one-time, fifteen-minute link to the address issued it.

V · Common questions

Questions readers ask.

Does each subsidiary entity get its own DKIM/SPF/DMARC posture?

Yes. Each bound domain is provisioned with its own RSA-2048 DKIM key, its own SPF record pointing at Amazon SES, and an independent DMARC policy you set per domain. A subpoena or DMARC report for the agency does not pull in the parent LLC's mail.

Is there a per-user fee, or does each entity get its own bill?

Folio is single-user, single-bill. A holdco that owns four subsidiary domains pays one Studio or Holding Co. subscription — not four. Most operators expense the subscription against the parent and treat the per-domain identities as cost centres internally.

Can the agency send invoices and the SaaS send password resets from the same inbox without one drowning the other?

Yes. Each domain has independent sending throughput and reputation in Amazon SES. A high-volume transactional send from the SaaS does not consume the agency's sender quota, and bounce metrics are tracked per-domain rather than globally.

What happens to a domain's mail if I sell the underlying entity?

Unbind the domain from the holdco's Folio account; the buyer's team can bind it to their own account using the same DNS records issued by Folio. There is no data migration to negotiate — DNS is the boundary.

Does support cover all four subsidiaries, or only the billing entity?

Holding Co. tier includes priority support against every bound domain on the account. Tickets reference the affected domain rather than a per-entity license.

VI · Adjacent readers

Other shapes of the same problem.

VII · Sources & further reading

Where the claims come from.

Open the first letter

One reader. Four balance sheets.

Start free, no card. Bind the holdco first; route its inbound mail through Folio and see one morning of editorial reading. Upgrade when you want the agency, the Shopify brand, and the SaaS in the same inbox without collapsing the entities your accountant keeps separate.

Start free — no cardRead the manual

Updated 11 May 2026 (2026-05-11)