The team starts with the price before the value metric is clear.
If you cannot explain what the buyer is paying for, any number will feel arbitrary.
Pricing is where product value, buyer tolerance, and revenue model meet. If those pieces do not fit, the spreadsheet will not save you.
This page is for teams trying to answer:
Plain English first. Value metric, packaging, and buyer fit second.
Pricing, Broken Down
Most B2B SaaS teams run A/B tests on onboarding flows but have never run a structured pricing test — despite pricing having 10x the revenue impact of most UX changes.
The gap between what customers are willing to pay and what you're currently charging is usually measurable from usage data, upgrade behaviour, and willingness-to-pay signals.
Which features are used by accounts that upgrade, expand, or churn tells you more about pricing structure than any survey.
WHY PRICING STRATEGY IS HARD TO GET RIGHT
"Our pricing page hasn't changed since our Series A. The market has moved, our product has expanded, and our customers are completely different now. But nobody wants to touch it because it feels risky and nobody owns the work."
CEO — B2B SaaS, $18M ARR
"Our enterprise customers are paying the same as our mid-market customers. Some use the product every day across 50 seats. Some barely log in. We know the packaging is wrong but we don't have the data to redesign it with confidence."
VP Revenue — SaaS, $35M ARR
"We added a free tier eighteen months ago. Signups went up. Paid conversions didn't. We're carrying free users who we can't convert and we're not sure if the problem is the product, the limit, or the upgrade prompt — or all three."
Head of Growth — PLG SaaS, Series A
"Leadership wants a higher-priced tier for enterprise. But we don't know which features enterprise accounts actually value, which ones drive expansion revenue, or how to structure a tier that would actually convert. The data is there — we just haven't connected it to the pricing work."
Chief Product Officer — B2B SaaS, $50M ARR
What It Is
It is not just a number on a pricing page. It is the way the company decides what value to monetize, which buyer to serve, how to package the product, and how to grow revenue without creating friction the product cannot support.
Good pricing is visible in the value metric, the packaging logic, the upgrade path, and the way the team talks about change. If those pieces are inconsistent, customers notice faster than the finance model does.
That is why pricing changes should start with the product shape and buyer behavior, not the homepage copy.
Where Teams Get It Wrong
The number on the screen usually reflects a deeper mismatch in value, packaging, or buyer logic.
The team starts with the price before the value metric is clear.
If you cannot explain what the buyer is paying for, any number will feel arbitrary.
The packaging is trying to do too many jobs at once.
That is how plans become hard to compare, hard to buy, and hard to explain.
The team uses discounting to hide a weak model.
Discounts can close deals, but they do not fix the underlying mismatch between value and willingness to pay.
Pricing changes are launched without a test plan.
That creates confusion, support issues, and a lot of opinion after the rollout is already live.
What Good Looks Like
The pricing model matches a meaningful product behavior, not a random internal KPI.
The structure feels native to the buyer's decision process, not forced to fit a finance template.
The team knows what to change, what to watch, and how to roll it out without guessing.
How ProductQuant Approaches It
Good pricing usually gets simpler once the team stops treating it like a debate and starts treating it like a diagnosis.
ProductQuant starts with Product DNA, buyer behavior, and the revenue motion already showing up in the data. Then the value metric, packaging, and change path are shaped around that structure.
If the issue is really positioning, the pricing audit often gets paired with competitive positioning. If the issue is really expansion or usage, the worksheet and workbook make the next step concrete.
Look at product behavior, buyer fit, and current revenue motion before changing the page.
Define the value metric and the packaging logic in plain language.
Use the worksheet and workbook to pressure-test options before a live rollout.
Keep the change narrow enough that the team can learn from it.
When pricing matches product behavior, revenue gets easier to explain and easier to grow.
Related Guides And Proof
These are the most relevant ProductQuant assets if you want strategy detail, change planning, or a real example of pricing work in context.
CLIENT WORK
Analysed feature usage by plan, upgrade triggers, and churn patterns to identify a significant willingness-to-pay gap. Produced a packaging redesign brief with a clear value metric and tier structure the team could test safely.
See the sprint →Identified which features free-tier users were hitting before churning versus converting. Redesigned the free tier limit to hit naturally at the point of highest value, increasing upgrade prompt relevance without changing the product.
See the workbook →
WHO DOES THIS WORK
Founder, ProductQuant · MSc Big Data & Business Analytics · BSc Behavioural Psychology · 8+ years B2B SaaS
Jake approaches pricing strategy from the analytics layer first — which features drive upgrades, which usage patterns predict expansion, and what the WTP signals in your existing customer data say before designing any new packaging or price point. The background in behavioural psychology means pricing is treated as a decision-design problem, not just a revenue optimisation exercise.
COMMON QUESTIONS
Questions about your specific situation? Book a call →
Best Next Step
This page is educational first. If you want help shaping the model or testing a change, these are the most relevant ProductQuant paths.
If the value metric feels unclear or the packaging debate keeps looping, start with the pricing audit or the worksheet.