Business email pricing: plans, fees and buying questions

Any figure quoted on a page like this is wrong by the time you read it. Prices change, tiers get renamed, and the plan that was cheapest last year moved a feature you rely on into the one above it. So this page is about the shape of business email pricing: how the bill is assembled, which parts of it grow, and how to work out your own number from your own headcount.

Do that once and you can price any offer in the category in about twenty minutes, permanently.

What to take away

• Nearly every offer in this category is built from the same few components.
• Per-seat pricing is the default in this category, and it has a simple property: your bill is a straight line through your headcount.
• The cheapest paid tier in this category is not a smaller version of the expensive one.
• Take any offer and fill this in with figures you obtain yourself, from the vendor's current published pricing.

How the bill is assembled

Nearly every offer in this category is built from the same few components. Identify them and you can compare things that look nothing alike. Where an offer uses a term loosely, the standard definitions of cloud service models are a fair reference for deciding whether two things are even the same kind of purchase.

Per seat, per month, usually with an annual option. The unit is a mailbox with a human attached. This is the headline number and the one everyone compares. It is also the one least likely to determine what you actually pay.

A commitment discount. Paying yearly is cheaper than paying monthly. The trade is flexibility: an annual commitment normally fixes your seat count for the term, so you pay for people you no longer employ until renewal. If your headcount moves a lot, the monthly premium is buying you something real.

A floor. Some offers have a minimum number of seats, or a minimum spend, or a price that only applies above a certain size. Small teams pay list price; large ones do not.

Storage. Sometimes per seat, sometimes pooled across the organization. The difference matters enormously and is discussed below.

Add-ons. Archiving, extended retention, advanced filtering, compliance and legal-hold features, additional security tooling. These are priced separately often enough that you should assume they are until you have confirmed otherwise.

Everything that is not on the price page at all. Migration, one-off setup, training, and the administrative time to run it. Real money, invisible in any comparison table.

Per seat versus flat: which shape fits you

Per-seat pricing is the default in this category, and it has a simple property: your bill is a straight line through your headcount. Predictable, and it punishes exactly one thing, accounts for entities that are not people.

That is where the shape starts to matter. Every organization needs addresses that no individual reads: a general inquiries address, a role address for invoices, an address for a department, an address for a system that sends notifications. Whether those cost a full seat is one of the most consequential pricing questions in the category, and it is rarely on the price page.

Ask specifically:

• Are aliases, extra addresses that deliver into an existing mailbox, free and unlimited, or capped, or chargeable?
• Are shared mailboxes, which several people open and work in, a licensed seat or not?
• Are distribution lists, which fan a message out to several recipients, free?
• Does a suspended or archived former employee's mailbox still consume a paid seat?

For a small business those four answers can change the bill by a large fraction, entirely independently of the advertised per-seat rate. A team of ten people might genuinely need considerably more than ten addresses, and whether that costs ten seats or thirty is decided by these answers.

Flat-rate offers exist, usually bundled with hosting or a domain. They tend to be cheap and to withhold the administrative and security features that make email manageable at any scale. That can be exactly right for a team of three and a serious problem for a team of forty.

What the entry tier usually withholds

The cheapest paid tier in this category is not a smaller version of the expensive one. It is the same mail service with the administrative apparatus removed. The pattern is consistent enough to plan around:

Commonly held back from the cheapest tier	Why you may need it
Single sign-on with your identity provider	Without it, email passwords are managed separately from everything else, and offboarding is manual
Automated user provisioning and deprovisioning	Determines whether adding and removing people is a script or a chore
Detailed audit logging, and its retention	The record of who did what, needed after any incident
Retention policy and legal hold	Required by some obligations; also the only defense against a mass deletion
Archiving beyond the standard mailbox	Where mail goes when the mailbox limit becomes the binding constraint
Advanced filtering and threat protection	The difference between a spam filter and a security control
Larger or pooled storage	See below
Support with a response commitment	Matters the first time mail stops flowing

None of that is unreasonable: those features cost the vendor money to build and run. What matters for your budget is that the requirement which forces you upward is usually a governance requirement, not a mail requirement. Teams routinely discover that they need the higher tier for one item on that list, and pay the full difference across every seat to get it.

So work out which of those you actually need before you compare headline rates. Comparing entry tiers is only meaningful if the entry tier is a tier you could genuinely use.

Storage and retention are the real cost driver

Mail volume only grows. Nobody deletes anything, attachments get bigger, and the cost of storage is the cost that compounds with time rather than with headcount.

The questions that determine what this costs you:

• Is storage per seat or pooled? Per-seat storage means a heavy user hits their ceiling while quiet colleagues sit on unused space. Pooled storage lets the organization absorb that variation. For any team with a few high-volume mailboxes, pooled is worth a meaningful premium.
• What happens when a mailbox fills? Mail stops arriving, or older mail moves to an archive, or you buy more. Each is a different operational experience and only one of them is quiet.
• Is the archive included, extra, or a separate product? Archiving is frequently sold as an add-on, and it is the add-on most likely to become mandatory.
• Does a former employee's retained mailbox consume storage, a seat, or both? Organizations that keep leavers' mail for compliance reasons often find this line growing faster than their headcount.
• What does retention actually cost? Longer retention means more storage, and sometimes a higher tier as well. If you have an obligation to keep mail for a defined period, price that period, not the default.

Set the retention period from your obligations rather than from the tier on offer. Retention attaches to a class of content rather than to a container, which is the logic behind published records control schedules, and knowing which of your mail actually carries an obligation is what turns an unbounded storage bill into a decision.

Model this over the term of the contract rather than at signing. A price that is fine at today's volume and painful at three years of accumulation is a common outcome.

What happens to the bill as you grow

Growth does not scale the bill smoothly. It moves in steps:

• Crossing a tier boundary. The move upward applies to every seat, not just the new ones. Hiring one person can raise the cost of the other forty.
• Crossing a governance threshold. Hitting the size where you need single sign-on, or audit retention, or formal offboarding, forces the same jump for a non-technical reason.
• The storage ceiling arrives before the seat ceiling. Usually two to three years in, and usually as a surprise.
• The leaver population accumulates. If you keep departed staff's mail, that population only grows.
• Mid-term additions may not get your negotiated rate. Check how seats added after signing are priced, and whether they can be removed before renewal.

The useful discipline is to price two scenarios: your team as it is now, and your team at whatever size you would consider a good outcome in three years. If the second number is unacceptable, you have learned something now rather than at renewal.

Build your own model

Take any offer and fill this in with figures you obtain yourself, from the vendor's current published pricing.

Line	What to enter
Human seats	Actual headcount who need a mailbox
Extra addresses needed	Role, department, and system addresses: count them honestly
Of those, how many cost a seat	The answer to the alias and shared-mailbox questions above
Leaver mailboxes retained	Now, and your estimate in three years
Tier required	Driven by the governance list, not by the mail features
Storage: per seat or pooled	And the ceiling that applies
Add-ons you actually need	Archiving, retention, filtering, support
Commitment	Annual saving, against the cost of being locked to a seat count
One-off costs	Migration, setup, training
Administrative time	Hours per month, at a real internal rate
Cost of leaving	See below

Then run the whole thing twice: at today's size and at your three-year size. The gap between those two numbers is the thing worth negotiating over.

Price the exit too

The cost of leaving belongs in the model, because it is the reason people stay on offers they have outgrown.

Ask before you commit: in what format can you export mail, calendars, and contacts; can an administrator run that export without the vendor's help; how long does the export take at your data volume; and what happens to your data after termination, how long you have to collect it, and what is deleted when.

An offer with an ordinary price and an easy exit is usually cheaper over five years than a slightly better price with an export process that requires a support ticket.

Where to read next

Two lines in the model are settled outside the mail product. Leavers' mailboxes and non-human addresses are counted in the administration layer, the arrangement underneath the mailbox is priced in the hosting decision, and storage bought here often duplicates storage you already hold, which the storage overview covers.

Common questions

Should we commit annually for the discount?

Not in the first year. The discount is real and so is the chance of discovering a problem in month three, and an annual commitment removes your position at exactly the moment you most need one.

Do aliases cost money?

Sometimes, and the answer varies more than any other line here. Count the addresses that no individual reads before you ask, so that the question is specific: does this number of shared and role addresses consume paid seats.

What happens to a leaver's mailbox?

Whatever you decide, it should be a decision rather than a default. Options are to convert it to a shared address, to archive it, or to delete it after a stated period. Each has a different cost and only one of them is free.

Is a cheaper offer with limited storage a false economy?

Usually, because mail volume only goes up and the moment of pain arrives without warning. Price the growth rate from your own last two years rather than from an assumption, and check what actually happens when a mailbox reaches its ceiling.