Most founders don't validate product ideas. They ask a few friends, post on Twitter, get encouraging replies, and start building. Six months later they have a product that polite people call "interesting" and nobody uses.
117| 118|The numbers are stark. According to CB Insights' post-mortem analysis of startup failures, 42% of failed startups cite "no market need" as the primary cause — the single largest category, ahead of running out of money (29%) and team problems (23%). The product worked. The market didn't want it.
119| 120|This happens because building is easier than validating. Writing code feels like progress. Asking strangers if they actually have the problem you're solving is uncomfortable and slow. Founders rationalize past it: "I'll validate after I build a prototype." But by then, six months of sunk cost makes honest evaluation nearly impossible.
121| 122|Here's how to validate before you build — specifically, how to find out who has the problem, not just whether the problem exists at all.
123| 124|The standard advice is to do customer interviews — talk to 10 to 20 potential users, ask about their problems, and look for patterns. Good advice, poorly executed in practice.
127| 128|The core flaw: founders interview their networks. If you're a software engineer in San Francisco, your network is disproportionately software engineers, startup people, and tech-adjacent professionals. They're also your friends, which means they're motivated to be supportive rather than honest.
129| 130|Even when founders branch out beyond their immediate network, they tend to find people who look and think like them. A nurse's aide in rural Tennessee, a shift worker at a distribution center in Ohio, a single parent working two part-time jobs — these people don't appear in the founder's Twitter followers or LinkedIn connections. But they might be exactly who needs the product.
136| 137|The result is a biased validation sample. You get enthusiastic responses from people who share your worldview and lifestyle, interpret that as market demand, and build for a narrow segment while assuming you're building for everyone.
138| 139|The second problem: even good interviews capture what people say, not what they do. "Would you use this?" is a different question from "Do you currently pay $15/month for something that imperfectly solves this?" People are polite. They nod. They say "yeah, that would be useful." They don't pull out a credit card.
140| 141|Before you can evaluate market demand, you need to answer a more specific question: which specific people have this problem acutely enough to pay for a solution?
144| 145|That's problem-solution fit (PSF). It's the degree to which your product's solution addresses a real, acute problem for a specific audience — where "acute" means the person is already spending money, time, or emotional energy to deal with the problem. PSF isn't about whether the problem is real. Almost every product solves a real problem for someone. PSF is about whether the problem is real enough, for specific enough people, that they will pay for a better solution.
146| 147|Not: "Does this problem exist?" (It almost always does, for someone.) But: "Which specific groups of people experience this problem severely enough to pay for a solution — and who has already solved it in a way your product can't beat?"
150|The distinction matters because PSF is segmented. Different demographic groups experience the same problem at very different intensities. Take a habit-tracking app. Everyone struggles with habits sometimes. But when we evaluated this product concept against 250 Census-grounded synthetic personas, the PSF scores were dramatically uneven: urban shift workers (nurses, retail workers, hospitality staff) scored 84 out of 100, while suburban office commuters scored only 38.
153| 154|Why? Office workers have an accountability system they don't realize they have: the commute, the 9am start, the colleague who asks about the gym. Their work schedule structures their habits involuntarily. Shift workers have none of that. A rotating 3-on/4-off schedule shares no anchors with anyone in their social circle. Their problem is acute. Office workers' problem is mild. See the full habit accountability app analysis for the complete breakdown.
155| 156|The fundamental insight is that demographic segments experience problems differently. And yet most early-stage validation treats the market as homogeneous — "would someone use this?" rather than "would a 35-year-old night-shift nurse pay for this, and why doesn't a 40-year-old suburban commuter have the same problem?"
159| 160|An audience discovery approach evaluates your product concept across multiple demographic segments simultaneously, looking for where the problem is acute and where it isn't — and specifically for counterintuitive findings (the segment you didn't expect turns out to have the highest need).
161| 162|What does this look like in practice? One approach is to build a grid:
163| 164|This is hard to do rigorously by hand, because your instincts about which segments matter are themselves biased. You'll over-weight segments that resemble your own experience and under-weight ones that don't.
172| 173|Modest Idea runs this evaluation using 250 synthetic personas grounded in Census PUMS data, evaluated by multiple AI models with intentional variation — different temperatures, different model providers — to reduce systematic bias. The personas span age, income, education, occupation, family structure, and region. The output is segment-level PSF scores with reasoning, so you can see not just who scores high, but why.
174| 175|The methodology isn't a replacement for real customer interviews. It's a way to identify which segments to interview. Instead of asking your Twitter followers if they'd use a cashflow planning app, you learn that creative freelancers earning $30K–70K/year score 89 on PSF while high-income consultants score 31 — because the consultants already have a CPA. You know to focus your interviews on the first group, not the second. See the cashflow planner analysis for context.
176| 177|Beyond PSF scoring, there are behavioral signals that indicate a product idea needs more validation before you build:
180| 181|Everyone says it's great but nobody can say specifically who needs it most. "Oh yeah, everyone struggles with this" is a red flag. If the problem were universal, there would already be dominant solutions. If every segment scores 50–60 with no standouts, the product either needs to be repositioned or the problem isn't acute for any segment.
182| 183|Your target audience is "everyone." Every founder says this. No product serves everyone equally. If you can't name three specific demographic or situational groups — not just "millennials" or "professionals" — you haven't segmented. You've assumed.
184| 185|You can't describe what your target users are currently doing instead. High-PSF segments always have inadequate workarounds. The shift worker is using a general-purpose calendar app and forgetting to check it. The creative freelancer is using a spreadsheet that doesn't model irregular income. If you ask "how do you deal with this today?" and the answer is "I don't really have a problem with it," you're talking to the wrong segment.
186| 187|Confusing politeness with validation. People will tell you your idea is interesting, useful, and needed. They're being kind. Ask different questions: "How much do you spend per month on this problem, currently?" "When did this last cost you something concrete — time, money, or stress?" Specific answers indicate real PSF. Vague enthusiasm doesn't.
190|Your own experience is your only data point. Founders build for themselves constantly — it's often how the best ideas start. But "I have this problem" is the beginning of validation, not the end. The question is whether your experience generalizes, and to whom. If you can't explain why someone whose life looks nothing like yours would have the same problem, you might be building a tool for yourself.
193| 194|Assume you've done the work. You have segment-level PSF scores. Your habit app's highest-fit segment is shift workers, not productivity-Twitter office workers. Your cashflow tool's best segment is creative freelancers, not the high-income consultants you initially imagined. Now what?
197| 198|Build for the high-PSF segment first. Not for everyone. Not with the medium-PSF segment in mind "to keep the addressable market larger." The high-PSF segment is where you'll find the users who will pay, refer others, and give you honest feedback because they actually need the product to work.
199| 200|Everything changes when you know your real segment:
201| 202|The medium-PSF segments don't disappear. They become your growth path once you've built something that works deeply for the high-PSF group. But launching to everyone simultaneously means building for no one specifically, which usually means a mediocre product that solves the problem adequately for segments that have other adequate solutions.
210| 211|Validation isn't about confirming your idea is good. It's about learning which version of your idea is genuinely needed — and by whom.
212| 213|Get PSF scores for your product concept across 250 Census-grounded personas and 6–8 demographic segments.
216| Start your analysis → 217|A 5-step process for evaluating problem-solution fit, with scoring templates and real case studies from 250-persona analyses.
Get the Free Guide →