The Startup Idea Validation Checklist — 47 Questions to Kill or Confirm Your Idea in One Weekend

The best validation work happens before you're too emotionally attached to the idea to hear bad news. That window — the period between having a clear problem hypothesis and starting to build — is when honest scrutiny is most valuable and least threatening. The questions below are designed to be worked through in a single weekend: a structured audit of your idea that should, by Sunday evening, tell you whether it is worth pursuing seriously or whether your time is better spent elsewhere.

They are grouped into five sections: problem, market, competition, founder fit, and early signal. Work through them in order. Answer honestly. If an answer makes you uncomfortable, that discomfort is the data.

The problem section. Is the problem you're solving specific enough to describe in one sentence without vague language? Does it affect a defined group of people rather than "everyone"? Is it experienced regularly — weekly or more — by your target user, or is it an occasional inconvenience? Is it currently unsolved, or do your target users have workarounds they've become comfortable with? If they have workarounds, how much friction do those workarounds actually create? Have you seen evidence of people spending money or significant time to address this problem — in forums, in reviews of competing products, in how they currently behave? Can you describe what your target user's situation looks like before your product and after, in specific concrete terms? And finally: is the problem painful enough that someone would change their behaviour to resolve it?

If you reach the end of that section without confident answers to at least six of the eight questions, the problem statement needs more work. Vague problems produce vague products. The effort of sharpening the problem now saves months of misdirected building later.

The market section. Can you name specifically the people who have this problem — their role, industry, current behaviour, stage of life? Can you estimate how many of those people exist, and does that number produce a revenue outcome worth pursuing even with a conservative conversion rate? Is the market growing, flat, or contracting — and does that trajectory help or hurt you? Do the people in this market have budget, either money they currently spend on adjacent problems or clear authority to make purchasing decisions? Can you reach this market through channels available to you, or does your go-to-market depend on distribution you don't have and can't build quickly?

Two market questions that often get skipped. Is the market consolidated enough that you could become the dominant player in a specific niche, or is it so fragmented that consolidation is effectively the product you'd need to build? And: have you checked whether your target market uses language that matches your value proposition — do the words you use to describe the problem match the words they use to describe it? Mismatched language is one of the most reliable signals that you don't yet understand the market you're entering.

The competition section. Can you name the three products your target users most commonly use to address this problem today — including the informal ones like spreadsheets, email threads, and manual processes? For each competitor, what is the specific thing they do poorly that your product would do well? Is your differentiation real and immediately noticeable, or subtle enough that a user would take weeks to appreciate it? Have any of your main competitors raised significant funding in the last eighteen months, and if so, what does that say about the competitive dynamics you're entering?

The hardest competition question: if a well-resourced competitor with existing distribution shipped a version of your product tomorrow, what would happen to your business? If the honest answer is "most customers would leave within a year," you need to be explicit about what switching costs you'll create in the meantime and how fast you can build them. Acknowledging this risk early is not a reason to stop — it's a design constraint that should shape what you build first.

The founder fit section. Do you have direct experience of the problem you're solving — not observed or researched experience, but personal experience as someone who has lived it? If not, do you have deep access to the community of people who do? Do you have any expertise, relationships, or distribution advantage in this market that a stranger building the same product wouldn't have? Are you willing to spend two to three years on this specific problem — not two to three years on "being a founder," but on this particular, often unglamorous problem?

Two more founder fit questions worth sitting with. Are you building this because you see a real problem that needs solving, or because the technology is interesting and you're working backwards to find a use case? And: do you have the appetite for repeated rejection — from customer interviews, from early sales conversations, from pitches that go nowhere — that the early stage of every startup requires? Founder fit is not just about skills. It is about whether the specific grind of this specific market is something you can sustain for long enough to find out if it works.

The early signal section. Before you build, what is the minimum action a potential customer could take that would constitute real demand — not interest, but a commitment of time or money? Have you tested that signal already? If yes, what was the result, and what does it tell you? If no, what is stopping you from running that test this week? Have you spoken to at least ten people who fit your target profile — not friends or family, but people who would have no reason to encourage you — and asked questions designed to surface their actual behaviour rather than their hypothetical enthusiasm?

Continuing the signal section. Are there communities, forums, or existing audiences where your target users gather, and if so, have you spent time listening before approaching as a seller? Have you looked for evidence of manual workarounds in your target market — people solving the problem with spreadsheets, Slack automations, or sheer administrative effort because no good tool exists? Manual workarounds are one of the strongest possible demand signals. And finally: is there a version of this business you could test in one week with no code — a form, a doc, a manual service — and if so, why haven't you run that test yet?

At the end of this audit, the pattern of your answers should be clear. Strong, confident answers across all five sections mean you have a well-structured foundation. Weak spots in one section mean that section is your next task. Weak spots in multiple sections mean the idea needs more time in ideation and validation before you're ready to build.

Running through this checklist with an AI co-founder like Kooio produces better results than running it alone — not because Kooio has information you don't, but because answering these questions to a structured prompt that pushes back on vague answers forces the kind of honest articulation that most founders skip when reviewing their own ideas. The discipline of being made to explain your assumptions is the same discipline that makes a good co-founder useful.