Simon-Kucher & Partners studied more than 10,000 product launches across three decades. The finding that should concern every product manager: 72% of new products fail to meet their financial targets or fail entirely. The leading cause is not bad engineering, poor timing, or weak distribution. It is pricing.
That statistic comes from Madhavan Ramanujam and Georg Tacke’s research, published in Monetizing Innovation. Their conclusion is blunt: most product teams design the product first and figure out pricing later, if they figure it out at all. The result is a product that customers may want but won’t pay for at the price the business needs.
Product pricing strategy is not a finance exercise. It is not a sales negotiation. It is a core product decision, and PMs who treat it otherwise are giving away the most consequential lever they have.
The Default That Costs Companies Revenue
In most organizations, pricing follows a predictable pattern. Engineering builds the product. Product management defines the features. Then, sometime between beta and launch, someone from finance runs a cost-plus calculation, or a sales leader picks a number based on competitive benchmarks. The PM is barely in the room.
This happens because pricing feels like it belongs to the people who “own the numbers.” Finance understands margins. Sales understands deal dynamics. But neither group understands the customer’s perception of value at the feature level, which is exactly what determines whether a price point actually works.
Patrick Campbell, founder of ProfitWell (acquired by Paddle in 2022), analyzed pricing data from over 30,000 SaaS companies. His most consistent finding: 40% of SaaS companies haven’t revisited their pricing in 18 months or more. And companies that run systematic pricing optimization see 12% to 40% higher year-over-year revenue growth compared to those that don’t.
The gap is not information. The gap is ownership. When no one on the product team owns the pricing conversation, pricing becomes an afterthought that gets locked in at launch and never revisited.
What “Feature Shock” and “Minivation” Actually Cost
Ramanujam’s research identifies four distinct ways companies fail at monetization. Two of them are directly caused by product managers who don’t engage with pricing early enough.
Feature shock happens when a team packs too many features into a single product, tries to charge a premium, and discovers that customers don’t value the bundle the way the team expected. The product does too much, costs too much, and resonates with no one specifically.
Minivation is the opposite problem: a well-targeted product, correctly scoped, but priced too low because no one tested what customers would actually pay. The product succeeds in adoption but fails as a business. Revenue that should have been captured disappears permanently.
Both failures trace back to the same root cause. The team never had the willingness-to-pay conversation during product development. They designed the product in a vacuum and attached a price at the end.
I spent years in IT operations at a Saskatchewan telecom and watched this play out repeatedly. The engineering team would build something genuinely useful. Product management would write up the value proposition. Then a pricing committee would set the rate based on competitor benchmarks and margin targets. Nobody asked customers what they would pay. We would launch, see lower-than-expected adoption, and blame marketing. The problem was never awareness. It was price-to-value alignment that nobody tested.
The Willingness-to-Pay Conversation Is a Discovery Activity
The fix is not complex, but it requires product managers to treat pricing as part of product discovery rather than part of launch.
The Van Westendorp Price Sensitivity Meter is one of the most accessible methods. It uses four questions in customer interviews:
- At what price would this product start to seem too expensive to consider?
- At what price would you start to question the quality because it seems too cheap?
- At what price would you say it’s getting expensive but you’d still consider it?
- At what price would you consider this a great deal?
Plot the responses, and the intersection points reveal an acceptable price range. It takes 15 to 20 interviews to produce useful data. Product managers who are already running continuous discovery interviews can add these four questions to existing sessions without scheduling anything new.
For more complex products (multiple tiers, feature bundles, usage-based components), conjoint analysis provides sharper data. It presents respondents with different feature-and-price combinations and measures which tradeoffs they prefer. This is how Porsche developed the Cayenne in 2003: the team tested willingness to pay for individual features before finalizing the design. By 2015, the Cayenne was generating roughly half of Porsche’s total profit.
The point is not that every PM needs to become a pricing analyst. The point is that willingness-to-pay data should inform product decisions the same way usability testing and customer interviews already do.
What Pricing Ownership Looks Like in Practice
Owning pricing does not mean PMs set the final number unilaterally. It means they own the inputs, the analysis, and the recommendation. Three practices separate PMs who own pricing from PMs who don’t.
They test price sensitivity before scoping. Before committing to a feature set, they know what customers would pay for each capability. This prevents feature shock (building things customers won’t pay for) and minivation (underpricing things they will).
They revisit pricing on a regular cadence. OpenView Partners found that companies regularly reviewing and optimizing pricing strategy see 30% higher growth rates than those that don’t. ProfitWell’s research shows that companies effectively measuring willingness to pay achieve 23% higher average revenue per user without significant conversion impact. The top-performing PMs put pricing on the quarterly review agenda alongside metrics, roadmap, and competitive positioning.
They frame pricing as strategic positioning, not arithmetic. Ramanujam’s core insight is that how you charge often matters more than how much you charge. Subscription versus usage-based versus per-seat versus outcome-based: these are product decisions that shape customer behavior, retention, and expansion revenue. OpenView’s data shows 61% of B2B SaaS products now explore usage-based models, and 86% of companies valued above $100M use at least three pricing dimensions. The monetization model is part of the product itself.
The Strategic Cost of Sitting This One Out
When product managers don’t own pricing, three things happen predictably.
First, the product gets priced on cost or competition rather than value, which usually means it is priced too low. McKinsey has estimated that a 1% improvement in pricing translates to an 11% increase in operating profit. That sensitivity means even small pricing mistakes compound quickly.
Second, pricing becomes static. It gets set at launch and stays frozen while markets shift, customer segments evolve, and competitive dynamics change around it. A product that was priced correctly eighteen months ago may no longer reflect the value it delivers today.
Third, the PM loses strategic leverage. Pricing decisions determine which customers you attract, which features justify investment, and which market segments you can serve profitably. A PM who does not influence pricing is making product strategy with one hand tied behind their back. Pricing shapes product-market fit as directly as the feature set does.
The practice is straightforward: add willingness-to-pay questions to your next five discovery interviews. Bring the findings to your next pricing or strategy conversation. Start treating the price as a product feature, not a finance output.