Field note · 11 min read

The Email Cost Calculator for Solopreneurs: What Five Domains Actually Cost You

Learn how to price your own domain portfolio in one sitting: the per-seat trap, the per-domain alternatives, and the hidden costs that never show up on a pricing page.

14 October 2026 · Updated 14 October 2026 · FolioInbox

An email cost calculator for solopreneurs should calculate costs per domain, not per person. If you run five separate domains—such as an agency, a consulting brand, an e-commerce shop, and two holding projects—mainstream email platforms force you to pay as if you were five separate human beings or sacrifice your sending reputation on aliases.

Most solo operators do not need collaboration suites, shared inboxes, or file storage tiers for multiple team members. You need one human inbox that can send and receive across multiple domains, where each entity maintains its own cryptographic DKIM signature and professional identity. When evaluating an email hosting comparison, the arithmetic changes dramatically when measured per domain rather than per seat.

Why Your Email Bill Doesn't Match the Number of Domains You Own

The core mismatch in small business email billing stems from a basic assumption: traditional enterprise software assumes one custom domain belongs to an organization with many employees. Software providers structure pricing around user seats. But solopreneurs, holding-company-of-one founders, and multi-brand creators flip that architecture upside down. You are one person who owns five, eight, or twelve domains.

When you evaluate the Google Workspace pricing page, you see per-user monthly rates. If you maintain five independent workspaces to keep identities, signatures, and credentials clean, you pay for five separate seats. That single-operator portfolio suddenly carries recurring overhead designed for a mid-sized office.

To avoid paying for separate user seats, solo operators typically attempt three technical workarounds:

One primary workspace seat with secondary domain aliases: You connect additional domains to a single account. While cost-effective, every secondary domain sends under the primary domain's DKIM signature, or exposes the primary address in message headers.
Consumer webmail "Send As" configurations: You route mail into an existing mailbox and set up custom SMTP credentials. This setup frequently breaks cryptographic alignment, tripping spam filters at major consumer inboxes.
Stitched-together multi-vendor routing: You combine separate forwarding relays, transactional sending providers, and basic IMAP mailboxes across disparate platforms to save cash, spending your weekends debugging DNS propagation failures.

This guide approaches your infrastructure purely as a cost-per-domain equation. Collaboration tools, meeting software, and team document systems are excluded from the balance sheet. The goal is to determine the exact cash and maintenance cost required to run five distinct sending domains reliably.

The Email Cost Calculator for Solopreneurs: Run Your Own Numbers

To run your own email cost calculation, gather four baseline numbers across your current setup:

Total domain count: The number of active brands, stores, or legal entities requiring outbound communication.
Active addresses needed: Whether you need one clean address per domain (e.g., alex@brand.com) or multiple aliases per property.
Cryptographic requirement: Does each domain require its own isolated DKIM selector and return-path alignment for commercial credibility?
Billing cadence: Annual billing commitments versus month-to-month flexibility.

The baseline scenario evaluates a solo founder operating five custom domains, requiring one primary address per domain, billed on an annual cycle in 2026.

The structural difference between providers comes down to their billing unit:

Per-seat platforms: The cost multiplies by the number of human accounts. If you purchase separate accounts to keep domain branding, signatures, and keys unlinked, your bill multiplies linearly by five.
Per-domain or resource-pooled platforms: The cost is indexed against domain limits, storage buckets, or global outbound sending quotas, allowing one person to manage multiple domains under a single flat rate.

Behind the headline price are indirect costs: the hours spent manually formatting TXT and CNAME records at your registrar, troubleshooting deliverability flags when transactional receipts land in spam, and tracking multiple software renewals. You can model your portfolio to compare annual commitments directly.

What Google Workspace Actually Costs When You Only Need One Seat

Calculating the true cost of Google Workspace for multiple domains requires looking past the standard per-user headline rate. If you purchase a single user seat on Google Workspace Business Starter, you pay for one mailbox account.

Inside a single account, you can add secondary domains as domain aliases. When you do this, you can receive incoming messages across those web properties without paying for extra user licenses. However, outbound sending creates structural deliverability hurdles for independent brands:

Shared identities: Setting distinct signatures, profile icons, and outbound display identities across multiple alias domains within one seat requires continuous manual adjustment.
DKIM alignment gaps: Modern deliverability relies on strict DMARC compliance. DMARC requires SPF or DKIM to align with the domain displayed in the "From" header. When aliases route through a primary Workspace identity without isolated cryptographic signing, authentication checks can fail at receiving mail transfer agents.

If you split each domain into its own Workspace account to ensure pristine authentication, separate drive spaces, and independent identities, your annual expense multiplies by five. For an operator running multiple projects, paying for five separate office-suite seats provides zero operational leverage.

There is a sensible boundary: if your businesses actively rely on shared team calendars, drive storage, collaborative documents, and integrated video conferencing on every single domain, Google Workspace remains a functional choice. But if you simply need secure, authenticated email delivery on five custom domains, paying for five productivity-suite seats is an inefficient allocation of capital.

The Per-Domain Alternatives, Priced Side by Side

Several providers decouple domain quantity from human user seats. When evaluating platforms for a single operator managing a portfolio, examine how each vendor structures its core pricing unit and outbound authentication.

Platforms handle domain architecture differently across the market:

Migadu's pricing uses an infrastructure model based on outbound sending volume and server resources rather than per-user seats, allowing multiple domain configurations under shared resource pools.
Purelymail's pricing bills based on combined resource consumption (storage and data usage) with support for hosting multiple custom domains without seat surcharges.
Zoho Mail: Offers email-only plans separate from its CRM platform, though multi-domain identity routing often requires navigating broader suite configurations.
Fastmail: Provides dedicated domain management and alias handling geared toward productivity users, though its tier structure scales with account features.
For properties that do not need to originate outbound messages, simple inbound forwarding is often sufficient. According to the Forward Email FAQ, forwarding-only services provide an option for domains that solely require inbound message redirection to an existing mailbox without full outbound infrastructure.

If your third, fourth, or fifth domain only exists to collect inbound contact forms, inbound forwarding is practical and economical. But if that domain must send outbound agreements, investor updates, or customer support replies, sending through an unauthenticated forwarder compromises deliverability.

Provider	Primary Billing Model	Outbound Cryptographic Signing	Optimal Fit
FolioInbox	Flat plan tiers based on domain bands and send volume	Dedicated per-domain DKIM and signatures	Single operators managing 2 to 12+ domains needing separate outbound branding
Migadu	Outbound volume and resource limits	Supports multi-domain keys	Technical administrators comfortable with daily rate caps
Purelymail	Metered infrastructure usage	Custom domain keys supported	Cost-focused technical users comfortable with minimal interface layering
Google Workspace	Per-user seat licenses	Single primary domain authentication per seat	Businesses requiring integrated office documents, storage, and video suites
Forward Email	Forwarding and outbound relays	Authenticated relays on paid tiers	Domains requiring inbound redirection without full standalone webmail

Each tool serves a specific architecture. A solopreneur's primary challenge is balancing outbound deliverability against setup and ongoing maintenance overhead.

The Hidden Line Items: DNS Time, Deliverability and the Cost of a Broken Domain

Technical overhead and deliverability failures carry real business consequences:

1. DNS Provisioning Overhead

Each sending domain requires foundational DNS records: SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), DMARC (Domain-based Message Authentication, Reporting, and Conformance), and MTA-STS (Mail Transfer Agent Strict Transport Security). Configuring five domains manually means generating, formatting, pasting, and testing separate DNS entries across registrars like Cloudflare, Namecheap, or GoDaddy. A single typo in an SPF string invalidates the entire record.

Automated protocols reduce this overhead. Services supporting the Domain Connect standard allow mail hosts to configure these required DNS records automatically via API at supported registrars, removing the need to copy and paste cryptographic keys by hand.

2. The Invisible Cost of Authentication Failure

When an outbound domain lacks an isolated DKIM key aligned with its specific "From" header, major receiving providers classify the message as high-risk. Invoices, customer proposals, and password reset links land in spam folders. The recipient rarely alerts you that your message went missing; business opportunities simply drop off.

Before moving any domain, check your current configuration using the free domain health audit. It inspects your SPF, DKIM, DMARC, and MTA-STS records instantly, displaying results without an email gate.

A simple operational rule applies: if a domain sends transactional receipts, proposals, or client communications, it requires dedicated DKIM signing. If a domain simply redirects passive traffic, basic MX routing or forwarding is sufficient.

Where FolioInbox Fits in the Calculation

FolioInbox is designed around this exact architecture: one unified mailbox that sends and receives across multiple custom domains, maintaining dedicated DKIM keys and distinct signatures for each brand, built strictly for a single operator.

Folio pricing is flat per plan rather than metered by user seats, structured by domain tiers:

Solo Plan: Configured for smaller setups of up to three domains, featuring an outbound limit of 1,000 sends per month, dedicated DKIM keys, distinct signatures, and standard email support.
Studio Plan: Tailored for portfolios of up to ten domains, including an outbound cap of 6,000 sends per month, dedicated DKIM keys, distinct signatures, and priority support.
Holding Co.

Review the service boundaries before purchasing:

Evaluation and Trial Structure: Folio has no free plan. New accounts get a 14-day evaluation: 100 sends on up to two domains, no card required; when it ends, sending stops and receiving continues. Paid plans (Solo, Studio, Holding Co.) need a card: chosen during the evaluation they start with a 14-day trial; chosen after it, they are charged the day they start.
Message Constraints: Attachments are capped at 15 MiB per message. Mail storage is included and unmetered by plan tiers.
Encryption Architecture: Folio encrypts mail in transit (TLS) and at rest, but is not end-to-end or zero-knowledge encrypted: mail is stored server-side and readable by Folio for spam filtering and search.
Hosting Model: Folio is a proprietary, hosted service; its source code is not public. Folio is a fully hosted service and cannot be self-hosted or run on your own servers or infrastructure.
Authentication: Account sign-in uses magic links or passkeys. There are no static passwords.
Setup Integration: Domain setup uses a single-screen interface. For domains managed at registrars supporting Domain Connect, all DNS records publish automatically.
Single-Operator Boundary: Folio has no shared or team inboxes, message assignment or internal notes. Solo has no seats.

If you need an internal collaboration platform to assign customer tickets across employees, this architecture is not the right choice. For verification of technical boundaries, consult the capability contract at https://folioinbox.com/.well-known/product-capabilities.json.

When the Cheaper Option Is the Wrong Option

Cost calculations should rarely override core functional requirements. You should avoid consolidating onto a single-operator platform if:

You manage staff who must share access to incoming customer tickets, assign messages, or leave internal notes.
You rely on integrated office ecosystems like Google Docs, Sheets, and Meet tied to a single identity.
You require zero-knowledge or client-side PGP encryption for strict compliance mandates.
Your technical infrastructure requires self-hosted, open-source mail stacks managed on your own servers.

Consolidating your infrastructure onto a per-domain platform makes financial and operational sense when:

You are a solo operator running between two and a dozen commercial domains.
You want each brand to send under its own verified cryptographic DKIM key and custom signature.
You face an impending renewal deadline, such as an upcoming Google Workspace renewal, or you need to reconfigure domains due to platform service deprecations like the AWS WorkMail end-of-support timelines.

Migrating five domains typically takes under an hour if your DNS records are centralized. Run through a quick decision audit: count your domains, verify that you are the sole human operating them, determine whether each brand needs outbound sending credibility, and compare the annual totals before your existing contracts renew.

Frequently Asked Questions

How much does Google Workspace cost for multiple domains if I only need one user?

If you only need one user seat, you can add secondary domains as domain aliases at no extra license fee. However, all outbound mail from those aliases routes through your primary seat's DKIM signature, which can trigger deliverability failures. If you create separate accounts to give each of five domains its own isolated DKIM key and identity, you must pay for five individual Workspace licenses.

Is there a free way to calculate email hosting costs across several domains?

Yes. You can evaluate costs based on domain count and sending volume without an email gate. You can also generate proper authentication strings using a free SPF record generator before migrating your DNS records.

Do I need a separate DKIM key for each domain I send from?

Yes. To pass modern DMARC alignment checks, the domain listed in your "From" header must match the domain validating the DKIM signature. Sharing a single DKIM key across multiple distinct domains can cause receiving mail servers at major providers and corporate firewalls to route outbound messages to spam.

What is the cheapest way to host email for five domains as one person?

The most economical path depends on whether you send or only receive. If your domains only receive mail, free or low-cost forwarding services offer a modest outlay. If all five domains must send outbound messages with aligned DKIM keys, using a flat-rate multi-domain provider or an unmetered infrastructure host like Purelymail is substantially less expensive than paying for five productivity seats.

What happens to my email if I let an AWS WorkMail account lapse?

When an AWS WorkMail organization or account lapses, Amazon terminates the receiving endpoints and rejects incoming SMTP traffic with non-delivery reports (NDRs). Stored mailboxes are marked for deletion per AWS retention schedules. You must export your mailbox contents to S3 or local storage and repoint your domain MX records before the termination date.

Do the Arithmetic Before You Renew

The calculation that matters for solopreneurs is simple: divide your total annual email software spend by the number of domains you actively run. If you are paying for full-featured enterprise productivity suites for domains where you only need clean, authenticated sending and receiving, you are subsidizing collaboration software you do not use.

Check the technical foundation of your portfolio first. Run the free domain health audit to check SPF, DKIM, DMARC and MTA-STS across every domain you own—with no email gate. Then model your portfolio using an email cost calculator for solopreneurs before your next provider invoice automatically renews.