Price and value are often used as if they mean the same thing. They do not. Price is a number on an invoice. Value is the benefit the customer gets, measured in their own terms: money saved, revenue gained, risk reduced, time freed. A customer buys when they believe the value comfortably exceeds the price. Every pricing approach is ultimately a way of deciding where in the gap between cost and value the price should sit.
Three ways to set a price
Cost-plus pricing starts with what it costs you to deliver and adds a margin. It is common in IT services, where effort is estimated in person-months and multiplied by a rate. It is simple and defensible, but it ignores the customer completely. A fix that saves a client ₹5 crore and one that saves ₹5 lakh would be priced identically if they took the same effort.
Competitor-based pricing looks at what alternatives cost and positions relative to them: a little cheaper, at parity, or at a premium. It reflects market reality but assumes the products are comparable, which is often untrue, and it can lead to a race to the bottom.
Value-based pricing starts from the customer’s perspective: what is this worth to them compared with the best thing they could do instead? Cost becomes a floor, below which you should not sell, rather than the starting point.
Economic value, step by step
A structured way of thinking about this, described by Thomas Nagle and colleagues in The Strategy and Tactics of Pricing, is economic value estimation. It has two components.
Reference value is the cost of the customer’s next best alternative. That might be a competitor’s product, an in-house solution, or simply continuing as they are.
Differentiation value is the worth of whatever makes your offer better or worse than that alternative. Positive differences add value; negative ones, such as a longer implementation, subtract it.
Total economic value is reference value plus net differentiation value. It is the most a fully informed, rational customer should be willing to pay.
A worked example: accounts payable automation
A mid-sized manufacturer processes supplier invoices manually. It is evaluating two automation tools. The established competitor costs ₹20 lakh a year and would let the company redeploy six accounts staff, each costing about ₹6 lakh a year, so ₹36 lakh of savings.
Your product delivers the same labour savings. It also has a feature the competitor lacks: it approves invoices fast enough for the company to capture early-payment discounts from suppliers. Suppose suppliers offer 2% off for early payment and about ₹20 crore a year of invoices qualify. In principle that is ₹40 lakh. But the competitor can capture some of these discounts too, just less reliably. If a careful analysis suggests your product would capture an extra ₹15 lakh beyond what the competitor achieves, that is your differentiation value.
- Reference value: ₹20 lakh (the competitor’s price)
- Differentiation value: ₹15 lakh (extra early-payment discounts)
- Economic value: ₹35 lakh
Notice what is not in that calculation: the ₹36 lakh labour saving. Both products deliver it, so it does not justify paying more for yours. This is the most common error in value selling: claiming credit for benefits any alternative would also provide.
Pricing at the full ₹35 lakh leaves the customer no reason to switch, because they would be indifferent. A price of perhaps ₹26 to ₹30 lakh shares the differentiation value: the customer gets a better deal than the alternative, and you get a premium over the competitor that is grounded in something measurable.
What this changes in a sales conversation
Value-based pricing only works if the seller knows the customer’s numbers. That is why discovery matters so much. Without knowing invoice volumes, supplier terms and current approval times, the salesperson cannot quantify differentiation value, and the conversation falls back to comparing prices.
It also changes how price objections are handled. When a buyer says “your product is ₹8 lakh more expensive”, a value-aware seller does not immediately discount. They return to the difference: does the buyer agree with the early-payment estimate? If the buyer disputes it, that is a useful conversation. Perhaps fewer invoices qualify than assumed, in which case the price premium may genuinely be unjustified for this customer.
Packaging value into tiers
In SaaS, value-based thinking also drives packaging. Different customer segments get different value from the same features. A small business might value basic automation; a large enterprise might value audit trails, approval workflows and ERP integration far more. Tiered plans let each segment pay roughly in line with the value it gets. The choice of pricing metric matters too: charging per invoice processed tracks value more closely than charging per user, if value grows with invoice volume rather than headcount.
Limits and honest caveats
Value is perceived, not just calculated. A customer who does not believe your early-payment estimate will not pay for it, however solid the model. Credibility through references, pilots and customer data matters as much as the arithmetic.
Value also varies between customers. A single list price cannot match every customer’s economic value, which is why value-based pricing in practice involves segmentation, tiering and sometimes negotiation within limits.
And value-based pricing does not mean charging whatever the market will bear. Overreaching damages trust and invites competition. The aim is a price the customer can see is fair relative to their alternatives, which happens to be the most durable kind of price there is.
Written by the RP Strativa Team. The company and figures in the example are illustrative.
Leave a Reply