Almost every SaaS pricing page claims to be "value-based." Almost none of them are. Real value-based pricing means the price is set by estimating the economic value the customer captures from your product and taking a defensible share of it — not by adding a margin to your cost to build the thing, and not by pricing a few dollars under or over the nearest competitor. Cost-plus and competitor-matching are both easier to defend in a board meeting because they're legible and comparable. Value-based pricing is harder to defend because it requires an actual model of customer economics, which most companies never build — so they use the phrase in their pitch deck and price on competitor anchoring anyway.
The three pricing philosophies, and why two of them win by default
Cost-plus pricing asks "what did this cost us to build and run, plus a margin" — it guarantees profitability on paper but has no relationship to what the customer would actually pay, which means you either leave money on the table with customers who'd gladly pay more, or you overprice a commodity feature nobody values highly. Competitor-matching asks "what does everyone else charge" — it's fast, defensible, and avoids sticker-shock objections, but it also caps your price at the market's current consensus even when your product delivers meaningfully more value, and it locks you into following competitors' pricing mistakes. Value-based pricing asks "what is this worth to the customer, in their own terms" — hours saved, revenue protected, risk avoided, headcount not hired — and prices against that. It wins on defensibility with sophisticated buyers and on margin, but only if you can actually quantify the value, which is the part almost everyone skips.
Ask anyone on the pricing team: "If we doubled the price tomorrow, which specific customer segment would still say yes, and why?" If the honest answer is a guess, you're not pricing on value, you're pricing on nerve. Real value-based pricing means you can name the dollar value a segment gets and show your price is a defensible fraction of it — commonly cited rules of thumb put a sustainable price somewhere in the 10-20% range of the quantifiable value delivered, though the right fraction varies a lot by category and switching cost.
How to actually estimate a value metric, without faking precision
Estimating value doesn't require a management consultancy engagement — it requires talking to customers about outcomes in their own units before you talk about price. For a tool that automates a manual process, that's hours saved multiplied by a loaded hourly cost. For a tool that reduces error or risk, it's the expected cost of the errors it prevents, which requires customers to be honest about how often those errors happened before. For a tool that drives revenue, it's incremental revenue attributable to the tool, which is the hardest to isolate and the easiest to overclaim. The discipline that matters isn't modeling precision — it's triangulating with a range from multiple customer conversations and multiple methods, then pricing conservatively against the low end of that range so the value story survives scrutiny from a skeptical buyer's finance team, rather than presenting a single suspiciously precise number that collapses under the first "how did you calculate that."
Why most SaaS companies claim value-based pricing but don't practice it
Value-based pricing requires two things most companies underinvest in: customer research deep enough to quantify outcomes, and organizational nerve to price above the market average when the value case supports it. It's much easier to open a competitor's pricing page, subtract 10%, and call the resulting number "value-based" because the deck says the product delivers more value than the competitor's. That's competitor-matching with better branding. The tell is usually in how pricing changes over time: companies practicing real value-based pricing adjust price when the value delivered changes — a new capability that meaningfully increases outcomes justifies a price increase independent of what competitors charge — while companies doing competitor-matching mostly move price in response to what competitors do, regardless of what their own product just got better at.
Telling a buyer "this is worth $200k a year to you, so $30k is a bargain" only lands if you can show your work in terms the buyer already trusts — ideally their own numbers, validated by their own team, not a case study from a different industry. A value claim asserted without a customer-specific calculation reads as a sales tactic, and a skeptical buyer will price-anchor you right back down to the competitor rate you were trying to price above.
Wrapping up
Value-based pricing is real, and it's the only one of the three philosophies that can justify pricing above the market average without relying on a lucky lack of competition. But it only works if you do the unglamorous part: quantify the customer's outcome in their own units, triangulate a defensible range instead of faking a precise number, and revisit price when the product's delivered value actually changes — not just when a competitor moves. Most companies skip that work, price off the competitor's page instead, and borrow the value-based label for the pitch deck. The label is free. The pricing power it implies is not.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.