Value-Based vs Cost-Based Pricing
Value-Based vs Cost-Based Pricing — 💰 Pricing Strategy for Digital Products. Two questions, two different prices; Functional, emotional, and social value; Turning an outcome into a number; Fictional Taskbook case: the full calculation; Segments and value metrics change the decision; The value-price worksheet. Practical assignment: Estimate a price for one…
Demo edition. The materials are undergoing editorial review.
Topics covered
- Two questions, two different prices
- Functional, emotional, and social value
- Turning an outcome into a number
- Fictional Taskbook case: the full calculation
- Segments and value metrics change the decision
- The value-price worksheet
Two questions, two different prices
Cost-based pricing starts with: “What do we need to charge?” You add the costs of delivering the product and apply a markup. In a fictional example, servers cost $10, support costs $5, and allocated development costs $15 per customer per month. The total cost is $30; a 50% markup produces a $45 price.
Value-based pricing asks: “What is this outcome worth to the customer?” You first estimate the result for a specific segment, then consider charging a share of that value and check whether the resulting price covers your costs.
Cost-plus can be useful for interchangeable products, contracts built around costs or capacity, and as an initial control point. For a differentiated digital product, however, it does not show how much the customer gains from a better feature. It can also suggest cutting the price after reducing a server bill even though the customer’s benefit has not changed.
A practical rule is: costs help set the floor; value and available alternatives constrain the ceiling. That does not mean every price between those points will work. The customer must still recognize and believe the claimed outcome.
Functional, emotional, and social value
Functional value is an observable outcome: hours saved, costs avoided, or additional profit. “The report now takes 30 minutes instead of four hours” is a useful starting point because the difference can be checked.
Emotional value concerns confidence, relief, or a sense of control. Social value appears in relationships: the team coordinates more easily, or a client receives a clearer service. Do not assign an arbitrary dollar amount to these feelings. First build a causal bridge to an observable result. For example: reliable figures → fewer repeated checks → a faster decision. Or: a shared project view → fewer status requests → less staff time spent coordinating.
If that bridge is unverified, keep the benefit qualitative instead of turning an assumption into revenue. The same product can have different value for different segments: saving two hours matters differently to a solo worker and to a team where a delay blocks ten people.
Turning an outcome into a number
Three calculations provide a useful first estimate:
| Outcome | Calculation | | --- | --- | | Time saved | hourly value × hours saved | | Cost avoided | cost of the real alternative − remaining cost after adopting the product | | Additional profit | extra sales × contribution per sale or contribution-margin percentage |
In a fictional example, a tool saves 5 hours a week and the time is worth $50 an hour. That is $250 a week, or $1,000 in a four-week month. Do not mix weekly hours with a monthly rate, and do not call extra sales profit: variable costs may still have to be deducted from revenue.
For scenario analysis, calculate 10%, 20%, and 30% of the estimated value: $100, $200, and $300. These percentages are a teaching heuristic, not a proven universal benchmark. Compare each price with your costs and the next-best alternative. If a $50 spreadsheet provides 70% of the required outcome, saying “we create $1,000 of value” does not by itself justify $500. The relevant advantage is the additional outcome compared with what the customer would actually choose.
Fictional Taskbook case: the full calculation
Assume fictional Taskbook serves a 6-person agency. Each person spends 1.5 hours a week chasing updates in chat and email. Over four weeks, that is 6 × 1.5 × 4 = 36 hours. At a fictional value of $40 per hour, estimated monthly value is 36 × $40 = $1,440. For a simple scenario, round it to $1,400.
Ten percent of $1,400 is $140. If serving the agency costs $6, gross margin is ($140 − $6) ÷ $140 = 95.7%, or about 96%. The main alternative costs $60, so $140 is more than twice its price.
At $12 per user, the agency pays 6 × $12 = $72: about 5.1% of $1,400 and 20% more than the $60 alternative. The calculation shows a small share of estimated value being captured, but it does not prove the price should immediately rise to $140. First verify the original 1.5 hours, the real value of that time, how much of the saving the product causes, and whether the segment considers the advantage over the alternative sufficient.
Segments and value metrics change the decision
An average value across all customers hides important differences. In fictional Taskbook, a small team using only a task list might get nearly the same outcome from a free spreadsheet. An agency with many clients might use the client portal and automations, avoid dozens of status requests, and receive far more value. One price based on an “average customer” may be too high for the first group or too low for the second.
Define the segment by its use situation, then choose a value metric: the unit along which the price changes, such as active users, projects, or processed transactions. A useful metric is observable, understandable on an invoice, and roughly increases with customer benefit. User count is weak when one user can generate all the value or when per-seat charges cause a team to restrict access that would otherwise be useful.
A possible decision for the case is a basic plan for simple work management and a separate agency plan containing the client portal and automations. This is a packaging hypothesis, not a conclusion produced by arithmetic alone; it still needs to be checked with the relevant segments.
The value-price worksheet
Spend 30–45 minutes producing one worksheet for a specific segment. State who the typical customer is, what job they perform, and what alternative they use now. Choose one functional outcome and show the complete calculation using a consistent time period. Add an emotional or social benefit only through an explicit connection to an observable result.
Next, calculate prices at 10%, 20%, and 30% as scenarios. For each, calculate gross margin with (price − cost to serve) ÷ price and the difference from the alternative. If a price is far higher, state the specific additional outcome that could explain the premium and how you could verify it.
Finish with two sentences: “Our current price captures about __% of estimated value” and “Before changing the price, we need to test the assumption that __.” The result is a boundary for further investigation, not an automatic new price.
Practical assignment
Estimate a price for one segment
Continue to learningCourse outline
- Why Most People Price Wrong
- Value-Based vs Cost-Based Pricing
- Talking to Customers About Price
- Free Trials: Fundamentals That Work
- Reverse Trials: The Premium-First Approach
- Freemium vs Free Trial vs Reverse Trial
- Price Testing: Methods and Pitfalls
- Tiering and Packaging
- Selling Annual Plans
- Price Psychology: Anchoring, Decoy, and Charm Pricing
- When and How to Raise Prices
- Your Pricing Launch Checklist