In this article
Thinking harder does not validate a business idea.
Doing five specific things, in order, and looking at what comes back does. Skip the order and you get noise: a friend’s encouragement mistaken for market demand, a competitor’s existence mistaken for proof, a gut feeling mistaken for evidence.
This guide walks through the five-step process, in sequence. Each step produces one piece of evidence. By the end, you will have enough to make a go, wait, or kill call — not a guess.

The Validation Process at a Glance
Validation is not one test. It is a sequence, and the sequence matters — each step either confirms or kills the assumption the next step depends on.
| Step | What You Do | Time Needed | What It Proves |
|---|---|---|---|
| 1. Name the problem | Write the problem and the person who has it in one sentence | About 30 minutes | Whether you can describe a real problem, not a vague ambition |
| 2. Talk to strangers | Run Mom Test-style conversations with people outside your circle | 3 to 5 days | Whether the problem is real and painful enough to act on |
| 3. Look for demand signals | Search where your buyer already complains, pays for workarounds, or competes for a fix | 1 to 2 days | Whether unprompted demand already exists |
| 4. Run a pre-sell test | Collect a real commitment — deposit, waitlist, or pre-order — from strangers | One weekend | Whether people act, not just talk |
| 5. Decide | Score what you found against a clear threshold | About 30 minutes | Whether to build, gather more evidence, or move to the next idea |
Most solopreneurs can run all five steps in one to two focused weeks. Skipping straight to building is faster in the short term and far slower once you count the months spent building something nobody asked for.
Step 1: Write the Problem in One Sentence, and Name the Person Who Has It
Validating a business idea starts with a problem statement specific enough to be falsified: one sentence naming a specific person and the specific frustration they experience. “People want to be more productive” cannot fail a validation test. “Freelance designers who lose two hours a week reconciling invoices across three tools” can.
This is the step most people skip because it feels too simple to matter. It matters more than any of the four that follow.
A vague problem statement makes every later step useless. If you cannot name who has the problem, you cannot find them to interview in Step 2. If you cannot state the problem precisely, you cannot search for it in Step 3. If your pre-sell page in Step 4 describes a feeling instead of a frustration, nobody will care enough to act on it.
Write your problem statement using this template: “[Specific person] struggles with [specific frustration] when they try to [specific task], which costs them [specific cost — time, money, or stress].”
Test the sentence by reading it to yourself. If it could describe half the working population, it is not specific enough. If it names a person you could find in a particular subreddit, Slack group, or LinkedIn search filter, you are ready for Step 2.
Step 2: Talk to Five People Who Are Not Your Friends or Family
The second step is running structured conversations with people who match your problem statement and have no relationship with you. The goal is not feedback on your idea. It is evidence about their life — what they have actually done about this problem, not what they say they would do about yours.
This is where most solopreneurs quietly sabotage themselves. They describe the idea, ask “would you use this?”, and hear enthusiasm. Enthusiasm from someone who likes you is nearly worthless — Rob Fitzpatrick’s The Mom Test is built entirely around this one observation: people are too polite to tell you your idea is bad, so you have to ask questions that do not give them the option to lie.
The fix is to ask about their past, not your future product. “How do you currently handle this?” instead of “would you use a tool that does this?” Past behavior is a fact. Future intent is a guess dressed up as an answer.
Aim for five conversations minimum before drawing any conclusion. If the same complaint shows up in four out of five, you have a pattern. If every conversation surfaces something different, either your problem statement from Step 1 was too broad, or the problem is not as common as you assumed.
For the exact wording to use in these conversations, the Mom Test framework breakdown covers the three core rules, and Customer Interview Scripts has ready-to-use question sets organized by what you are trying to learn.

Step 3: Look for Demand Signals Before You Build Anything
A demand signal is evidence that people are already trying to solve this problem without your product — paying for a workaround, complaining in a public forum, or searching for a solution. Existing demand signals mean you are entering a market that already exists. Their absence does not kill the idea, but it means you are creating demand instead of meeting it, which is a slower and more expensive path.
Before you ask anyone anything, look for the trail your target person has already left. Search Reddit threads, Indie Hackers posts, and niche forums for the exact frustration from your Step 1 sentence. Look at what tools, spreadsheets, consultants, or manual workarounds people currently pay for or tolerate. Check whether competitors — even imperfect ones — already exist and have paying customers.
Three things count as a real demand signal:
- Paid workarounds. People spending money on a clunky substitute (a generic tool bent to fit the job, a freelancer hired to do it manually).
- Public complaints with specifics. Not “this is annoying” but a detailed rant that shows the person has thought about the problem repeatedly.
- Existing competitors with active users. A crowded market with mediocre incumbents is often a better sign than an empty one — it means people are already paying to solve this.
What does not count: a lack of competitors. Believing you found an empty market is one of the most common reasons solopreneurs build something nobody wanted — per CB Insights’ analysis of startup post-mortems, “no market need” consistently ranks as the leading cause founders cite for failure, and in most of those cases the founder assumed demand existed and never checked for a trail. An empty market is more often a sign nobody has found a workable solution worth talking about than a sign of untapped opportunity.

Step 4: Run a Pre-Sell Test to See If Strangers Will Act, Not Just Talk
A pre-sell test asks strangers to commit something real — an email, a deposit, a pre-order — before the product exists. It is the step that separates a validated idea from an interesting conversation, because commitment costs something and talk does not.
Conversations tell you whether a problem is real. They do not tell you whether people will pay to fix it. That gap is where a pre-sell test comes in.
Build a single page: one sentence describing the problem, one sentence describing the outcome, and one action — a waitlist signup, a small deposit, or a full pre-order. Tools like Carrd or Gumroad can have this live in under two hours; no code required. Post it in the same communities where you found demand signals in Step 3, not to your existing network. Friends converting tells you about your friendships. Strangers converting tells you about your market.
For the exact mechanics of running this over a single weekend — what to put on the page, where to post it, and how to read the results — the One-Weekend Demand Test walks through the full setup and gives interpretation ranges for the numbers you will see.

Step 5: Make the Go, Wait, or Kill Call
The final step is scoring the evidence from Steps 1 through 4 against a clear threshold, then committing to one of three outcomes: build with confidence, gather more evidence in a specific weak area, or kill the idea and move to the next one. The only wrong outcome is deciding to keep “researching” indefinitely.
By this point you have four pieces of evidence: a specific problem statement, conversation patterns from real people, demand signals from the wider market, and a real (or absent) commitment from strangers. Weigh them together instead of any single piece in isolation. Strong customer conversations with zero pre-sell interest is a different picture than strong pre-sell interest with vague, inconsistent conversations.
If most of the evidence points the same direction, the decision is straightforward: build (all four signals positive), or kill (all four signals absent or contradictory). The harder case is mixed evidence — real problem, weak demand signal, no pre-sell traction. That is a “wait” verdict: go back to the specific step that came up weak and gather more evidence there before committing months of build time.
For a more granular scoring model that weighs each category numerically, the Idea Validation Scorecard breaks this same decision into 15 checkpoints across five categories. The complete evaluation guide walks through each criterion in depth if you want the reasoning behind the score, not just the number.

Want to run your own idea through this process without building the scoring model yourself?
The Idea Validation Scorecard packages the same evaluation logic from Step 5 into a 20-minute exercise with a clear go, wait, or kill recommendation.
Free. No signup required to read it.
Frequently Asked Questions
How long does it take to validate a business idea?
A focused pass through all five steps typically takes one to two weeks: about a day to write the problem statement and start outreach, three to five days for customer conversations, one to two days for demand-signal research, and one weekend for the pre-sell test. Validation does not require months, only structured effort over a short period.
Can I validate a business idea without spending any money?
Yes. All five steps use free or low-cost tools: a notebook or Google Doc for Step 1, calls or messages for Step 2, public forums and search for Step 3, and a free-tier landing page builder like Carrd or Google Forms for Step 4. The only real cost is time, typically one to two weeks of it.
What is the difference between validating and evaluating a business idea?
Validating is the process of gathering new external evidence — conversations, demand signals, a pre-sell test. Evaluating is scoring the evidence you already have against a structured framework. The Idea Validation Scorecard and the full evaluation guide cover the scoring side; this process covers how to generate the evidence in the first place.
What if my idea fails the validation process?
Then the process did its job. Finding out in one to two weeks that an idea lacks demand costs far less than finding out after six months of building. A failed validation is not wasted effort — it is a specific, evidence-based reason to move to your next idea instead of your best-sounding one. The Idea Validation Scorecard helps you compare multiple ideas against the same criteria so the next one you pick has better odds.
Keep Reading
What to Do Next
Choose the path that fits where you are right now.
Get the 7-Day Idea Test (Free)
Download the free 7-Day Idea Test. One task per day. Four evidence signals. One clear go, wait, or kill result — before you spend months building the wrong thing.
Send Me the PlaybookStart Reading
Read the step-by-step setup guide for your platform.
Related Articles
The Idea Validation Framework: A Structured Approach for Solopreneurs
A practical idea validation framework covering problem fit, demand signals, willingness to pay, and founder fit — before you commit months to building.
Why "Would You Pay for This?" Is the Wrong Question
Asking 'would you pay for this?' feels like validation but produces noise, not signal. Here is what the question tells you and what to ask instead.
How to Validate a Product Idea Before You Build Anything
Validation is not asking your friends. It is collecting specific evidence that a real problem exists and that real people will pay to solve it.