How to test willingness to pay before building

Primary question

How can a founder test willingness to pay without first building the full product?

Practical takeaway

Willingness to pay is best tested through specific pricing conversations, narrowed offers, and small commitments that create some real buyer friction.

Key points

Talk about price earlier than feels comfortable.
Offer a narrow service, pilot, or manual workflow before a full product.
Treat hesitation as data, not as a cue to widen the product promise.

Offer

Test a concrete offer, not a vague product concept

Buyers can agree that a problem matters and still refuse to pay for your approach to solving it. That is why willingness-to-pay testing needs a concrete offer: a pilot, a manual service, a paid audit, or an early-access commitment with an actual price attached.

The goal is not to maximize conversion at this stage. The goal is to learn whether the buyer sees enough value to cross some real line of commitment.

Specific outcome beats feature list.
Small paid commitments are valid signals.
A narrow paid pilot is often better than a free broad beta.

Note

Praise is cheap

The moment money enters the conversation, buyers stop role-playing and start prioritizing. That is when the signal gets real.

Signals

Watch for behavior that creates friction for the buyer

Strong willingness-to-pay signals usually involve some friction: agreeing to a number, introducing procurement or a manager, sharing internal data, or committing time to a structured pilot. These are stronger than compliments because they require effort and risk.

Weak signals look nice but do not move the buyer. 'Keep me posted,' 'This is interesting,' and 'We should try this sometime' are all softer than they sound.