The business idea validation checklist: 10 questions to answer before you build
Validation feels fuzzy until you have a concrete checklist. Ten yes/no questions, all answerable with community data, that tell you whether your idea is ready to build or still needs research.
Most founders skip validation. Not because they think it's unimportant, they know it matters, but because validation feels fuzzy and open-ended. What does "validated" actually mean? How do you know when you're done?
This checklist gives you ten concrete, answerable questions. If you can say yes to eight of them with evidence, your idea is validated enough to start building. If you're guessing at more than three, you need more research.
All ten questions can be answered using community data, specifically, the bing.ly Ideas tool, before you write a single line of code.
1. Can you find 20 people who have described this problem unprompted?
Not people you interviewed. Not people who responded to a survey you sent. People who posted publicly, without knowing you were watching, about a problem that your product would solve.
If yes: the problem is real. If no: either the problem is rare, or you're searching with the wrong framing.
2. Are the pain point posts from multiple sources, not just one community?
A problem that appears only on one subreddit might be a community-specific frustration, not a structural market problem. A problem that appears on Reddit, Hacker News, App Store reviews, and G2 is platform-agnostic, it's a real problem wherever the customer type gathers.
3. Are people describing the problem in consistent language across different posts?
If 20 people independently use the same phrase or metaphor to describe the problem, you've found the authentic voice of the customer, and your marketing copy.
If everyone describes it differently, the problem may be too vague to solve with a single product.
4. Is the problem occurring frequently, not just once?
Posts that say "this happens every day" or "we deal with this constantly" or "it comes up every sprint" are describing a recurring problem. Recurring problems are worth solving. One-time problems are not.
5. Are there buying signals, evidence that people spend money to solve this?
Filter the bing.ly Ideas tool to Buying Signals and look for references to current tools people pay for, budgets they mention, and prices they've accepted or rejected.
No buying signals doesn't mean the problem isn't real, it may mean the market is unmonetised. But it raises the bar for your validation: you need stronger evidence of willingness to pay.
6. Do existing solutions fail in a specific, consistent way?
If people complain about current tools, what specifically do they say is broken? The more consistent and specific the complaint, the clearer your differentiation opportunity.
Generic complaints like "it's too expensive" are less useful than specific ones like "it can't do X without a full export and re-import."
7. Can you reach the target customer without paid advertising?
Identify the community, subreddit, forum, or professional network where your target customer gathers. If you can get in front of 100 potential customers for free, distribution is not a launch barrier.
If the only way to reach them is paid ads, your cost of customer acquisition is high from day one.
8. Is the problem consistent across multiple user types within your segment?
If the problem only appears in posts from one very specific user type (e.g., only solo founders at pre-revenue startups), your addressable market may be too narrow.
If the problem appears across several related user types in your segment, the market is wider.
9. Are there feature requests that point at a specific, buildable solution?
Filter to Feature Requests and look for requests that describe a concrete capability. "I wish there was a way to export this as a PDF" is a feature. "I wish this was better" is not.
Specific, actionable feature requests are a product spec. If you can find 10 of them that point at the same core capability, you know what to build first.
10. Is post volume growing or at least steady over the past 12 months?
A problem with declining community discussion may be one that's been solved, is declining in relevance, or has peaked. A problem with steady or growing discussion is one that remains unsolved and relevant.
Check the trend, not just the count.
What to do with your score
8-10 yes answers: build. You have enough evidence to start with confidence.
5-7 yes answers: build slowly. Ship the absolute minimum, validate with real users fast, and use their feedback to close the remaining gaps in your research.
Below 5 yes answers: research before building. At least two or three of the unanswered questions are hiding important risks. Spend another week on community research before writing any code.
Validation isn't a gate you pass once. It's an ongoing practice that makes every decision you make after it better.
Track your AI visibility with bing.ly
See how ChatGPT, Perplexity, Claude, and Gemini answer questions about your brand, and monitor community signals across Reddit, Hacker News, and more.
Get started free