What Business Email Hosting Really Costs Over Three Years
Ask three providers what business email hosting cost looks like and you will get three per-user figures. They will be roughly similar, and none of them will be your actual bill. What decides the invoice is how a provider counts a user, what happens when a mailbox fills, what you pay for someone who left in March, and what it costs to move at all. This is for the person who signs the invoice, not the person who runs the server.
The per-user price is a unit price, not your bill
Multiplying headcount by the advertised rate gives a number that is wrong in a predictable direction: always too low, and the gap widens with time.
Three variables sit between the unit price and the invoice, and none appears on a pricing page. The count: what the provider treats as a billable seat, which is rarely your payroll. The term: what the price does when your headcount changes mid-commitment. The exit: what you can retrieve, and how easily, when you leave.
Model the organisation rather than the staff list. Write down every address that must receive mail independently, add the mailboxes you will keep for people who have left, and multiply by the rate you will actually be on in eighteen months.
| Cost line | How it is usually charged | What to check before signing |
|---|---|---|
| Mailboxes | Per active user, per month | Whether aliases and shared mailboxes count as users |
| Storage | An included quota, extra sold in blocks | Whether the quota is per user or pooled, and what happens at 100% |
| Leavers | Often a full seat, sometimes an archive rate | Whether a departed user's mailbox can be converted without a charge |
| Billing term | Yearly discount, monthly premium | How mid-term hires are priced, and whether seats can be reduced |
| Migration | One-off fee, or free with conditions | Who actually runs it, and what is excluded |
| Leaving | Almost never priced | Export format, and whether IMAP stays open during notice |
You are billed for seats, not for people
A twelve-person company does not need twelve mailboxes. It needs twelve, plus info@, sales@, accounts@ and careers@, plus something for the bookkeeper who visits monthly. That is seventeen billable objects behind a headcount of twelve.
The distinction that decides the bill is between an alias and a mailbox. An alias delivers into a mailbox that already exists: no storage, no password, no separate login, and almost always free. A shared mailbox is a real mailbox with its own store, permissions and history. Providers differ on whether that is billable, and four shared mailboxes on a twelve-person team is a third again on your invoice.
The trap is the workaround. Teams that discover shared mailboxes are billable make info@ an alias onto the office manager's personal mailbox, or share one login between four people. Both cost more later. The alias sends replies from the wrong address unless send-as is configured, and breaks the day that person leaves. The shared login destroys the audit trail: you cannot say who read a message or sent a reply, and you cannot offboard one person without changing a password four people rely on.
Price shared mailboxes properly at the outset. They move business email hosting cost more than the headline rate does, and paying for them is cheaper than the cleanup.
Storage is the cost that arrives in year three
Fifty gigabytes per user reads as limitless on day one. It is not limitless in year three, because mail growth is wildly uneven across a team.
The mechanism matters. A mailbox grows with the number of messages and, far more sharply, with attachments. Someone in sales or operations receiving signed contracts, plans and photographs can add several gigabytes a year. A colleague sending short internal mail may add a few hundred megabytes. An average consumption figure therefore tells you nothing, because you do not pay by average. You hit the ceiling one mailbox at a time.
What happens at the ceiling catches people out. A full mailbox stops accepting mail. Depending on the provider, senders get a bounce or their message queues and is dropped later. Either way the user does not learn this from a warning banner; they learn it when a customer says they never got a reply. That is a commercial cost which never appears on the invoice.
Two things reduce it. Mailbox storage sold as a pooled quota beats a strict per-user one, because pooling lets eleven light users subsidise the heavy one. And set an archive policy early, moving anything older than about twenty-four months out of the primary mailbox. First confirm archived mail stays searchable from the client, and whether archive storage is included or billed separately. An archive you cannot search is a backup.
Leavers are the line item that appears at month nine
Nobody budgets for the mailboxes of people who no longer work for them, and almost every organisation pays for some. You usually cannot delete a mailbox on someone's last day: handover takes weeks, customers reply to threads that are two years old, and record-keeping obligations often outlast the job. So the mailbox stays. If your provider bills a retained mailbox as a full seat, a thirty-person company with normal turnover can be paying for four or five people who left — a permanent increase in your true cost per user.
There are three ways out, in descending order of preference. Convert the mailbox to a shared mailbox the departing person's manager monitors, which keeps the address live and the history intact. Or export it to a file, delete the account, and set an alias so the address still delivers. Or forward the address to a colleague and delete the rest.
Forwarding is the option to be careful with, because it gets mistaken for retention. Forwarding moves new mail. It does nothing about the years of existing mail in that mailbox, which disappears when the account does. If you have a retention obligation, forwarding does not meet it.
The question to ask before signing is narrow: when a user is deactivated but their mailbox is retained, what is it billed as?
Yearly billing is cheaper until you hire mid-term
The annual discount is genuine and usually worth taking. The trade-off is that it fixes your seat count at the moment you pay, and organisations do not hold still for twelve months.
Hire four people in month seven and you have two options, neither free. You add seats prorated to the existing renewal date, which is tidy but applies the discount to a partial year. Or the new seats start their own twelve-month clock — the outcome to avoid. Within two years you have three renewal dates and no single point at which you can renegotiate or leave.
The second-order problem is that seats rarely go down mid-term. Commit to forty and drop to thirty-two, and you will generally pay for forty until renewal. The rule follows directly: commit annually to the seats you are confident you will still need in twelve months — your floor, not your forecast — and add the rest as you hire.
For context, our own rates: Business Mail is
Migration costs land twice, coming in and going out
Moving in is the cost people expect and still underestimate. Moving out is the cost nobody prices, and it decides whether you are a customer or a hostage.
Coming in, the constraint is throughput. Email migration runs over IMAP, and the source provider throttles it. A 40 GB mailbox is not a forty-minute job; it can run for days, which is why any sensible migration includes a dual-delivery window where both systems receive mail. Folder structure and read or unread flags normally survive. Calendars and contacts often need a separate export. Shared-mailbox permissions almost never migrate and must be rebuilt by hand.
"Free migration" usually means a self-service tool and a documentation page, not an engineer. That is reasonable, but budget the internal hours — someone is doing that instead of their job.
The DNS cutover deserves separate attention. Changing MX records is quick; getting SPF, DKIM and DMARC right decides whether your mail lands in inboxes or in spam for the following fortnight. If you would rather not own that, choose a provider that handles it — our business email on your own domain sets up SPF, DKIM and DMARC for you.
Then ask the exit question: can you export every mailbox in a standard format, and does IMAP stay open during your notice period? A provider whose only export path is its own tool is one you cannot leave cheaply.
What a business email hosting cost looks like at Postmarrow
We publish two per-user rates and no negotiated tiers below Enterprise, so the arithmetic above is straightforward to run against us.
Business Mail is
The comparison that matters is not our email line against another provider's email line. If you already pay separately for messaging, a task tracker and a meetings tool, add those subscriptions together first: a bundled suite either removes those bills or it does not. Where it does, the saving is usually larger than any difference in the email rate. Where your team will not give up its specialist tools, buy email on its own and ignore the bundle. The full breakdown is on our pricing page for cloud and self-hosted plans.
Frequently asked questions
Do shared mailboxes like info@ cost extra?
It depends on the provider, so ask before comparing prices. An alias is almost always free. A shared mailbox with its own storage and permissions is a separate object, and many providers bill it as a seat — which on a small team can move your total by a fifth.
Is 50 GB per user enough?
For most roles, comfortably, for years. The risk is the outlier, not the average: one person receiving large attachments daily reaches a ceiling eleven colleagues never approach. Plan an archive policy before anyone gets close, and check whether the provider warns administrators at 80 per cent of quota or only the user.
Is yearly billing always cheaper?
Cheaper per seat, yes; cheaper overall only if your seat count is stable. Commit to the people you are sure you will still need in twelve months, then add seats as you hire — and confirm mid-term additions align to your existing renewal date rather than starting a second one.
What does it cost to leave a provider?
Rarely a fee, and usually a fortnight of someone's attention. The real costs are the migration window, rebuilding shared-mailbox permissions by hand, and the deliverability risk during the DNS change. Confirm at signing that you can export mailboxes in a standard format and keep IMAP through your notice period.
Does self-hosting work out cheaper?
The licence cost falls; the operational cost moves to you rather than disappearing. You take on the server, patching, backups, monitoring and — the hard one — sender reputation, because a server that lands in spam filters costs more in lost business than it saved in fees. It suits larger teams and data-residency rules, when someone's job includes running it. Our approach is on the security page.