How to read a software plan comparison table

Read a software plan table as three questions. Which tier holds the features you need? Which modules are sold separately? Which add-ons or limits apply to a team your size? Then price the plan you expect to need in a year, not just the one that fits today.

Plan comparison pages are built to sell, so they lead with the middle column and a row of ticks. The decisions that change your bill tend to sit lower down: in footnotes, in a "contact sales" cell, or on a separate add-ons page. Ten minutes with the table and a list of your real needs saves a surprise at renewal time.

Tiers, modules and add-ons: what each word means

Term	What it usually means	What to check
Tier	A bundle of features at one price level, such as a starter, standard and advanced plan	Which tier holds every feature on your must-have list
Module	A functional area, such as invoicing, projects or a sales pipeline, that can be switched on or bought on its own	Whether a module is included in your tier or charged on top
Add-on	An extra sold beside any tier: more storage, extra seats, a premium integration or priority support	Whether you need it from day one, and how it is billed
Limit	A cap inside a tier: users, records, documents, projects or API calls	What happens when you reach it: a block, a warning or a forced upgrade

Many vendors combine all four. A plan might include two modules, cap the number of users, and sell a third module as an add-on that is free in the next tier up. That is normal, but it means the cheapest column is rarely the cheapest answer.

Six things to read before you compare prices

1. The footnotes. Seat minimums, annual-billing requirements and fair-use limits often live under the table rather than in it.
2. The pricing basis. Per user, per company, flat fee or by usage. The basis decides how the bill grows as you hire; the guide to per-user, per-company and flat-fee pricing compares them.
3. The cells that say "contact sales". A feature with no listed price is usually a negotiation. Ask for it in writing before you commit.
4. Security and admin rows. Some vendors place single sign-on, audit logs or role controls in a higher tier than the core product. If your team needs them, price that tier from the start. The guide to single sign-on for a small business explains when it matters.
5. Usage-priced extras. Messages, documents sent, storage or AI usage can be metered separately. E-invoicing is a common example; see how PEPPOL access is priced.
6. The downgrade path. Moving down a tier can remove features or hide data. Many vendors keep the data but hide the screens, so ask what you keep and what you lose.

A worked way to compare two plans

Feature counts make plans look further apart than they are. A short worksheet keeps the comparison honest:

1. List your jobs. Write down the five to ten things the software must do every month, such as sending invoices, tracking time or approving hours.
2. Map each job to a row. For each plan, mark which tier, module or add-on covers it. A job no column covers is a gap, not a tick.
3. Count people, not seats. Note who needs full access, who needs to view, and who needs to submit something once a week. Some plans price these roles differently.
4. Price year two. Add the hires and the modules you expect to need within twelve months. A plan that is cheap today and jumps a tier at your next hire may cost more overall.
5. Add the switching cost. Migration, training and a slower few weeks are part of the price. The guide to what switching business software really costs lists them.

Signs a plan table is hiding something

• Ticks with asterisks. A feature marked as included "with limits" may be a cut-down version of what the next tier offers.
• Different words for the same thing. "Projects" in one column and "project tracking" in another can be two different products.
• Monthly prices that assume annual billing. Check the price if you pay month by month.
• Modules you cannot switch off. If you pay for areas your team will never use, a lighter plan elsewhere may fit better.

None of these is a reason to walk away. They are questions to ask before you sign, and a trial is the best place to test the answers: see how to evaluate business software with a free trial or demo.

Frequently asked questions

What is the difference between a module and an add-on?

A module is usually a functional area of the product, such as invoicing or projects, that can be switched on as a whole. An add-on is usually an extra on top of any plan, such as storage, seats or a premium integration. Some vendors use the words the other way round, so read what each one includes.

Should a small business choose the middle tier?

Not by default. The middle tier is often designed to look like the sensible choice. Start from your list of jobs and pick the lowest tier that covers all of them, then check whether your next twelve months push you up a level.

Are add-ons cheaper than upgrading to a higher tier?

Sometimes. One or two add-ons can cost less than a full tier upgrade, but several add-ons can cost more than the tier that includes them. Price both routes with your real team size before you decide.

What happens to my data if I downgrade a plan?

It depends on the vendor. Many keep the data and hide the screens of features you no longer pay for; some limit how much you can store. Ask before you downgrade, and export what you need beforehand if the answer is unclear.