A pricing page is a sales document, arranged so the smallest number is the one you see first. That number is typically per seat, per month, billed annually — three qualifiers doing quiet work behind it. This is for anyone about to move a team off a free plan, and it ends with a way to compute what you would actually be committing to rather than a recommendation.
The verdict
Ignore the headline number. The figure that should decide this is your committed annual cost: the seats you would really pay for, at the lowest tier that contains the feature you actually need, on the billing term you can actually hold to, plus whatever your usage costs above the included limits. Work that out before you compare tools. The tool with the lower per-seat price can land higher on that line.
| What the page shows | What to price instead |
|---|---|
| Per-seat price | Seats you'll actually pay for |
| "Save with annual" | Discount vs. odds you switch |
| Included usage | Cost at your real volume |
| Tier feature list | Tier holding your must-have |
Per seat, when half your seats barely log in
Per-seat pricing treats seats as interchangeable. On a working team they aren't. A few people live in the tool; others open it once a week to read something someone else made.
Four questions decide what that costs you:
Is there a cheaper role? Viewer, guest, and read-only seats are sometimes free, sometimes discounted, sometimes not offered. If viewers are free, the per-seat price matters less than your count of editors — and your real question becomes who genuinely needs to edit.
Are seats named or concurrent? A named seat belongs to a person. A concurrent seat is a shared key: five occasional users can share fewer seats if the vendor allows it. Most modern SaaS is named, but the exceptions are worth finding.
Is there a seat minimum? Some tiers start at a floor. A team below that floor pays for seats it will not fill.
What happens when someone leaves mid-term? Adding a seat mid-term is often prorated and charged immediately. Removing one is frequently not refunded — the seat stays paid until renewal, or converts to a credit. This detail sits in the billing FAQ or the terms of service rather than the pricing page.
Per month against per year
The annual discount is priced against the odds you leave. You pay up front for months you may not use, and the discount is what the vendor charges you for giving up the option to walk away.
You can settle it with one multiplication. Take the discount on the page as a decimal — call it D. Annual billing pays off if you stay longer than 12 × (1 − D) months. Anything shorter and the monthly plan would have cost you less, because the unused months are money you don't get back.
So the question is not "is the discount good." It's whether you would confidently still be using this tool past that month. If you are mid-migration, mid-reorg, or evaluating two tools in parallel, monthly costs more per month and buys you the right to be wrong.
Two things to check before signing an annual term: the notice period for cancellation before auto-renewal, and whether the price you're quoted is the price at renewal. Introductory rates that step up in year two are common enough to be worth a search of the terms.
Usage limits are a second price
Above the seat price sits a meter — storage, API calls, automation runs, records, contacts, minutes, build hours. Find the meter closest to your actual workload and price that, because it's the one that will move.
- Where is the ceiling? Per workspace, or per seat? A per-seat allowance grows with the team; a per-workspace one doesn't.
- Does it reset? A monthly allowance and a standing cap behave differently under a busy quarter.
- What happens at the ceiling? A hard stop, a throttle, a per-unit overage charge, or an automatic bump to the next tier. A hard stop is a schedule risk. An overage is a budget risk. Decide which one you'd rather explain.
- What is the overage rate? If the page doesn't state it, that's the question to ask before you buy, not after your first spike.
The feature held one tier up
Vendors put the gate where a customer becomes serious: single sign-on (SSO, letting people log in with your company account), granular permissions, audit logs, API access, admin controls, guaranteed support response times.
The cost of clearing that gate is not the price difference between tiers. It's the difference multiplied by the seats on the plan and by twelve months — because tiers apply to the whole workspace, not to the one admin who needs the audit log. A single compliance requirement can double the bill for people who will never notice the feature.
That reframes the question. Is the feature available as an add-on rather than a tier? Is it a hard requirement from your security review, or a preference you can defer? If it's a requirement, your tier is already decided and you're only comparing vendors at that tier.
The costs that aren't on the pricing page
Implementation or onboarding fees. Migration help. Sandbox or extra environments. Priority support sold separately. Invoicing instead of card payment, which some vendors gate behind a minimum spend. Tax shown or not shown. And the exit cost: what an export actually gives you, in what format, and whether the structure survives it.
The one line to compute
Fill this in for each tool, on paper, before you look at a pricing page again:
- Editor seats you'd pay full price for
- Plus viewer or guest seats that aren't free, at their rate
- At the price of the lowest tier that includes your must-have feature
- Times the billing term — use the annual figure printed on the page rather than assuming twelve times the monthly rate
- Plus expected overage on the meter closest to your workload
- Plus one-time fees
That's your committed annual cost. Then divide it by the number of people who will open the tool in a given week. Compare tools on cost per active user. It's a less flattering number than the one on the page, and it's the one you're actually signing for.
Who should skip this
You're on a free tier that fits. The arithmetic costs more time than it saves. Revisit when you hit a limit, not before.
Your team is about to change shape. If you're hiring, merging teams, or reorganizing, the seat count you'd compute today is fiction. Stay monthly until it settles.
The feature is mandated. If your security review requires SSO, the tier is chosen for you. Skip the tier analysis and spend the effort comparing vendors at that tier instead.
The annual bill is small next to what the problem already costs you. If the tool replaces something you're paying for in another line item, price the difference, not the tool.
Next step
Open the pricing page for the tool you're closest to buying and write down one number: committed annual cost, at the tier that holds your must-have feature. If you can't fill in a term of it — the overage rate, the renewal price, the rule for a seat that leaves mid-term — that's the email to send to their sales or support before you commit, not after.