Seat Minimums and Annual Contracts in Email Software

Seat minimums and annual contracts in email software are where the real price of a tool hides — not on the pricing page, but in the contract clauses underneath it. A seat minimum can force you to buy for headcount you don't have. An annual term can auto-renew past the date you meant to leave. And a true-up clause can bill the people you hire in month nine at a rate you never agreed to.

None of this is illegal or even unusual — it's standard SaaS contracting, the same shape Stripe's own billing documentation describes for any subscription business that sells by seat. The problem is that these terms sit in the fine print, not the pricing table, and they can move your real cost 20 to 40 percent from what the per-seat sticker implies. This guide walks the criteria that actually decide your bill, scores the packaging shapes email and helpdesk tools actually ship in, works through what a real team pays under each one, and names where we land on our own.

The criteria that actually matter#

Six things decide what you actually pay, and none of them show up on the page that lists the per-seat price.

• Seat minimum — the smallest number of paid seats a vendor will sell you, whether or not you have that many people.
• Seat granularity above the minimum — whether you buy the exact headcount you have, or round up to the vendor's next block.
• Contract term — month-to-month with no commitment, or an annual term with a lower rate and a lock-in attached to it.
• Auto-renewal window — how many days before the term ends you have to cancel, or the contract renews itself automatically.
• True-up terms — the rate you pay for seats added mid-term, and how often the vendor reconciles the count.
• Seat reduction — whether you can lower your paid count during an active term, or only at the next renewal.

Scoring the packaging shapes#

These are the shapes email and helpdesk software actually ships in, not a ranking of individual vendors — a mechanism like a seat minimum can attach to almost any brand, but the shape is what decides your bill.

A worked example: pricing a 7-person team three ways#

Assume three vendors charge the same per-seat list price, so the only variable is the packaging shape. A 7-person team shopping all three pays a different real price for identical software, and the gap isn't in the sticker at all.

Neither shape is free of trade-offs. The block vendor's slack capacity is a real asset once you're inside it — three more hires cost nothing until the block runs out. The exact-seat vendor never wastes a seat, but every hire is a new line on the invoice the day they start. The number that decides which is cheaper for your team isn't the list price on either page — it's how close your actual headcount sits to a block boundary, and how often you expect to cross one.

The same math changes again if your signed contract carries a true-up clause. A true-up lets a vendor bill seats added mid-term, and if your original rate came from a volume discount or a negotiated call, the true-up rate is often the full list price rather than your discounted one, until the whole contract reconciles at renewal. Read the true-up language before you assume a mid-year hire costs what your spreadsheet says it should.

Red flags to catch before you sign#

These are the clauses that turn a reasonable per-seat price into a much larger one, and every one of them is negotiable if you catch it before you sign.

• A true-up clause that never states the rate for added seats. Silence usually defaults to full list price, not your negotiated one.
• An auto-renewal notice window under 60 days. Thirty days is common and easy to miss; ask for 60 or 90 in writing.
• No language anywhere about reducing seats mid-term. If the contract is silent on removal, assume you can't, and you'll pay for people who left until renewal.
• A seat block sized to the vendor's billing convenience rather than your growth curve. Ask what happens at every headcount between where you are and double it.
• A "committed spend" minimum dressed up as a seat count. Read closely for whether you're actually committing to a dollar floor that doesn't move even if headcount does.
• A quoted per-seat rate that lives on a sales email instead of inside the signed contract. Only the number written into the contract is enforceable at renewal.

What we'd pick, and why#

For a small-to-mid-size team, the shape worth choosing is the one with the smallest fixed floor, exact seats above it, and a contract you can adjust without a renegotiation call: a low minimum so you're not buying headcount you don't have, no forced blocks so hiring one person costs one seat, and billing you can shift between monthly and annual without signing anything new.

We build AI Emaily, and that's the shape we picked for our own Team plan. The floor is three seats, where the shared audit trail and Autopilot live. Above three, you add or remove seats one at a time from the billing portal — no blocks of five, no waiting for a renewal to drop a seat you no longer need — and you can switch between monthly and annual billing whenever it suits your team, rather than being boxed into whichever one you picked at signup.

That floor is still a floor, and it's honest to say so: a two-person team that specifically wants Team's shared inbox and audit trail is still buying a third seat it doesn't have a person for. Below three people, Pro or Autopilot's single-user pricing has no seat mechanics to read at all, and is the better fit until your headcount actually crosses that line.

Every plan, including Team, starts with a 7-day free trial rather than a standing free tier, so you can test the seat math against your real headcount before any contract exists. And if what you actually need is a single enterprise agreement across hundreds of seats with dedicated procurement terms, that's not the self-serve shape we — or most of the vendors in the table above — are built to sell.