Most companies need one mailbox per employee, plus one per shared function that a team actually works out of (like support@ or billing@), plus a small growth buffer. A 10-person company typically needs 12 to 15 mailboxes. Automated senders such as no-reply@ usually do not need a mailbox on your email platform — they are configured at your sending service instead, which is where most people overcount.
NevTan Mail is secure, ad-free business email on your own custom domain, with a built-in calendar, meetings, and role-based admin controls.
This guide gives you a formula, corrects the most common overcounting mistake, and shows how the answer changes depending on how your provider charges.
The Formula
Total mailboxes = People who need an inbox + Shared function mailboxes + Growth buffer (10–15%)
Automated senders are counted separately, and often cost nothing on your email platform at all.
Each term is explained below, along with why the third category trips up most calculations.
Step 1: How Many People Need Their Own Inbox?
Count everyone who needs to send and receive mail as themselves: full-time employees, part-time staff, interns, and long-term contractors. A workable threshold is anyone working roughly 20 hours a week or more, or anyone communicating externally on your behalf at all.
Never share one mailbox between two people. Shared credentials destroy accountability — you cannot tell who sent what — and they make offboarding impossible to do cleanly. If two people need to work the same address, that is a shared function mailbox, which is a different thing entirely and is covered in Step 2.
Use a consistent naming convention: firstname@, first.last@, or flast@. Pick one before you create the first account, because changing it later means changing every business card, invoice template, and email signature you have.
💡 Pro Tip: Create the mailbox on the new hire's first day, not their first week. Onboarding documents, calendar invitations, and tool provisioning all key off that address.
Step 2: Which Shared Functions Need Their Own Mailbox?
Shared function addresses — info@, sales@, support@, billing@, hr@ — are not tied to a person. They give customers a stable point of contact that survives staff changes, and they let whoever is available respond.
The question to ask for each one is: does a team need to work out of this inbox, or does mail just need to reach someone?
If you need… | You need | Because |
|---|---|---|
Multiple people reading and replying from one address, with shared history | A mailbox | The conversation needs to live somewhere central |
Mail simply forwarded to one person's existing inbox | An alias, if your provider offers them | No separate storage required |
One message delivered to several people's own inboxes | A group or distribution list | It is broadcast, not collaboration |
This distinction is where budgets are won or lost. If sales@ just forwards to the founder, it does not need to be a paid mailbox. If three people work the support queue together, it does.
Typical counts: a solo founder needs one or two shared addresses. A 10-person company usually needs three or four. A 50-person company might need six to eight, roughly one per customer-facing department.
Alias and group support varies significantly between providers, and it is not always documented on the pricing page — check the feature list or documentation for whichever provider you are evaluating, and confirm before budgeting around it.
Step 3: Do Automated Senders Need Mailboxes? (Usually Not)
This is the most common overcounting error. Addresses like no-reply@, notifications@, orders@, and newsletter@ send mail from your application, e-commerce platform, CRM, or marketing tool — not from your email platform.
Those services authenticate as your domain through DNS records you publish. They do not need a mailbox on your business email host to send. What they need is:
SPF authorization for each sending service, so receiving servers accept mail sent on your behalf.
DKIM keys published for each platform that offers them.
A DMARC policy covering the domain overall.
So a company sending order confirmations and a monthly newsletter typically needs zero additional mailboxes for them — just correct DNS. Our guide to domain authentication and why business emails land in spam covers publishing records for multiple senders without breaking the SPF lookup limit.
Two caveats worth knowing:
Keep bulk marketing separate from your day-to-day business mail. Sending campaigns from the same reputation as your invoices puts both at risk — see transactional vs marketing emails for how to separate them. For campaigns, NevTan Engage handles multi-channel sending from within the same suite.
And do not send marketing from no-reply@. Replies to campaigns are useful signal, and unmonitored no-reply addresses hurt engagement. Use a monitored address that routes somewhere real.
💡 Pro Tip: Audit which external services already send as your domain before adding any addresses. Publishing DMARC in monitoring mode for two weeks will show you every one of them, including the ones nobody remembers setting up.
Step 4: Add a Growth Buffer
Add 10–15% on top of your total for hiring, contractors, and needs you have not anticipated.
How much buffer you actually need depends entirely on your provider's billing model, and this is worth understanding before you commit:
Billing model | Buffer strategy |
|---|---|
Per user, per month | Keep the buffer tight — every unused seat is recurring waste |
Per mailbox, per year | Buffer matters less; annual per-mailbox rates are typically low enough that a spare mailbox or two is negligible |
Free tier with a mailbox cap | The cap is your real constraint, not cost — plan around the ceiling |
NevTan Mail uses the second and third models together: pricing is per mailbox per year, with up to 10 mailboxes at 5 GB each free forever, and paid packages supporting up to 100 mailboxes. That inverts the usual advice — the thing to plan around is not per-seat cost but the point at which you cross the free tier's mailbox ceiling.
Review quarterly either way. The reason is security as much as cost: a former employee's active mailbox is a liability regardless of what it costs.
Step 5: Document and Review Quarterly
Keep a single source of truth listing every mailbox, its purpose, and who owns it. A spreadsheet is fine. Update it whenever an account is created or removed.
Each quarter, check for:
Mailboxes belonging to people who have left — deactivate immediately, not eventually
Shared addresses nobody monitors any more
Duplicates from naming-convention drift
Storage approaching its limit on any mailbox
Whether your buffer matches your actual hiring pace
This takes about thirty minutes and prevents both account sprawl and the more dangerous problem of orphaned access.
💡 Pro Tip: When someone leaves, do not simply delete the mailbox. Convert it to a forward or transfer ownership to their manager for a defined period, then remove it. Deleted mailboxes take their history with them, and that history is often needed later.
A Worked Example
BrightPath Design is a marketing agency with 12 full-time employees and 3 regular contractors, plus a small store selling design templates.
People needing an inbox: 15.
Shared functions: They initially listed five — info@, sales@, support@, billing@, projects@. On examination, info@ and sales@ both routed to one business development lead, so those became forwards rather than separate mailboxes. projects@ duplicated their project management tool and was dropped. That left two genuine shared mailboxes: support@ (three people work the queue) and billing@ (finance and the office manager both need history).
Automated senders: no-reply@ for order confirmations, newsletter@ for campaigns, alerts@ for site monitoring. All three send from external platforms, so they needed zero mailboxes — only SPF and DKIM entries.
Total: 17 mailboxes (15 + 2), plus roughly 15% buffer = 20.
The draft version of this calculation, counting every shared and automated address as its own paid mailbox, produced 27. The difference is entirely in Steps 2 and 3 — asking what each address actually needs to do, rather than assuming every address equals a mailbox.
How Many Do You Need? By Company Type
Your situation | People | Shared mailboxes | Automated | Typical total |
|---|---|---|---|---|
Solo founder | 1 | 0–1 | 0 (external) | 1–2 |
Small business (2–10) | 2–10 | 1–3 | 0 (external) | 3–14 |
Growing (11–50) | 11–50 | 3–6 | 0 (external) | 15–58 |
Remote-first | Headcount | 3–6, possibly regional | 0 (external) | Headcount + 3–6 |
E-commerce | Headcount | 2–4 ( | 0 (external) | Headcount + 2–4 |
Start smaller than you think you need. Adding a mailbox takes a minute; untangling twenty unused ones takes an afternoon.
Why This Formula Works
The principle underneath it is separating identity from function.
An individual mailbox represents a person — it carries accountability, permissions, and a login. A shared mailbox represents a function that outlives whoever currently performs it, so customers keep a stable contact point through staff changes. An automated sender represents a system, and systems need authentication, not inboxes.
Conflating these three is what produces both overspending and disorder. Counting no-reply@ as a mailbox wastes money on nothing. Running support@ as one person's forward means the queue stops when they take leave. Sharing a personal login between two people means you cannot answer who did what.
A clean structure also makes security straightforward. When every address has a known purpose and owner, publishing SPF, DKIM, and DMARC records is a mechanical task rather than an archaeology project — and correct authentication is what keeps your mail out of spam folders. NevTan Mail includes guided setup for those records during domain configuration.
Five Mistakes to Avoid
Sharing one login between people. A security and accountability failure, and usually a terms-of-service violation. Use a shared mailbox with individual access instead.
Counting every address as a mailbox. Aliases, groups, and externally-sent automated addresses often need no mailbox at all. This is where most overcounting happens.
Leaving former employees' mailboxes active. A live account belonging to someone who no longer works for you is an open door. Deactivate on the last day.
Running business email on a personal address. No custom domain means no authentication control, no admin layer, and no ownership of your addresses — see business email on your own domain.
Ignoring storage per mailbox. For most providers, storage is the constraint that bites before headcount does. Check what each mailbox actually gets, and what expanding costs.
Frequently Asked Questions
How many business email accounts does a small business need? A business with 1–10 employees typically needs 3 to 14 mailboxes: one per person, plus one to three shared function mailboxes such as support@ or billing@. Automated senders like no-reply@ usually require no mailbox, since they send from your application or e-commerce platform rather than your email host.
What is the difference between a mailbox and an email alias? A mailbox has its own login, inbox, and storage, and is normally what you pay for. An alias is an additional address that routes to an existing mailbox, with no separate storage. Use a mailbox when a team needs to work an inbox together; an alias when mail simply needs to reach one person. Alias availability varies by provider — verify before relying on it.
Do automated emails need their own email account? Usually not. Addresses like no-reply@ and notifications@ send from external services — your store platform, CRM, or transactional email provider — which authenticate as your domain through SPF and DKIM records. They need correct DNS, not a mailbox.
How many email accounts do I need for a team of 20? Roughly 24 to 28. That is 20 individual mailboxes, three to five shared function mailboxes, and a 10–15% buffer. Automated senders are handled through DNS rather than additional mailboxes.
Is it cheaper to have fewer email accounts? It depends on the billing model. Under per-user-per-month pricing, every unused seat is meaningful recurring cost. Under annual per-mailbox pricing, the difference between 18 and 20 mailboxes is often trivial. Either way, eliminate genuinely unused accounts — the security argument holds regardless of price.
Can I use a catch-all address instead of multiple accounts? A catch-all receives mail sent to any address on your domain. It is useful for capturing typos, but it is not a substitute for real addresses: it collects large volumes of spam and makes ownership ambiguous. Use specific addresses for anything customer-facing.
How many mailboxes does NevTan Mail support? Up to 10 mailboxes at 5 GB each are free forever with your own domain. Paid packages are priced per mailbox per year and support up to 100 mailboxes, with storage tiers from 5 GB to 250 GB per mailbox. Check the pricing page for current figures, since plans change.
How often should I review my mailbox count? Quarterly. Look for departed employees' accounts, unmonitored shared addresses, duplicates, and storage nearing its limit. It is a thirty-minute task that addresses both cost and security exposure.
Conclusion
The count itself is straightforward: one mailbox per person, one per shared function a team actually works, plus a modest buffer. The judgment is in Steps 2 and 3 — recognizing that not every address needs a mailbox behind it.
Get that right and your structure stays clean as you grow. Every address has a purpose and an owner, offboarding is a defined process rather than a scramble, and your authentication records are maintainable because you know what sends as your domain.
NevTan Mail is built for this: mailboxes for your whole team created in a few clicks, role-based admin controls separating who manages domains from who manages billing, guided SPF, DKIM, and DMARC setup, TLS-encrypted connections, and no ads or data selling on any plan. Ten mailboxes at 5 GB each are free forever, so you can build the structure properly before spending anything.
Read what NevTan Mail includes end to end, compare it with Google Workspace or Microsoft 365, or create your account and set up your team's addresses today.
