How to validate a product idea before you build it

Every garage, hard drive and kitchen drawer has a graveyard of things someone was sure people wanted. The glow-in-the-dark spatula. The app that was “Uber, but for lawn gnomes.” None of these failed because the maker was lazy. They failed because nobody checked whether anyone would actually pay before the building started.

Validating a product idea just means collecting evidence, before you invest serious time or money, that real people have the problem and would pay for your answer to it. Here’s a practical way to do it, most of which costs nothing but a bit of nerve.

1. Write the idea in one sentence

If you can’t explain it in one sentence, you can’t test it. Fill in the blanks:

For [who], who struggle with [problem], [product] is a [what it is] that [what it does differently].

“For people with tiny apartments who struggle to fit a desk, the Clickshelf is a wall-mounted desk that folds flat to 5 cm.” Now you know exactly who to talk to and what to ask. “For everyone, it’s a thing that’s better” is not a sentence. It’s a cry for help.

2. Check that people already spend money on the problem

This is the step most people skip because it feels backwards: competition is usually good news. If other products already solve the problem, people are demonstrably paying for it. Your job is to be better for a specific group, not to invent demand from scratch.

• Search Google, Amazon, Etsy, the App Store or Steam for what your customer would type.
• Read the one- to three-star reviews of the closest products. That’s a free list of what people wish existed, written by people with wallets.
• No competitors at all? Either you’ve found a gap, or you’ve found a problem nobody cares enough about to pay to fix. Assume the second until proven otherwise.

3. Go where your people already hang out, and listen first

Subreddits, Discord servers, Facebook groups, forums, the comments under videos in your niche. Spend a few days just reading. How do people describe the problem? What have they already tried? What do they complain about at 1 a.m.?

Then ask questions, and don’t pitch. Most communities ban self-promotion, and the fastest way to get no useful answers is to open with “So I’m building a thing…”.

4. Ask about the past, not the future

“Would you buy this?” is the worst question in product development. People are kind, hypothetical money is free, and everyone’s future self is extremely disciplined. Ask about what they’ve actually done instead:

• “When did this problem last come up for you?”
• “What did you do about it?”
• “Have you paid for anything to fix it? How much?”
• “What’s annoying about the thing you use now?”

Rob Fitzpatrick’s short book The Mom Test is built around exactly this idea, and it’s worth an evening. The title says it all: your mom will say she loves it. She also said your school play was “very brave.”

5. Put a real version in front of people and measure actions

Compliments are not data. Actions are. Give people something concrete to react to (a page, a few photos or mockups, a short video) and a clear action to take:

• Sign up to be notified when it launches.
• Say “I want this” on a public listing.
• Join a waitlist with their email.
• Pre-order or put down a deposit, which is the strongest signal there is (more on that below).

On Lifthoff, you can post a product as an Idea before it exists. People browsing can tap I want this, and you see the count, plus views, clicks and where visitors came from. Share the link in the communities from step 3 and you’ll quickly see whether the interest is real or just polite. You can browse other product ideas testing demand to see how people present theirs.

6. Decide what “yes” looks like, before you look

This is the part that saves you from yourself. Before you share anything, write down the number that would convince you to keep going, and a date. For example: “If 100 people I don’t know say they want this within 30 days, I’ll make a prototype.”

The right number depends on your price and your market, so pick one that feels a little uncomfortable. What matters is that you pick it first. Otherwise 12 sign-ups (eight of them relatives) somehow starts to look like a movement.

7. Pre-sell if you can

Nothing validates an idea like someone handing over money for it. A pre-order, a paid deposit or a crowdfunding campaign turns “sounds cool” into “I’m in.” Be upfront about timelines and refunds, and only take money for something you can actually deliver. Nothing un-validates an idea faster than angry customers.

If pre-selling isn’t possible yet (say it’s an app or a game), a waitlist or a store wishlist is the next best thing, especially if you can see how many people act on it.

8. Read the results honestly

• Strong yes: you hit your number with people you don’t know, and some asked when they can buy. Build the smallest version that delivers the core promise.
• Maybe: interest, but from a different group than you expected, or for a different feature. That’s not failure. That’s the market telling you what to build.
• No: nobody bit, even after you shared it widely. Congratulations: you just saved yourself months. Tweak the idea, the audience or the pitch, and test again.

The short version

1. Write the idea in one sentence: who, what problem, what’s different.
2. Check that people already pay to solve the problem.
3. Listen where your audience hangs out before you pitch.
4. Ask about past behaviour, not hypothetical purchases.
5. Show something real and measure actions, not compliments.
6. Set your “yes” number and deadline before you look.
7. Pre-sell if you can.
8. Be honest about what the results say.

Validating an idea isn’t about proving you’re right. It’s about finding out quickly and cheaply whether you are. The glow-in-the-dark spatula might still be a hit. You’ll just know before you order 10,000 of them.