How to find out if people will pay for your idea

There's a specific moment every founder knows.

You've done the research. You've talked to potential customers. Every conversation has gone well. People say the same things: "I would definitely use this." "We need something like this at our company." "How soon can I sign up?"

You build for three months. You launch.

Nobody pays.

Not because the product is bad. Not because you built the wrong thing. Because "I would use this" and "I will pay for this" are completely different statements — and most founders never test the second one before building.

Here's how to test it.

Why positive conversations don't predict revenue

People are wired to be encouraging. When a founder — who is clearly excited, clearly vulnerable, clearly hoping for validation — describes their idea, most people will find the generous interpretation.

They're not lying. They're being kind.

But kindness isn't a buying signal. The test of whether someone will pay for something is whether they actually pay for something. Nothing else comes close.

The corollary: if someone tells you they would pay, and you ask them to pay right now, and they find a reason not to — that's data. The most important kind. If you haven't yet confirmed the problem exists in the first place, start with how to validate a SaaS idea without building anything.

The five methods that actually work

Method 1: Pre-sell before you build

The cleanest signal is money.

Before building: create a simple page describing what you're building. Offer early access at a discount. Put a payment form on it.

If people pay: you have product-market fit evidence before writing a line of code. If people click but don't pay: you have a curiosity gap, not a market. If nobody clicks: the problem, the solution, or both aren't resonating.

What to charge: 40-60% of what you plan to charge at full price. "Get access for €19/month when we launch (normally €39) — 50 spots."

The discount creates urgency. The limit creates scarcity. Both reveal who actually wants this versus who is casually interested.

Tools to use:

• Stripe payment links for the actual transaction
• A single-page site (even a Notion page or Carrd) to describe the offer
• A Google Form or Typeform as an alternative if Stripe feels too committal for the stage

The threshold: if 20 strangers (not friends or family) pre-pay for a product that doesn't exist yet, you have strong signal. 5 is interesting. 0 tells you to pivot.

Method 2: The price anchor test

If pre-selling feels too early, use price anchoring in conversations.

Instead of asking "would you use this?", ask: "If this product solved [specific problem], what would you pay for it?"

Then do the anchor: "Some tools in this space charge €50/month. Others charge €200. What feels right for this?"

Watch what happens. If they flinch at €50 and say "I'd pay €10 max" — your market may not support your business model. If they say "€50 seems fair for what you're describing" — you have pricing validation.

The key is to ask about price before describing the product in detail. Once someone is excited about the product, they'll anchor to whatever you tell them. Ask about price while it's abstract.

Method 3: Commitment-based waitlist

Not all waitlists are equal.

A waitlist that asks for an email reveals curiosity. A waitlist that asks for something more reveals intent.

Options:

• "Join the waitlist — first 100 members lock in 50% off forever" (requires them to believe in the value before getting the discount)
• "Request early access — tell us about your current workflow" (the application friction filters for serious users)
• "Founding member: pay €X now for lifetime access when we launch" (money upfront — the cleanest signal)

The more the waitlist costs (in time, money, or commitment), the more it filters. A waitlist of 500 people who clicked a form tells you less than 50 people who wrote a paragraph about their pain to request access.

Method 4: The fake door test

If you already have a product with users, add the new feature as a button before you've built it.

"[New Feature] — Coming soon. Click to be notified."

Track click rate. Users who click are revealing demand. If 20% of your users click the "coming soon" button for a feature, that's stronger signal than any survey result.

This only works if you already have a product. But if you do: use it.

Method 5: Consulting first

Before building a product, offer to solve the problem manually as a service.

You charge €500-€2000 to do manually what your software will eventually automate. You find out: are people willing to pay at all? What's their actual workflow? What does the output need to look like for them to value it?

This is the most expensive validation method in time, but the most revealing. You get paid while learning. You understand the customer's real workflow, not their described workflow. You discover the edge cases that will break your assumptions.

Many successful SaaS companies started as consulting. The product was built from the pattern that emerged after solving the same problem 20 times. For a faster version of this signal-gathering, see how to validate demand in 24 hours.

What the numbers actually mean

If you run a pre-sell:

| Result | Interpretation | |--------|---------------| | 0 of 100 visitors paid | Messaging problem, pricing problem, or no market | | 1-5% conversion | Weak signal — market exists but acquisition or pricing is off | | 5-15% conversion | Strong signal — build with confidence | | 15%+ conversion | Exceptional — scale the acquisition now |

These numbers assume cold traffic — people who don't know you. Sales to warm audiences (friends, your Twitter following, your existing customers) are directionally useful but not sufficient. You need strangers to pay.

The conversation that reveals everything

If you're talking to potential customers in person or on calls, one question reveals more than any other:

"What would have to be true for you to start using this today?"

Not "would you use this?" Not "do you like the idea?" What would have to be true for it to happen today.

Listen carefully. The answers split into two types:

Concrete conditions: "I'd need it to integrate with Notion, and I'd need to be able to export to CSV." — These are buildable requirements.

Indefinite conditions: "I'd have to see more examples of it working" or "I'd want to try it for a month first for free." — These are polite deflections. The person is not ready to buy. No amount of feature development will change that.

The concrete conditions tell you what to build. The indefinite conditions tell you this person isn't your early adopter.

The only validation that counts

Everything above filters toward the same thing: does a specific person, with a specific problem, have sufficient motivation to exchange money for your solution?

You'll never know with certainty before building. But you can raise your confidence above the baseline of "people said they liked it."

The founders who build the right things aren't lucky. They asked harder questions earlier. They made people commit before the product was ready. They used "no" data as aggressively as "yes" data. When the data points to a dead end, the key skill is knowing how to kill a bad idea quickly — before it costs you months.

The uncomfortable question is: "Will you pay €X right now?"

Ask it before you build. The answer is worth six months of your life.

Check if your idea has market demand →