From Strategy to Action: Pricing Frameworks

Pricing is the most important product decision that product managers routinely delegate to the CEO, finance team, or whoever is loudest in the strategy meeting.

I’ve made this mistake. Watched features team built generate zero revenue because they were priced wrong. Seen brilliant products struggle because pricing confused customers. Participated in three-hour pricing debates that ended with “let’s think about it more” (classic “let’s circle back” etc.) and reconvene next month.

Eventually figured out: pricing isn’t a finance problem. It’s a product problem dressed in a spreadsheet.

The Pricing Problem Nobody Admits

Product has a “premium” tier priced at hundreds/month. What makes it premium? Nobody can give a coherent answer. “It’s for bigger companies”, “Enterprises”.

Looking at the data, turns out most of premium customers are actually smaller companies who’d hit the user limit on the standard plan. They weren’t buying premium features - they were renting access to their own data.

The pricing model is lying about what customers value. Did they want premium features? They actually want to not have artificial restrictions on basic functionality.

Restructured pricing around actual value - data volume and API access, not “enterprise features.” Customers should understand what they are paying for.

Understanding the Fundamentals

Core Concepts: What Pricing Actually Communicates

Pricing isn’t just “what we charge.” It’s communication. Every pricing decision sends signals about positioning, value, and who you think your customers are.

Free tier says: “We think you’re not sure yet.” Or “we need scale more than we need immediate revenue.” Or “we’re growth-stage and optimising for user acquisition.”

High entry price says: “This solves an expensive problem.” Or “we’re positioning for enterprise.” Or “we want fewer customers who value this highly.”

Per-seat pricing says: “Value scales with team size.” Or possibly “we couldn’t figure out value-based pricing so we defaulted to the SaaS standard.”

We charged per-seat when we should have charged for data processed. Result: large teams with light usage paid too much (and churned), small teams with heavy usage paid too little (and maxed out infrastructure without contributing revenue).

Pricing model mismatch tanks products. Get the model right and pricing becomes easy. Get it wrong and no amount of optimisation will fix it.

Why Product Managers Should Own This

Finance thinks about pricing as revenue optimisation. Sales thinks about it as deal closer or blocker. Product should think about it as user experience and value communication.

Three pricing changes that should have been product decisions but are made elsewhere:

Example one: Sales wants a “let’s talk” enterprise tier for deals over some threshold. Sounds reasonable. Problem: it trains enterprise buyers to never self-serve, even when they would have. Conversion time for enterprise goes from a couple of weeks to months because everything becomes a negotiation.

Example two: Finance wants to add a setup fee to improve cash flow. Kills conversion. Turns out customers mentally separate “paying for the product” from “paying to start using the product” and the setup fee feels like a punishment for buying.

Example three: Marketing wants a lower entry price to improve ad conversion. More signups from people who weren’t the target market. Support costs go up, activation goes down, churn accelerates.

All three changes make sense from finance/sales/marketing perspectives. All three damage the product experience. Product managers need to be in the room when pricing decisions are made.

Common Pitfalls and How to Avoid Them

Mistake One: Copying Competitor Pricing

Every pricing discussion I’ve been in has included someone saying “Competitor X charges Y, so we should be around there.”

This is how you end up with undifferentiated positioning and price wars.

We were pricing identically to three competitors. All of us charged per-user, all in the ten of euro/user/month range. Competing on features, not value.

We repositioned around a different metric: projects managed. Found that customers with complex projects valued us way more than customers with simple projects, regardless of team size.

Changed pricing to around 50 euro/month for 5 projects, 200 euro/month for unlimited. Same customers, 2.3x average revenue. Because we stopped competing on per-user pricing and started competing on outcomes.

The rule: Understand your actual differentiation before you look at competitor pricing. If you’re truly differentiated, competitor pricing is barely relevant.

Mistake Two: Optimising Price Before Proving Value

Classic mistake: launch product, see poor conversion, decide the problem is price, discount heavily, get customers who don’t value the product.

You launch at 99 eur/month. Conversion is poor. You drop to 49 eur/month. Conversion can improve but engagement might tank. Why? You can attract people who want cheap tools, not people who have the problem you solve.

Then you spend two months improving the product, especially onboarding and time-to-value. You raise the price back to 99 eur/month. Conversion improves, engagement stayed high. Modal? Turns out price isn’t always the problem - it might be value delivery.

When to optimise price: After you’ve nailed positioning, value delivery, and have reasonable conversion. Not before.

Mistake Three: Ignoring Price Psychology

Numbers aren’t neutral. 99 eur feels different from 100 eur, even though it’s 1% difference. Annual pricing with monthly breakdown feels different from monthly pricing even when the math is identical.

Same price. Different framing. Different conversion rates.

Also: showing annual savings (“Save x eur/year”) works for SMBs. Doesn’t work for enterprises. They don’t care about that. They care about budget predictability and avoiding monthly PO paperwork.

The lesson: Test your pricing messaging as rigorously as you test your product. The psychology matters as much as the number.

Putting It Into Practice

A Framework That Actually Works

Most pricing frameworks are theoretical. Here’s one I’ve use:

Step 1: Identify your value metric What do customers get more of when they get more value from your product? Users? Data processed? Projects shipped? Revenue generated?

We thought it was “reports generated.” Turned out to be “decisions made with confidence.” Those aren’t the same thing. One suggests usage-based pricing, the other suggests outcome-based.

Step 2: Find natural breakpoints Where do customer needs cluster? Usually you’ll see small teams (1-10 users), mid-market (10-50), and enterprise (50+). Or light usage, moderate usage, heavy usage.

Don’t create artificial tiers based on features. Create tiers based on customer segments that have genuinely different needs.

Step 3: Price to value, not cost If your product saves customers 10k/month, you can charge 2k/month and it’s a bargain. If it saves them 200/month, charging 150/month is expensive.

I’ve seen teams price based on development costs. Wrong mental model. Your costs determine profitability, not pricing. Customer value determines pricing ceiling.

Step 4: Test anchoring Show three tiers. Middle one should be your target. Bottom one is the “I’m not sure yet” option. Top one is the “I need everything” option that makes the middle one look reasonable.

Making Pricing Changes Without Destroying Trust

Changing pricing on existing customers is risky. Do it badly and you tank retention. Do it well and nobody complains.

The rules:

• Grandfather existing customers for at least 12 months: Give them time to adapt their budgets
• Communicate early and clearly: 90 days notice minimum, explain the reasoning
• Provide an upgrade path that makes sense: If you’re changing the model, help customers understand what their new tier should be
• Watch for edge cases: There’s always one customer whose specific use case breaks with the new model

Key Takeaways

Let’s make this concrete:

• Pricing is a product decision, not a finance decision - It communicates positioning, value, and target market. Product managers should own it.
• Price to value metric, not to costs or competitors - Understand what customers actually value, find the natural breakpoints, price accordingly.
• Don’t optimise price before proving value - If conversion is low, the problem is usually product/market fit or value delivery, not price.
• Test pricing messaging as carefully as pricing numbers - 99 vs 100, annual vs monthly, savings vs cost - framing matters enormously.
• Use three-tier anchoring - Bottom tier for uncertain, middle tier as target, top tier to make middle look reasonable.
• Grandfather existing customers when changing pricing - Give them 12+ months on old pricing, communicate early, handle edge cases individually.

Final Thoughts

Pricing is product. It’s positioning, communication, and value exchange. Get it wrong and nothing else matters - brilliant product, terrible pricing is still a failing business.

Start by understanding your actual value metric. Not what you think customers should value, what they actually value. Talk to them. Look at usage data. Find the pattern.

Then build pricing that matches that value metric, with natural tiers based on real customer segments, priced to the value you deliver.

And test the psychology as much as the numbers. How you frame the price matters as much as what the price is.

Your pricing is probably wrong right now. That’s fine. So is mine. The question is whether you’re treating it as a product problem you can iterate on, or a finance problem you set once and forget.

Have questions or thoughts? Get in touch - I’d love to hear from you!