Pricing is decided without the PM in the room at most B2B SaaS companies — and that's why so many pricing structures compound problems over time. The value metric (what you charge on), tier design (which features belong where), and upgrade experience are product decisions requiring deep product knowledge. Product leaders should own the value metric conversation, stress-test pricing from the customer experience perspective, and bring usage data to the table that no other function has.
Here's a pattern I've seen at almost every B2B SaaS company I've worked at or worked with: pricing is decided in a room that doesn't include the PM who built the product being priced.
Finance does a competitive analysis. Sales says what they can sell. Marketing says what the market will bear. Someone builds a model. A number comes out. The PM finds out in the all-hands.
This is backwards. And it's why so many SaaS pricing structures are wrong in ways that compound over time.
What makes pricing a product problem
Pricing isn't just about the number. Pricing is about the experience of becoming a customer, expanding as a customer, and perceiving value as a customer. Those are product problems.
When you structure pricing as a tier design decision, you're making product decisions: Which features belong in which tier? How do you define the value metric — is it seats, usage, outcomes? Where do you put limits that feel fair vs. punitive? What does the upgrade path look like from the customer's perspective?
None of these questions can be answered well without deep product knowledge. But most pricing processes treat them as secondary inputs — things to validate after the commercial model is set, not things to co-design from the start.
The value metric is everything
The most important pricing decision isn't the price. It's the value metric — what you charge on.
Charge on seats in a product that scales on usage, and you'll have enterprise customers capping their seat count and sharing logins. Charge on usage in a product where the value is about organizational alignment, and you'll have customers afraid to expand because their bill becomes unpredictable.
The value metric should map to how customers perceive the value they get. That requires understanding how customers actually use the product, what outcomes they care about, and where they'd feel the pricing was "fair" vs. "punishing." That's ethnographic product work — not competitive benchmarking.
The value metric should map to how customers perceive value — not to what's easiest to measure.
Packaging is product architecture
Your pricing tiers are, in effect, a product architecture decision. When you decide what's in the Free tier vs. the Pro tier vs. the Enterprise tier, you're deciding what product you want which customers to have access to.
Get this wrong and you create misalignment between your commercial motion and your product experience. Sales sells one thing. The product delivers something different. Customer success bridges the gap. NPS goes down. Churn goes up. Everyone blames each other.
I've seen this happen at companies with genuinely great products. The product was excellent; the packaging was wrong. It created the wrong expectations at the top of the funnel, and the company paid for it downstream for years.
How product leaders should engage with pricing
If you're a VP or CPO, here's how I'd think about your role in pricing:
Own the value metric conversation. Before anyone talks about what price to charge, the product team should have a perspective on what you charge on. Push for that conversation to happen early, not as an afterthought.
Represent the customer experience of pricing. When the commercial team presents pricing tiers, your job is to stress-test the customer experience. Walk through the upgrade moment: why would a customer upgrade, at what point, and does the tier design make that feel obvious or confusing?
Connect packaging to product roadmap. If a feature is going into Enterprise tier, what does that mean for the roadmap? Are you building features that are only for a tier that represents 5% of your customer base? That's a strategic product decision, not just a commercial one.
Bring data from the product. Usage data, feature adoption rates, customer journey maps — these are inputs to pricing decisions that only the product team has. If you're not bringing them to pricing conversations, nobody else will.
The portfolio view of your product lines
Most pricing conversations treat each product in isolation. The more powerful frame is a portfolio view: each product has a different job at a different stage of growth, and your pricing strategy should reflect that.
A mature product with high market share and strong margins has a different pricing job than a new product trying to win share in a competitive market. The mature product can afford to protect profit. The new product may need to prioritize growth even at the cost of near-term margin. These products should be priced differently, and the margin from one can fund the growth investment in the other.
I learned this explicitly during my time building pricing at a B2B SaaS company through its growth years and eventual acquisition. We had a high-volume core business and a newer marketing product. The instinct was to price them similarly. The right move was to treat them as separate portfolios with different objectives: profit maximization on the mature side, growth optimization on the emerging side. Getting that distinction right changed how we thought about every individual pricing decision.
Pricing principles as a decision framework
One of the most useful things a product team can do is establish explicit pricing principles before facing specific pricing decisions. Without principles, every pricing question becomes political. With principles, you have a shared framework for evaluating tradeoffs.
The ones I've seen work in practice:
Price for value, not cost. Your price should reflect the value customers get, not what it costs you to deliver. This sounds obvious, but most companies default to cost-plus pricing because it's easier to defend internally.
Keep it simple enough to be self-serve. If a customer can't understand their bill or predict their costs, you have a pricing model problem. Complexity in pricing creates friction at every stage: sales, onboarding, expansion, renewal. The test: can a customer explain to a colleague what they'd pay and why?
Reward loyalty and growth. Long-term, high-growth customers are worth more to your business than their revenue alone suggests. Price structures that reward growth behavior (volume discounts, multi-year incentives, expansion pricing) create alignment between customer success and commercial outcomes.
Not every feature needs to be monetized. Forgoing monetization on certain capabilities is a legitimate strategic choice. Some features should be in every tier because they increase perceived value and differentiation. The question isn't "should we charge for this?" but "what does charging for this do to how customers experience the product?"
The common objection
The most common objection I hear is: "Pricing belongs to revenue/finance/GTM. Product should focus on the product."
I understand the instinct. But pricing is the commercial expression of your product strategy. If you let other functions define it entirely, you're ceding a huge lever in how your product creates and captures value.
That doesn't mean product should own pricing unilaterally. But you should have a strong seat at the table — with a point of view grounded in how the product actually works and how customers actually experience it.
The companies that get pricing right treat it as a cross-functional problem where product has an equal voice. The companies that struggle with pricing tend to have product playing defense — reacting to commercial decisions rather than co-creating them.
The difference is whether your pricing reflects your product strategy or contradicts it.