The team had branded addresses, a Gmail habit, and a growing Workspace bill. They did not want a new workflow. They wanted the same workflow with less overhead.
They used four role-based addresses: founder@, billing@, sales@, and support@. Only the founder needed a true mailbox. The other three were routing rules that landed in one inbox.
The old setup
Workspace handled their addresses, but most people still lived in one inbox. The company was paying for mailbox infrastructure that nobody used as a true standalone mailbox.
- Each alias had a paid seat behind it.
- Replies bounced between tabs and accounts.
- Cost scaled with headcount, even when usage did not.
Why they left
- Mailbox cost grew with headcount.
- Most addresses were aliases, not real inboxes.
- The team wanted to keep Gmail as the daily workspace.
- They only needed one place to read and reply.
What changed
| Before | After |
|---|---|
| Each role had a mailbox | One inbox received the aliases |
| Users jumped between accounts | Users stayed in Gmail |
| Pay per seat | Pay for routing only |
Forward handled the branded addresses. Gmail stayed the place where replies happened. Customers saw the same domain in the From line, so the change was invisible to them.
Migration rules
- Keep only the mailboxes that truly need storage or separate logins.
- Move role addresses to forwarding rules first.
- Set send-as for the aliases the team replies from most.
- Test each alias with an external sender before canceling seats.
When this works
This pattern works best for small teams, agencies, and founders who live in one inbox. It does not fit teams that need deep collaboration inside the mail product, heavy shared-drive usage, or strict inbox separation for compliance.
Results
- Lower monthly spend.
- Fewer things to manage.
- Same public email identity.
- No retraining for the team.
The lesson was simple: if you only need routing, you do not need to buy the whole mailbox stack. Keep the inbox. Drop the seat tax.
Rule of thumb: if an address exists for brand or function, forward it. If it needs storage, permissions, or separate retention, keep a real mailbox.