How to Price a SaaS Product for Growth: A Proven Playbook

How to price a SaaS product for growth (without guessing your way there)

A founder once sent me his pricing page with a note that said, "I think we're too cheap, but I'm scared to touch it." His product converted fine at $19/month. His churn was brutal. He'd raised a seed round, hired two engineers, and was burning through runway faster than his MRR could cover. He wanted me to tell him the magic number.

There is no magic number. But there is a process — and most SaaS teams skip it because pricing feels like a decision you make once, not an experiment you run continuously. In my experience, pricing is the single highest-leverage growth variable you control, and you are almost certainly leaving money on the table if you haven't revisited it in the last six months.

Here's how to actually price a SaaS product for growth, from willingness-to-pay research through the metrics that tell you whether it's working.

Why pricing drives growth more than features do

A feature launch might move conversion by a few percentage points. A pricing change can move it by double digits. I've watched a 30% price increase on a mid-tier plan produce better retention, because the customers who stayed were the ones who actually needed the product — not the ones who'd signed up because it was cheap.

Pricing is a filter. It tells the market who you're for.

The growth math nobody wants to do

Say you have 1,000 customers at $29/month. That's $348,000 in annual recurring revenue. Now say you raise the price to $49/month and lose 20% of customers. You now have 800 customers at $49. That's $470,400 ARR. You lost 200 customers and gained $122,400 in revenue.

The catch? Those 200 churned customers represent support tickets you no longer handle, onboarding calls you no longer run, and refunds you no longer process. Your cost to serve drops too. The real gain is larger than the headline number.

Most SaaS founders underprice by a wide margin — usually because they're pricing for the customer they were two years ago, not the customer they have today.

How do I price my SaaS product effectively?

Effectively means you have evidence, not vibes. The process has four stages, and skipping any of them is how you end up guessing.

Stage 1: Willingness-to-pay research

You need to talk to at least 20 existing customers and 10 prospects. Two methods work well:

• Van Westendorp Price Sensitivity Meter — ask four questions: at what price is this too cheap to trust, a bargain, getting expensive, and too expensive to consider. The intersection points give you an acceptable range.
• Gabor-Granger — show a specific price, ask "would you buy at this price?" then adjust up or down. This produces a demand curve, not just a range.

I'll admit, the first time I ran Van Westendorp I had no idea how to read the output. The chart looked like a crime scene. But the "too cheap" boundary alone was worth the effort — it revealed that our $9 tier was actively signaling low quality to enterprise buyers.

Stage 2: Packaging and tier design

Pricing is the number. Packaging is what you get for that number. Get the packaging right and the price almost sets itself.

A rule of thumb: the middle tier should be your best-selling plan. If your cheapest tier dominates, your packaging is misaligned — you've made the entry plan good enough that nobody upgrades. If your most expensive tier dominates, you've priced the middle too close to it.

Stage 3: Testing the change

Never roll out a new price to everyone at once. Run it to new customers for 60–90 days. Measure conversion rate, average contract value, and support ticket volume. If conversion drops by more than 15%, something in the packaging is broken, not the price.

Stage 4: Sequencing the rollout

Existing customers get grandfathering or a migration path. New customers get the new price immediately. I usually recommend a 6–12 month grandfather window — long enough to be fair, short enough that your revenue isn't permanently capped by legacy contracts.

What is the 3 3 2 2 2 rule of SaaS?

The 3-3-2-2-2 rule is a rough benchmark for how a healthy SaaS revenue base should be distributed across customer segments. The idea is that you want roughly 3 large enterprise accounts, 3 mid-market accounts, and then 2 of each progressively smaller segment — or in some versions, 3 accounts at the top, 3 in the middle, and a tail of smaller ones.

Its purpose is concentration risk management. If one customer represents 40% of your ARR, you don't have a business — you have a hostage situation. That customer can renegotiate your price, demand custom features, and leave you scrambling if they churn.

In practice, the exact numbers matter less than the principle: your revenue should be spread across enough accounts that no single loss is catastrophic. For early-stage SaaS, this often means deliberately turning down enterprise deals that would dominate your book, or raising prices on smaller tiers to build a broader base.

I've seen this play out painfully. A company I advised had one client generating 60% of revenue. When that client left, the company had to lay off half the team within a quarter.

What is the rule of 40 in SaaS?

The Rule of 40 says your growth rate plus your profit margin should equal at least 40%. If you're growing 60% year over year and losing 20% in margin, you score 40. If you're growing 10% and profitable at 30%, you also score 40.

It's a proxy for sustainability. It says: you can grow fast and lose money, or grow slowly and bank profits, but you can't do neither.

Pricing connects to this directly. Cutting prices to chase growth usually lowers your margin without proportionally lifting your growth rate — you end up scoring below 40. Raising prices tends to improve margin while mildly reducing growth, which pushes your score toward or above the threshold.

How to use it for pricing decisions

Run the arithmetic before any price change. If you're at 45% growth and -5% margin, you're at 40 — balanced. A price cut that lifts growth to 55% but drops margin to -20% leaves you at 35. Worse.

The Rule of 40 doesn't tell you what price to charge. It tells you whether your pricing decision is net positive for the business, or just for the top line.

What are the 5 C's of pricing?

The 5 C's of pricing are a framework for evaluating any price decision from five angles:

1. Cost — your floor. Know your fully loaded cost to serve one customer.
2. Customers — their willingness to pay, budget authority, and perceived value.
3. Competition — what alternatives they'll compare you to, including doing nothing.
4. Compatibility — how your price aligns with your brand positioning and sales motion.
5. Channel — the margin structure your resellers, partners, or app store need to make money.

I find the first three get all the attention and the last two get ignored. That's a mistake. A price that's perfect for direct sales can be wrong for a partner channel that needs 30% margin. And a price that's incompatible with your positioning — say, $5/month for a product you describe as "enterprise-grade" — creates cognitive dissonance that kills conversion.

Use the 5 C's as a checklist before every pricing change. If any one of them is out of alignment, fix it before you ship the new price.

Choosing the right pricing model for growth

The model you pick shapes your growth curve more than the numbers in it. Here's how the main options compare.

Model	Best for	Growth characteristic	Main risk
Flat-rate subscription	Early-stage, simple products	Predictable, low ceiling	Underpricing heavy users
Tiered (good/better/best)	Most B2B SaaS	Natural upgrade path	Middle tier cannibalization
Per-seat	Collaboration tools sold top-down	Aligned with customer growth	Punishes adoption within accounts
Usage-based	Infrastructure, API, data products	Expands automatically with value	Revenue unpredictability
Hybrid (platform fee + usage)	PLG motion with enterprise upsell	Balanced predictability and expansion	Complexity in billing and forecasting

For bottom-up products — where individual users sign up and teams expand organically — hybrid models tend to win. You get a predictable base fee and a usage component that scales with the value delivered. The friction is billing complexity, but tools like Stripe and Metronome handle that now.

For enterprise sales motions, tiered seat-based pricing still works, but expect pressure on the per-seat component as buyers push back. I've seen more deals in the last two years get stuck on seat counts than on headline price.

When and how often should you reprice?

Once a year, minimum. Some teams do it every six months.

The trigger signals are clear: your win rate is above 60%, your sales cycle is getting shorter, prospects never push back on price, or your churn is concentrated in customers who don't fit your target profile. Any of those means you're underpriced.

The opposite signals — long sales cycles, high discounting, prospects who say "we need to think about it" — mean the price is fine but the packaging or value story is broken.

A note on grandfathering

Grandfathering existing customers forever is a growth trap. You end up with a book of business that pays yesterday's prices against today's costs. I recommend a scheduled migration: 12 months at the old price, then a transition to the new price with a small loyalty discount (say 10%).

Some customers will leave. The math usually says you're better off. Run it before you decide — don't assume.

The thing most teams get wrong

They treat pricing as a launch activity. Set it, forget it, move on to the next feature.

Pricing is a living part of your product. It should be reviewed on a cadence, tested with real customers, and adjusted when the evidence changes. The founders I've seen grow fastest are the ones who talk about price the way they talk about product — obsessively, with data, and without ego.

The founder with the $19 plan? He ran the research, repackaged into three tiers, and moved his middle plan to $59. Conversion dropped 8%. ARR went up 47% in five months. He didn't lose customers. He found the ones who should have been paying him all along.

That's what pricing for growth actually looks like. Not a number you pick. A process you run.