A Rule, Not a List
One convention applied across everyone, plus the role addresses that sit beside it — where enquiries land, where invoices go, who owns the ones nobody is named on.
sarah@ reads beautifully until you hire the second Sarah. The format you pick now is the one fifty people will live inside.
A single good-looking address is not the output worth having; the rule behind it is. Below: the rule itself, the stress test it has to survive, and what each format gives away.
One convention applied across everyone, plus the role addresses that sit beside it — where enquiries land, where invoices go, who owns the ones nobody is named on.
Each rule gets run against the awkward cases — two people sharing a first name, a hyphenated surname, a name that is not two words — so the break shows up now.
Every format says something to a stranger. Full name in the address makes you findable and guessable; an initial gives less away; a role address gives nothing but belongs to nobody in particular.
Three steps from a domain and a list of names to a convention you can publish.
Your domain, the people you have, and roughly how many you expect to have. Mention anything already in use that cannot be changed.
It writes out each convention in full for your actual people, runs the collision cases, sets the role addresses, and says what each option costs in privacy and in length.
Pick one and write it down, because a convention nobody recorded is not one. Save the run as a Playbook so the next hire gets an address without a discussion.
Twenty tidy addresses solve today. A convention solves the next forty hires.
The format is chosen by whoever set up the domain, usually in ten minutes, usually for themselves. It then applies to every person hired afterwards, including the ones whose names do not fit the shape it assumed. That is an organisational decision made as if it were about one inbox.
.jpeg&w=1920&q=75)
An address is not just an inbox. It is on the invoices, the cards, and it is the recovery route for every account registered with it. Getting the convention wrong is cheap for a week and expensive from then on, which is the reverse of how the decision usually feels.
.jpeg&w=1920&q=75)
There is nothing to look up here. An email address on a domain you control is available because you say it is; what matters is whether the rule behind it holds. A free provider is different, and that one you do have to try.
.jpeg&w=1920&q=75)
Once the convention exists, giving the next person an address stops being a conversation and becomes a lookup — including the awkward cases, because those were decided in advance rather than improvised on someone's first morning. Your AllyHub never starts from scratch again, so onboarding gets faster every time.
.jpeg&w=1920&q=75)
Founders setting up a domain, companies about to grow, people leaving a free provider, and freelancers building a professional front.
You bought the domain an hour ago and the mail setup wants an address before it will do anything else. Whatever gets typed into that box becomes the house style by accident, and nobody revisits it until it is already awkward.
Five people is where every convention still works. Somewhere between fifteen and fifty is where two of them share a first name, someone joins with a name the pattern did not anticipate, and what seemed obvious stops covering the room.
Moving from a personal address to your own domain is the moment people start reading you differently, and the format is what they read before the message. It is also the last easy time to choose, because nothing has been printed yet.
One person, one domain, and no colleagues to collide with — which makes the trade-off privacy rather than growth. How much of your name sits in front of the @ decides how easily a stranger guesses it and how much a scraper gets for free.
Explore more AI-powered tools across research, content, and data.

Amazon Bestsellers Scraper — pull any ranking list with rank position, ASIN, price, and rating. No code, no Amazon API, all marketplaces. Try AllyHub free.

Amazon Product Scraper — pull structured product data from any Amazon domain without code or the Amazon API. Export JSON or CSV. Try AllyHub free.

Amazon Niche Finder — start from your interests, a category, or a rival, and get underserved niches scored on demand vs competition. Try AllyHub free.
Guides on email conventions that survive the company growing.

Struggling to scrape Amazon product data without getting blocked? Learn safe, effective Amazon scraper methods using APIs, no-code tools, and Python.

Discover the 10 best Amazon competitor analysis tools used to track competitors, uncover keyword gaps, and understand why top listings outperform yours.

Discover the best Amazon SEO tools to boost your rankings, find high-converting keywords, and outpace competitors. Reviewed and ranked for e-commerce marketers.
Formats, collisions, availability, and the addresses already in use.
Usually a tool that turns your name and a brand word into twenty or thirty tidy-looking addresses. The list is the easy part; what determines whether you regret the choice is which pattern those addresses follow, and whether it still works once there is more than one of you.
Yes, for one domain. Several domains or brands at once, longer team lists, and storing the convention so it applies itself to new joiners are what the paid plans cover.
It depends which problem you would rather have. The first is short, friendly, and collides the moment two people share a name. The second scales almost indefinitely and hands a stranger your full name plus a guessable pattern for everyone else in the company. An initial and a surname sits between them and is harder to read out over the phone. There is no correct answer, only the one you thought about.
On your own domain there is nothing to check — you decide what exists. What gets flagged instead is a collision inside your own team, which is the version of "taken" that actually causes trouble. If you are naming an address at a free provider, that one has to be tried at signup.
Most produce a list and stop at the address. Here the output is the rule, written out against your actual people, stress-tested on the names that break it, and kept — so the twentieth hire gets an address the same way the second one did.