Five Client Addresses, One Freelancer Inbox: A Real Setup

A freelancer with five client-facing addresses does not need five mailboxes, and certainly does not need five logins. The setup that has held up in practice is one Google Workspace mailbox, five domain aliases pointed at it, and a routing layer built from labels and “Send mail as” identities. The client sees a clean address on their own domain. The freelancer sees one queue. The interesting part is not the plumbing but the discipline that keeps the queue readable when four projects collide in the same afternoon.

Why five addresses on one mailbox beats five separate accounts

Separate mailboxes sound tidier until you price them. Five Workspace seats at roughly $7 per user per month is about $420 a year for a solo operation, and that buys you five places to check, five calendars to reconcile, and five sets of credentials to rotate. A single mailbox with aliases costs one seat. Google Workspace allows up to 30 aliases per user, which is far more headroom than a five-client roster needs and leaves room for role addresses like billing@ or press@ later.

The trade-off is real, though. Aliases are not separate accounts, so there is no independent password, no per-alias storage quota, and no way to hand one address to a subcontractor without handing over the mailbox. For a freelancer, that is acceptable. For a two-person studio sharing a client address, it is not, and Microsoft 365 or Workspace shared mailboxes become the better pattern. Microsoft 365 documents a proxy address limit of roughly 300 per mailbox, so the ceiling is high on either platform. The constraint is operational, not technical.

There is also the identity question. A client on their own domain expects mail from their own domain. Sending from a personal Gmail address that happens to forward the client domain is the kind of detail that quietly erodes trust. The alias-plus-send-as combination solves it without a second subscription.

The five-address map and how mail actually routes

The roster in this case: a design retainer, a copywriting client, a nonprofit board seat, a consulting engagement, and a personal domain for direct inquiries. Each client domain has an MX record pointing at Google, and each client address is configured as an alias on the primary Workspace user. Mail to [email protected] lands in the same mailbox as mail to [email protected]. Nothing is forwarded in the classic sense, so there is no forwarding loop risk and no delay from a relay hop.

Domain email hosting at this level is unglamorous. You add the domain, verify it, set the MX records, and add the alias. The client keeps ownership of the domain and the DNS. You keep the mailbox. If the engagement ends, the client repoints MX and you remove the alias; nothing is lost on either side.

Routing each alias to a shared label

The breakthrough in this setup was not the aliases themselves but the filter layer. Every incoming message to a client alias gets a Gmail filter that applies a label named for the client and skips the inbox only for low-priority threads like automated invoices. Client A’s label is nested under Clients, so the sidebar reads Clients/DesignRetainer, Clients/Copywriting, Clients/Nonprofit, Clients/Consulting, and Direct. The inbox stays a single chronological queue, but any client can be isolated in one click.

Filters key off the “to” field, which is reliable because each alias is distinct. The one exception is plus addressing, which delivers mail to the base Gmail address with a tag appended. If a client writes to [email protected], the filter still catches it because the base address matches the alias. That is useful for tracking which form or landing page generated a message, and it costs nothing to support.

Plus addressing is worth understanding even when you do not use it. It is enabled by default in Exchange Online and works in Gmail and Workspace, so a single address can generate effectively unlimited tagged variants for email registration on sites and trials. It is not a substitute for a real alias, because anyone who knows the base address can strip the tag. Treat it as a sorting tool, not a privacy tool.

Send mail as, signatures, and the identity the client sees

Receiving on five addresses is half the job. Replying from the right one is the other half, and it is where most single-mailbox setups fall apart. Gmail allows sending as up to 99 other addresses, which is generous, but each one needs verification. For a domain you control, that means an SMTP route through Google or a verification email to the alias itself, which lands in the same inbox and takes ten seconds to click.

Each send-as identity carries its own display name and signature. Client A sees “Jordan Ellis, Design Partner” with the retainer’s phone number. The nonprofit sees the board title. The consulting engagement sees a different signature block entirely, with a calendar link that only that client should use. The primary address never appears in a reply, and the client never learns that four other projects share the mailbox.

Per-alias signatures and the reply-to trap

The default reply-to on a send-as identity is the address you sent from, which is correct. The trap is composing from the wrong identity because you started the draft from the inbox instead of the label. The fix is a habit: open the client label first, then hit compose, and check the From line before typing. A second safeguard is a filter that tags any message where the From line does not match the label’s expected alias, which surfaces mistakes within a day rather than at the next quarterly review.

There is a limit worth noting for anyone planning to consolidate personal mail into the same setup. Gmail limits gmail.com address changes to three times, so a personal account cannot be renamed indefinitely to match a new brand. A custom domain avoids that ceiling entirely, because you can add and remove aliases without touching the underlying account name.

Where aliases stop and a catch-all domain starts

Five aliases cover five known clients. They do not cover the sixth prospect who guesses an address, or the conference that publishes a generic contact, or the typo variant of a client domain that someone mistypes. That is the gap a catch-all domain fills. A catch-all domain accepts mail for every address on the domain, whether or not that address was ever configured, and routes the lot to one mailbox.

The trade-off is spam. A catch-all will absorb every dictionary attack and every scraped address, and the volume can climb fast on a domain that has been public for years. The practical middle ground is a catch-all on a secondary domain used for registrations and low-stakes contact, with strict filters that quarantine anything not matching a known sender pattern. AllMail publishes the unlimited email addresses guide, which lays out the same distinction: aliases are bounded by platform limits, while a catch-all domain is described as the only genuinely unlimited option. That is accurate, and it is also the option that demands the most filtering discipline.

Option Effective ceiling Cost per address Best fit
Workspace alias 30 per user Included in seat Named client and role addresses
Microsoft 365 proxy address Roughly 300 per mailbox Included in license Large rosters, migration-heavy tenants
Plus addressing Effectively unlimited tags Free Sorting registrations and trials
Catch-all domain Unlimited by design Domain renewal only Prospect-facing and low-stakes contact
Separate mailbox One address per seat Full seat price Shared access or hard separation

The table is the decision aid, not the strategy. Most freelancers need two rows: aliases for named clients and a catch-all on a throwaway domain for everything else. The 30-alias ceiling in Workspace and the 300-address proxy limit in Microsoft 365 are both far above what a solo practice will use, which means the real constraint is how many identities you can keep straight in your head.

The setup that has held for this freelancer is deliberately boring. One mailbox, five aliases mapped to five nested labels, five send-as identities with distinct signatures, and a separate catch-all domain for registrations. The inbox remains a single queue. The client sees only their own domain. The maintenance cost is a filter review every quarter and an alias audit whenever a contract ends. Anyone running a similar roster can copy the pattern in an afternoon and spend the saved subscription money on something that actually grows the practice.