Pricing is the highest-leverage thing on the product surface and the thing teams touch the least.
The same team that runs ten experiments a quarter on onboarding will leave the price page untouched for three years. The price was set early, the unit economics seemed to work, and now nobody wants to be the person who reopens it. So it sits — quietly losing the company revenue, the product team conversion, and the customers who would happily have paid more for a clearer offer.
Pricing isn't a finance problem. It's a product problem with the biggest delta to growth of anything you can change.
Why pricing gets stuck
Three reasons it doesn't move:
It feels irreversible. People assume changing prices breaks trust with existing customers. In practice, grandfathering existing plans is straightforward, and most users barely notice changes to plans they're not on. The fear is much larger than the actual cost.
Nobody owns it. Pricing sits awkwardly between product, finance, marketing, and sales. When ownership is split four ways, the default state is no one moves. The team that should own pricing is the team closest to the customer behaviour — that's almost always product.
It looks like a one-time decision. The pricing page launches. That feels like the end of the project. But pricing is the same as any other part of the product — it has bugs, it has dead weight, and the customers it's optimised for change as the company grows. A pricing page that worked at 100 customers is almost never the right one at 10,000.
Where the leverage actually is
Three places teams underuse:
Plan structure. The shape of your plans tells the customer what to buy. Three plans, well-named, with clear differences, drive radically different conversion than four plans where two of them basically do the same thing. Most pricing pages have at least one plan that exists for historical reasons and confuses the choice.
Packaging. Which features go in which plan, and what's metered versus included, controls how customers grow into the product. Get this wrong and you push customers into a plan they outgrow in a month or stay in for two years longer than they should. Both are revenue you're leaving on the table.
The actual price. Even within the same plan structure, the number matters. Most SaaS prices were set by looking at competitors and rounding. That's a fine starting point and a terrible long-term position. The right price is the one customers find slightly painful but worth it. Most teams are well below that line.
How to actually run pricing
Treat it the way you'd treat any product surface.
Look at it quarterly. Not to change it every time — to ask whether the assumptions behind it still hold. Has the customer base shifted? Do the plans still match how people use the product? Are sales conversations getting stuck on the same objection? If the answer to any of these is yes, you have a pricing experiment to run.
Talk to customers about it. Not "would you pay more?" — that question gives useless answers. Better: "what would you have to see to upgrade?", "what feels overpriced about your current plan?", "how do you decide between us and the cheaper option?". The answers expose where the pricing maps to value and where it doesn't.
Run real experiments. New visitors are an easy A/B surface. New plans, new prices, new packaging — all testable at low risk if you scope carefully. Most teams skip this because it feels scary. It's much less scary than holding the wrong price for two years.
What you'll find when you actually look
A few patterns that show up almost every time a team takes pricing seriously again:
The cheapest plan is overserving its users. People on the entry plan are getting more than they should. Strip a couple of features out and most of them upgrade. The fear is they'll churn. Usually, they don't.
The middle plan is doing two jobs badly. It's both the upgrade path and the workhorse plan, and it's optimised for neither. Splitting it usually adds more revenue than it takes away.
The top plan is underpriced. The customers buying the most expensive plan are usually the ones least price-sensitive. A 20–30% increase rarely loses anyone. The teams that test this almost always wish they'd done it earlier.
The shift
Stop treating pricing as a finance question. It's a product question with the biggest revenue impact of any single change you can make.
Look at it. Talk to customers about it. Run small experiments. Move it.
The teams that do this consistently grow faster than the ones with better products and stuck prices. That's how big the lever is.
If you're focused on growth metrics, pricing is where the highest-leverage move usually sits. And if your launch plan is a growth plan, the price you launch at is part of that plan — not a separate decision.