Before asking about price, define what you’re validating
Willingness to pay (WTP) is the maximum price a customer would accept for an offer in a specific situation. It is not a fixed value of the product: it can vary according to the segment, how urgent the problem is, the available alternatives, and the value each customer perceives.
It is also not the same as ability to pay. Someone may consider a solution valuable and still lack the budget to buy it; or have the budget but prefer another option. That’s why survey responses alone are not enough to confirm that commercial demand exists.
Before researching, define the product, the customer it is intended for, and the purchase scenario. For recurring services, specify whether the price is paid monthly or annually; in all cases, state the currency and what the offer includes.
Checklist for researching your first customers
1. Check that the problem matters
- What task, need, or difficulty is the customer trying to solve?
- How often does it occur, and what happens if it isn’t resolved?
- What solution do they use today, even if it is manual or imperfect?
- What would prompt them to look for an alternative now?
- Who experiences the problem, who decides on the purchase, and who controls the budget?
The answers help distinguish curiosity from a need that is already consuming time or resources. If the problem is not a priority, a positive reaction to the concept may not translate into a purchase.
2. Position the offer against its alternatives
- What products, services, or processes compete for the same budget or solve the same problem?
- How much do those alternatives cost, and what do they include?
- What would the new offer need to improve to justify a different price?
- Which features are essential, and which are optional?
- What risks does the customer perceive in switching solutions or providers?
The comparison should describe a realistic situation, rather than presenting the product in isolation. WTP research can be less accurate if it omits the context and options the buyer would consider. The Value Comparison Method (VCM), introduced by Kellogg researchers and validated in thirteen studies, aims to incorporate these comparisons when measuring how much customers would pay.
3. Research price with clear questions
- What price would you expect for this offer, given its features and the alternatives mentioned?
- At what price would it seem like a good purchase? At what price would it start to seem expensive?
- At what price would you rule it out?
- What would change your answer: more features, a guarantee, lower risk, or a different payment option?
- Would the purchase be made by an individual, or would it require approval from another person or department?
Open-ended questions can reveal how customers think; questions with specific prices make it possible to compare responses. To evaluate alternatives or combinations of features, a choice analysis may be considered. It’s best to combine methods and not treat any stated response as definitive proof of a purchase.
4. Separate interest, value, and budget
- Does the customer already pay to solve the problem? How much, and how often?
- Which budget would the purchase come from?
- Is the proposed price understood as a one-time, monthly, or annual payment?
- What specific benefit do they expect, and how would they decide whether it was worthwhile?
- Who could block the purchase, even if the user wants to try the product?
These questions distinguish perceived value from budget constraints and the purchasing process. In B2B sales, a favorable response from the user alone does not confirm that there is a budget, purchasing authority, or a viable timeline.
Signals worth tracking
No single metric proves WTP. To test the pricing hypothesis, observe signals that fit your sales model:
- Conversion by price and segment: what proportion moves forward when presented with a specific offer, broken down by customer type.
- Acceptance of a commercial proposal: whether interest turns into a verifiable action, such as accepting a quote or starting the purchasing process.
- Objections and reasons for dropping out: whether the obstacle is price, lack of budget, a preferred alternative, a missing feature, or perceived risk.
- Expected revenue and demand at different prices: compare scenarios without assuming that the price that maximizes sales also maximizes revenue.
- Feature valuation: identify which benefits support an offer or package and which do not seem to justify an additional charge.
If the observed response is weak, don’t automatically attribute the result to price: it may also indicate that the problem isn’t urgent, the offer isn’t clear, or relevant features and trust are lacking. Similarly, high demand at a low price does not prove that it is the most suitable price: it could leave value uncaptured.
End validation with a verifiable decision
Summarize which segments show signs of purchase, which alternatives they use, which conditions affect acceptance, and what price or range was tested. Also note the limitations: the sample’s size and composition, the research channel, and the gap between a hypothetical response and an actual purchase.
The goal is not to find a universal figure, but a pricing hypothesis supported by the customer’s context and testable against behavior. If the price doesn’t convince customers, review both the fit between the value and the offer and the segment and purchasing conditions; changing only the figure may not solve the problem.