.jpeg)
Business email addresses look varied, but they rarely are. Behind almost every work address is one of about ten naming patterns, and just two cover roughly three-quarters of B2B: first.last@ and flast@ (jordan.lee@ and jlee@). Whether you are setting up addresses for your own company or trying to reach one specific person, that predictability is the whole story.
It cuts two ways. When you are setting up your own email, the patterns tell you which format to standardize on so your team looks consistent and colleagues stay easy to reach. When you are trying to reach someone else, the same patterns mean their address is usually guessable from their name and their company's domain, if you know which format that company uses and can confirm you got it right.
This guide covers both. We list the ten common formats with examples, the role-based addresses every business should own, and which patterns enterprises use versus startups, drawing on a study of 336,782 B2B addresses. Then the part most readers came for: how to predict a contact's address from their name, and why a prediction stays a guess until it is verified, especially at the large companies where catch-all domains quietly defeat ordinary checks.
TL;DR: Business email addresses look varied but rarely are: about ten naming patterns cover B2B, and two dominate, first.last@ (jordan.lee@, 47.7%) and flast@ (jlee@, 26.8%), together roughly three-quarters of all addresses; first@ suits small teams (8.1%), and about 8.6% follow no name-based rule. Role addresses like info@, support@ and sales@ are for receiving, not cold sending. Formats get more predictable as companies grow: first.last@ reaches 74.2% at 10,000+ staff, while the informal first@ peaks around 17% at tiny teams. To reach one person, generate candidates from their name and domain, rank them by company size and industry (large firms almost always first.last@ or flast@), then verify the top guess before sending, because a wrong guess bounces and bounces damage sender reputation. The catch is that the biggest, easiest-to-predict companies cluster catch-all domains (our Fortune 500 study: 47% catch-all, 69% catch-all or gateway-fronted), where an ordinary check accepts every guess and confirms nothing. Conclusive catch-all verification tests whether the specific mailbox exists, turning a ranked guess into a real valid or invalid answer.
What is a business email address format, or naming pattern?
A business email address format, also called a naming pattern or naming convention, is the consistent rule a company uses to build every employee's address from their name. Choose a rule like first.last@, and Jordan Lee becomes jordan.lee@company.com, Priya Shah becomes priya.shah@company.com, and every future hire follows the same shape.
Companies standardize for practical reasons, not aesthetics. A single rule makes creating each new mailbox automatic, lets employees reach a colleague they have never emailed by guessing the pattern, and avoids name collisions as headcount grows, which is why larger firms lean on formats that include the last name. The side effect, and the one that matters if you do outreach, is that a consistent internal rule is also a predictable external one.
The 10 business email address naming patterns (with examples)
Here are the ten name-based formats you will actually run into, each with an example using the name Jordan Lee at company.com. The share column comes from Sendburg's analysis of 336,782 B2B addresses, the clearest recent read on how common each one is.
One caveat that sits outside these ten: about 8.6% of business addresses follow no name-based rule at all. They are aliases, shared inboxes, and custom conventions that no pattern predicts, which is worth remembering when you guess, because not every address is guessable.
The two formats that dominate B2B (first.last@ and flast@)
Two patterns do most of the work. first.last@ (jordan.lee@) is the single most common at 47.7%, and flast@ (jlee@) follows at 26.8%. Together they account for roughly three-quarters of all B2B addresses.
Both win for the same reason: they are unambiguous and they scale. Including the full last name keeps collisions rare, so a growing company seldom has to break its own rule, and anyone can rebuild a colleague's address from their name alone. If you had to bet on one format for a contact you cannot look up, first.last@ is the bet, and flast@ is the runner-up.
Other personal patterns you will encounter
The long tail is small but worth recognizing. first@ (jordan@) is the informal favorite of small teams and startups, and at 8.1% it is the third most common overall. After that the numbers fall away fast: firstlast@ and first_last@ (2.3% each) are just first.last@ without the dot or with an underscore, f.last@ (2.1%) compresses it further, and last@, last.first@, first.l@, and first-last@ together make up only a few percent, surfacing in formal industries, in systems built around long surnames, or as one-off conventions. You will rarely guess these first, but you should know them when you see them.
Role-based and company email address examples
Personal addresses are only half of a company's setup. The other half is role-based addresses: shared mailboxes owned by a function rather than a person, so they survive turnover and let a team share the load. These are the "company" addresses customers recognize.
The common set:
- info@: general inquiries, the front door that goes on your site, invoices, and directories.
- hello@: a friendlier alternative to info@, common with consumer and startup brands.
- support@: customer questions and issues, the address you print in help docs.
- sales@: new business, quotes, and partnerships.
- billing@: invoices, payments, and vendor paperwork.
- contact@ and team@: general or small-team catch-alls when you would rather not point at one person.
Pick a small set and publish them consistently. Two or three (usually info@ or hello@, support@, and billing@) cover most businesses. Treat each as a commitment, since anything sent to support@ is something a customer expects answered, so publish only the ones you will actually staff.
One rule matters for outreach: role addresses are for receiving, not cold sending. Run a cold campaign from info@ or sales@ and you invite trouble, because receiving systems treat mail from generic role addresses with extra suspicion, and the address carries no individual sender reputation to lean on. Publish role addresses for inbound, and send outreach from a real person's address.
Which patterns do enterprises use versus smaller companies?
The most useful fact for predicting an address is that formats get more predictable as a company grows. In the same Sendburg data, the share of employees on first.last@ climbs steadily with headcount.
At enterprises with 10,000 or more staff, nearly three in four addresses follow first.last@, almost double the rate at companies of 1 to 10. Small teams are the mirror image: the informal first@ sits on roughly 17% of addresses at 1-to-10-person companies and all but vanishes at enterprise scale. The practical rule is simple. The larger your target company, the more confidently you can predict its format, usually first.last@, occasionally flast@.
There is a catch that runs the other way, and it is one we have measured ourselves. The same large companies are where catch-all domains and security gateways cluster; our study of the Fortune 500 found the majority of those domains configured exactly that way, and that is where a confident guess becomes hard to confirm. So enterprises are the easiest place to predict a format and, at the same time, the hardest place to prove you got it right. We come back to why, and what to do about it, below.
How to predict a business email address from a name
Put the patterns to work and you can usually reach someone from just their name and where they work. The method is three steps: generate the candidates, rank them, and confirm the winner.
Build the likely patterns from a name and domain
Start with two inputs: the person's first and last name, and their company's email domain (usually the same as its website, so Jordan Lee at company.com). Then drop the name into the common formats to generate candidates:
- jordan.lee@company.com (first.last)
- jlee@company.com (flast)
- jordan@company.com (first)
- jordanlee@company.com (firstlast)
- j.lee@company.com (f.last)
- jordan.l@company.com (first.l)
and so on through the patterns above. This is what email-finder tools call permutation: one name and domain become a short list of realistic guesses. Doing it by hand is fine for a few contacts; for more, a permutation tool builds the list in seconds.
Narrow the candidates by company size and industry
A list of ten guesses is not a prediction. Rank them. Company size does most of the ranking for you, as we just saw: at a large enterprise, lead with first.last@ and flast@ and you are usually right, while at a small startup first@ jumps up the list. Industry nudges it too, with formal fields like law and finance skewing toward first.last@ and the occasional last.first@, and small tech teams leaning informal. Ranking turns ten blind guesses into one or two confident candidates, which is the difference between reaching someone and spraying their entire domain.
Verify before you send, because a guess is not an answer
Ranking gets you a likely address, not a confirmed one, and that gap matters. Send to a wrong guess and it bounces, and bounces are what damage your sender reputation and push future email toward spam. So the final step is non-negotiable: verify the address before you send anything to it. A verification check confirms whether the mailbox actually exists, turning your best-ranked guess into a real answer or telling you to move to the next candidate. There is one situation where ordinary verification cannot do that cleanly, which is exactly what the next section is about.
Why catch-all domains make standard verification unreliable, and how to resolve it
Here is the problem the whole predict-and-verify workflow runs into. A catch-all domain is configured to accept mail sent to any address at that domain, whether or not the mailbox exists. So when you test your best-ranked guess against a catch-all domain, the server says "accept", and it would say "accept" to jordan.lee@, jlee@, and total-nonsense@ alike. An ordinary verification check reads that "accept" as valid and reports success for every candidate, which means it confirms nothing.
That turns your careful ranking back into a coin flip. You know the format is probably first.last@, the server accepts it, and you still cannot tell whether jordan.lee@ is a real person or an address that quietly bounces into a void after you send.
This is not a rare edge case, and it clusters exactly where you most want to reach people. In our own study of the Fortune 500, 47% of those companies run catch-all domains, and 69% are catch-all, gateway-fronted, or both. The largest, highest-value companies, the ones whose formats are easiest to predict, are also the ones most likely to accept every guess you make. Prediction gets you to the door; catch-all is the reason the door tells you nothing.
Resolving it takes more than a standard check. Conclusive catch-all verification goes past the "accept" to test whether a specific mailbox actually exists, returning a real valid-or-invalid answer instead of a blanket “catch-all”. That is what turns a ranked guess into a usable contact on the domains where standard verification gives up, and it is where Allegrow fits in this workflow: not in generating the patterns or ranking them, but in confirming the one you land on.
Common mistakes with business email addresses
Whether you are creating addresses or chasing them, the same handful of mistakes cause most of the trouble.
- Mixing formats within one company. When the founder is jordan@ and everyone else is j.lee@, addresses become unguessable and the company looks disorganized. Pick one pattern and apply it to everyone.
- Decorating with numbers or nicknames. jordan_lee2@ or jlee1997@ reads like a personal account from another era. Solve a name collision with a middle initial or a format switch, never a number.
- Using a free domain for business. A @gmail.com or @outlook.com address quietly costs you trust in sales and support conversations. Send from your own domain.
- Cold-sending from a role address. info@ and sales@ are for receiving; running outreach from them invites spam filtering and carries no personal sender reputation to lean on.
- Trusting an unverified guess. A predicted address is a hypothesis. Emailing it without verifying is how bounce rates climb and sender reputation slips, especially on catch-all domains.
Conclusion
Business email addresses are far more predictable than they look. About ten patterns cover the field, two of them (first.last@ and flast@) account for roughly three-quarters of B2B, and the larger the company, the more heavily it standardizes. That predictability works in both directions: it tells you how to build a clean, consistent address for your own business, and it lets you reconstruct a contact's address from little more than their name and their domain.
The limit is the last step. A predicted address stays a guess until it is verified, and on catch-all domains, which our Fortune 500 data shows cluster at the biggest companies, an ordinary check cannot tell a real mailbox from an accepted-but-empty one. Prediction narrows the field; verification is what confirms the answer.
If you are predicting addresses to reach real people, that final check is the part worth getting right. Start a free trial of Allegrow to verify your predicted contacts, including the catch-all and enterprise domains where guessing plus a basic checker falls short, so what enters your outbound is confirmed rather than assumed.
Frequently asked questions about business email address formats
What is the most common business email address format?
first.last@ (jordan.lee@) is the most common business email format, used by 47.7% of B2B addresses in Sendburg's study, followed by flast@ (jlee@) at 26.8%. Together those two cover roughly three-quarters of all business email addresses, which is why first.last@ is the safest guess for any contact.
What are examples of professional email address formats?
The main personal formats are first.last@ (jordan.lee@), flast@ (jlee@), first@ (jordan@), firstlast@ (jordanlee@), f.last@ (j.lee@), and last.first@ (lee.jordan@). first.last@ is the default at most companies; smaller teams lean on first@. The examples table above lists all ten.
What role-based email addresses should a business have?
Most businesses need two or three: info@ or hello@ for general inquiries, support@ for customer issues, and billing@ for payments, plus sales@ if you field new-business questions. These are for receiving, though. Do not run cold outreach from them, since receiving systems treat role addresses with extra suspicion.
How do I find or predict someone's work email?
Take the person's name and company domain, generate candidates across the common formats (first.last@, flast@, and so on), then rank them by company size and industry, since larger firms almost always use first.last@ or flast@. Finally, verify the top candidate before sending, because an unverified guess bounces.
Can you guess a business email address reliably?
You can predict the likely format with good odds, especially at large companies that standardize, but a prediction is not a confirmation. Always verify a guessed address before emailing it. On catch-all domains the need is greater still, since the server accepts every address and an ordinary check cannot tell which is real.
Why do my guessed emails bounce?
Guessed emails bounce for three reasons: the wrong pattern, a mailbox that does not exist, or a catch-all domain hiding an invalid address behind an "accept". Verifying before you send prevents all three. It matters most at big companies: in our Fortune 500 study, 47% run catch-all domains and 69% are catch-all, gateway-fronted, or both.
Do enterprises use different email formats than small companies?
Yes. Enterprises standardize heavily on first.last@ (74.2% at companies with 10,000+ staff in Sendburg's data) with flast@ second, while small companies and startups often use the informal first@. The larger the company, the more confidently you can predict its email format.
What is the most common email format at startups?
Even at startups, first.last@ is still the single most common format, on about 38% of addresses at companies with 1 to 10 employees in Sendburg's data. The difference is that the informal first@ (jordan@) is far more common at that size, roughly 17% and about four times its enterprise rate, so at a small startup first@ is a realistic second guess in a way it never is at a large company.
.jpg)
