Willingness to pay · 9 min read
Will Customers Pay for Your Startup Idea? 7 Tests That Produce Real Evidence
Asking people what they would pay produces weak evidence. Here are seven progressively stronger willingness to pay tests, in order, with the ethics of deposits and refunds handled properly.
Published by the Skoora team
Key takeaways
- Price questions asked in the abstract measure politeness, not budget.
- Evidence strength tracks what the customer gives up: attention, then a decision, then money.
- Trade-off questions beat price questions, because a real budget is always a choice against something else.
- A paid pilot with a written scope is the most informative test most founders can run in a month.
- Refund policies and delivery dates must be explicit before you accept money, without exception.
Willingness to pay is the assumption founders test last and need first. It is easy to see why. Asking about money feels like asking for a verdict on yourself, so the question gets softened until it cannot produce a real answer. "Would you pay for this?" is a hypothetical, and hypotheticals get generous replies. The seven tests below get progressively harder for the customer to say yes to, which is exactly what makes the later ones worth running.
Why price questions produce weak evidence
When you ask someone what they would pay, three things go wrong at once. They have no context for the decision, so they guess. They want the conversation to stay pleasant, so they guess high. And they are answering for a hypothetical version of themselves who has already decided to buy, which is not the person you need to convince.
The other failure is quieter. Price questions put the buyer in the role of adviser, and advisers give opinions freely because opinions are free. As soon as a test costs the buyer something, they stop advising and start deciding.
When someone declines a real offer, they usually tell you why, and the reason is specific: the budget sits with a different team, the current workaround is good enough, the timing is wrong until next quarter. Those objections are the map of your business. Vague enthusiasm gives you nothing to fix.
Read effort and evidence together
Rank tests by how much effort they demand from the customer, and you get a reasonable proxy for how much the result is worth. The matrix below is a way to plan a sequence of tests, not measured data. Low-effort tests are still useful, as long as you never treat them as proof of revenue.
Framework
Commitment matrix: customer effort against evidence strength
| Test | Customer effort | Evidence strength | What you learn |
|---|---|---|---|
| Trade-off interview | Low | Weak | Reveals whether a budget exists to displace. |
| Price anchoring conversation | Low | Weak | Surfaces the real ceiling and the real approver. |
| Refundable deposit | Medium | Moderate | A real payment decision with the stakes lowered. |
| Preorder at a real price | Medium | Moderate | Money now for a stated delivery date later. |
| Paid concierge service | High | Strong | Pays for the outcome, not for a promise. |
| Paid pilot with written scope | High | Strong | Forces the buyer through internal approval. |
| Completed payment at list price | High | Strong | Revenue, plus a renewal decision to watch. |
The practical rule: run one low-effort test to sharpen your message, then move up. Founders who stay in the bottom-left corner for months are collecting comfort, not evidence.
The seven tests, weakest to strongest
1. Trade-off interviews
Instead of asking what someone would pay, ask what they would give up. "If this cost the same as the tool you use for X, which one would you keep?" or "Where in your current budget would this money come from?" A real intention to buy always displaces something. If the money would come from nowhere in particular, you are talking to someone who likes the idea and cannot fund it.
Follow it with a question about the last comparable purchase they made: what triggered it, who approved it, how long it took. You are mapping the buying process, and that map determines whether a founder-led sale is even feasible.
2. Price anchoring conversations
Present two or three concrete packages with real numbers and watch which one the person reacts to. The signal is not the choice, it is the shape of the reaction. Immediate agreement at your highest price usually means they are not budgeting seriously. A specific objection like "that is above what I can approve without my director" tells you the real ceiling and the real decision maker in one sentence.
Do not run this as a survey. Anchoring only works in conversation, where you can ask why.
3. A refundable deposit
Ask for a small, fully refundable deposit to hold a place in the first cohort or the first month of delivery. It is a genuine decision because it requires a payment step, and it is honest because the money comes back on request, in full, with no conditions. Say this in writing before they pay.
Deposits work best when the thing being reserved is scarce for a real reason, such as your own limited capacity to deliver by hand. Invented scarcity is a bad habit that also produces bad data.
4. A preorder at a real price
A preorder collects payment now for delivery later at a stated date. This is much stronger evidence than a deposit, and it carries a real obligation. State exactly what the buyer receives, when, what happens if you miss the date, and how they get their money back. A Stripe payment link is enough to run this without building a checkout.
If the thought of taking a preorder makes you uncomfortable because you are not sure you can deliver, that discomfort is information. Either narrow the promise until you can honor it, or run the concierge test instead.
5. A concierge service, paid
Deliver the outcome manually for a small number of paying customers. No product, just you doing the work with whatever tools exist. This is the highest ratio of learning to cost available to most founders, and it is the format Strategyzer's experiment library returns to repeatedly for exactly that reason.
You learn three things at once: whether the outcome is worth money, what the work actually involves, and which parts of your imagined product were never necessary. It also produces your first real reference customers, which no landing page can do.
6. A paid pilot with a written scope
In B2B, the paid pilot is the test that matters. A short engagement, a defined scope, an agreed success measure, an invoice. It forces a buyer to go through the internal motions of approving spend, which is the part that kills most enterprise ideas quietly.
Charge something real even if it is small. A free pilot has a much worse completion rate, because nothing internally is at stake and the champion has nothing to defend. Write the pass or fail measure into the agreement so the renewal conversation is about evidence rather than sentiment.
7. A completed payment for the real thing
The last rung is the ordinary one: someone pays your list price for the product, uses it, and either renews or does not. It is the only test that produces revenue rather than a proxy for it. Everything before it exists to get you here with fewer wasted weeks.
Watch the second payment more closely than the first. First payments can be bought with goodwill, urgency, or your own persistence. A renewal is the market speaking without you in the room.
The ethics of taking money early
Testing willingness to pay means accepting money for something that may not exist yet. That is legitimate, and it stops being legitimate the moment the buyer does not fully understand what they bought. Keep four things unambiguous, in writing, before any payment.
- What the buyer receives, described as an outcome rather than a feature list.
- When they receive it, with a specific date rather than a vague soon.
- The refund terms, including how to request one and how long it takes.
- Whether the product exists today. If it does not, say so plainly.
Refunding a preorder because you decided not to build is not a failure. It is the correct end to a test that gave you the answer you needed, and it costs vastly less than a year spent building the wrong thing.
Turning the results into a decision
Two or three of these tests will give you enough to act on. Before you interpret them, write down what you predicted. Willingness to pay evidence is unusually easy to rationalize after the fact, because there is always a story about wrong timing or the wrong contact.
01Count decisions, not conversations
How many people faced a real choice with a cost attached, and what did they choose. Everything else is context.
02Read the objections for patterns
Budget owner, timing, and existing workaround are the three most common blockers. Each implies a different fix, and they are not all fixable by you.
03Check the price against the value they described
If the buyer cannot name what the outcome is worth to them in rough numbers, you have a positioning problem before you have a pricing problem.
04Name the next test or stop
One narrower audience, one clearer offer, or an honest stop. Repeating the same test with more people rarely changes the answer.
For the pricing side of this once you have evidence, our guide on the startup idea validation checklist covers the wider set of checks, and how to test an idea before building covers running these tests on a small budget. If demand itself is still unproven, start with testing demand before building an MVP.
Frequently asked questions
Keep reading
- How to test demand before building an MVPA practical sequence for testing demand for a startup idea before you build: name the riskiest assumption, pick the right audience, and gather evidence from behavior instead of opinions.
- How to validate a B2B SaaS idea before writing codeA concrete process for validating a B2B SaaS idea before building: pick a narrow buyer and workflow, interview without pitching, find the budget owner, run a concierge version, and ask for a paid pilot.