Short answer: Prove the problem is real before you build. That is how to validate a startup idea. Talk to 10 to 20 people who have the problem. Ask what they do about it today, not what they might buy one day. Then put a live test page in front of strangers. Ask for something that costs them: an email, a pre-order, a deposit. Commitments count. Compliments don’t.
TL;DR
- 42% of failed startups died from “no market need.” That is the top cause, ahead of running out of cash. (CB Insights)
- Prove the problem first. A painful problem with a so-so fix beats a slick fix nobody needs.
- Ask people what they did, not what they would do. “Tell me about the last time this happened” beats “would you use this?”
- A test page beats an MVP. Dropbox’s 3-minute video took its waitlist from 5,000 to 75,000 overnight. The product did not exist yet.
- Take money early. Only about 9% of founders pre-sell. They learn the truth that everyone else pays for at launch.
Why most startup ideas die
CB Insights read what founders wrote after their startups died. The most common cause of death was “no market need.” 42% of them built something nobody wanted. (CB Insights) Running out of cash gets the blame more often. But the cash ran out because too few people cared. Validation finds that out early. The test costs a weekend, not two years. The full list is in why startups fail.
Most first-time founders fall into the same trap. They fall in love with a fix. Then they hunt for a problem it fits. Building feels like progress. The discipline is to sit with “I don’t know if anyone wants this yet” until you get a real answer. Most of us built the whole thing first, then went looking for users. Some of us did it twice.
What does it mean to validate a startup idea?
To validate a startup idea, you gather real proof before you build. The proof has to show one thing. A specific group of people has a problem. It hurts enough that they will pay to make it go away. A poll of your friends does not count.
People blur three things together:
- Market research tells you the market exists and how big it is. Useful. But a big market full of people who won’t switch is a graveyard.
- Idea validation tells you this group has this pain and will act on it.
- Product-market fit comes after you build. It is when demand starts pulling the product out of your hands.
Step 1: Prove the problem, not your fix
Write down the problem, not the product. Open with “I’m building an app that…” and you have skipped the question. The question is this. Does the pain come often, and does it cost enough? Are people already trying to fix it today?
You are hunting for what some founders call a Tier 1 problem. The pain is so bad that people have already built a workaround. An ugly one. A tangle of spreadsheets, or a part-time hire doing it by hand. Duct-tape fixes are the best green flag there is. They prove people already spend money and time on this. People describe them in public, and finding those threads on Reddit takes an afternoon.
Now the flip side. If nobody fixes it today, there is often no problem. “No competitors” is the scariest phrase in a pitch deck.
Step 2: Talk to 10 to 20 people (The Mom Test)
Customer interviews are where you win or lose. They are also where founders fool themselves most. People are nice. Ask “would you use an app that does X?” and they say “sure, sounds great.” Saying no to your face is awkward. You end up with a folder of compliments. You will mistake it for proof.
The fix is The Mom Test, by Rob Fitzpatrick. Ask questions even your mom could not lie about. Ask about the past and the present. Never ask about a future they imagine.
- Bad: “Would you pay for a tool that does this?” You’ll hear “yeah, probably!” Worthless.
- Good: “Walk me through the last time you dealt with this. What did it cost you?” You’ll hear a real story with real stakes.
Field rules:
- Ask what they did, not what they think. Last week’s actions predict the future. What they say they’ll do does not.
- Talk less than they do. If you are pitching, it is a sales call. Stop talking and dig.
- Chase the money and the workaround. “What do you use now? What does it cost you, in dollars or hours?” Money already changing hands is the loudest proof.
- Talk to skeptics. People who won’t switch tell you more than people who love you.
On numbers: a pattern shows up around 5 conversations. A feel for price comes around 10. Real confidence comes past 20. Immad Akhund had about 90 conversations before he wrote a line of Mercury’s code. He talked to founders, investors, and lawyers. He wanted to know if the rules would even allow it. Karri Saarinen did this before Linear. He spent about a year in chats with coworkers at Uber, Airbnb, and Coinbase. He kept hearing the same complaint. Software was slow. That became the first thing Linear fixed.
Step 3: Get a yes that costs them something
“Cool idea!” costs nothing to give. That is what it is worth. A commitment costs the giver something. An email address, or money down. The cost is what makes it data.
Bob Moore of Crossbeam saw this. He was pitching early ideas to other founders. One response was worth trusting. Someone offered to introduce him to a customer. That put their own name on the line.
Rank commitments by what they cost the giver:
| Cheap (means little) | Costly (means a lot) |
|---|---|
| “Great idea!” | Gives you their email for early access |
| A thumbs-up on your post | Books a call, or joins a design-partner program |
| “I’d definitely use that” | Pre-orders, or puts down a deposit |
| A survey answer | Introduces you to their boss or their team |
Step 4: Put up a test page
Most guides mention this step and walk right past it. It is the fastest honest read on demand you can get.
A test page is a real landing page for a product that does not fully exist yet. Some call it a smoke test or a fake-door test. It has a clear headline, the promise, maybe a mock screenshot, and one button (“get early access,” “join the waitlist”). Send cold traffic to it. Then measure whether strangers act. A click is a small commitment. A small commitment is worth more than a big compliment.
The classic example is Dropbox. Drew Houston put up a 3-minute demo video before he built the hard sync engine. The beta waitlist jumped from 5,000 to 75,000 people overnight.
What a good test page needs:
- One promise, one button. The single outcome your user wants, and one way to say yes.
- Real traffic. Post where your target users already are. Or spend $50 to $100 on ads to buy honest strangers. Warm traffic from friends lies.
- A pass bar you set before you look. If fewer than 2 to 5% of cold visitors give you an email, the message is not working. The problem or the audience is off. Above that bar, you are onto something.
This is where an idea validation tool earns its place. Don’t guess at a pass bar. Run the search against real threads instead. You get what buyers wrote, in their own words, with a link to each thread. You also get the communities to send traffic to. Four minutes instead of two weeks. If you want to shop around first, we line up the best idea validation tools and say where each one beats us. Two matchups get searched most: ValidatorAI alternatives and ValidatorAI vs VenturusAI. We put ourselves on the line in ProofMachine vs ValidatorAI.
Step 5: Sell it before you build it
A test page measures interest. A pre-sale measures belief. MicroConf’s survey found the number. Only about 9% of founders pre-sell before building. Read that as an advantage. The ones who ask for money early get the truth. Everyone else pays for it after launch.
Failory calls the reason the “Niceness Gap.” People say your idea is great to spare your feelings. Almost nobody hands over a credit card to be polite. Money burns the niceness away.
Proof you don’t need scale:
- Kettle & Fire: Justin Mares spent $50 on Bing ads that sent people to a pre-order page. He booked $500 in pre-sales in two weeks. He had a real bone-broth business before any stock.
- Steph Smith pre-sold a product to 86 buyers in under 24 hours, about $1,270, to an audience she had built.
- Maven: Gagan Biyani ran a “Minimum Viable Test.” It was a live course taught with Sam Parr. It pulled in about $150,000 from the first cohort, with a 9/10 rating, before he built the platform.
You don’t need a payment system either. “I’m taking $20 deposits for the first 10 spots, refundable if I don’t ship” is a pre-sale. The number of yeses is worth more than 100 survey answers.
How to score what you found
Founders collect a pile of notes. Then they stall on the decision. Score the idea on five things, each with a clear pass bar. Rate each from 1 to 5:
| What you check | Fails (1–2) | Passes (4–5) |
|---|---|---|
| How bad the problem is | “Minor annoyance, I guess” | People already pay for a fix, or hack one together |
| Will they pay | “I’d use a free version” | A pre-order, a deposit, or money already spent on a worse tool |
| Demand from strangers | You have to explain the problem first | Cold traffic to your page converts above your pass bar |
| Can you reach them | Scattered, no shared meeting place | Gathered in communities you can name |
| Does the message land | People nod politely | People finish your sentence and ask “when can I get it?” |
Two rows predict failure best: “Will they pay” and “Demand from strangers”. A 1 or 2 on either kills the idea, no matter how good the rest looks. Fix the problem or the audience first, then build. If you want the way to decide, not the tactics, read our idea validation framework. Four gates in a row, with the pass mark written before the test.
How long should this take?
Validation is a ladder. You climb only as far as the proof takes you. Give each rung a time limit:
- A weekend (2 to 4 hours): desk research. Is anyone fixing this today, and what do they charge? Where does the audience gather? Kill the clearly dead ideas here, for free.
- Two weeks (about 20 hours): 10 to 20 Mom Test interviews, plus a live test page with one button and real traffic. This is where most ideas should live.
- A month: a pre-sale or a Minimum Viable Test. Real money or real commitments from strangers.
Write production code only after that. Each rung earns you the right to climb the next one.
Mistakes that kill good ideas
- Pitching friends and family. They love you, so they lie. Talk to strangers who have the problem.
- Asking what-if questions. “Would you use this?” invites an easy yes. Ask about the last time it happened.
- Counting praise as commitment. Enthusiasm is free. Emails and money are not.
- Skipping the price question. Love is not revenue. Test the wallet early.
- Validating forever. Set your pass bars, hit your time limit, then decide: build it or kill it.
You have proof. Now what?
A validated idea with no users is still only an idea. You built a page to test demand. Now it is the page you send your first real users to. Don’t tear it down. Point traffic at it.
Your first users are already in a room, arguing about the problem. So getting your first users from Reddit is the natural next step after a green light. To find that room without reading a thousand threads yourself, run an idea validation search and start from what it brings back.
Before you decide, run your idea through the idea validation tool. You get the threads where people describe the problem in their own words, and the communities they post in. You get a verdict that is allowed to say no, and a score built from five counts. The counts: complaints traced to a page, businesses like yours that clear $5,000 a month, people who named a price, communities found, rivals named. The report ends with the way up: up to five suggested changes to your brief, each tied to the check it helps. About four minutes.