The 7 most common business email formats (and which to pick)

Choosing an email format sounds trivial. It isn't. The pattern your company picks today gets locked in for the lifetime of the business — every new employee, every signature, every business card. Pick the wrong one and you spend the next decade explaining why one teammate is j.smith@ and another is jsmith@.

Here are the seven formats real companies actually use, ranked by how well they hold up at scale.

1. first.last@company.com

The most common professional format. Used by Apple, Stripe, most consulting firms, and the majority of public companies. Reads as the person's actual name, makes business cards look clean, and is almost impossible to misread when spoken aloud.

Best for: companies that want their emails to read as human, and don't mind a slightly longer address. The default recommendation for most teams.

The edge case

Hyphens and apostrophes. Names like O'Brien or Smith-Jones need a documented rule — most teams strip the special character (obrien, smithjones) but some keep the hyphen. Decide before your first hire with one.

2. flast@company.com

Short and unambiguous. Used by Amazon (famously), many enterprise sales orgs, and most US tech companies founded between 2000 and 2010. Survives name collisions well because the first initial almost never clashes with the surname.

Best for: teams that send a lot of email and want shorter addresses. Auto-completion in CRMs and customer email platforms is faster.

The edge case

Two people with the same first initial and same surname. Pick a tiebreak rule and document it: most teams append 2 or a middle initial.

3. first@company.com

Used almost exclusively by small companies (under 30 people). Friendly, casual, instantly recognizable. Breaks the moment you hire the second Alex.

Best for: startups under 25 people who want a personal feel. Have a migration plan ready for when you grow past that.

4. first_last@company.com

Mostly seen in academic and research institutions. The underscore reads slightly less clean than a dot in print, but it's unambiguous when typed. Survives all the same edge cases as first.last with the same benefits.

Best for: universities, labs, research orgs, and anywhere addresses get printed in formal documents.

5. firstlast@company.com

The dotless version. Cleaner than flast but harder to parse for names with ambiguous boundaries — markhanson vs markha nson isn't obvious. Has fallen out of favor as company sizes grew and parsing ambiguity hurt.

Best for: rare. Pick first.last or flast instead.

6. f.last@company.com

First initial, dot, full surname. The British convention. Used by many UK firms and a chunk of European consulting. Short, scannable, and survives common first-name collisions because the surname always appears in full.

Best for: UK/EU companies, or any team that wants the surname to dominate the address.

7. first.l@company.com

First name, dot, last initial. The least common pattern — used by some consumer brands that want maximum personal feel. Suffers from the same collision problem as first@ the second you hire a Sam with a different surname starting with the same letter.

Best for: small consumer brands where the email feels like a direct line to a real person.

How to actually decide

Three questions decide it for most teams:

1. How big do you expect to get? Under 25 people: first@ is fine. Over 25: pick a format with surname.
2. Do customers spell the names back to you on calls? If yes, first.last wins because it reads as a name. If no, flast is shorter and easier to type.
3. Do you have international names with non-ASCII characters? Decide a transliteration rule upfront. Most teams strip accents (ramón → ramon) and remove hyphens.

Once you've picked, document it. A two-line note in your HR onboarding doc saves your IT team a hundred ad-hoc decisions a year.

What about reverse-engineering a company's format?

If you're doing sales outreach or hiring research and you need to guess a company's email format from one known address, the formats above cover ~95% of cases. Find one employee's email anywhere (their LinkedIn signature, a press release, a podcast bio), and you know the pattern for every other employee.

Our email address generator runs through every plausible format for any name and a custom domain in one shot — useful when you have the name and the company but not the pattern, and you want a candidate list to verify.

TL;DR: first.last@company.com if you want the safe default. flast@company.com if you optimize for short. Don't mix patterns within the same company — pick one and keep it for the decade.