Pricing is strange territory for product managers. It has more impact on revenue than almost any feature you'll ever ship, and yet most PMs go years without touching it. It lives with founders, or finance, or a pricing committee that meets twice a year and changes nothing.
Then one day you're asked to package a new product, or a tier isn't converting, and suddenly pricing is your problem. Here's the working foundation: not a full monetization education, but enough to reason clearly and avoid the classic mistakes.
The One Idea That Matters Most: Price to Value
There are three basic ways to set a price:
- •Cost-plus: what it costs us, plus margin. Fine for manufacturing, nearly meaningless for software, where marginal cost approaches zero.
- •Competitor-based: what they charge, adjusted. Useful as a sanity check, dangerous as a strategy, because it assumes competitors know what they're doing and that your value equals theirs.
- •Value-based: what the solved problem is worth to the customer. This is the right anchor for almost all software pricing.
Value-based pricing sounds abstract until you ask the practical question: what does this problem cost the customer today? Hours of manual work, error rates, missed revenue, tool spend you'd replace. If your product saves a team ten hours a week, the value is quantifiable, and your price should be a defensible fraction of it.
This is why pricing work starts with customer interviews and not spreadsheets. "What have you tried? What does this cost you? What did you pay for that?" are pricing research questions, and you can ask them in the discovery conversations you're already having.
The Value Metric: What You Charge For
Before the number comes the unit. Per seat? Per usage? Per outcome? Flat rate? This choice, the value metric, matters more than the price itself, because it determines how your revenue scales.
The ideal value metric has three properties:
- •It tracks the value the customer receives. More usage of it = more value gotten.
- •Customers can predict it. Surprise bills breed churn and procurement hatred.
- •It grows as the customer grows, giving you expansion revenue without a sales fight.
Per-seat pricing dominates B2B because it's predictable and roughly tracks value for collaboration tools. But it punishes products where value doesn't scale with headcount, and it motivates customers to share logins. Usage pricing tracks value beautifully for infrastructure but scares buyers who can't forecast it. Hybrids (a platform fee plus usage, or seats with usage tiers) are common precisely because the pure forms have sharp edges.
If a customer would happily pay more as they get more value, and your metric doesn't capture that, you chose the wrong metric.
Packaging: Good, Better, Best (and Its Traps)
Packaging is which capabilities go in which tier. The standard pattern is three tiers, and it exists because it works: a low tier to reduce entry friction, a middle tier where you want most customers to land, and a high tier that anchors value and serves your biggest accounts.
The judgment calls that make or break it:
- •The fence question. Which features keep customers in higher tiers? Good fences are features that matter to customers with more value at stake (SSO, audit logs, advanced permissions for enterprises). Bad fences are core value withheld, which just makes the low tier feel broken.
- •The upgrade path. A customer should hit the ceiling of their tier naturally, right as their value grows. If nobody ever upgrades, the fences are wrong. If everyone immediately needs the top tier, the middle is fake.
- •Simplicity. Every tier, add-on, and asterisk adds sales friction and support burden. When in doubt, fewer options. Confused buyers don't buy; they defer.
A note on freemium: free tiers are an acquisition strategy, not a generosity program. They make sense when free users convert at a reasonable rate, refer others, or feed a network effect. Otherwise they're a cost center with good vibes.
Changing Prices Without a Mutiny
At some point you'll raise prices or restructure packaging. This is where more goodwill gets burned than anywhere else in product. The playbook that avoids the worst of it:
- •Grandfather thoughtfully. Existing customers keep their price for a defined period, or permanently on their current terms. The revenue you "lose" is cheaper than the churn and public anger you avoid.
- •Give long notice. 60 to 90 days minimum for B2B. Procurement cycles are real.
- •Pair the increase with visible value. A price change alongside a major capability lands very differently than one alongside nothing.
- •Explain like an adult. Customers accept "we've added X and Y and are updating prices for the first time in three years" far better than corporate mumbling.
- •Arm your teams. Support and sales will absorb the reaction. Give them the reasoning and the talking points before customers have the news. (This is stakeholder management with revenue attached.)
Testing and Evidence
You mostly can't A/B test prices the way you test button colors. Showing different customers different prices for the same thing has fairness, legal, and PR problems, and B2B sample sizes rarely support it anyway. What you can do:
- •Interview for value and willingness to pay. Techniques like Van Westendorp's four questions (at what price is it too cheap, a bargain, getting expensive, too expensive) give you a defensible range from a few dozen conversations.
- •Test packaging on new cohorts. New customers can get new packaging while existing ones keep theirs; compare conversion and mix.
- •Watch win/loss and discount data. If sales discounts every deal 30%, your list price is fiction. If you never lose on price, you're probably underpriced. Both signals are sitting in your CRM right now.
- •Measure the full funnel after any change. Conversion, mix across tiers, expansion, churn. Price changes ripple; a conversion dip can be fine if ARPU and retention rise. Have the metrics framed before the change ships.
The Underpricing Epidemic
One opinionated note, because it's the most common pricing disease in software: most products, especially from newer companies, are underpriced. Teams price from their own anxiety rather than the customer's value. The result is a price that makes the product look cheap (buyers read price as a quality signal), starves the company, and is scary to correct later precisely because it went uncorrected so long.
If churn is low, discounting is rare, and customers close without haggling, you're likely underpriced. Raising prices is uncomfortable for a week. Being underpriced is expensive forever.
The deeper cost is strategic: underpricing locks you out of investments. The support quality, the enterprise features, the reliability work your customers actually want all require margin to fund. Cheap products stay thin, then lose to competitors who charged properly and reinvested. Price is part of the product.
Where the PM Fits
You may never own the final pricing call, and that's fine. Your job is to bring the inputs nobody else has: what customers say the problem costs them, which capabilities they'd pay more for, how value actually maps to usage. PMs who show up to pricing conversations with that evidence shape the outcome regardless of who signs off, and "led pricing and packaging for X" is a genuinely differentiating line on a senior PM resume.
Want a role where you'll get closer to the business side of product? Browse open PM positions at productmanagerjobboard.com.