firstname@ vs firstname.lastname@: An Email Format That Scales to 50

The address format you pick with three employees is the one you will still be explaining with fifty. Change it later and every business card, signature, CRM record and mailing-list subscription has to move with it. This guide compares the common formats on the criteria that matter as you grow, gives a decision rule, and shows how to migrate if you already chose badly.

Quick answer

Use firstname.lastname@ as the standard from the day you have two employees, and give every person a firstname@ alias while it is still unique. That combination gives you short, friendly addresses today and a collision-proof rule tomorrow. Only very small teams that will never grow past ten should stay on firstname@ alone, and initials-only formats are best avoided outside law and accountancy firms where they are already the norm.

The formats compared

• firstname@ (amara@) — shortest and warmest; collides as soon as you hire a second Amara; hard to guess for outsiders, which cuts spam but also cuts legitimate cold contact.
• firstname.lastname@ (amara.ncube@) — the most common corporate standard worldwide; easy to guess from a LinkedIn profile; collides only on identical full names; slightly long on business cards.
• firstnamelastname@ (amarancube@) — same guessability as the dotted form, but harder to read aloud and easy to mistype.
• f.lastname@ or flastname@ (a.ncube@, ancube@) — compact; collides when two people share a surname and initial (common in many countries); reads impersonal.
• initials@ (an@, ajn@) — traditional in professional practices; collides constantly, leaks nothing to guessers, unreadable to customers.
• lastname.firstname@ — used in some German, Japanese and Hungarian companies; confuses international contacts, avoid unless it is your market's norm.

Decision criteria that matter at 50 people

1. Collision handling: what happens with two people called John Smith? Have a written rule before it happens (e.g. add the middle initial: john.a.smith@, never a number).
2. Guessability: sales and press contacts should be able to derive an address from a name. That argues for firstname.lastname@ and against initials.
3. Readability over the phone and on WhatsApp: dots and full words survive dictation; runs of initials do not.
4. Leavers and re-hires: when amara@ leaves, the alias must be reassigned or retired. With firstname.lastname@ as the canonical address you can simply retire the short alias.
5. Regional names: many names have multiple spellings or no surname convention that matches Western forms. Let people choose the transliteration they use elsewhere, and keep the same rule for everyone.
6. Mailbox count and cost: on OquMail the free plan covers 15 mailboxes across 3 domains, and aliases such as firstname@ cost nothing extra, so the alias-plus-canonical approach fits a small team without a bill.

Write the rule down

Email address standard - [Company]

Canonical address: firstname.lastname@[yourdomain].com
  - Lowercase, ASCII letters only, no accents (e.g. jose.nunez@, not josé.nuñez@)
  - Hyphenated surnames keep the hyphen: mary.okoro-adams@
  - Preferred first name is allowed if used consistently at work

Short alias: firstname@[yourdomain].com
  - Granted while unique. First person to hold a first name keeps it.
  - Retired, not reassigned, when that person leaves.

Collisions: identical full names add the middle initial (john.a.smith@).
  Never append numbers (john.smith2@).

Role addresses (hello@, billing@, careers@) are shared mailboxes, never a person's canonical address.

Leavers: mailbox converted to forward to the manager for 90 days, then to an auto-reply for 90 days, then deleted.

How to migrate an existing team

1. Create the new canonical address for each person as a mailbox and keep the old address as an alias into it. Nobody loses mail on day one.
2. Update signatures, website team page, CRM user records and the invoicing tool's sender address in one afternoon.
3. Ask each person to send one "my address has changed" note to their top twenty contacts and to update their LinkedIn contact info.
4. After six months, review the old aliases. Keep any that still receive genuine mail; retire the rest.
5. Add the standard to your onboarding checklist so every new hire is created the same way on their first day.

Mistakes teams regret

• Using nicknames as canonical addresses (bigmike@) and then having to explain them to enterprise clients.
• Appending numbers on collision (sarah2@), which tells everyone that Sarah is the second Sarah.
• Letting the founder keep a personal Gmail as their "real" address while everyone else is on the domain.
• Reassigning a leaver's firstname@ to a new hire, so the new hire receives the old employee's personal and confidential mail.
• Mixing formats because two managers set up their own teams differently; fix it now, before it is 50 people.

Common questions

Is firstname@ unprofessional?

No. It is friendly and works well in small companies. The problem is not tone but collisions and reassignment, which is why the recommendation is to keep it as an alias rather than as the canonical address.

Should executives get different formats?

No. One rule for everyone is easier to explain and harder to socially engineer. A CEO can have ceo@ as an additional role alias if you want a public leadership address.

What about people with one name or very long names?

Let them choose a form they are comfortable with, apply the same rule about lowercase ASCII, and record the exception in the standard so the next administrator does not "fix" it.