Most SaaS pricing decisions are competitor-benchmarking exercises. The founder looks at what similar products charge and sets a price nearby. This anchors the price to the competitors’ cost structures, not to the customers’ value perception. Those are different numbers.

The customer value perception number is what the buyer thinks the product is worth given their specific situation. It can be higher than the competitor price. It can be much higher. Most founders never find out because they anchored to the competitor benchmark before testing the customer’s perception.

The Three-Input Pricing Framework builds pricing decisions from customer evidence, competitive context, and cost structure in the right order. This article is for the founder who has set their price based on what competitors charge and hasn’t revisited it since.

Why Competitor-Anchored Pricing Underperforms

The obvious failure mode: the price is set below the competition on the assumption that lower price wins more deals. Win rates don’t improve. The lower price signals lower value.

The deals that would have closed at full price close at the discounted price. The deals that wouldn’t have closed at the discount close at the discount and then churn. The value match wasn’t there.

The less visible failure is that pricing-based competition attracts price-sensitive buyers. Price-sensitive buyers churn at higher rates than value-driven buyers. The pricing strategy that optimizes for conversion produces a customer base that optimizes for churn.

The deepest failure is permanently anchored expectations. Once the market knows what you charge, moving the price upward requires re-educating everyone who evaluated you at the lower price. The cost of underpricing compounds over time and is very difficult to undo.

The Three-Input Pricing Framework

Input 1: Customer value perception

Customer value perception is what the buyer is willing to pay given the specific outcome the product delivers to them.

Value perception is found in:

  • What buyers say when asked “what would you pay to eliminate this problem?” in discovery calls
  • What buyers say when comparing the product to their current solution in win calls
  • What buyers cite as the price objection threshold in lost deal interviews

The value perception input requires asking different questions than founders typically ask in sales calls. Most sales calls surface what the product does. The value perception questions surface what the outcome is worth.

Input 2: Competitive pricing context

Competitive pricing context is where your price sits relative to alternatives in the buyer’s evaluation.

This is not just what competitors charge. It includes:

  • What price the buyer was comparing you against (could be a competitor, a consultant, or a spreadsheet)
  • How the buyer described the price comparison in the sales conversation
  • Whether price came up as a positive signal (you’re cheaper for comparable value) or a negative signal (you’re more expensive for unclear differentiation)

The pricing context data lives in sales conversation notes and win/loss records. It is rarely analyzed systematically.

Input 3: Cost structure

Cost structure defines the floor below which pricing becomes unprofitable.

For SaaS, the relevant cost structure inputs are:

  • Gross margin requirement (what percentage of revenue needs to survive after cost of goods sold)
  • Customer acquisition cost (what it costs to bring in a customer, which the pricing needs to recover)
  • Required payback period (how many months until the customer pays back their acquisition cost)

Cost structure sets the floor. Customer value perception sets the ceiling. Competitive pricing context tells you where within that range the market is currently positioned.

How the Conductor Surfaces the Pricing Evidence

The pricing conversation that used to mean a whiteboard and a lot of guesswork takes twenty minutes when the evidence is already in hand. The difference is not a better spreadsheet. It is that the inputs a pricing decision needs have been gathered as they happened rather than reconstructed under deadline.

Three kinds of evidence sit in the Library. The first is what customers said about value in sales calls. The second is what they said about price when they switched or stayed. The third is what the win/loss records show about price in deal outcomes.

Ask the Conductor: “From last quarter’s sales calls and win/loss records, where do customers perceive value and where do they hit price resistance?” The Conductor is the AI that reads your own deal history rather than the open market, so its answer reflects what real buyers did. The pricing review opens on that, not on where a benchmark says a company like this should land.

The sales process documentation from Article 22 is one of the sources the Conductor queries when answering this question. Pricing objections documented in Part 3 of the sales process are a direct input to pricing decisions.

Run the Value Perception Test Before the Next Pricing Review

In the next five discovery calls, add one question at the moment when the prospect describes the problem: “What would it be worth to your team to solve this completely?”

Do not suggest a number. Do not anchor. Let the prospect answer.

After five calls, you have five data points on customer value perception that your current pricing either captures or leaves behind.

The Price Set by Competitor Benchmarking Is Usually Too Low

The founders who find out what customers are actually willing to pay almost always find the number is higher than their current price. Not always. But often.

The competitor-benchmarked price captures some of the value the product delivers. The evidence-based price captures more. Try Kiluma free for 14 days at kiluma.ai.