Field note · 16 min read

Emcognito vs Google Workspace for portfolio operators: the multi-domain math, honestly

Google Workspace is excellent software priced for teams. Emcognito is for one operator running several businesses on several domains. The pricing math, the deliverability gaps in Workspace aliases, when Workspace genuinely wins, and a concrete migration path with real reviewer quotes from G2, Capterra, Hacker News, and the official Google Workspace community forums.

One-paragraph answer. Google Workspace is excellent productivity software priced for teams: per user, per month, billed per tenant. Emcognito WebMail is for one human running several businesses on several domains, billed flat, multi-domain by default. If you have employees per LLC and you live inside Drive / Docs / Meet, stay on Workspace. If you are one operator with three to seven brands and you want every domain in one inbox with its own DKIM signature and its own reply-from identity, Emcognito was built specifically for that shape and is roughly a third to a sixth the cost depending on how many brands you run.

The pricing math, honestly

Google Workspace lists three small-business tiers. The annual-commit numbers are the ones the marketing pages lead with, and they are what most operators actually pay:

  • Business Starter — $7 per user per month (annual) / $8.40 (flexible monthly)
  • Business Standard — $14 per user per month (annual) / $16.80 (flexible monthly)
  • Business Plus — $22 per user per month (annual) / $26.40 (flexible monthly)

Source: Google's published pricing page and the dated USD breakdown at emailvendorselection.com, page-dated 19 May 2026. Prices stepped up 17–22% in January 2025 when Gemini was bundled into all plans, and stepped again in 2026 (enterprise pricing guide, May 2026).

The question that breaks for portfolio operators is not "what is the per-user price." It is "what counts as a user when I have five businesses."

The three configurations and what each one really costs

There are exactly three ways to run multiple businesses on Workspace. Each has its own bill and its own set of compromises.

Configuration A — N separate Workspace tenants, one per business. Each LLC gets its own Workspace account, its own admin console, its own billing, its own DKIM/SPF setup, its own login. Five businesses, five solo mailboxes, Business Starter annual: $35 per month, or $420 per year. Add a Standard tier per tenant for Drive and the bill goes to $70 per month. Cleanest legal/billing separation. Worst day-to-day workflow: five Chrome profiles, five password managers, five separate inboxes that you have to remember to check.

Configuration B — one Workspace tenant, secondary domains per business. Adding a secondary domain itself is free. But each mailbox on a secondary domain is still a paid user license at the tenant's plan rate. Per Office Consumer's multi-domain explainer, citing Google's own billing: "Each user on a secondary domain consumes one paid license, just like the primary." Five mailboxes across five businesses in one tenant is still five seats — $35/month Starter, $70/month Standard. The bill is the same as Configuration A. The savings are admin (one console) and the cost is tenant isolation (one billing entity, shared policies across all LLCs — Google's own multi-domain limitations doc states "You can't directly set different policies or configuration settings for different domains").

Configuration C — one user, multiple domain aliases, "Send mail as" for outbound. This is the configuration that looks free and isn't. Domain aliases (where existing users get extra email addresses at no extra cost) are receiving-only by default. To send from those addresses, you configure Gmail's "Send mail as" feature — and each external sending domain still needs its own DKIM key set up in the admin console. Skip that step (most people do) and outbound from the alias is unsigned for the From-domain, fails DMARC alignment, and gets downranked. The community-thread evidence of this gap goes back years: "DKIM not added to 'Send mail as' addresses" and the long-running DKIM Signature Not Applied for Email Sent from Alias Domain. Configuration C is technically $7/month for one seat. It is also the configuration most likely to silently break your deliverability the day you actually need to send a brand-critical email.

Emcognito's price, for direct comparison

Emcognito WebMail bills flat per account — not per user, not per domain. Three plans cover the portfolio-operator shape. The annual cadence is the apples-to-apples number against Workspace's $7/user/month annual rate above:

  • Solo — $2.99/month annual ($35.88/year) or $3.50/month flexible monthly. Up to three domains.
  • Studio — $12/month annual ($144/year) or $15/month flexible monthly. Unlimited domains. The plan most portfolio operators end up on.
  • Holding Co. — $29/month annual ($348/year) or $39/month flexible monthly. Adds priority support and onboarding.

Live numbers on the pricing page. Per-domain RSA-2048 DKIM is generated automatically when you bind a domain — included in every plan. The math at one, three, five, and ten brands, annual on both sides since that is what most operators actually pay:

  • One brand: Workspace Starter $7/month ($84/year) · Emcognito Solo $2.99/month ($35.88/year)
  • Three brands, separate tenants: Workspace $21/month ($252/year) · Emcognito Solo $2.99/month ($35.88/year) — still inside Solo's three-domain cap
  • Five brands, separate tenants: Workspace $35/month ($420/year) · Emcognito Studio $12/month ($144/year)
  • Ten brands, separate tenants: Workspace $70/month ($840/year) · Emcognito Studio $12/month ($144/year)

The Solo-to-Studio step lands at brand four, where the three-domain cap is reached and unlimited-domain billing takes over. By brand five the bill is roughly one-third of Workspace. By brand ten it is roughly one-sixth. Studio is the per-month figure the rest of this post uses.

The portfolio-operator workflow gap

The pricing math is the headline, but it is not the reason most operators eventually move. The deeper reason is that Workspace was designed for N humans, one company — not one human, N companies.

What that means in practice, working from the most common workflow patterns:

Aliases solve receiving, not sending

Domain aliases route inbound mail at any address on the alias domain to one mailbox. That's the receiving half. The sending half is where the alias model collapses. Each sending domain needs its own DKIM key, configured per-domain in the admin console, or outbound from that address goes unsigned for the From-domain. The Google admin community has multi-year-old threads about exactly this gap (see the DKIM "Send mail as" thread linked above). For an operator running five brands where each brand's deliverability reputation is independent and consequential, the alias model is a workaround, not a solution.

"Send mail as" leaks identity across brands

Even with DKIM configured correctly per domain, the "Send mail as" UI in Gmail composes from the seat owner's account by default. Replying to a client of Brand A while you have the Brand B from-address sticky on the composer is a one-keystroke mistake. Workspace's mitigation is the dropdown picker on each compose. The portfolio-operator mitigation is being more careful than the software is. The category-correct mitigation is software that picks the right From address from the address the inbound was sent to. Emcognito does that by default; the web app and the Android app both auto-select the reply From to match the recipient address on the incoming message, with per-domain DKIM signing every time.

Five Chrome profiles is a workflow, not a product

The honest reason most multi-business operators stay on Workspace longer than they should is inertia: switching email providers is hard, and the per-tenant-per-LLC config still functions. The complaint that eventually tips them is always the same shape — one human, several domains, several logins, several bills — and it surfaces wherever solo operators gather, including Google's own Workspace community and Hacker News (both cited further down).

His solution was Configuration C (one tenant, aliases). For an operator whose brands send transactional or marketing mail and need clean per-domain sending reputation, that solution carries the deliverability tax described above. The configuration he picked is reasonable for his own ventures; it is not the right answer for every shape.

Per-LLC billing is a tax of its own

The reason serious portfolio operators run Configuration A (N tenants) instead of B (one tenant, secondary domains) is rarely cost — the bills are identical — and usually billing. Each LLC needs its own invoice, its own card, its own line item that ends up in that LLC's books. One Workspace tenant is one customer of Google, billed to one card, with one invoice line. Allocating that bill across five legal entities at the end of the quarter is the kind of bookkeeping friction that pushes operators back to N tenants and back to the $35/month Starter math.

Structured comparison, honest column for Workspace

Row by row. The Workspace column is written without caricature; the cases where Workspace genuinely wins are pulled out of this table and handled in the dedicated "When Workspace wins" section below.

Workspace vs Emcognito WebMail — capability-by-capability for portfolio operators
Capability Google Workspace Emcognito WebMail
Per-domain DKIM Supported, configured manually per sending domain in the admin console. Missing DKIM on "Send mail as" alias domains is a documented gap. RSA-2048 DKIM generated automatically when you bind a domain. No manual step.
Reply-From auto-selection Manual picker on each compose. Defaults to the seat owner's primary address. Auto-picked from the recipient address on the inbound message. Override per send if needed.
Billing per domain Per user per tenant. Cheapest legitimate path is one tenant with secondary domains, but every mailbox on a secondary domain still consumes a paid license. Flat per account. One subscription covers unlimited domains on the Studio plan.
Visual identity per domain One logo and one branding theme per tenant, applied across every domain in that tenant. Per-domain colour stripe applied to every message in the reading view; the brand a message belongs to is visible before you tap.
Multi-LLC tenant isolation Clean only if you run N tenants — one per LLC. Inside one tenant, billing and admin are unified. Single account, one bill, multiple domains. If per-LLC invoicing is a hard requirement, Emcognito does not currently issue separate invoices per domain — see "When Workspace wins."
Shared Drive / Docs / Calendar with employees Full suite. Drive, Docs, Sheets, Slides, Meet, Calendar — first-class. Email-first. Calendar and booking links ship; Drive/Docs do not. If you need a shared documents layer for employees, Workspace is the right tool.
Mobile app Gmail iOS and Android, with the maturity of a decade-old product. Android available now on Google Play (install link); iOS in progress at time of writing.
Sign-in Password plus 2FA, often SMS. Account-recovery through Google's standard flow. Magic-link plus device biometric / passkey. No password stored.
Sending infrastructure Google's own sending infrastructure. Excellent at scale, opaque when something goes wrong. Amazon SES with per-domain RSA-2048 DKIM, per-domain reputation, threading headers preserved for Gmail and Outlook reply folding.
Annual price for five domains, one operator $35/month ($420/year) for five separate Business Starter tenants, or $7/month for one tenant with "Send mail as" if you accept the alias-DKIM tax. $12/month ($144/year) on Studio. Per-domain DKIM included, five domains or fifty, same price.

When Google Workspace wins

The previous sections argue the multi-domain case is materially better on Emcognito for portfolio operators. They argue nothing about Workspace as a product, because Workspace is excellent software and pretending otherwise would be both wrong and the kind of post nobody links to. Workspace wins, plainly, in four scenarios.

You have employees per LLC, and they need to share documents. Drive, Docs, Sheets, and Slides are best-in-class, and the per-user-per-month bill is the price of admission to the most mature collaboration suite in business software. If each of your LLCs has two or three employees, you are paying for seats anyway, and the per-domain math gets diluted. At five LLCs with three humans each, you are buying fifteen seats no matter what, and the multi-domain question is a rounding error on top of the suite question. Stay on Workspace.

Per-LLC billing and admin separation is a legal requirement. If your accountant or your operating agreement requires separate invoices, separate admin posture, and separate data residency per LLC, the right answer is N Workspace tenants — not because Workspace is built for it, but because cleaner tenant isolation is the byproduct of running separate accounts. Emcognito today bills one account for unlimited domains; if you need invoices broken out per LLC, this is the configuration Emcognito does not yet match.

You are embedded in the Google ecosystem. If your team uses Google Meet for everything, your CRM integration is Google Calendar, your phone tree is Google Voice, and your file sharing is Drive links, the switching cost of moving the email layer out of the Google graph is real. Workspace's product gravity is not a marketing claim — it is genuine. If your operational stack is Google-first and you are not actively trying to leave, the per-user bill is the cost of staying in the graph.

You need enterprise-grade admin controls. Workspace's Admin Console, Vault, retention policies, audit logs, and SSO integrations are mature. If you are scaling past the solo-operator shape and you need single-sign-on, eDiscovery, or per-OU policy granularity, Workspace is the answer. Emcognito does not currently ship a Workspace-equivalent admin layer because the target user is a solo operator and the admin layer would be over-engineering for them.

If any of the four above apply, the rest of this page is irrelevant. The right move is to stay on Workspace and use Configuration A (N tenants, clean separation) or B (one tenant, secondary domains, accept the unified-admin tradeoff) and tune the DKIM keys carefully.

When Emcognito wins

The cases where the math and the workflow both point at Emcognito, in order of how often we see them in the inbox.

One operator, three to seven brands, each on its own domain. This is the portfolio entrepreneur shape. The bill is roughly $3 versus $35 per month. The reading surface is one inbox with color stripes per brand instead of three to seven Chrome profiles. The reply From is auto-picked. The per-domain DKIM is generated when you bind the domain. The category-correct features for the category-correct shape.

Solo founder with a main product, a side experiment, and a thing in stealth. This is the solo-founder shape. Per-domain DKIM matters because the main product cannot afford to have the side experiment's deliverability mistakes poison its sending reputation. Workspace's "Send mail as" with shared sending infrastructure is the configuration that loses you a customer at exactly the wrong moment. Emcognito's per-domain SES sending isolates the reputations.

Multi-LLC operator where one tenant per LLC is the bottleneck. This is the multi-LLC owner shape. The per-seat price is the most common Workspace complaint in Google's own community forum (the thread cited below), and it lands hardest here: for an operator running five LLCs with one or two mailboxes each, the per-seat tax is the dominant feature of the bill, and the multi-LLC operator feels it five times harder than a single-company customer.

Inbox-fatigue patterns. The "I have four Gmail tabs open" complaint is mundane until you notice the same complaint surface on Hacker News, Indie Hackers, and the Google Workspace Admin Community simultaneously. The thread title "I am a one person business. Why is it so expensive. I'm only using email!" is on Google's own community forum, not invented. The HN user Cordivae's 2022 thread opened with "I hate Google Workspace so much. Not because of the product, which seems fine… All I ever wanted was my own Gmail domain. I have zero use for the business functionality." — a comment that still rings true for the solo-operator shape three years and two price hikes later.

If you recognise yourself in those quotes, you are the population this product was built for.

Migration path

Even if zero readers of this post migrate today, the migration path is the part that makes the page a real resource rather than a marketing landing. The full sequence, sequenced one domain at a time:

  1. Pick the lowest-stakes domain first. The side-experiment domain, not the main brand. Mistakes on the experiment domain do not cost customers; mistakes on the main brand do.
  2. Sign up at wm.emcognito.com/login and bind the first domain. The DNS wizard generates the MX, DKIM, SPF, and DMARC records and outputs them in a format the Cloudflare / Namecheap / Route 53 dashboards understand. The first domain is free during the 14-day trial — no card required.
  3. Set up forwarding inside Workspace before flipping MX. Inside the Workspace admin for the domain you are migrating, forward all inbound to the new Emcognito mailbox. Run in this co-existence mode for 3–7 days so any in-flight conversations land in both inboxes and you can verify nothing is missed.
  4. Flip the MX records. Change the domain's MX to point at Emcognito's inbound. Propagation is usually within an hour. Inbound now lands directly at Emcognito, and you can turn off the Workspace-side forwarding rule.
  5. Export historical mail. Follow Google's Workspace data-export guide (which walks you through takeout.google.com) to export the mailbox as MBOX. Archive locally; you do not need to import historical mail into Emcognito unless you actively reference old threads (most operators don't — the historical archive lives on disk).
  6. Repeat for the next domain. One domain per week is a comfortable cadence. Domain five typically takes thirty minutes because the muscle memory is built.
  7. Cancel Workspace seats at the next renewal. Do not cancel mid-cycle — Workspace bills annual contracts up front in most configurations and the prorated refund is not worth the friction. Wait for the renewal date, then downgrade or cancel.

The whole sequence end-to-end is typically 7–14 days if you run one domain at a time. Doing all five in parallel is faster on paper and slower in practice — mistakes happen when you cannot keep track of which domain is in which migration state.

FAQ

How much does Google Workspace cost if I run multiple businesses on separate domains?

Google Workspace bills per user. If you put each business on a secondary domain in one tenant, each mailbox on a secondary domain still consumes a paid license at the plan rate ($7/user/month annual on Business Starter, $14 on Standard). If you run each business as its own Workspace tenant for billing or legal cleanliness, you pay one Workspace subscription per LLC. Five businesses with one solo mailbox each comes out to roughly $35/month annual ($42/month flexible monthly) on Business Starter.

Does Google Workspace charge per domain or per user?

Per user, not per domain. Adding a secondary domain itself is free, but every active mailbox on that domain — including info@, sales@, hello@ — consumes a paid license at your plan's per-user rate. Domain aliases (which mirror an existing user's primary address) are free; secondary-domain mailboxes with their own logins are not.

Can I use one Gmail account for multiple businesses?

You can configure Gmail's "Send mail as" to send from secondary addresses, but each external sending domain still needs its own DKIM key set up in the Workspace admin console, and missing DKIM keys on "Send mail as" aliases is a documented deliverability gap (community thread, issue tracker). Aliases are a receiving solution, not a sending one — they work for triage, not for protecting per-brand sending reputation.

What's the best Google Workspace alternative for solopreneurs with multiple brands?

If the goal is collaboration with employees, Microsoft 365 or Zoho Workplace are the strongest suite alternatives. If the goal is multi-domain email for a solo operator running two to seven brands, Emcognito WebMail is built specifically for that shape: one flat subscription, unlimited domains, per-domain DKIM, color-striped per-brand reading view. Fastmail and Migadu are also reasonable email-only alternatives — Fastmail for a polished webmail experience with custom domains, Migadu for per-domain pricing where you are hosting many domains with light traffic.

Why does sending from a Google Workspace alias sometimes land in spam?

Mail from a "Send mail as" alias still routes through your primary domain's sending infrastructure by default and only signs with the alias domain's DKIM if you have explicitly configured a per-domain DKIM key in the Workspace admin console. If the alias domain lacks DKIM, the message is unsigned for that domain, fails DMARC alignment, and gatekeepers (Gmail's own inbound included) downrank or spam-folder it. This is a documented Workspace operational gap, not user error.

Is it cheaper to run separate Google Workspace accounts or one with multiple domains?

Mathematically, one Workspace tenant with secondary domains is cheaper than N separate tenants for the same number of mailboxes — because secondary domains themselves are free to add. The tradeoff: one tenant means one billing entity (a problem if each LLC needs separate billing for accounting/legal cleanliness), shared admin policy across all domains (per Google's own multi-domain limitations doc), and shared default DKIM/SPF infrastructure unless you configure per-domain keys explicitly. Most operators who choose N tenants do so for billing-separation reasons, not cost reasons.

How do I migrate from Google Workspace to Emcognito without losing mail?

Four-step process, sequenced one domain at a time: (1) Set up the Emcognito account and bind each domain, including per-domain DKIM publishing through the DNS wizard. (2) Inside Workspace, forward all inbound for the migrating domain to the new Emcognito mailbox for a 3–7 day co-existence window. (3) Once the new mailbox is confirmed working, flip the MX records on each domain. (4) Export historical mail using Google's Workspace data-export guide (it directs you to takeout.google.com), archive locally, then cancel Workspace seats at the next renewal. End-to-end is typically 7–14 days if you run one domain at a time. See the migration section above for the full sequence.


Related reading. The mathematics page in chart form is at /compare/google-workspace. The pricing page is /pricing. The Android app, for reading the inbox between meetings, is wm.emcognito.com/android. For the shape-specific pages: portfolio entrepreneurs, solo founders, multi-LLC owners.

First 25 sends and the first domain are free, no card. Start at wm.emcognito.com/login, bind the lowest-stakes domain first, and see whether one inbox at one flat price buys you more than what the Workspace bill buys you today. Cancel if it doesn't.

§ Sources & further reading