Do I need Google Workspace, or is domain email routing enough?

The comparison people are actually making

Searches that pit a mail suite against forwarding are usually asking a narrower question than they appear to: “I want [email protected] instead of a free consumer address — what is the least I have to buy?”

That is a fair question with a clear answer, and it is worth separating from the broader one. A full suite is not overpriced — it sells a great deal more than an address, and for a team that needs the rest of it, nothing here argues otherwise. But if the address is the whole requirement, a suite charges every person every month for a workplace most of them will not open.

If the requirement is “mail from my own domain, arriving where I already read mail”, routing does that completely. If the requirement includes calendars, documents or central control, routing does not do it at all.

When a full suite is clearly right

There are four requirements that routing genuinely cannot meet, and any one of them settles the decision on its own.

1. 1

   People need to book time in each other's calendars

   Shared calendaring with free/busy visibility is a suite feature. There is no routing equivalent, and improvising one with invitations is worse than paying for it.

2. 2

   People edit the same documents at the same time

   Collaborative editing, shared drives and permissions belong to a suite. Sending files back and forth is exactly the problem suites were built to end.

3. 3

   You must control mail centrally when someone leaves

   If mail lands in a person's own inbox, you cannot read it, export it, or hold it after they go. When that matters — regulated work, disputes, records requirements — you need accounts you administer.

4. 4

   Compliance requires retention, legal hold or audit

   Retention policies and audited access are administrative features of a mail platform. Routing has no mailbox to apply them to.

When routing is clearly right

Routing wins where the suite's extra features have no user, and where a second inbox would make things worse rather than better.

• Role addresses. info@, bookings@, accounts@, support@. These are not people, they do not need calendars, and paying per seat for them is paying for nothing.
• People who already live in an inbox. A partner who has used the same account for fifteen years will not check a second one, and pretending otherwise creates missed mail rather than professionalism.
• Contractors and part-timers. Someone doing two days a month needs an address on your domain and does not need a workplace.
• Families and small groups. One domain, an address each, everyone keeps their own inbox. There is no organisation to administer.
• Domains that must not go dark. An address you can repoint in seconds when a person leaves is more robust than a mailbox you have to keep paying for.

The part people get wrong: replying

Routing delivers mail addressed to your domain into an inbox someone already has. Replying from that inbox as your domain address is a separate step, and it is the part that decides whether the whole arrangement feels professional or improvised.

Set up properly, the recipient sees your domain address and nothing else — the reply looks exactly as it would from a full suite. Set up badly, or not at all, the reply goes out from the personal address, which tells every customer what your arrangement is and often loses the thread.

Deciding without migrating anything

This decision does not have to be made on paper, and it does not have to be made all at once. Both options can run on the same domain simultaneously, which means the honest test is cheap.

1. 1

   Answer the four suite questions first

   Calendars, documents, control of departing staff, compliance. A yes to any of them means you are buying seats for at least some people, and the only remaining question is how many.

2. 2

   Count the addresses that are not people

   If the list is short, this decision does not matter much. If it is long — and it usually is — that is where the cost difference lives.

3. 3

   Try one role address, free, on your real domain

   Not a trial account on a test domain. bookings@ or hello@ on the domain you actually use, delivering to the inbox you actually read, for a fortnight.

4. 4

   Test the reply, not just the delivery

   Send a reply as the domain address and look at what the recipient sees. That is the experience your customers will have, and it is the thing worth judging.

5. 5

   Then decide, with evidence

   Keep seats for the people who opened the calendar and the documents. Route everything else. Nothing about this is irreversible.

What it costs to change your mind later

Both directions are possible. They are not equally cheap, and the asymmetry is worth knowing before you choose rather than after.

The practical consequence is a small asymmetry in how to hedge. If you are unsure, starting with routing and adding seats later costs you very little. Starting with seats and removing them later is also fine — provided you export before the licence lapses, which is a thing people intend to do and then discover is much harder once the account is gone.