Value-based pricing sets a price from what the outcome is worth to the buyer, rather than from what it costs to produce or what competitors charge. For software, where marginal cost is close to zero, it is the only one of the three anchors with any real information in it. Its difficulty is that it requires knowing what the problem currently costs the buyer, which most teams have never measured.
Before publishing a price, and any time the price was set by looking at a competitor or by picking a number that felt safe. It needs a buyer whose current cost you can quantify, which is why it works better in B2B than in consumer.
What value-based pricing is
Value-based pricing sets a price from what the outcome is worth to the buyer, rather than from what it costs you to produce or what competitors charge.
The idea is old, well established in economics and industrial marketing, and codified for modern practice by writers including Thomas Nagle and Reed Holden. What makes it particularly relevant to software is that the alternatives are so weak there: marginal cost is close to zero, so cost-plus anchors on a number with no relationship to value, and a competitor’s price encodes their costs and their buyer rather than yours.
Its difficulty is a single hard input. You have to know what the problem currently costs the buyer, and most teams have never measured it.
- Four possible anchors, one useful For software
Cost, competitor, value, gut. Marginal cost near zero rules out the first, and the fourth is the default.
- One hard input What the problem costs them
In their numbers: hours, headcount, error rate, churn. Skip it and this becomes gut pricing with better vocabulary.
- Find the reference price Often not a competitor
A salary, an agency retainer, or the cost of doing nothing. It frames the number before you say one.
- The calculation is a hypothesis Cards confirm it
Stated willingness to pay overstates real willingness by a consistent margin.
Why it matters
Founders price low. Almost universally, and for a consistent reason: they price against their own discomfort about asking for money rather than against what the buyer gets.
The specific damage is that a published price is very hard to raise. Every buyer who has seen it is anchored, and a rise reads as a penalty even when the product has improved. The number set in an uncomfortable afternoon becomes the ceiling on the business for years.
Founders describe this as something they will fix later. Almost nobody fixes it later. The price becomes part of the product’s identity by about month four, and moving it after that costs a conversation with every customer you have.
Anchored to What it costs you to deliver, plus a margin
The buyer does not care what it costs you. For software, marginal cost is near zero, so this anchors on a number with no relationship to value.
Anchored to What the nearest alternative charges
Their price encodes their costs, their buyer and their strategy. Copying it imports all three, and none of them are yours.
Anchored to What the outcome is worth to this buyer
Requires knowing what the buyer currently loses, which most teams have never measured.
Anchored to What feels defensible in the moment
Reliably lands low, because founders price against their own discomfort rather than against buyer value.
Finding the number
The method has one genuinely hard step and several easy ones. The hard step is quantification.
Ask what the problem costs today, and insist on numbers. Not “it is frustrating” but “it takes two people about six hours a week”, or “we lost three deals last quarter because the follow-up slipped”. Those are answers you can multiply.
Then find the reference price. This is the thing they will compare you to, and it is frequently not a competitor. A tool that saves a day a week is compared against a part-time hire. A tool that replaces an agency is compared against a retainer. A tool that prevents an error is compared against the cost of the last error, if there was a memorable one.
Your price is a share of the value created. Ten to thirty per cent is a common working range, and where you sit inside it is a positioning choice rather than a calculation.
The fence question
- It rises as the customer gets more value
Fails when: Seats, when one power user does all the work and the rest never log in.
- The customer can predict their bill
Fails when: Raw API calls, when nobody in the buying organisation knows how many they will make.
- It is countable without argument
Fails when: "Value delivered", or anything requiring a quarterly negotiation about what counts.
- Growing it is good for the customer, not just for you
Fails when: Storage, which grows because deleting things is hard rather than because they gained anything.
- It does not punish the behaviour you want
Fails when: Per-seat, on a collaboration tool whose whole value is getting more people in.
When to run it
- You are about to publish a price and it was chosen by looking at a competitor.
- Your buyers can tell you what the problem costs them in hours or headcount.
- Deals close too easily, which usually means you are underpriced.
- You have added significant capability without revisiting the number.
- Every customer is in your cheapest tier that technically works.
- You do not yet know whether the problem is real. Use The Mom Test →
- You need a buyer-perception band rather than a value calculation. Use Van Westendorp →
- Your value scales with consumption rather than with the buyer. Use Usage-Based Pricing →
- You need distribution more than you need revenue right now. Use Freemium Strategy →
Against the alternatives
What is this outcome worth to the person buying it?
Gives you: A price derived from quantified value, with a stated reason
What range does the market treat as acceptable?
Gives you: A price band. Constrains the value number from the other side
What does it cost us, plus a margin?
Gives you: A number unrelated to value. Near-useless for software
What does the nearest alternative charge?
Gives you: A reference point. Importing it imports their business model
Value pricing in practice: Slack
A company giving money back, on purpose, because the alternative was charging for value it had not delivered.
Slack · 2014 onwards
Gave money back for seats that were not being used, and grew faster for it.
Slack charged per active user and refunded, as credit, for anyone who had been paid for but had not used the product. A customer with 300 paid seats and 200 active ones was billed for 200.
From a quarterly revenue perspective this is self-harm. From a value-metric perspective it is the only coherent position: if the price is meant to track the value received, then billing for unused seats is charging for value that was not delivered, and the customer notices.
It also removed the main objection to a wide rollout. Nobody had to forecast adoption before buying, because over-buying carried no penalty.
- Billing basis
- active users, not licences
- Immediate revenue effect
- negative
- Effect on expansion friction
- removed the forecasting objection
What it shows: Choosing the value metric is the pricing decision. The number attached to it is arithmetic afterwards, and a metric that overcharges quietly is a metric the customer will eventually audit.
When it won’t help you
- It needs a quantified buyer cost you may not be able to get
The whole method rests on knowing what the problem costs today. Some buyers genuinely do not know, some will not say, and in consumer markets the question barely makes sense.
Instead: Use a perception-based method such as Van Westendorp where the value calculation is unavailable, and be honest that it is the weaker instrument.
- Value differs enormously between buyers
The same product can be worth a hundred pounds to one customer and ten thousand to another. A single value-based price necessarily fits neither well, which is what tiering exists to fix and why the fence choice matters so much.
Instead: Segment first. A value-based price for an undefined buyer is an average of two irreconcilable numbers.
- Stated value overstates real value
Buyers describing what a problem costs them are estimating, usually generously, and often about a problem they have already partly worked around. The calculation reliably produces a number above what anyone will actually pay.
Instead: Treat the output as a ceiling to test against, not a price to publish.
- It says nothing about whether you can capture the value
A product can create ten thousand pounds of value and be unable to charge for it, because the value is diffuse, the buyer has no budget line for it, or the saving accrues to someone other than the person who signs.
Instead: Check who benefits and who pays. Where they differ, the value calculation describes a person who is not your customer.
Further reading
- Thomas Nagle & Reed Holden, The Strategy and Tactics of Pricing. The standard text.
- Van Westendorp. The buyer-perception band that constrains the value number.
- Usage-Based Pricing. When value scales with consumption rather than with the buyer.
- Freemium Strategy. When distribution matters more than immediate revenue.
- Emotional Friction States. Ranking which problem is worth pricing against.
- Pricing strategy calculator. The four price points, run on your own numbers.
How to apply Value-Based Pricing
- 1
Quantify what the problem costs the buyer today
Hours per week, error rates, headcount, lost deals, churn. In their numbers, not yours. This is the whole method and the reason most teams skip it: it requires interviews specifically about cost, which are less enjoyable than interviews about features.
- 2
Find the reference price they are already anchored on
What are they comparing you to? Often not a competitor. A junior hire, an agency retainer, a consultant's day rate, or the cost of continuing to do nothing. The reference sets the frame before you have said a number.
- 3
Work out your share of the value created
A common working range is ten to thirty per cent of the quantified value. Below that you are leaving money on the table; far above it and the buyer starts asking why they should not do it themselves. The exact share is a positioning choice.
- 4
Choose the fence that tiers actually vary along
Which dimension does willingness to pay genuinely track? Company size, volume, seats, criticality. Getting this wrong is how a well-researched price still leaks money, because every customer sits in the tier that suits them rather than the one that reflects their value.
- 5
Test the number against revealed preference
A value calculation is a hypothesis. Put the price in front of real buyers and watch what happens: a pre-sale, a deposit, a live test. Stated willingness to pay overstates real willingness by a consistent margin.
- 6
Re-derive it when the product changes what it is worth
Value-based pricing is a function of the outcome you deliver, so shipping something that changes the outcome changes the price. Most teams add capability for years without revisiting the number.
Common mistakes
- **Pricing from your costs.** For software marginal cost is near zero, so cost-plus anchors your price to a number with no relationship to what the buyer gets.
- **Copying the nearest competitor.** Their price encodes their costs, their buyer and their strategy. Copying it imports all three, and none of them are yours.
- **Never quantifying the buyer's current cost.** The method has exactly one hard input and this is it. Skipping it turns value-based pricing into gut pricing with better vocabulary.
- **Assuming the reference price is a competitor.** Frequently it is a salary, an agency retainer, or the cost of doing nothing, and each of those sets a very different frame.
- **Choosing a fence that does not track value.** Tiering on a dimension willingness to pay ignores means every customer self-selects into the cheapest tier that works.
- **Treating the calculation as the answer.** It produces a hypothesis. Real buyers with real cards are what confirm it, and they systematically disagree with surveys.
How ShipFit operationalizes this
ShipFit runs Value-Based Pricing as one of the growth and monetisation models in Stage 4 (How to Win?), then applies it concretely in Stage 6 (How to Charge?). Stage 6 starts from the problem cost established at Stage 3 rather than from competitor prices, so the price is derived from what the buyer currently loses. The [Van Westendorp](/frameworks/van-westendorp) band constrains it from the buyer-perception side, and the two together produce a range with a stated reason.
ShipFit runs 55 frameworks across 9 decision stages
Value-Based Pricing is one tool in a bigger toolkit. The full library covers market sizing, buyer discovery, MVP scoping, pricing, and launch.
The Mom Test
Q3Rob Fitzpatrick
Validation question methodology, real interviews, not theater
Jobs-to-be-Done
Q2-Q4Clayton Christensen
Functional, social, and emotional jobs your product fulfills
7 Powers
Q4Hamilton Helmer
Strategic moats: Scale, Network, Counter-positioning, Switching, Brand, Cornered Resource, Process
Van Westendorp PSM
Q6Feature-weighted price sensitivity analysis without guessing
Blue Ocean Strategy
Q4Kim & Mauborgne
ERRC framework: Eliminate, Reduce, Raise, Create
Fake Door Testing
Q7Pre-build behavioral validation with landing pages and apology modals
+ 49 more: TAM/SAM/SOM Analysis, Porter's Five Forces, Market Timing Analysis, Unit Economics (LTV/CAC)...
Frequently asked questions
What is value-based pricing?
How do I work out what my product is worth to a customer?
What is the difference between value-based and cost-plus pricing?
What is a value fence?
Does value-based pricing work for consumer products?
Keep exploring
The 9-step playbook from market verdict to ship-ready spec.
Rahul Vohra's method for measuring product-market fit and improving it: the 40% benchmark, the survey mechanics that make it comparable, and the roadmap it produces.
The Mom Test is Rob Fitzpatrick's framework for customer interviews that generate real signal. Not praise. Three rules, applied step-by-step, with examples.
Most founders ship an MVP that's actually V1.3 with bugs. Real MVP scoping cuts ruthlessly until you can name the one hypothesis V1 proves, and ships a product that tests it.
Most early-stage competitive analysis is a 2x2 with your product in the top-right quadrant. The real version is harder, more boring, and tells you whether you can actually win.
Does each customer make you money? Or cost you money?
Two to four weeks of focused work for a single idea. Stage 1 (market verdict) takes a day. Stages 2-3 (buyer + pain) take a week of interviews. Stage 4 (positioning) takes two days. Stage 5 (V1 scope) takes a day. Stages 6-7 (pricing + behavioral evidence) take 1-2 weeks because you need 20+ buyers and a Fake Door Test running. ShipFit compresses the decision time to 30-60 minutes; the gating work is the human conversations between stages.
Validation for solo founders with no cofounder to push back. ShipFit forces 9 decisions and argues with your idea in 2 minutes on real data. Start free.
Claude Code is a brilliant coding tool that will say yes to almost any idea. ShipFit is a decision engine built to disagree with you when the data says no. Use ShipFit to decide what to build. Use Claude Code to build it.
Ready to make your next product a success?
9 decisions between your idea and a product worth building.