The solo founder's idea validation checklist

You don't have a co-founder to argue you out of a bad bet or a research team to validate a good one. This checklist is the whole loop, in order, sized for one person and about three weeks of part-time work. Each item links to a deeper piece if you want it.

Week 1: define what you're testing

• Write the idea in one paragraph. Plain language, no jargon, the version you'd say out loud.
• Name the segment precisely. Not "small businesses" — "freelance designers who invoice 5+ clients a month." If you can't get specific, that's problem number one.
• List your assumptions. Everything that has to be true for this to work.
• Turn the top assumptions into 3–5 hypotheses across problem, willingness to pay, behavior, solution fit, and market. Make each one specific enough to be wrong. See turning a fuzzy idea into testable hypotheses.
• Write the failure condition for each hypothesis before you collect any data. If you can't picture a plausible "no," the hypothesis is still too vague.
• Rank hypotheses by risk. Test the one the whole idea depends on first.
• Draft a screener question that disqualifies people who don't have the problem.
• Draft 8–12 questions about behavior and past spend, not opinions. Pull from customer discovery interview questions.
• Check every question for leading language. Remove any mention of your solution before the problem is established. See the Mom Test rewrites.

Week 2: collect evidence

• Find where your segment gathers — subreddits, Slack and Discord groups, LinkedIn, niche newsletters.
• Recruit 10–20 qualified people for round one. Quality of fit beats volume. See how many customer interviews you need.
• Run the screener first and politely end conversations with non-qualifiers.
• Ask about the last specific time the problem came up, every time.
• Follow up three times on every interesting answer: why was that a problem, what did you do, what happened next.
• Record everything (with permission). You'll need exact quotes later.
• Ask for referrals at the end of every conversation.
• If running a survey instead, keep it under 12 questions, screener first, open-text questions early. See idea validation survey questions.
• Test willingness to pay against real past spend, not a hypothetical number. See willingness to pay survey questions.

Week 3: read the verdict

• Score each hypothesis — confirmed, weakened, or inconclusive — against what people actually reported.
• Check your scoring against the bar you set in week 1. Don't move the goalposts now.
• Look for the stop signals: mild problem language, no existing workaround spend, no recent instance, purely hypothetical willingness to pay.
• Roll the hypotheses into one read: build it, refine it, keep testing, or weak demand.
• If it's a kill, write down which assumption broke. That's what you'd change on another run. See when to kill a startup idea.
• If it's "refine," change one variable — segment, price, or framing — and run another focused round.
• If it's "build," write the one-line summary of the evidence so you can point to it when you doubt yourself in month three.

The mindset that makes it work

• A clean "no" in week three is a win. It hands you back five months.
• You are the least objective person about this idea. Decide your criteria before the data arrives.
• Enthusiasm from friends is not evidence. Behavior from strangers is.
• One good screened respondent beats ten unscreened ones.

Common questions

Can I really validate an idea in three weeks?

For one hypothesis-testing round, yes. Some ideas need two or three rounds, especially if the first is ambiguous. But a build-or-kill signal on the core problem is a three-week job, not a three-month one.

What if I've already started building?

Run the checklist anyway, starting from week 1. The cost of confirming a weak idea now is a few weeks. The cost of finding out post-launch is everything in between.

Do I need a budget?

Not really. A small budget for a recruiting panel speeds up week 2, but relevant communities and direct outreach work for free.

What's the most-skipped step?

Writing the failure condition before collecting data. It's the one thing that stops a weak result from being rationalized into a green light.

Run the whole checklist in one place

Hypothis walks a solo founder through this exact loop — hypotheses, a screened research round, adaptive follow-ups, and a scored verdict that's allowed to say no. It's free during early access. See how it works or create your account.