How to Tell If People Will Pay for Your Idea (Before You Build It)

The most dangerous words in early-stage validation are "people seemed interested."

Interest is cheap. It requires nothing from the person expressing it. No money changes hands. No behavior changes. No habit gets disrupted. Someone can be genuinely interested in an idea and never pay for it in a thousand years.

What you actually need to find out is whether people will pay. That's a much harder question -- and a much more specific one to test.

Here's how to do it before you build anything.

Why "Would You Pay for This?" Is the Wrong Question

The obvious approach is to ask directly. "Would you pay for something like this?" Founders do this constantly. The answers they get are almost always useless.

When you ask someone to predict their future payment behavior, you're asking them to do something cognitively difficult: imagine a product they haven't used, compare it against alternatives they don't have in front of them, estimate how much value they'd get from something hypothetical, and then give you a number. Most people can't do that accurately. So they guess, or they default to polite.

You'll hear a lot of "yeah, I'd probably pay around $20/month for something like that." Then you build it, price it at $20/month, and the same people don't subscribe.

It's not that they lied. They genuinely couldn't predict their own behavior accurately in a hypothetical scenario.

The question you need to answer isn't theoretical. It needs to be grounded in something real -- a behavior they've already shown, a price they've already paid, a decision they've already made.

Signal 1: What Are They Already Paying For?

The most reliable predictor of future spending is past spending.

In your customer conversations, ask this directly: "What tools or services are you currently paying for to handle [the problem your product solves or adjacent to it]?"

Then listen carefully.

If someone is paying $50/month for three different tools that collectively, imperfectly handle what your product would do cleanly -- that's meaningful. They've demonstrated that they have budget, they've demonstrated that they consider software a legitimate way to solve this problem, and they've demonstrated that the current solutions aren't good enough.

If someone has never paid for anything in this category and relies entirely on free tools and manual workarounds -- that doesn't mean they won't pay. But it means you're also selling them on the category, not just your product. That's a harder problem.

The best prospects are people who are already paying for something adjacent that doesn't fully work. They have the habit, they have the budget mentality, and they have dissatisfaction with the status quo. Your job is to be the obvious upgrade.

Signal 2: The Budget and Authority Questions

For B2B ideas especially, willingness to pay is meaningless unless you're talking to the right person.

Two follow-up questions that reveal this fast:

"Is this something you'd expense, or would you need to get approval?"

If they say they can expense it themselves -- below their personal spending threshold -- then you're close to a real deal conversation. If they say it would need to go through procurement or get manager sign-off, you're selling into a longer, more complex cycle. Both are valid markets; they're just different products.

"What do you currently spend on [category] per month or per year?"

This isn't asking what they'd pay for your product. It's asking about existing realized spend. If they're spending $200/month across four tools that do what you'd do in one, and they know that number off the top of their head, they're used to thinking about this as a cost of doing business. That framing is where your pricing conversation should live.

Signal 3: Prior Substitution Behavior

Here's an underrated question: "Have you ever switched tools in this category? What prompted the switch?"

Someone who has switched tools before -- who has actively compared options, gone through the switching friction, and paid for a replacement -- has done something important. They've proven they're not locked in by inertia. They move when they find something better.

Founders often fear churn. But for validation purposes, the person who churned from a competitor is your ideal early customer. They've already established that they evaluate and switch. They know what the bad version looks like. They're actively looking for the right one.

The flip side: if someone says they've been using the same solution for five years and never thought about switching -- even if they're unhappy -- that's a softer signal. Inertia is a real economic force.

Signal 4: The "What Would You Stop Paying For?" Test

Here's one of the most telling questions you can ask in a customer interview:

"If you started using something that solved this problem properly, what would you cancel?"

This question does several things at once.

It grounds the conversation in real cost. They're not imagining what they'd spend; they're thinking about what they'd cut. That's cognitively easier and more honest.

It tells you about your actual competition. The thing they say they'd cancel is your real competitor -- not the thing you've been comparing yourself to, but the thing you'd actually replace in their life and budget.

And it reveals whether the value is clear. If someone can immediately and confidently name two things they'd cancel if your product existed, the value proposition has landed. If they have to think for a long time and say "I'm not sure," the value is still fuzzy -- either in your framing or in their mind.

Signal 5: The Van Westendorp Price Questions

This is a framework from pricing research that surfaces a natural price range without asking people to guess what they'd pay.

Ask these four questions in sequence:

1. "At what price would this seem so cheap that you'd question the quality?"
2. "At what price would this seem like a good deal -- you wouldn't hesitate?"
3. "At what price would it start to seem expensive, but you might still consider it?"
4. "At what price would it be way too expensive, no matter how good it was?"

You're looking for the range between question 2 and question 3. That's where most people's acceptable price window lives. If multiple people independently give you similar ranges, you're calibrating your pricing on actual psychology rather than guesswork.

One important note: this works best with people who've already confirmed the problem is real for them. Asking someone who doesn't strongly feel the pain their price ceiling is mostly noise.

Signal 6: The Smoke Test with Real Money

At some point, you need to put a real price in front of real people and see what happens.

This doesn't mean building and launching. It means adding a purchase-intent mechanism to your landing page.

Create a Stripe payment link with your proposed price. Add a button to your page: "Pre-order at founding member rate -- [your price] / month." When someone clicks and arrives at checkout, you're measuring the most concrete signal available: how many people went far enough down the purchase path to see a real charge page.

You can handle this ethically without deceiving anyone. Show a confirmation page or a note at checkout: "We're finalizing development. Your card won't be charged until we launch, and you can cancel at any time before then. We'll contact you before any charge is made."

This isn't a fake door. It's an honest pre-order mechanism. It removes the ambiguity of "would you pay?" entirely, because the person has to confront a real price and a real payment form.

Even three or four completed or seriously attempted checkouts from cold traffic -- strangers who found you organically and got to the payment screen -- is a meaningful signal. It's qualitatively different from any number of email signups.

Signal 7: The Embarrassment Test for B2B

For business products, here's a simple framing test that predicts payment probability:

Would the person be embarrassed to tell their team they're not using a solution for this problem?

If someone would say "I can't believe we're still doing this manually when a tool exists" -- that's a strong buying signal. The social or professional cost of not having the solution has exceeded the financial cost of buying it.

If someone would shrug and say "Yeah, we've always done it this way and it works fine" -- that's a weak signal. The status quo feels acceptable, which means your price needs to do a lot of work to justify disruption.

You can surface this in conversation by asking: "If a colleague asked you why you haven't solved this yet, what would you tell them?" The answer tells you how the person rationalizes their current state. A lot of rationalization ("the tools out there are all too complex, too expensive, not quite right") usually signals genuine frustration. Easy acceptance ("eh, it's not really a priority") tells you the problem doesn't rise to the level of budget-justifying.

Putting It All Together

You don't need to use every signal on this list. But before you commit to building, you should have clear answers to these three questions:

1. Are they already spending money in this category? If yes, you have a budget-aware audience. If no, you're fighting inertia.
2. Did anyone get to a real checkout screen and not immediately leave? Even one pre-order attempt from a stranger is your strongest data point.
3. When you asked what they'd cancel, did they answer quickly and specifically? Fast, specific answers mean the value proposition is real to them.

Willingness to pay can't be proven before you build. But it can be strongly indicated -- or strongly contradicted -- by the behaviors people show you before the product exists.

Trust behavior over words. Always.