Comparing 3+ SaaS tiers objectively — without the spreadsheet hell

Comparing SaaS pricing tiers is structurally harder than comparing products. Three vendors might each have five tiers (Free, Starter, Pro, Business, Enterprise). That’s 15 tier-options in your comparison set before you even consider add-ons and annual-vs-monthly differences. A naive spreadsheet blows up fast, and the vendor wants it to — tier complexity is a pricing strategy, not an accident.

Here’s a framework for comparing SaaS tiers that keeps the compare tractable, accounts for the psychological tricks pricing pages use, and produces a defensible answer in about 10 minutes using Phronesis.

The three pricing-page tricks

Every SaaS pricing page uses at least one of these:

The anchor tier. The highest-priced tier exists to make the tier you’re supposed to buy look reasonable. If Enterprise is $5000/mo and Pro is $500/mo, Pro feels cheap. Without the Enterprise anchor, Pro would feel expensive. Recognize this: the anchor tier is usually not a real product, it’s a price ornament.

The feature cliff. Vendors move one critical feature into the next tier up to force upgrades. API access, SSO, admin controls, audit logs — these are almost always one tier above where you’d naturally start. The pricing page doesn’t advertise this; it’s in the fine print under “available in all higher tiers.”

The usage-unit surprise. The headline price is per seat. The actual bill is per seat + per API call + per workflow + per GB of storage. Usage tiers are the single biggest gap between “what the pricing page says” and “what the first bill says.” Always ask: what are the usage units, and what are the overage rates?

A defensible comparison has to survive all three. That means evaluating tiers on the features-you-actually-need basis, not on the tier-label basis.

The framework

A weighted-criteria model for SaaS tier selection:

• Critical features present — 25% (binary: is every must-have feature in this tier?)
• Nice-to-have features present — 10%
• Total first-year cost (including usage) — 20%
• Cost at 2× current scale — 10% (your usage will grow)
• Upgrade path is graceful — 10%
• Support tier and SLA — 10%
• Data portability and exit cost — 10%
• Contract flexibility (can you cancel?) — 5%

Weights sum to 100. Notice that headline price is only 20%. The price discussion is typically 80% of buying conversations and deserves to be ~20% of the decision — because the other structural factors (features, upgrade path, exit) cost more over time.

Step 1: Build your must-have list

Before looking at any vendor’s pricing page, write down the features you need. Be specific. Not “reporting” but “monthly cohort retention reports filterable by UTM source.” Not “integrations” but “Zapier, HubSpot, and Postgres CDC.”

The list should have 5–12 items. If you have 30, you haven’t prioritized. Come back when you have a real must-have list, not a wish list.

This step is the one buyers most often skip. Without a must-have list, you’re shopping for tiers instead of for features, and every tier looks plausible. With a must-have list, most tiers disqualify themselves in 30 seconds.

Step 2: Map tiers to features, not labels

For each vendor, ignore the tier names (Starter, Pro, Business). List the minimum tier that includes every item on your must-have list. That’s the tier you’re actually evaluating, not the one on the pricing page.

Example: Vendor A’s “Pro” tier looks right at $500/mo, but your must-have list includes SSO. SSO is in Business ($1200/mo). So you’re actually comparing Vendor A at $1200/mo, not $500/mo. The pricing page tried to hide this. Your must-have list exposed it.

Step 3: Price your actual usage

Get the usage model from each vendor. Ask for three scenarios:

• Your current usage (seats, API calls, workflows, storage as of this quarter)
• Your 12-month projected usage (usually 1.5–3× current)
• Your 24-month projected usage (2–5× current)

Price each scenario. This is tedious; do it anyway. The number that comes out is the actual TCO, and it often reorders your tier ranking dramatically. A vendor whose headline tier price is 30% lower but whose usage model is 2× more expensive at scale is the wrong pick, and you wouldn’t see it without running the three-scenario analysis.

Step 4: Run the compare through Phronesis

With your must-have list, your actual-tier price, and your three-scenario usage costs, drop the three vendors into Phronesis with the weighted criteria above. The three blind analyst models will score each on each dimension and produce a ranked output.

Two things to look for in the output:

Split dimensions. If the analysts split on “upgrade path is graceful” or “contract flexibility,” that’s the dimension worth probing during your next conversation with the vendor. The split is telling you the dimension is subjectively evaluated, which means it’s where vendor marketing is doing its heaviest lifting.

Dominant losses. If a candidate loses on “total first-year cost” by a wide margin, ask whether the extra cost buys anything on other dimensions. If not, disqualify. If yes, compute the per-dollar value of the upgrade and decide if it justifies.

The renewal trap

Here’s the variable buyers almost always miss: what is the price in year 2 and year 3?

Many SaaS vendors offer aggressive first-year pricing to get you on the product. Renewal pricing is often 30–60% higher. If you budget on first-year price, you’ll be surprised at renewal. The vendor knows this — they’re pricing to the attachment cost of leaving, not to the value of staying.

Ask explicitly, in writing, what renewal pricing looks like. Two answers matter:

• What’s the pricing uplift assuming you don’t grow usage?
• What’s the pricing uplift assuming you grow usage by 2×?

If the answers are “we negotiate at renewal” (i.e., undefined), treat the vendor as higher-risk. If the answers are specific and modest (5–15% uplift), they’re trustworthy on price. If the answers are specific and aggressive (30%+), you’ve been warned.

The per-seat creep

Most SaaS vendors price per seat. Your seat count is not static. As your team grows, your per-month cost grows linearly — faster than your revenue grows in most cases. The per-seat model is designed to capture growth value from you.

Three mitigations:

Negotiate volume discounts upfront. At 25 seats, 50 seats, 100 seats — get the discount tiers in writing. Most vendors will give you this if you ask, and many hide it unless you do.

Check the “inactive user” policy. When someone leaves your company, you remove them from the tool. Do you get prorated refunds, or do you pay until renewal? A vendor that doesn’t prorate is silently expensive when you have turnover.

Look for usage-based alternatives. Some tools offer usage-based pricing alongside per-seat. If your team rarely uses the tool, usage-based is cheaper. If your team uses it constantly, per-seat is cheaper. Model both and pick.

The annual-discount math

Vendors typically offer 15–20% off for annual billing. This is real savings, but it also locks you in. Before you take the annual discount, ask:

• How confident are we that we still want this tool in 12 months?
• What’s the cancel policy? (Usually no refunds for annual.)
• What’s the upgrade cost if our usage grows mid-year?

If you’re confident on #1 and the answers to #2 and #3 are reasonable, take the annual discount. If any of the three is weak, pay the monthly premium. 18% of the annual cost is a small price to pay for optionality when the fit is uncertain.

The “free tier is a wedge” problem

Many SaaS products offer generous free tiers. The free tier is almost always a wedge — the product is usable for toy workloads but the features you actually need are paid. Budget for the paid tier you’ll need within 6 months, not the free tier you’ll start on.

The pattern applies inside your own company too. If you adopt a free-tier tool, budget a line item for the day you’ll outgrow it. Tools that reach critical mass in your team are very hard to swap out. Better to pay for the paid tier on day one and negotiate, than to scale the free tier into a critical dependency and get squeezed at the paid conversion moment.

Comparing across vendor categories

A real-world complication: sometimes the “same category” vendors are actually three different products.

Example: you’re evaluating HubSpot, Mailchimp, and Salesforce for email marketing. HubSpot is a CRM with marketing built in. Mailchimp is an email tool with some CRM features. Salesforce is a CRM with marketing requiring a $$$ add-on. These are not commensurable as-is — you have to pick whether you’re buying CRM or email-first.

If you’re tempted to compare across categories like this, your must-have list is too broad. Narrow the comparison to vendors in the same category, then compare categories at a higher level.

The 10-minute workflow

Step by step:

1. 2 minutes: Write your must-have list.
2. 3 minutes: For each vendor, map tiers to features and find the minimum tier that covers your list.
3. 3 minutes: Price three usage scenarios per vendor.
4. 2 minutes: Drop into Phronesis with the weighted criteria.

Total: 10 minutes. Output: a defensible ranking with explicit tradeoffs, plus a document you can show your CFO or your team that explains why you picked what you picked.

Compare that to the alternative: 4 hours in a spreadsheet, one vendor wins because they had the cheapest headline price, and 8 months later you discover the usage overage was 3× the quoted number. The structured workflow produces a better answer faster, and the answer survives the renewal conversation.

The broader point

SaaS pricing is a negotiation, not a decision. The vendor’s pricing page is the opening move. Your must-have list, TCO scenarios, and weighted-criteria comparison are the counter-moves. Phronesis is the tool that makes the compare tractable when you have three vendors each with five tiers each with multiple usage axes.

Don’t skip the structure because the comparison feels simple. The simpler you think it is, the more money the vendor is making from your lack of rigor.