SaaS pricing research turns pricing from an internal debate into an evidence-driven decision. Instead of asking founders, sales leaders or competitors what the product should cost, research examines what customers value, how much they are willing to pay, which value metric makes sense, which plan differences matter, and how price affects conversion, retention and expansion. The strongest pricing process combines qualitative interviews with quantitative surveys, product usage, sales data, competitor context and real purchase behavior. No single method produces a permanently correct number. Customer value changes as the product, market and competitive alternatives evolve, so pricing research should be treated as a recurring operating discipline. Current guidance from Stripe and Paddle similarly emphasizes customer value, willingness to pay, segmentation and testing rather than relying on cost-plus formulas alone. This guide explains the major SaaS pricing research methods and how to combine them into a practical process before launching, repricing or restructuring your plans.
Start With the Pricing Decision You Need to Make
Pricing research becomes more useful when the question is specific. “What should we charge?” is too broad because price is connected to packaging, value metrics, customer segments, annual billing and sales motion. Define the decision before choosing the research method. You may need to know whether a Starter plan should exist, whether enterprise buyers will accept a platform fee, whether per-seat pricing discourages adoption, how much annual discount is necessary, or whether customers prefer usage-based billing. Each question requires different evidence. Interviews can uncover why customers value the product, while a willingness-to-pay survey can estimate price ranges and product data can reveal natural usage segments. A clear decision also prevents research from producing a large collection of interesting comments that do not change the commercial model. Write the decision, the customer segment and the hypotheses first, then select methods that can confirm or challenge those assumptions.
Interview Customers Before You Survey Them
Qualitative interviews should usually come before a large pricing survey because they reveal the language, outcomes and alternatives customers actually care about. Speak with new customers, long-term customers, power users, churned accounts, lost prospects and enterprise buyers when possible. Ask what problem existed before the product, what they used instead, what changed after adoption, which capability matters most, what would happen if the product disappeared and how the purchase was justified internally. Avoid turning the interview into a direct negotiation by asking only “what would you pay?” Customers are more reliable when describing trade-offs, alternatives and perceived value than when inventing one hypothetical number. The interview also reveals which variables belong in the survey. If customers repeatedly talk about transactions rather than users, that may indicate a better value metric. If enterprise buyers focus on risk and governance, plan packaging should reflect those outcomes rather than only feature quantity.
Research Customer Alternatives and the Cost of Doing Nothing
Willingness to pay depends on what the customer would do without your product. The alternative may be a competitor, a spreadsheet, manual labor, internal development, a collection of smaller tools or simply leaving the problem unsolved. Quantify those alternatives because they establish commercial context. If a customer already spends $2,000 per month on an inefficient process, a $500 SaaS product can look inexpensive even when competitors charge less. If the problem is optional and a free workaround is good enough, a premium price will be difficult to sustain. Ask customers what they used before, why they changed, what switching cost existed and what the old workflow cost in time, money or risk. This also improves positioning because pricing is easier to defend when the company can explain the economic difference between the product and the real alternative. Competitor pricing should be included as evidence, but it should not define the final price automatically.
Use Van Westendorp for Perceived Price Ranges
The Van Westendorp Price Sensitivity Meter is a survey method that asks respondents four price questions: when the product feels too cheap to trust, when it feels like a bargain, when it starts to feel expensive but still worth considering, and when it becomes too expensive to buy. The method can help identify perceived pricing boundaries and compare sensitivity across customer segments. It should not be treated as a machine that outputs the correct SaaS price because respondents are still answering hypothetical questions. The strongest use is directional: compare segments, package concepts or customer maturity levels and identify where perceptions differ. Use realistic product descriptions and make sure respondents understand what is included. A survey filled with unqualified prospects can produce misleading results because willingness to pay depends on use case and value received. Combine Van Westendorp results with interviews, usage behavior and real sales data before changing public pricing.
Use Gabor-Granger to Estimate Purchase Intent at Different Prices
The Gabor-Granger method presents a product at different price points and asks how likely the respondent would be to purchase. By varying the price across respondents or sequentially, the company can estimate how demand changes and model potential revenue. This is more directly connected to purchase intent than asking for one open-ended price, but it remains survey evidence rather than an actual transaction. The method works best when the product and package are clearly defined and respondents resemble real buyers. Analyze results by segment rather than averaging enterprise and SMB customers together. A price that maximizes expected revenue for one group may suppress adoption in another. Gabor-Granger can also compare monthly and annual offers or different packaging concepts. Use the results to identify promising ranges for real-world testing, not to justify false precision. Actual proposal acceptance, conversion and retention should validate whether the survey reflected real buyer behavior.
Use Conjoint Analysis When Packaging Is the Real Problem
Conjoint analysis is useful when customers choose among combinations of features, limits, support levels and prices rather than evaluating one number in isolation. Respondents select between hypothetical packages, allowing researchers to estimate the relative importance of different attributes. This can reveal whether customers value automation more than storage, whether SSO materially increases enterprise willingness to pay, or whether a higher usage allowance matters more than premium support. Conjoint research is more complex to design and analyze than a simple pricing survey, so it is most useful when the SaaS product already has enough customers and plan complexity to justify the effort. Poorly chosen attributes can create misleading results. The package options should reflect realistic commercial decisions, and price must be included as one of the attributes. Conjoint is strongest for packaging architecture rather than for finding a single perfect list price.
Analyze Sales Data and Discount Behavior
Sales conversations contain valuable pricing evidence because prospects are making real decisions with real budgets. Review accepted proposals, lost deals, discount requests, procurement objections, sales-cycle length and reasons for choosing competitors. If nearly every enterprise deal closes only after a 30% discount, the issue may be list price, packaging, weak value communication or sales behavior. If customers accept the price quickly but negotiate heavily on implementation, the commercial problem may sit outside the subscription. Track discount rate by salesperson, segment, geography and plan because averages can hide inconsistent behavior. Also examine whether discounted customers retain differently from full-price accounts. Heavy discounting can attract customers who were never a strong fit. The SaaS pricing discounts guide explains how to govern concessions while preserving pricing integrity. Sales data is especially useful because it reflects actual buyer resistance rather than hypothetical survey intent.
Use Product Usage to Find Natural Pricing Segments
Product data can reveal pricing structure that customer interviews alone cannot show. Analyze users, usage, transactions, storage, automation, AI activity, feature adoption and team size across accounts. Look for clusters that correspond to different levels of value or cost. If high-retention customers naturally use one feature set and larger organizations consistently need another, those patterns can support tier design. If accounts with similar seat counts have radically different usage and economic value, per-user pricing may be a weak metric. Usage distributions are also essential for setting allowances in hybrid or consumption pricing. Model the 25th, 50th, 75th, 90th and 99th percentile rather than relying only on averages, because power users can create both expansion opportunity and margin risk. Product data shows what customers actually do after buying, which often provides stronger pricing evidence than what they said they expected to do before purchase.
Run Win-Loss Analysis for Pricing and Positioning
Win-loss interviews with prospects can distinguish pricing problems from broader product or sales problems. A lost deal labeled “too expensive” in CRM may actually mean the buyer did not understand differentiation, needed a missing integration, preferred a competitor’s contract structure or lacked urgency. Speak directly with a sample of won and lost prospects and ask how they compared alternatives, what nearly stopped the purchase, how the price felt relative to value and which commercial terms mattered. Separate the headline objection from the underlying reason. If a competitor wins consistently despite a higher price, reducing your price may not solve the problem. If buyers love the product but cannot fit the minimum commitment into budget, packaging may be the issue. Win-loss analysis is particularly valuable before a price cut because it prevents the company from responding to every sales loss as though lower pricing is the universal answer.
Measure Willingness to Pay by Customer Segment
Pricing research should almost never report one company-wide willingness-to-pay number. Different segments can receive different value and have different budgets. Compare SMB, mid-market and enterprise customers; different industries; high-value use cases; geographies; team sizes; and acquisition channels where sample size permits. Paddle’s 2026 pricing guidance, for example, highlights that willingness to pay can vary by region and that B2C, B2B and enterprise businesses often require different pricing structures. Segmentation can reveal where the company is underpricing or overpricing. A low universal price may be necessary to convert small businesses but can leave enterprise value uncaptured. Instead of forcing one compromise, the company can use tiers, value metrics or enterprise contracts. Segmentation should remain commercially defensible: the difference in price should correspond to differences in value, scale, service or product requirements rather than arbitrary customer characteristics.
Test New Pricing With Customer Cohorts
Survey research should eventually be validated through real customer behavior. One practical method is to launch new pricing for new customers while preserving the existing structure for the installed base temporarily. Compare conversion, plan mix, average revenue, annual adoption, discounting, retention, expansion and support behavior across cohorts. Avoid changing too many variables simultaneously if you want to understand what caused the result. A new price combined with new plan names, feature packaging and trial rules may improve performance, but you will not know which element mattered. Price testing also requires ethical and operational care because customers can react negatively when identical buyers discover different long-term prices. Use controlled rollouts, segment tests or time-based cohorts rather than endless randomized pricing. The goal is to validate research with actual willingness to pay while preserving commercial consistency.
Do Not Optimize Only for Initial Conversion
A lower price can improve conversion while reducing revenue quality. Customers attracted by a cheaper plan may churn faster, demand more support, expand less or generate lower gross margin. A higher price can reduce signup volume while improving average revenue and customer commitment. Pricing research should therefore measure the full customer lifecycle. Track logo churn, gross revenue retention, net revenue retention, expansion, downgrades, margin, customer acquisition payback and lifetime value by price cohort. Usage-based products also need consumption growth and bill volatility. The strongest price is not necessarily the one with the highest landing-page conversion rate. It is the one that creates the best long-term relationship between customer value and company economics. Our SaaS pricing best practices guide covers these downstream metrics in more detail.
How Often Should SaaS Pricing Research Be Repeated?
A formal pricing review at least annually is a useful discipline for many SaaS companies, but major product or market changes can justify research sooner. New AI capabilities, different infrastructure costs, expansion into enterprise, new competitors, changing customer segments or rising discount pressure can all alter willingness to pay. Pricing research does not always lead to a price increase. It can reveal that plan packaging is confusing, a value metric is outdated, annual discounts are too generous, or one segment should receive a new tier. Keep a continuous feedback loop through sales objections, churn reasons, product usage and customer interviews so the company does not wait years before discovering that monetization has drifted away from value. Stripe’s value-driven pricing guidance similarly emphasizes ongoing customer listening, quantitative research and behavioral evidence rather than treating pricing as a one-time launch exercise.
A Practical SaaS Pricing Research Process
A practical sequence is: define the pricing decision, segment customers, run qualitative interviews, quantify customer outcomes, map alternatives, analyze sales and product data, then choose a quantitative method such as Van Westendorp, Gabor-Granger or conjoint when appropriate. Build several pricing and packaging hypotheses and model what representative customers would pay. Validate the most promising structure through real proposals or new-customer cohorts. Measure conversion, revenue, retention, expansion and margin, then revisit the research when evidence conflicts with the original assumptions. This process avoids the two extremes of pricing by intuition and pricing by survey alone. Research should reduce uncertainty enough to make a better commercial decision, not create the illusion that one statistical output eliminates judgment. The value-based pricing guide can help connect these methods to customer outcomes and value metrics.
Final Verdict
SaaS pricing research is strongest when qualitative insight, quantitative analysis and real buying behavior reinforce one another. Customer interviews reveal the value story, surveys estimate sensitivity, product data exposes natural segments, sales data shows real resistance and cohort testing validates whether customers actually behave as predicted. Do not search for one permanently correct number. Build a pricing system that reflects customer value and can evolve as the market changes. Segment the evidence, measure long-term economics and distinguish pricing problems from packaging or positioning problems before making large changes. A disciplined research process reduces the risk of underpricing, overpricing and unnecessary complexity while giving founders and revenue teams a defensible reason for every major pricing decision.
Frequently Asked Questions
What is SaaS pricing research?
SaaS pricing research is the process of gathering evidence about customer value, willingness to pay, packaging preferences, value metrics and price sensitivity before setting or changing prices. It can include customer interviews, surveys, competitor analysis, product usage, sales data, win-loss interviews and real pricing tests. The objective is to reduce uncertainty and create a pricing model that customers understand and that produces sustainable conversion, retention, expansion and margin.
What is the best method to measure willingness to pay?
No single method is universally best. Van Westendorp can identify perceived price ranges, Gabor-Granger can estimate purchase intent at different prices, and conjoint analysis can evaluate trade-offs between price and package features. Customer interviews and real sales behavior are necessary to interpret the results. The strongest research combines multiple methods because survey answers remain hypothetical until customers make actual purchase decisions. Choose the method according to the pricing question you need to answer.
How many customers should be interviewed for pricing research?
The required sample depends on how many customer segments you need to understand and how diverse the market is. Qualitative interviews are useful when patterns begin repeating consistently within a segment, while quantitative surveys require larger samples for reliable comparison. It is usually better to speak with a smaller group of highly relevant customers than a large group of poorly qualified respondents. Include different lifecycle stages such as new, long-term, churned and lost prospects so the research does not reflect only your happiest customers.
Should SaaS copy competitor pricing?
No. Competitor pricing is useful for understanding market conventions, buyer expectations and possible value metrics, but competitors may serve different segments, have different costs or simply have weak pricing themselves. Use competitors as context and combine that information with customer value, willingness to pay, product usage and margin analysis. A differentiated product can justify a different model or price when the customer outcome and positioning support it.
How often should SaaS pricing be researched?
A formal annual review is a practical baseline for many companies, but research should occur sooner when the product, costs, customer segments or competitive environment changes materially. New AI features, enterprise expansion, strong discount pressure or changing usage patterns can all justify a new study. Continuous signals from sales, product usage, churn and customer success should be monitored even between formal pricing projects.
Can pricing research tell you the exact right price?
No. Research can identify ranges, customer segments, sensitivity and likely trade-offs, but the final price still requires commercial judgment and real-world validation. Customer willingness to pay changes over time, and survey responses can differ from actual behavior. Use research to narrow uncertainty and create strong hypotheses, then validate the price through new-customer cohorts, sales proposals and long-term retention and expansion data.
