The Value-Based Pricing Revolution: The More Value Users Receive, the More They Should Pay – How to Apply It and Why It Is Inevitable

The sentence I hear most often in pricing meetings is this: “The competitor charges 49 dollars a month, let's come in a bit under.”

There's a quiet surrender inside that sentence. You're handing the right to set your price to your competitor. And you don't even know how they set theirs. Most likely, they looked at someone else too. When an entire market copies each other's prices, nobody has actually asked customers what they're getting.

The second most common sentence is about cost: “Our server and support cost per user is this much, let's add a reasonable margin.” At least this approach won't put the company in the red. But in software, the link between cost and value barely exists. Serving one customer might cost you pennies, while the difference your product makes for that same customer is worth thousands. Cost-plus pricing hands that entire difference to the customer as a gift.

Three paths, three different questions

There are basically three ways to set a price, and each one asks a different question.

Cost-plus asks, “What does it cost us?” Competitor-based asks, “What is the market charging?” Value-based asks, “What does the customer gain from this?”

The first two look inward and sideways. The third looks at the customer. Since the start of this series I've argued that value is created on the customer's side. If that's true, price has to come from there too.

Customers should pay as much as the value they receive. Not a cent more, and not much less.

The second half of that sentence usually gets overlooked. Value-based pricing doesn't just mean asking for more money. It also means not charging, or charging little, to customers who aren't getting value. The sense of fairness is the model's greatest strength. A customer looking at their invoice should be able to say, “Yes, that makes sense.”

Finding the value metric

In practice, value-based pricing starts with finding the right value metric. I touched on this in the previous piece; here I want to make it more concrete.

There are three common structures. Per-seat pricing looks at how many people use the product. Usage-based pricing looks at how much the product is used: messages sent, transactions processed, data stored. Outcome-based pricing looks at what the product achieves: customers won, tickets resolved, revenue recovered.

These three form a ladder that climbs closer to value. Seat count is a distant proxy; it assumes value grows with headcount. Usage is closer, but still a proxy; heavy use doesn't always mean high value. Outcome is the closest to value itself.

So why doesn't everyone price on outcomes? Because outcomes are hard to measure, attribution is debatable, and for the customer the bill can become unpredictable. Not knowing “what will my bill be at the end of the month?” is an unacceptable risk for many companies. The right metric is usually not the perfect one, but the one close enough to value that customers can understand it and trust it.

Measuring willingness to pay

The most feared part of value-based pricing is asking customers directly about money. Teams either never do it or do it badly.

The bad version is asking, “How much would you pay for this?” People don't answer that honestly; they either lowball to push the price down or overstate out of politeness.

A better starting point is the often-cited Van Westendorp method. You ask four questions: At what price would this be so cheap you'd doubt its quality? At what price would it feel like a bargain? At what price would it start to feel expensive, but you'd still consider it? At what price would you not consider it at all? Where the answers intersect gives you an acceptable price range. Not an exact number, a range. But that range is far firmer ground than a figure you guessed by looking at a competitor.

What I value most, though, is the conversation beyond the numbers. When you ask customers how they did this job before your product, how much time and money they spent, what they lost when they made mistakes, you hear the true size of your value in their words. These conversations are often surprising. A feature you thought was trivial is, on its own, the reason someone pays. Another you proudly showcase means nothing to anyone.

Segments don't get the same value

A natural consequence of thinking in value is this: different customers get different value from the same product.

A solo freelancer and a fifty-person agency may use the same tool. For one, it saves a few hours a week; for the other, it's the backbone of the entire operation. Charging both the same price means either losing one or undercharging the other.

That's the real job of packaging: mapping different levels of value to different price levels. Each plan should be shaped around the value a specific customer type receives, not around feature counts. To do that, you first need to know your segments. Who uses your product, for which job, to reach which outcome?

Moving forward with small experiments

The shift to value-based pricing doesn't happen in one big decision. I always recommend small steps.

Testing a new plan structure on new sign-ups is the safest way to learn without disrupting existing customers. Applying a value metric to a single segment first gives you results without putting your whole customer base at risk. When announcing price changes to current customers, keeping the old price for a while lets you move forward without damaging trust.

The most dangerous stance in pricing is deciding once and never touching it again. The second most dangerous is changing it randomly every month. The right way is to move like you would with any other product decision: with a hypothesis, with measurement, with patience.

Why it's inevitable

In the title I called this shift inevitable. I mean something specific by that.

With AI, the amount of work many products deliver per user is changing dramatically. What used to take ten people can now be done by one person and a piece of software. In that world, per-seat pricing starts to undermine itself. The better your product works, the fewer seats a company needs, and the less you earn.

That's why in the years ahead we'll see pricing shift from counting people to measuring work done and outcomes delivered. Companies that prepare for this early will keep capturing the value they create. Those clinging to seat counts will watch their revenue erode as their product gets better.

In the next piece I'll zoom in on a much smaller moment: the one where the customer reaches for their wallet. Where, when and why to place a paywall.