Will People Pay for My Idea? How to Find Out Before You Build

The gap between “I love it” and “I’ll pay for it”

Founders consistently overweight positive reactions to their idea. Someone says “this is brilliant, I would definitely use this” and it feels like validation. It is not. It is politeness, or genuine enthusiasm that has no purchase intent behind it, or both.

The problem is structural. Expressing enthusiasm for an idea costs nothing. Paying for it costs money. These are not the same behaviour and they do not predict each other. The history of failed startups is full of founders who mistook the first for evidence of the second.

This is not cynicism — it is calibration. You need to understand the difference between social feedback and market feedback, because only one of them pays the bills.

Why surveys and interviews mislead you

The standard advice is to do customer interviews. Talk to fifty people. Ask them about their problems. This is genuinely useful — but only if you know what you are listening for and what to ignore.

The mistake is asking hypothetical questions. “Would you pay for something that did X?” is a hypothetical question. The answer tells you what someone believes they would do, not what they will actually do. Behavioural research consistently shows these diverge by a wide margin. People consistently overestimate their willingness to adopt new products and underestimate their resistance to changing habits.

Surveys are worse. A survey asking “how much would you pay for this?” to a hundred people will produce numbers that bear no relationship to actual conversion rates. It is not that people are lying — they are just not actually making a purchase decision when they fill out a form.

What actual willingness to pay looks like

Real willingness to pay shows up in behaviours that require something from the person — not just words. There is a rough hierarchy, from weakest to strongest signal:

• WeakestVerbal enthusiasm in an interview or demo
• WeakCompleting a survey, answering email
• ModerateSigning up for a waitlist with an email address
• StrongJoining a waitlist that requires referrals to move up
• StrongerPre-ordering or paying a deposit for something that doesn't exist yet
• StrongestPaying full price for a working version, even a rough one

Most early-stage validation stops at the top of this list. The founders who get real signal push to the bottom. They ask for money before the product exists. This feels uncomfortable. It also tells you more in a week than six months of interviews.

The pre-sale test

The most reliable way to find out if someone will pay for your idea is to ask them to pay for it before you build it. This sounds aggressive. It is actually standard practice in many industries — construction, publishing, hardware, event ticketing — and it works in software too.

The mechanics are simple: build a landing page that describes what you are building and what it will do. Add a clear call to action — “reserve your spot for $X”, “pre-order now”, or even just “pay $X to be notified first and get early access.” Drive a small amount of traffic to it from the communities where your target customers exist.

Your conversion rate tells you more than any survey. A 0% conversion rate after 200 visits is a result. A 3% conversion rate is a different result. Both tell you something true that no interview would.

The fake door test

If a full pre-sale feels premature, a fake door test is a lighter version. You build the button — “Buy now”, “Start your trial”, “Get access” — but when someone clicks it, instead of a checkout they see a short message explaining that you are still building and asking for their email if they want to be first to know when it launches.

The click-through rate on the button is your signal. It tells you whether the headline and value proposition are compelling enough to make someone intend to pay. The email capture afterwards tells you how committed that intent is.

This test is most useful when you are uncertain which value proposition resonates. You can run the same landing page with three different headlines pointing to the same fake door and compare click-through rates directly.

How to ask the price question in an interview

If you are doing customer interviews, there is a specific way to ask about price that generates more honest answers than “how much would you pay?”

It is called the Van Westendorp Price Sensitivity Meter, and despite the name it is simple. You ask four questions:

• 1.At what price would this feel so cheap that you would question whether it actually works?
• 2.At what price would this start to feel like a bargain?
• 3.At what price would this start to feel expensive, but you might still consider it?
• 4.At what price would this be so expensive that you would not consider buying it regardless of quality?

The overlap between “still worth it” and “not too cheap to trust” gives you an acceptable price range. This is not a substitute for actual conversion data, but it is significantly more useful than asking someone to name a number in isolation.

The uncomfortable truth about your current data

If the only evidence you have that people will pay for your idea is verbal encouragement from interviews, friends, or informal feedback — you do not yet know if people will pay for your idea. You know that some people are enthusiastic about it. That is a different thing.

This is not a reason to stop. It is a reason to run one of the tests above before committing further. The further you build before finding out the real answer, the more expensive that answer becomes to act on.

The founders who find this out early have options. They can adjust the positioning, the price, the target customer, or the product itself. The founders who find this out after six months of building often do not — because by then, sunk cost has clouded their judgment and their runway has run out.

For a structured way to think through whether your idea has the right market, pricing model, and customer, read our post on how to validate a startup idea before you build anything.