How to Validate a Startup Idea Before You Build It

The most expensive mistake a maker can make is spending six months building something nobody wants. Validation doesn't guarantee success, but it dramatically reduces the risk — and most of it can be done in a week or two.

What you're actually validating

You're answering three questions:

1. Is the problem real and painful? People complain about it, spend time or money on it, or have hacked together workarounds.
2. Can you reach the people who have it? You know where they hang out online.
3. Will they pay (or switch) for a solution? Interest is cheap; commitment is the real signal.

1. Talk to people who have the problem

Find 10–15 people in your target audience and ask about their past behaviour, not your idea:

• "Tell me about the last time this problem happened."
• "What did you do about it?"
• "What have you tried? What did it cost you?"

Avoid "Would you use a tool that…?" — almost everyone says yes to be polite. Past behaviour predicts future behaviour; opinions don't.

2. Look for existing spending

If people already pay for imperfect solutions — tools, freelancers, spreadsheets someone maintains — that's a strong sign. Competitors aren't a bad sign either: they prove the market exists. Your job is to find what they do badly for a specific group.

3. Build a landing page before the product

Describe the outcome, show a mockup or a short video, and add one call to action: join the waitlist, book a demo, or pre-order. Then send focused traffic to it — from communities, posts and personal outreach. Our SaaS landing page checklist covers what to include.

What to watch:

• Conversion to signup from relevant visitors
• Replies when you email signups a question
• Willingness to talk on a 15-minute call

4. Ask for a real commitment

The strongest validation is someone paying before the product is finished: a discounted pre-order, a paid pilot, or a deposit. Even a handful of pre-sales tells you more than a thousand likes.

5. Build the smallest useful version

Once the signals are good, build the version that solves the core problem for one type of user — nothing more. Launch it early, to the people who signed up, and iterate based on what they actually use. A weekly launch is a good way to get that first version in front of early adopters.

Red flags

• Everyone says "great idea" but nobody signs up
• You can't name where your users spend time online
• The problem only exists for people who can't pay
• You're the only person you've spoken to

The short version

Talk to people about their past, look for existing spending, test a landing page, ask for real commitment — then build small and launch early.