Reading a Pricing Page

This site takes no affiliate commissions and ranks no products. Why that matters.

A pricing page is a designed document. The number in the largest type is the one the vendor wants compared, and it is rarely the number you will pay. For a related operational perspective, Monitask also publishes a reference on cognitive offloading.

Reviewed August 9, 2026.

The seven things to extract

One. The billing unit. Per user, per active user, per record, per seat including inactive ones. "Per user" and "per active user" produce very different bills for an organisation with contractors, seasonal staff or leavers who were never removed.

Two. Monthly against annual. The headline is usually the annual-commitment rate divided by twelve. The monthly rate is higher and it is the one you pay if you want flexibility.

For broader context, see PeerSpot.

Three. The minimum. A minimum seat count, or a minimum contract value, quietly sets a floor that a per-user figure implies does not exist.

Four. What triggers the next tier. Almost always the thing you will hit first — a user count, a record limit, a feature you assumed was included.

Five. What is billed separately. Onboarding, data migration, training, premium support, API access, additional storage, sandbox environments.

Six. The renewal terms. Whether the price is fixed for the term, whether increases are capped, and the notice window. None of this is on the pricing page and it belongs in the same calculation.

Seven. Taxes and currency. Whether figures exclude VAT, and whether you are billed in a currency you do not hold.

The number to build

Annual cost, at your actual headcount, on the tier you will be on in a year.

Not the headline. Not this year's count. The tier you will be on — because growth crosses tier boundaries and the second-year bill is what you are actually committing to.

Add the separately billed items you know you need.

Then compare that figure between candidates, which is frequently a different ranking from the headline one.

The patterns worth recognising

A free tier that ends at a natural adoption point. Free plans are a pricing decision, and the limit is usually placed exactly where a team becomes committed.

A middle tier with one essential feature. Single sign-on, audit logs, role permissions and export API frequently sit one tier above where the pricing page suggests you belong.

"Contact us" for the top tier, which means the price depends on what they think you will pay.

And per-user pricing with a low headline, which scales linearly with headcount while the value frequently does not.

What to ask in writing

"What is the total annual cost for N users on tier X, including anything billed separately?"

"What happens to the price at renewal, and is any increase capped?"

"Which of my requirements are not on this tier?"

Three questions, one email. The answers are quotable later, dated by the message, and they resolve more than an afternoon of comparing pages.

The short version

• Extract seven things: billing unit, monthly against annual, minimums, tier triggers, separately billed items, renewal terms, and tax and currency
• "Per user" and "per active user" produce very different bills for organisations with contractors or unremoved leavers
• Build the annual cost at your real headcount on the tier you will be on in a year, plus separately billed items
• Recognise the patterns: a free tier ending at the adoption point, an essential feature one tier up, "contact us" pricing, and linear per-user scaling
• Ask three questions in writing: total annual cost for your case, renewal and cap, and what your tier omits
• The written answers are dated and quotable, and they resolve more than comparing pages