How to test willingness to pay before you build
Test willingness to pay
To test willingness to pay you ask for a real commitment that costs something: money, a signed order, a refundable deposit, or a paid pilot, not a thumbs-up in an interview. The question is whether a defined buyer will change behaviour when price and payment terms are visible. Problem interviews and landing-page signups sit earlier in the chain; they help you decide whether to run a payment test, but they do not answer the price question by themselves.
This is for founders and innovation leads in Switzerland who already believe the problem is real and now need evidence that someone will pay for the outcome. For the wider menu of validation methods, see how to validate a startup idea. For pain and frequency before you talk about price, see problem validation before building.
How to test willingness to pay in practice
Pick one offer, one price, and one audience. Mixing tiers in the first test usually tells you which headline won, not whether anyone pays.
State the paid outcome
One sentence: who gets what, by when, under which terms. «Access to software someday» is vague. «Four weeks of manual bookkeeping cleanup for one entity» is testable.
Choose a commitment with cost
Strongest: invoice paid, card charged, or purchase order. Weaker but still useful: refundable deposit, paid workshop, or pilot fee credited toward a later contract. Weakest: verbal «I would pay» with no calendar or payment link.
Make price and terms visible before they say yes
Send the number, currency, renewal, and what is excluded. Surprises after enthusiasm are not a payment test; they are a negotiation you did not plan.
Run the test with strangers or arm’s-length buyers
Friends and family can pay as a favour. Note who had no social reason to help you. One paid stranger beats five polite interviews.
Write what would make you stop
Example: «If zero of ten targeted firms pay CHF 500 for the pilot, we do not build the self-serve product.» Without a falsifier, you will reinterpret silence as «not yet».
What counts as proof, and what does not
Money in your account, or a binding commercial document that finance would recognise, is the bar. A waitlist, a «very interested» email, or a survey band that says people might pay at some price is research input, not willingness to pay.
Stronger signals
- Paid pilot or annual licence from a buyer you did not coach through every objection
- Deposit or pre-order with clear refund rules, taken before the product exists
- Repeat purchase or renewal at the stated price, not only the first transaction
Weaker signals
- «We would buy if you had feature X» with no payment step
- Pricing-page clicks without checkout completion
- Discounted first month that nobody renews at list price
In Swiss B2B, procurement and data-processing questions often arrive after the first «yes». That delay does not erase a signed pilot, but it does mean one logo is not a channel strategy.
What a willingness-to-pay test does not prove
A successful payment test shows that at least one buyer valued the offer enough to commit under the terms you set. It does not prove you can acquire customers profitably, that the product will retain them, that your margin works at scale, or that the idea is defensible: ideas as such cannot be protected, only execution and branding (IGE overview on ideas).
Payment tests can justify a focused build or a priced concierge offer. They cannot replace legal review of contracts, tax treatment, or regulated industries. Stop when buyers pay but only at a discount you cannot sustain, or when everyone agrees the problem is real and still nobody will put money on the table under fair terms.
A made-up example: a priced pilot for compliance reminders
A made-up example: a founder sells reminder workflows to trustees in German-speaking Switzerland. Problem interviews are done; three firms describe the same monthly chase for missing documents. The founder offers a four-week pilot: one client portfolio, manual reminders sent from a shared mailbox, CHF 1’200, credited half toward a yearly licence if they sign within 30 days after the pilot. Five firms receive the same one-page offer with scope and exclusions (no integration, no liability advice). Two decline because internal IT must approve any external mail; one accepts and pays by invoice; two ask for a lower price without trying the pilot. The founder treats one paid pilot at the stated price as enough to build a narrow self-serve tool, and treats the two discount requests as pricing noise until a second stranger pays without negotiation.
Who should run the test now, and who should wait
If the problem is still a guess, run problem validation and sharper interviews before you invoice anyone. If you sell to a committee, test with a paid workshop or pilot for one department and document who signed. If you already have recurring revenue, use cohort and renewal data; your question is packaging or churn, not whether anyone will ever pay.
For checkout in Switzerland, card and TWINT through a provider such as Stripe is a practical path when you need online payment without building billing first (Stripe TWINT). Choose the mechanics after the offer is clear; the test is the commitment, not the payment brand.
Common questions
Is a free trial the same as testing willingness to pay?
No. A trial tests usage and habit. Willingness to pay needs a price shown and a payment or binding order. You can run both, but conflating them makes active users look like revenue.
How many paying customers are enough?
Enough to beat the falsifier you wrote in advance. For a narrow B2B offer, one or two arm’s-length payments at the target price may be enough to justify a build; for consumer subscription, you usually need more repeats before you trust the number.
When the Product Validation Package fits
The Product Validation Package fits when willingness to pay needs to be tested in product: a deployed app, analytics, paid acquisition, and measured conversion, not only invoices for a manual pilot. Weeks 1 to 4 put real software live; later weeks compare behaviour and cost per lead against the price you assumed. If you still need the first paid commitment without a build, stay with pilots and the broader startup idea validation guide before you book a build conversation on the contact page.
Written by
Aurum Avis Labs
Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.
Related Articles
You might also be interested in these articles
Customer interview questions: the Mom Test, for founders
Mom Test customer interview questions: ask about past behaviour, not your pitch. A question bank, limits, and who should skip interviews.
Problem validation before building: a practical sequence
Problem validation before building tests whether a real group feels enough pain to act, before you ship code. Steps, limits, and what it does not prove.