What Is Willingness to Pay?
Willingness to pay is the maximum price a buyer accepts before choosing an alternative. In B2B it is a distribution across segments, not a single number, and that distribution decides your list price, your tiers, and your discount floor. Most teams measure it once, badly, then price on memory for three years.
What Is Willingness to Pay in B2B?
Willingness to pay (WTP) is the maximum price a buyer will accept for a product before choosing an alternative. In B2B the alternative is rarely one competitor: it is a substitute, an internal build, or living with the workaround. Your ceiling with any buyer is what solving the problem is worth to them minus the cost of their best alternative.
WTP is a distribution, not a point. Buyers in the same market differ on budget, on the alternatives open to them, and on how much value they see. A mid-market operations lead and an enterprise procurement team buying the same software often sit 3 to 5x apart, and a single price underprices one while overpricing the other. Confusion is the enemy of willingness to pay: a buyer who cannot say what your product does, or which tier fits, cannot give you a valid number in any method. Sharpen the offer before you measure the price.
The non-obvious insight
WTP research fails in new categories because the benchmark does not exist yet. Buyers with no market reference anchor on an adjacent category or a budget line. The right method there is the reference-price interview: cost the buyer's workaround and anchor WTP on removing it. The full method set is in the willingness-to-pay research paper.
Why Willingness to Pay Determines Revenue Architecture
WTP data does more than set a price. It decides three structural things that compound over the life of the product.
Whether your list price creates margin or destroys it
A list price above your target segment's ceiling forces every deal through a discount. One below your highest-value segment's floor leaves money unclaimed. The 70th percentile of the segment's distribution captures most of the available revenue without systematic discounting; every unnecessary point of discount against a buyer at the ceiling is an EBITDA hit with no close-rate benefit.
Whether your tiers segment on their own or need a rep on every deal
In a working good-better-best structure, each tier sits at one segment's WTP threshold and buyers self-select. Tiers not anchored in WTP data fail to segment: too many buyers land in Good because Better is priced above its perceived value, or too few reach Best because the anchor is not credible. Both need a rep on every deal, which raises CAC and compresses margin at once.
Whether your discount floor is evidence or a guess
WTP data defines the price below which more discount does not improve conversion because buyers start to question quality. Without that floor, reps discount into a range that only destroys margin. The same data fixes the expansion ceiling in usage-based models, where an account whose consumption triples still needs a price it recognizes as fair.
WTP as Infrastructure, Not an Event
Companies that scale cleanly treat WTP research as infrastructure, not as an event before a price change. By the time they add sales headcount, WTP data already shapes deal structure, packaging, and rep training. Skip it and you pay in three places. Discount drift: a team averaging 18 percent at $10M ARR will average 24 percent at $30M if nothing structural changes, six points worth $1.8M a year. Packaging bloat: features land in tiers on the strength of internal debate. Misattributed churn: customers overcharged for features they never use leave at renewal, and the CRM calls it a competitive loss.
Tessellate Analytics: $400K to rebuild what was already in the CRM
A $12M ARR analytics platform raised a Series B and hired eight account executives in a quarter with no WTP research, no segment pricing rationale, and no deal desk rules. Within nine months average ACV had fallen 22 percent as new reps discounted to quota. A $400,000 pricing consultant's first recommendation was a six-week WTP study on data already in their CRM.
Before you add a rep you need price sensitivity documented by segment, packaging mapped to distinct buyer value profiles, and governance that says what needs approval. Every new rep is a new discount decision. Pull your last 50 deals and compare first quoted price to final price; if the average gap exceeds 15 percent, the problem compounds with every hire.
How to Measure Willingness to Pay in B2B
Five methods. Each is valid in a specific domain and misleading outside it. Start with the one that uses data you already own, and treat every survey result as a hypothesis to check against behavior.
1. Deal, renewal, and billing data (start here)
Your CRM holds a behavioral record of WTP most companies have never read. Pull 24 months of deals and, with 50 or more closed, regress win rate against price by segment: where win rate drops sharply is that segment's ceiling. Deals accepted at first quote are your most reliable evidence; rep-initiated discounts describe the rep, not the buyer. Renewals add a second read: the price where 80 percent renew without pushback is your floor, where 40 percent negotiate is your ceiling. It only sees WTP revealed against current packaging.
Best for: existing products with 12 or more months of deals. Cost: 40 to 80 analyst hours. Lead time: 2 to 3 weeks.
2. Reference-price interviews
Conversations with 8 to 15 buyers per segment that never ask “what would you pay.” Ask which outcomes they have achieved, which would be hardest without you, and what the alternative costs, including not solving the problem. Run the same protocol as deal debriefs with your last 20 wins and 10 losses, recording what the losses bought and paid. Twenty good debriefs beat 200 email surveys, and they explain the reasoning behind the number.
Best for: new categories and separating price objections from value objections. Lead time: 3 to 5 weeks.
3. Van Westendorp price sensitivity meter, anchored
Four price-perception questions: too cheap to trust, a bargain, getting expensive, too expensive. The curve intersections define the acceptable range and an optimal point. Never anchor on your current price. Tie each question to a quantified scenario (“at this price you would remove X hours of manual work a week”) to close the gap between what people say and do. Thirty respondents per segment gives a directional read, and loyal customers reveal the ceiling of the customer you have, not the one you want next.
Best for: repricing and launches where deal data is thin. Lead time: 4 to 6 weeks.
4. Conjoint analysis
Buyers choose between configurations at different prices, and the analysis returns what each feature is worth to them. It is the method for packaging redesign because it says which capabilities move WTP, not just where the ceiling sits. It needs 100 or more qualified respondents per segment and a category where buyers already trade off known attributes. In a category still forming, it returns a clean answer to a question buyers have not learned to answer.
Best for: packaging redesign and tier architecture in an established category. Lead time: 6 to 10 weeks.
5. Behavioral signals from product usage
The most reliable signals are behavioral and continuous. Adoption velocity: accounts activating three or more features within 45 days with sustained use have embedded the product in several workflows, and that switching cost is WTP. Usage frequency: find where the churn curve flattens; accounts above that threshold are price-action candidates, below it churn risks. Ticket mix: expansion-oriented requests signal a buyer pushing the product's boundaries. The framework and the targeted increase it enables are in the behavioral signals post.
Best for: targeting price increases and expansion between studies. Lead time: ongoing.
One more for teams with steady inbound flow: run two prices to matched cohorts for 90 days and track signed deals. If win rate and discount match, the higher price is your floor.
When Each Method Is Worth the Money
Your CFO approved the last study because the argument sounded reasonable. Your sales leader approved it hoping for rep conviction. Nobody modeled the return. Write the decision in one sentence first: “raise the enterprise tier from $2,500 to $3,200 a month for accounts above 200 seats” is a decision; “understand our pricing” is a research tax. Then model three scenarios (no change; 10 percent holding with 3 points of extra churn; 20 percent with 5 points) and count the months to the first contract at the new price.
The cost of delay, on your numbers
A $25M ARR business 15 percent below its ceiling forgoes about $3.75M a year, so six months of research plus three of implementation costs roughly $2.8M in delay. A $50,000 study that ends nine months of underpricing returns many times its cost; the same $50,000 on findings nobody can act on returns nothing. Proceed when the conservative scenario clears the cost by 10x in year one.
Ironbark Software: $65K produced a deck, 10 calls produced a decision
A $35M ARR vertical SaaS company spent five months and $65,000 and got a 90-slide deck with no price points. A three-week read of deal desk data plus ten customer calls later found the mid-market tier 30 percent underpriced against the value metric customers tracked. They raised it; net revenue retention moved from 104 to 117 percent in a year. The first study had no hypothesis and no decision rule.
Greyhaven Systems: 18 months between findings and the first contract
A $32M ARR platform's $95,000 study was right: the growth segment would bear 28 percent more. Implementation needed new governance and retraining for 22 reps, and nobody had planned it. Eighteen months passed before the first contract at the new price, and roughly $5.4M went unclaimed. A two-week implementation plan before the research would have been the best line in the budget.
When Surveys Mislead and When Conjoint Measures the Wrong Thing
A stated price carries no consequence, and the bias runs both ways. Customers who suspect the survey sets their renewal price anchor low. Fans and prospects asked whether an increase is “reasonable” say yes with nothing at stake. Self-selected respondents are your most engaged accounts. Only behavior settles it.
Lanternwood Learning: survey said $320, a competitor won at $380
A $14M ARR learning platform ran 200 surveys, 15 interviews, and a Van Westendorp. The acceptable point came back at $320 a seat against $265, so they repriced to $310. A year later a competitor entered at $380 and started winning; lost buyers said the higher price read as quality. Renewal-without-negotiation data and add-on attach pointed to a $420 to $480 ceiling. They repriced to $399, conversion held, and ARR went from $14M to $21M in 18 months.
Sablewood Software: 80 percent acceptance, then a 14-point win-rate drop
A $16M ARR vertical SaaS company surveyed its base: 80 percent said a 20 percent increase was acceptable. They took 18 percent everywhere. New-business win rate fell 14 points; renewals held at 88 percent, but the resisting 12 percent were the best expanders. Respondents were self-selected customers with goodwill prospects did not share. Deal debriefs and an anchored Van Westendorp produced the split that worked: 18 percent on renewal, 7 percent on new business.
Docket & Vale: conjoint in a category that had not formed
A $17M ARR legal tech platform ran a conjoint to set tiers in what it thought was a maturing category and got $299, $799, and $1,499. Win rate dropped 18 points. Buyers were not trading off feature sets; they were deciding whether to buy at all. Ten interviews found the objection was implementation risk, not price. They needed a pilot structure, not a lower number.
Anselm Analytics: two early deals anchored pricing for three years
An $11M ARR analytics platform had not changed price since launch because the founders remembered two early deals that needed heavy discounts. A three-week CRM audit found average discount at 8 percent, win rates rising, and those two deals' segment at 6 percent of pipeline. They raised prices 25 percent. Win rate dipped one point and recovered; ARR growth went from 34 to 51 percent. Intuition was right on direction, wrong on magnitude.
Two Buyers, One Price: The $77K Gap
Cairnwood Data, a $21M ARR governance platform, had kept the same pricing for four years. The board wanted an increase before an exit, the sales leader was against it, the CFO was for it, and nobody had evidence. A read of 24 months of deal data and 14 interviews found not a number but a split: WTP ran from $18K to $95K a year depending on whether the buyer was a compliance officer or a data engineering leader. Same product. Pricing had been set for the compliance buyer while data engineering grew to 40 percent of the base. A tier by use case at 2.2x lifted new data-engineering ACV 68 percent with no change in win rate and added $4.8M of ARR the next year.
Price sensitivity is a persona characteristic, not a company-size characteristic. A $500M company buying a compliance tool can be less price sensitive than a $10M one, because its compliance risk is existential. Segment by the job and the cost of not doing it. The tier mechanics are in the good-better-best guide.
How to Use WTP Data to Set Price Levels and Tiers
Research produces findings. Findings do not produce prices. The translation is where most programs waste their budget. If the finding is that your base sits well below the ceiling, the price increase playbook covers how to close the gap without losing the accounts.
Set list price at the 70th percentile, not the median
The median leaves money with the top half of the segment and still needs discounting to close the bottom. The 70th percentile captures most of the revenue and leaves room for a printed, governed discount. In a $36M ARR business with 180 customers at $200K ACV, a 15 percent gap to the ceiling is $5.4M of ARR already in customers' budgets.
Set the discount floor where conversion stops responding
Find the price below which conversion does not improve; that is the policy minimum. Then give reps the acceptance threshold for their segment. A rep who knows 90 percent of mid-market accounts accept above $85K anchors at $120K and concedes to $90K. A rep with no idea starts at $95K and panics to $70K.
Anchor the middle tier in the compromise zone
Buyers gravitate to the middle of three options. WTP data says where that zone sits for your core segment, typically the 50th to 70th percentile. If your enterprise ceiling sits 40 percent above SMB and you price for the average, you leave enterprise money unclaimed and price some SMB buyers out at the same time.
Cap the top tier at the expansion ceiling
The ceiling of your highest-value segment caps the Best tier without creating renewal risk. Under usage-based or hybrid models, if an account's consumption triples, that ceiling decides whether it keeps expanding or starts shopping at a price that feels disproportionate. Use data from the right segment and the right year: anything older than 24 months is directional, not operational.
What Fails in New Categories, and What to Do Instead
Willingness-to-pay research fails in new categories because the benchmark does not exist yet. Every survey instrument assumes a reference set: products compared, prices seen, trade-offs made. Remove it and the instruments keep producing numbers that describe the adjacent category the buyer reached for or the budget line they own. Van Westendorp answers cluster at round numbers. Conjoint measures trade-offs nobody has learned to make. Docket & Vale paid 18 points of win rate to learn this.
Instead: run reference-price interviews and cost the workaround in hours, headcount, tools, and risk, and find which budget line a solution comes from. Build a value-in-use model for three real accounts. Price a pilot that lowers the risk of starting, because in a forming category the objection is usually risk wearing a price costume. Run one cohort test, and re-measure at 12 months once real behavior exists. The launch sequence is in the new product pricing and packaging guide; model selection in the SaaS pricing strategy guide.
The 90-Day Research Cycle in Four Phases
Ninety days is enough for a decision-ready cycle, and waiting has its own bill: a $15M ARR company 20 percent below optimal loses about $750,000 a quarter. Orrin HR, a $9M ARR platform, ran its study for 18 months and four of eight interviewees churned before findings shipped; the internal audit it skipped would have shown its best segment in CRM data alone.
Phase 1, days 1 to 21: internal data audit
Pull 24 months of deals with first price, final price, buyer title, and segment. Calculate discount rate by segment, rep, and deal size. If top-quartile and bottom-quartile discount rates differ by more than eight points, you have your first finding.
Phase 2, days 22 to 45: customer interviews
Ten to fifteen structured win-loss interviews on one protocol. Ask about the moment price felt right or wrong, and what the alternative would have cost, including doing nothing. Cut answers by persona, not company size.
Phase 3, days 46 to 70: hypothesis validation
Write the hypothesis with a direction and a magnitude, test it against segment data, and model 12 months under three churn scenarios. Set the decision rule before you look: modeled loss above 12 percent means change the packaging, not the price.
Phase 4, days 71 to 90: decision and implementation plan
Document the change, the rationale, the expected impact, and the governance that protects it. Define grandfathering. Write what a rep says when asked why pricing changed. Name the 90-day metrics and an owner for each.
The WTP Research Checklist
- Write the pricing decision in one sentence, with a direction and a magnitude
- Model no-change, conservative, and base scenarios, and count the months to the first new-price contract
- Pull 24 months of deals: first price, final price, persona, segment, and who initiated the discount
- Read renewals for the price where 80 percent accept and where 40 percent push back
- Run 8 to 15 reference-price interviews per segment and 20 to 30 deal debriefs
- Van Westendorp to test a band, conjoint to design an offer, neither in a category that has not formed
- Anchor every survey question to a quantified scenario and a sample that looks like your next customer
- Build the behavioral signal report: adoption velocity, usage threshold, and expansion-ticket share
- Segment by persona and job, not company size, and date-stamp the dataset
- Set list at the 70th percentile and the floor where conversion stops responding, and write the implementation plan before the research starts
Company names and figures in worked examples are illustrative.
Willingness to Pay: Common Questions
What is willingness to pay in B2B, and why is it a distribution rather than a number?
How do you measure willingness to pay in B2B?
Van Westendorp or conjoint: which one fits a B2B pricing decision?
Why do willingness-to-pay surveys give the wrong answer so often?
What behavioral signals reveal willingness to pay before customers say it?
How do you turn WTP data into list price, discount floor, and tiers?
Why does WTP research fail in new categories, and what should you do instead?
How much does willingness-to-pay research cost, and when is it worth the money?
Find out if your pricing reflects actual willingness to pay
The FintastIQ Pricing Maturity Assessment includes a WTP alignment score: how well your current list prices and tier structure map to the revealed WTP in your closed deal data. You get a score and a specific action plan.