Value Based Pricing in SaaS: Why Only 11% Use It and What to Test

Value-based pricing should be your default when your product delivers measurable outcomes customers can quantify, because it lets you capture more revenue as customers scale rather than leaving money on the table. It also works well when your market tolerates differentiated pricing instead of commodity comparison. The rest of this guide walks through choosing a value metric, running lightweight research, and turning findings into priced tiers you can test.

TL;DR:

• Choose one primary billing metric that customers understand and that tracks value across segments; seats, transactions, or usage fit different products.
• Start with Van Westendorp to establish an acceptable price range, then use Gabor Granger for a specific price and conjoint analysis for tier bundles.
• Survey studies start around $149; basic price tests use 100 to 150 respondents per segment, while conjoint studies benefit from 200 to 300.
• Test prices with new signups separately from decisions about existing customers, and give current customers advance notice of changes tied to renewal.
• Track conversion, contract value, retention, and discounts; falling conversion with steady expansion flags an entry price problem, while weak expansion points to tier upgrades.

Table of Contents

• What value-based pricing means and how it differs from cost or competitor pricing
• Why pricing strategy drives acquisition, conversion, expansion, and retention
• Choosing a value metric: the billing unit that should track customer value
• Pricing research methods: Van Westendorp, Gabor-Granger, MaxDiff, and conjoint
• How to set a value-based price: a step-by-step playbook
• Implementation and governance: packaging, billing, and price discipline
• Practitioner evidence: turning pricing research into measurable revenue
• B2B segmentation and tiering considerations
• Communicating value-based pricing to customers
• Common challenges when moving from traditional to value-based pricing
• Integrating value-based pricing with sales enablement
• Examples of value-based pricing done well in SaaS
• Value-based pricing's effect on acquisition and retention
• Strategic perspective: where SaaS pricing leaders should invest next
• A managed path to turning pricing experiments into revenue
• FAQ
• Sources

What value-based pricing means and how it differs from cost or competitor pricing

The anchor is willingness to pay: what would a customer reasonably spend to capture the outcome your product delivers, whether that's hours saved, revenue generated, or risk avoided. This requires quantifying outcomes in dollars or a comparable unit, then pricing somewhere below that value so the customer keeps a visible surplus.

Two boundaries matter here. Your cost to serve sets a floor: price below it and you lose money on every account. The value the customer perceives sets a ceiling: price above it and they walk away or churn once the novelty wears off. Value-based pricing lives in the gap between those two lines, and the width of that gap is where your margin and negotiating room live.

This differs sharply from the two approaches most SaaS teams default to early on:

• Cost-based pricing starts with your infrastructure, support, and development costs, then adds a margin, a method that ignores what customers actually gain and tends to underprice high-impact products.
• Competitor-based pricing anchors to what similar tools charge, which keeps you safe from obvious mispricing but caps your upside at whatever the market has already settled on, win or lose.
• Value-based pricing starts with customer outcomes and works backward to a price, which is harder to calculate up front but scales naturally as the product delivers more value per account.

Only about 11% of SaaS companies report taking a genuinely value-based approach, while most still lean on cost or benchmark methods, according to survey data on SaaS pricing models. That gap is less a signal that value-based pricing doesn't work and more a sign that most teams default to the easier methods first. Pricing and packaging decisions sit upstream of nearly every growth metric you track, which is the subject of the next section.

Why pricing strategy drives acquisition, conversion, expansion, and retention

Pricing is not a finance decision bolted onto the product. It shapes who tries your product, who converts, how fast accounts grow, and whether they stay. A price set below perceived value leaves revenue on the table at every renewal. A price set above it slows signups and inflates churn once buyers compare outcomes to cost.

The sequence matters: value metric, then pricing model, then tier structure, then measurement, according to a guide to SaaS pricing and packaging from Stripe. Skip a step and the ones after it tend to misfire, since tiers built on the wrong metric fence off the wrong features and measurement ends up tracking the wrong signals.

Companies using platform or usage-based pricing are more likely to hit growth targets compared with base-fee and flat-fee models, according to the 2025 State of SaaS Pricing Report.pdf). That gap suggests pricing models tied to actual consumption give customers a clearer line between what they pay and what they get, which supports both initial conversion and later expansion.

Pricing power also depends on how differentiated your product feels and how costly it is for a customer to switch away. A workflow tool embedded in daily operations, with data, integrations, and trained users locked in, can sustain a higher value-based price than a point solution a buyer could swap out in an afternoon. Switching costs don't excuse overpricing, but they do widen the gap between your price floor and ceiling, which is exactly the room value-based pricing is built to use.

Choosing a value metric: the billing unit that should track customer value

Your value metric is the unit you charge for, seats, API calls, transactions, or outcomes, and it should rise in lockstep with the value a customer receives. Get it wrong and you either cap your own revenue as customers grow or create a billing experience customers resent.

Four properties define a strong value metric. It should be flexible enough to apply across customer segments without constant exceptions. It should be understandable without a sales call to explain it. It should align with customer budgets, meaning the line item makes sense against what they already allocate for the outcome. And it should scale so your revenue grows as customer usage and value grow, not stay flat while usage climbs.

A useful litmus test from the Stripe guide to SaaS pricing and packaging: if you need to explain the metric before you explain the price, reconsider the metric. Seats work cleanly for collaboration tools where headcount tracks usage. API calls or compute units work for infrastructure and data products where consumption is the value driver. Transactions fit payments, scheduling, or marketplace tools where each completed action has a clear dollar value behind it. Outcome-based metrics, like a percentage of revenue recovered or leads converted, fit products where you can isolate your contribution to a result, though they require more trust and more instrumentation to bill accurately.

Each model carries trade-offs:

• Per-seat pricing is simple to forecast and sell but can under-monetize products where value comes from usage intensity rather than headcount.
• Tiered pricing packages features into clear steps, which simplifies sales conversations but risks fencing off a feature customers need at a tier they can't yet justify.
• Usage-based pricing tracks value closely and scales revenue with consumption, but it makes forecasting harder for customers and for your own finance team.
• Hybrid pricing, a base platform fee plus usage, balances predictability with upside, which is why many infrastructure and data-heavy SaaS products land here.
• Outcome-based pricing aligns incentives tightly with customer results but demands clean measurement and a level of trust that takes time to build.

Pro Tip: Pick one primary value metric for your core plan and resist adding a second one until you've validated the first against at least two customer segments.

Most teams revisit their value metric once, maybe twice, in a product's lifetime, because changing it means re-platforming billing and retraining the sales team. Choosing well the first time saves that disruption later.

Pricing research methods: Van Westendorp, Gabor-Granger, MaxDiff, and conjoint

Before you set a number, you need evidence, and four established research methods cover most of what a SaaS team needs to validate pricing, according to a 2026 guide to pricing research methods for SaaS founders.

1. Van Westendorp Price Sensitivity Meter asks customers four questions about price (too cheap, cheap, expensive, too expensive) to map an acceptable price range for a single configuration of your product.
2. Gabor-Granger tests a sequence of specific price points against stated purchase intent, which produces a demand curve and a revenue-maximizing price for that configuration.
3. MaxDiff asks customers to pick the most and least valuable features from small sets, revealing which capabilities actually justify a higher tier.
4. Conjoint analysis, specifically Choice-Based Conjoint, has customers choose between bundles with varying features and prices, which models trade-offs across an entire tier structure rather than one price point.

Van Westendorp is useful only for establishing an acceptable range for a single offer. For tier or bundle pricing, practitioners lean on Choice-Based Conjoint because it models how feature and price trade-offs interact across multiple plans at once.

Sequence these methods by what you already know, a sequence worth calling the Pricing Proof Ladder:

Most founders skip this kind of research entirely, which is where many leave money on the table. Running even one small study produces a defensible price range instead of a guess, according to the SaaS founder pricing research guide.

The cost barrier has mostly disappeared. Self-serve survey tools now let teams run Van Westendorp, Gabor-Granger, MaxDiff, or conjoint studies starting around $149, instead of the multi-week, five-figure consulting engagements these methods used to require, according to the same SaaS Library guide. A sample of 100 to 150 current or prospective customers per segment is usually enough to get directionally reliable results for Van Westendorp or Gabor-Granger. Conjoint studies benefit from larger samples, closer to 200 to 300, because they're estimating more parameters at once.

How to set a value-based price: a step-by-step playbook

Once research gives you a range, turning it into a live price takes four deliberate steps.

1. Quantify the customer outcome in dollars. Translate the benefit, hours saved, revenue generated, risk reduced, into a monetary figure per customer segment, since this number anchors every price conversation that follows.
2. Derive a willingness-to-pay range from research. Use your Van Westendorp or Gabor-Granger output to set a floor and ceiling, then position your list price in the upper half of that range if your product is differentiated or switching costs are high.
3. Map ranges into tiers using feature fences. Use your conjoint or MaxDiff results to decide which features sit behind which price gate, keeping the gates aligned with how different segments actually use the product.
4. Design controlled price experiments before a full rollout. Run A/B tests on pricing pages for net-new signups, and test localized price points in distinct markets before changing global list prices.

A few practical notes make these steps work in production:

• Keep experiment groups large enough to detect a meaningful lift in conversion, not just directional noise.
• Separate new-customer pricing tests from existing-customer grandfathering decisions to avoid legal and trust complications.
• Localize prices based on regional willingness to pay, not just currency conversion, since the two produce very different numbers.
• Track leading indicators (trial-to-paid conversion, expansion revenue per account) before lagging ones (net revenue retention) show the full effect.

International price localization that adapts to actual willingness to pay, rather than simple currency conversion, correlates with higher growth and fewer missed targets, according to the 2025 State of SaaS Pricing Report.

Watch four KPIs after any pricing change: trial-to-paid conversion rate, average contract value, net revenue retention, and discount rate. A drop in conversion with flat expansion suggests the price is too high for new buyers but fine for existing ones. Flat conversion with falling expansion suggests the opposite: your entry price is fine, but your upgrade path isn't compelling enough.

Implementation and governance: packaging, billing, and price discipline

Setting the right price is only half the job. Operating it without chaos requires packaging that creates a visible upgrade path, billing infrastructure that can handle the model you chose, and governance that keeps discounting from eroding the price you worked to establish.

Packaging should make the next tier an obvious next step, not a cliff. Each tier should solve a slightly bigger problem than the one below it, with feature fences that map to genuine differences in customer needs rather than arbitrary feature withholding. If customers consistently ask for a feature from a higher tier shortly after signing up, that's a signal your fences are misplaced, not that your tiers are too aggressive.

Billing for usage-based or hybrid models needs metering infrastructure that can track consumption accurately and bill predictably, since customers tolerate usage pricing far better when their invoice never surprises them. Building this in-house is a real undertaking; most growing SaaS teams adopt billing platforms built for metered and hybrid pricing rather than extending a flat-fee billing system past its limits.

Sales enablement matters as much as the price itself. Reps need language that frames price around the outcome purchased, not the feature list, and they need clear boundaries on what they can discount without approval.

• Equip reps with a one-page value calculator tied to the customer's own numbers, not a generic ROI slide.
• Set discount thresholds that trigger deal-desk review above a fixed percentage, rather than leaving every discount to rep discretion.
• Tie price increases to renewal dates with advance notice, rather than surprising customers mid-contract.
• Review discount data quarterly to catch creeping exceptions before they become the new normal.

Companies with strict discount approval processes keep discounts under 10% much more often than those with flexible or informal guidelines, according to the 2025 State of SaaS Pricing Report. That gap is almost entirely a governance outcome, not a product or market one.

Pro Tip: Put your discount approval rule in writing before your first enterprise deal closes, not after a rep sets a precedent you can't walk back.

Infrastructure-heavy SaaS products tie price increases to renewal cycles more consistently than horizontal SaaS does, largely because switching costs are higher and the increase is easier to justify against measurable usage growth, according to part two of the State of SaaS Pricing report.

Practitioner evidence: turning pricing research into measurable revenue

Pricing experiments only matter if they connect to the growth motion that brings in and keeps customers, and that connection is at the core of effective growth strategies. Effective acquisition and retention systems are necessary to put a new price in front of real buyers, turning research into revenue instead of a slide deck.

A workable experiment sequence looks like this: run a lightweight survey to establish a price range, follow with a small-sample price A/B test on live landing pages, then roll the winning configuration out market by market rather than everywhere at once. Each stage uses actual paid traffic and real signups, which tells you more than a hypothetical willingness-to-pay question ever could.

A few playbook items we rely on when helping clients move from pricing theory to pricing revenue:

• Sequence surveys before paid tests, since a bad price range wastes ad spend testing numbers nobody would pay.
• Set a decision rule in advance for rolling out a price increase, such as requiring a lift in conversion or expansion revenue before expanding beyond the test market.
• Report conversion rate, average contract value, and expansion revenue weekly during any active price test, not just at the end.
• Pair pricing changes with onboarding adjustments, since a higher price only sticks when customers realize the value fast enough to justify it.

Services can be built around this kind of cycle, with paid acquisition testing, sales enablement, and onboarding optimization working together—often enhanced by tools like AI-assisted discovery and eligibility tooling—so a pricing change shows up in monthly recurring revenue rather than staying stuck in a spreadsheet.

B2B segmentation and tiering considerations

Value-based pricing in B2B SaaS rarely means one price for everyone. Different segments perceive different value from the same product, and your tier structure should reflect that rather than forcing a single structure onto every buyer type.

Start by segmenting on the outcome your product delivers, not just company size. A ten-person agency and a ten-person finance team might be the same headcount but derive wildly different value from the same workflow tool, which means they belong in different tiers or even different packaging altogether. Company size, industry, and use case all shape willingness to pay, and a strong value metric should let your pricing flex across those lines without a custom contract for every account.

Enterprise tiers typically earn their premium through things smaller segments don't need: dedicated support, custom security review, higher usage ceilings, or guaranteed service levels. Mid-market tiers often sit on the value metric itself, usage or seats, scaling smoothly as the account grows. Entry-level tiers should still reflect real value, not just a stripped-down trial dressed up as a plan.

Segmentation also protects your value metric from distortion. If a self-serve customer and an enterprise customer both buy per seat, but the enterprise customer gets ten times the operational value per seat, your pricing is systematically undervaluing the segment that matters most to your revenue, a gap that tiering with clear feature and support fences is built to close.

Communicating value-based pricing to customers

Customers resist price increases when they don't understand the value behind them, which makes communication as important as the number itself. The goal is to connect every price point to a specific outcome, not just announce a change.

Lead with outcomes, not percentages. A line that says "this plan includes faster processing that saves your team roughly 10 hours a month" lands better than a bare percentage increase, because it gives the customer something concrete to weigh against the cost. Sales and customer success teams need the same talking points so the message stays consistent whether it comes through an email or a renewal call.

Transparency about why a price is set the way it is also shapes how customers respond. Research on consumer inference, drawn from a study in the Journal of Consumer Research, finds that customers are less likely to accept a higher price when they suspect the seller's motive is purely profit-driven, while independent or transparent cues increase the likelihood they'll accept it. Translated to SaaS pricing: explaining the value basis of a price change, tied to features delivered or outcomes measured, builds more trust than a generic note about rising costs.

Give advance notice before any increase takes effect, ideally tied to the renewal date rather than mid-contract, and give existing customers a clear picture of what's new in exchange for the new price.

Common challenges when moving from traditional to value-based pricing

The hardest part of this transition is usually organizational, not analytical. Three challenges show up repeatedly.

Quantifying value is harder than it sounds. Teams often guess at outcome figures instead of measuring them, which produces a price that looks value-based but is really just a cost-based number with a new label. The fix is to pull real usage and outcome data from existing customers before setting new prices, even if that means delaying the rollout.

Sales teams default to old habits. Reps trained to sell on features or discount their way to a close will keep doing that unless given new language and new discount boundaries. Enablement has to come before the price change, not after.

Existing customers resist new structures. Grandfathering current customers on legacy pricing while applying value-based pricing to new signups avoids a backlash, but it also means running two pricing systems in parallel for a while, which billing infrastructure needs to support cleanly.

Treating value-based pricing as a bolt-on, changing the number without changing the value metric or packaging around it, tends to produce no material improvement in outcomes. The methodology only works when the metric, the packaging, and the price move together.

Integrating value-based pricing with sales enablement

A value-based price only holds up if the sales team can defend it in a live conversation. That means equipping reps with tools and language before the new pricing goes live, not after the first objection comes in.

Give reps a simple value calculator built around the customer's own numbers, so the conversation centers on what the customer gains rather than a list of features. Replace feature-based pitch decks with outcome-based ones that tie each tier to a specific result the buyer cares about.

Discount governance matters just as much as the pitch. A clear rule, discounts above a set threshold require deal-desk approval, keeps individual reps from undermining the pricing model deal by deal. Pricing changes also interact with how reps get paid: a mid-cycle price increase can shift commission calculations and revenue recognition timing, which is worth coordinating with finance under ASC 606 before the change goes live, so compensation plans don't quietly penalize reps for a pricing decision they didn't make.

Train reps on objection handling specific to value-based conversations, since "why did the price go up" needs a different answer than "why is this more expensive than Competitor X," and reps need both scripts ready.

Examples of value-based pricing done well in SaaS

A handful of recognizable patterns show how value-based pricing plays out in practice. Apple's approach to the iPhone and its broader ecosystem is a widely cited example of value-based pricing: pricing is set well above the cost of components because customers pay for the experience, ecosystem integration, and brand value rather than the bill of materials alone. The SaaS parallel is pricing based on the outcome a workflow delivers rather than the server cost of running it.

Payments platforms that charge a percentage of transaction volume rather than a flat subscription fee are another clear case: the price scales directly with the value processed, so a merchant doing $10,000 a month and one doing $1 million a month both pay in proportion to what the platform is actually doing for them.

Infrastructure and data platforms that price on compute or API usage follow the same logic. As a customer's usage grows, so does the value they're extracting, and the price grows with it automatically, without a renegotiation every time the account expands. This is part of why platform and usage-based pricing models correlate with stronger growth-target attainment, as shown in the 2025 State of SaaS Pricing Report: the pricing model itself removes the friction of manually capturing expansion revenue.

Value-based pricing's effect on acquisition and retention

Pricing shapes the entire customer lifecycle, not just the initial sale. On acquisition, a value-based price that's clearly tied to outcomes tends to qualify buyers better: customers who see the value proposition and still sign up are more likely to realize that value and stick around, compared to buyers drawn in purely by a low entry price.

On retention, value-based pricing creates a natural alignment: as the customer's usage or results grow, revenue grows with them, which means expansion happens without a renegotiation fight. This is a meaningful part of why usage and platform-based pricing models show higher rates of meeting growth targets, since expansion revenue accrues automatically rather than depending on a sales team catching every account that outgrew its plan.

The flip side is real too. A value-based price that outpaces what the customer can measurably attribute to your product invites churn at renewal, when the comparison between cost and outcome becomes unavoidable. That's why renewal-linked price reviews, paired with onboarding that helps customers actually realize value early, do more for retention than a price increase alone ever could. Products with high switching costs, such as infrastructure tools using onboarding sequences that embed deeply into daily workflows, can sustain this kind of pricing power longer than point solutions can.

Strategic perspective: where SaaS pricing leaders should invest next

Most SaaS teams still treat pricing benchmarks as the finish line: find the median competitor price, land near it, move on. That's backwards. Benchmarks tell you where the market has settled, not what your specific customers would pay for your specific outcomes. The teams pulling ahead in 2026 are the ones building an actual research capability, running Van Westendorp or conjoint studies routinely, not once during a founding-team debate about pricing.

Value metrics and localization are the two most underused levers. Most teams get the metric roughly right early and never revisit it, even as the product and its value delivery change. Fewer still localize pricing beyond currency conversion, which leaves real growth on the table in markets with different willingness to pay.

Operationally, renewal discipline and discount approval workflows deserve more attention than they get. Pricing power erodes quietly through discounting, not through a single bad pricing decision.

— Admin

A managed path to turning pricing experiments into revenue

Running a Van Westendorp study or building a conjoint survey is within reach for most teams now, but connecting a validated price to real paid traffic, qualified leads, and a sales process that actually closes at the new number is a different kind of work. That's the gap we close at SaaSLaunch.

We build the acquisition engines, sales processes, and retention systems that turn a pricing decision into measurable monthly recurring revenue, running the paid acquisition tests that validate a price point with real buyers, then building the sales enablement and onboarding that make the new price stick past the first renewal. One client engagement documented in our agency coaching case study shows the kind of compounding result a tightly run acquisition and conversion system can produce. If you've done the pricing research and want a hands-on team to run the paid tests, sales enablement, and retention work that turn it into revenue, see what we offer and get a sense of what a working engagement would look like for your product.

FAQ

What is value-based pricing in SaaS?

It requires a mindset shift across product, marketing, sales, and support, since every team has to help quantify and communicate that outcome, according to a quick guide to value-based pricing from Harvard Business Review.

What is Apple's value-based pricing strategy?

Apple prices products like the iPhone well above component cost because customers are paying for the experience, ecosystem integration, and brand value rather than the parts list. It's a commonly cited example of pricing anchored to perceived value instead of production cost, and the same logic applies when a SaaS product prices around the outcome it delivers rather than its server costs.

What is volume based pricing in SaaS?

Volume-based pricing charges customers according to the quantity they consume, such as number of transactions, API calls, or users, so the bill scales directly with usage. It overlaps with value-based pricing when the volume metric tracks genuine customer value, which is part of why platform and usage-based pricing correlates with stronger growth-target attainment, as shown in the 2025 State of SaaS Pricing Report.

How do I know which pricing research method to run first?

Start with Van Westendorp if you have little existing pricing data, since it establishes a general acceptable range with minimal setup. Move to Gabor-Granger once you need a specific revenue-maximizing price, then use MaxDiff or conjoint analysis once you're ready to design multi-tier packaging, following the Pricing Proof Ladder sequence.

What KPIs should I track after a pricing change?

Track trial-to-paid conversion rate, average contract value, net revenue retention, and discount rate in the weeks following any pricing change. A drop in conversion alongside stable expansion usually points to an entry price that's too high, while stable conversion with falling expansion suggests the upgrade path itself needs work.

Sources

• Pricing research methods for SaaS founders (2026 guide)
• To Profit or to Assist? How the Interplay Between Product Recommendations and Relative Prices Impacts Consumers’ Inferences and Choice

Recommended

• Turn SaaS Pricing Into Paid Acquisition Growth for Founders and PMs
• Convert Trials in Week 1: A Data Backed SaaS Lead Generation Playbook
• Cut Churn and Grow MRR With SaaS Content Strategy for Marketing Teams
• 90 Day SaaS Go to Market Plan for Founders: Validate One Motion