SaaS Pricing Strategy: How to Find Where Your Pricing Leaks Revenue

Most SaaS pricing strategies don't fail at the number. They fail at the structure: what the customer pays for, how tiers are cut, and whether the price can grow as the customer gets more value. A 10% price increase on the wrong structure fixes nothing. A better structure often lifts revenue per account before you touch the price.

We see the same five leaks in almost every pricing page we review. Here is how to find each one on your own page, and what to do about it.

1. The wrong value metric

The value metric is the unit you charge for. Per seat, per API call, per record, per outcome. The leak happens when that unit doesn't move with the value the customer gets. Charging per seat for a tool where one power user drives most of the value caps what you can earn from that account. Charging per API call when the customer cares about the result makes every call feel like a cost.

How to check: run your metric through the ACE test. Can the buyer verify it (Auditability)? Does your margin hold as it grows (Cost-Margin Fit)? Can you meter and bill it without custom work (Ease)? A metric that fails any of these is leaking revenue. The SaaS pricing models guide compares the options.

2. Packaging that doesn't match your segments

Tiers are often built around the roadmap: whatever shipped last goes in the top tier. Buyers don't think in features. They think in the job they need done. When tiers don't map to distinct segments, most accounts cluster in one tier and nobody has a reason to move up.

How to check: write down who each tier is for in one sentence. If two tiers describe the same buyer, or you can't name the buyer at all, the packaging is leaking.

3. Pricing cliffs that kill expansion

A cliff is a jump so large that a growing customer can't justify it. Going from $49 to $149 a month for one extra feature is the classic example. The customer stays on the lower tier, works around the limit, and eventually leaves.

How to check: look at the price ratio between neighbouring tiers. Anything above roughly 2.5x with a thin difference in value is a cliff. Fix it with a middle step or a usage add-on.

4. No expansion mechanism in the product

If revenue only grows when someone in sales asks for it, it grows slowly. Products that expand on their own build it in: usage thresholds that scale the bill, nudges when an account nears its limit, and add-ons inside a tier.

How to check: ask what happens when your best customer doubles their usage tomorrow. If the answer is "nothing, until renewal", you have no expansion mechanism.

5. Packaging, pricing model and value cycle out of line

This is the leak most teams miss, because each part looks fine alone. A Good-Better-Best structure on flat pricing keeps net revenue retention below 100%, because nothing grows between upgrades. An all-in-one package on a product where value arrives late leaves the customer nothing to expand into once they finally see the value.

How to check: map when your customer gets value (week one, month three, year one) against when your price can grow. If the price can't grow when the value does, the three are out of line.

Where to start

Fix the value metric first. Every other decision sits on top of it. Then remove the biggest cliff, because that is usually the fastest revenue you can recover. Research methods like Van Westendorp and Gabor-Granger help you set the number once the structure is right.

If you'd rather have an expert check all five for you, our Pricing Teardown does exactly this from your public pricing page. You get a private 6-page scorecard with the four fixes worth the most, within 48 hours.