Value Based Pricing for SaaS: How to Price and Defend It

Value based pricing for SaaS means you set your price from the economic outcome your product creates for a specific customer, not from what it costs you to build or run. The price tracks their upside, revenue won or cost killed, instead of your AWS bill plus a margin. I have spent over five years selling B2B SaaS, closed more than €4M in career revenue, and the single biggest lever on every one of those deals was not the feature set. It was whether I priced on value and could hold that price when the buyer pushed. That second part, defending it in the room, is where most founders fold. Let me walk you through both.

What value based pricing actually is (and what it is not)

Most SaaS pricing is cost-plus wearing a nicer outfit. You add up your costs, pick a margin that feels safe, glance at two competitors, and land on €49, €99, €299. It feels rational. It is also how you leave enormous money on the table, because your cost has nothing to do with what the customer gains.

Value based pricing starts from the other end. You ask one question: what is the measurable outcome this buyer gets, and what is that outcome worth to them in euros? If your tool helps a sales team book 30 extra qualified meetings a month, and each meeting is worth, say, €800 in pipeline, you are not selling €99 software. You are selling €24,000 a month of pipeline. Suddenly €99 looks almost insulting, to both of you.

To be clear about what this is not: it is not just slapping a bigger number on the same product and hoping. That is cost-plus with ego. Value based pricing is harder than that, because it forces you to actually prove the outcome before you name the price. If you cannot articulate the value in concrete terms, you have not earned the higher number, and the deal will expose that within about ninety seconds.

Why cost-plus pricing quietly bleeds your margins

Here is the trap. Cost-plus feels responsible, so nobody questions it, and it underprices your best customers while overpricing your worst ones. A ten-person startup and a 2,000-person enterprise both pay your €299 tier, even though the enterprise gets fifty times the value and could happily pay fifty times the price. You are subsidising the giants with a number built for the minnows.

It also wrecks your unit economics in a way that is easy to miss until it hurts. When your price is too low relative to the value delivered, you compensate by chasing volume, which inflates your acquisition cost and crushes payback. If you want to see exactly how that cascades, I broke down the math in this piece on SaaS unit economics, CAC, LTV and payback. The short version: a price that is 30 percent too low does not cost you 30 percent of revenue. It can cost you the whole growth model, because every other number is downstream of price.

And cost-plus trains your buyers to haggle. When a price looks like it was reverse-engineered from costs, buyers smell margin and go hunting for it. When a price is clearly tied to the value they receive, the conversation changes from “knock 20 percent off” to “help me justify this internally.” That is a far better room to be standing in.

How to find the value number before you ever name a price

You cannot price on value you have not quantified, and you quantify it in discovery, not in a pricing meeting. This is the part founders skip, and it is the part that makes everything else work. By the time I name a price, the buyer and I have already agreed on the value, out loud, in their words.

I build the value number from three things, and I get them by asking, not guessing:

That last move is the quiet trick. When you sketch the math on the call and the buyer says “actually it’s more like €1,200, not €800,” the value number stops being your sales pitch and becomes their own calculation. People do not argue with their own numbers. I co-founded Pink Pineapple partly on the back of deals that were won in discovery this way, long before anyone opened a pricing page.

Notice I did not say aim for a 10x ratio and then charge one tenth of the value. I said buyers want to see roughly that gap so the decision feels safe. Where you actually land inside that range is a packaging and model question. If you are still deciding how to structure tiers, usage, or seats around your value number, start with SaaS pricing models explained and then the deeper playbook on pricing B2B SaaS to maximise revenue. Value based pricing is the philosophy. The model is how you collect on it.

Defending value based pricing in the room

Here is where it gets real. You can do flawless value discovery and still lose the number in the last ten minutes, because the buyer pushes and your voice goes up half an octave. Defending the price is a skill, and it is mostly about staying calm and pointing back at the value you both already agreed on.

The first rule: do not discount by default. The instant a buyer says “that’s a lot,” most founders reach for a number to shave off. Do not. “That’s a lot” is not an objection, it is a reaction. Your job is to slow down and reconnect price to value, not to flinch. I usually just say something like: “It is a real number, yeah. Let’s put it next to what you told me this is costing you now.” Then I go quiet and let the math sit there.

When a genuine objection does come, handle the type, not the noise:

That last row is the single most useful habit I can give you. Price is never free to give away, so never give it away for nothing. If you concede on the number, you get something in return: a longer contract, an upfront annual payment, a case study, a reference call, a bigger seat count. A discount with no trade teaches the buyer that your price was fiction. A discount with a trade teaches them your price is a position you are willing to defend.

Second rule: sell the price to the person who feels the pain, then arm them to sell it internally. In B2B the human in the room is rarely the only decision maker. Your real job is often to make your champion look smart in a meeting you will never attend. So I hand them the value math in a format they can forward. “Here is the before, here is the after, here is the number, here is why it pays for itself in two months.” You are not defending the price once, you are defending it through someone else when you are not there.

Third rule: be willing to walk. Nothing defends a price like genuine comfort with hearing no. When a buyer senses you need the deal more than they need the outcome, your price becomes negotiable in their mind no matter what you say. When they sense you are fine either way, the value number does the talking. You earn that calm by having a pipeline, which loops right back to doing the discovery work so you are never pricing from desperation.

What this looks like when it works

Value based pricing is not theory for me, it is how I run every engagement. With IKI Health we built the sales motion around the outcome, not the tool, and the first month produced 30-plus qualified calls and two high-ticket deals. The deals were high-ticket precisely because the price was tied to what the product did for them, not to a feature comparison. The number was defensible because the value had already been agreed on, out loud, before anyone saw a contract.

If you take one thing from this: your price is a claim about the value you create, and you have to be able to back the claim and hold it under pressure. Get the value number first. Anchor the price to it. Then defend it like it is true, because if you did the discovery properly, it is.

If your pricing still comes from your costs and a nervous glance at competitors, that is the fastest money you will ever find, and you are probably sitting on a lot of it. I help SaaS founders rebuild this end to end, from the pricing strategy itself to the day-to-day work of a SaaS pricing consultant in your actual sales calls. If you want a straight read on where you are underpriced and how to defend a better number, book a sales audit with me and let’s go find it.

Frequently Asked Questions

What is value based pricing for SaaS?

Value based pricing means you set your price from the economic outcome your product creates for the customer, like revenue gained or cost removed, rather than from what it costs you to build and run it. The price tracks the buyer's upside, not your spreadsheet. Done right, a buyer sees far more value than they pay, so saying yes feels obvious.

How do I figure out the value number if the customer won't share their revenue?

You don't need their full P and L, you need three things: the metric your product moves, how often it moves, and what one unit of that movement is worth to them. Ask about current process cost, time spent, or deals lost, then build the math together in the call. If they correct your numbers, great, now the value number is theirs and much harder to argue with later.

Isn't value based pricing just charging more for the same thing?

No. Charging more without proof is just a higher cost-plus number with extra confidence. Value based pricing requires you to quantify and show the outcome before you name the price, so the figure is anchored to something real. If you can't articulate the value, you haven't earned the price, and the deal will tell you that fast.