Introduction: Demand Is Discovered, Not Assumed

Uncovering true market demand is among the most consequential—and most frequently misunderstood—tasks a startup founder faces. Many early ventures fail not because they lack technical competence or ambition, but because they build solutions in search of problems, relying on optimistic assumptions and flattering feedback rather than evidence. A disciplined approach to user understanding reframes “market research” as behavioral investigation: the founder’s goal is not to persuade people to like an idea, but to discover where a costly, persistent problem already exists and where users are demonstrably motivated to resolve it. In practice, genuine demand is revealed less by what people claim they might do and more by what they have already done, what they repeatedly struggle with, and what they are willing to sacrifice to make progress.

Start With the Problem, Not the Product

The first principle of effective discovery is to begin with the problem rather than the product. Founders often enter the market with a preferred solution and then seek confirmation that it is wanted. This approach invites bias and encourages interviews that function as disguised sales pitches. By contrast, a problem-first orientation treats the user’s current reality as the primary source of truth. The founder investigates what is painful, costly, or frustrating today, and assesses the intensity of that pain by examining the cost of the status quo. If a problem is truly urgent, users will already be spending time, money, or organizational effort to manage it—even if their current methods are inefficient. Where no such effort exists, “demand” is often an illusion created by polite encouragement or hypothetical interest.

Use Behavioral Evidence Instead of Opinions

To uncover reality, founders must prioritize behavioral evidence over stated intent. Conventional questions such as “Would you use this?” or “Do you like this idea?” tend to produce unreliable answers, because respondents are inclined to be supportive, avoid conflict, or speculate about a future they cannot accurately predict. More rigorous discovery relies on past-tense, context-rich interviewing that focuses on concrete events: what happened the last time the problem occurred, how the user responded, what tools were used, what trade-offs were made, and what consequences followed. This style of inquiry—often associated with “The Mom Test” approach—reduces false positives by anchoring the conversation in observable behavior rather than aspirational preference. The founder’s role is to listen more than speak, resist the temptation to pitch, and probe for specifics that reveal how the user’s workflow actually operates.

Observe Users in Context (Not Just in Interviews)

Observation strengthens discovery by capturing what users cannot easily articulate. Even well-intentioned respondents may omit critical details, normalize inefficiencies, or misattribute the causes of their frustration. Techniques such as shadowing, “day-in-the-life” studies, and careful review of community discussions can expose hidden friction and recurring workarounds. Online forums, niche communities, and professional groups often contain unfiltered accounts of struggle—questions that begin with “How do I…?” or complaints that begin with “Why is it so hard to…?”—which can serve as “digital exhaust” indicating where demand may be concentrated. When interview insights align with observed behavior in natural settings, the founder gains a more reliable map of the problem landscape.

Interpret Findings with Jobs to Be Done (JTBD)

A complementary framework for interpreting these findings is Jobs to Be Done (JTBD). Rather than treating users as bundles of demographic traits, JTBD focuses on the progress a person is trying to make in a specific circumstance. Users “hire” products not for their features, but to achieve functional outcomes, relieve emotional burdens, or satisfy social expectations. This lens clarifies why users switch tools, why they tolerate certain inconveniences, and what alternatives they consider acceptable. It also broadens the competitive set: the true competition is not only other startups, but also spreadsheets, manual processes, improvised internal tools, and the decision to do nothing. Understanding what users are currently “hiring” and what they would need to “fire” provides a grounded basis for designing a solution that fits real constraints and motivations.

Prioritize Lead Users and “Hacky” Workarounds

Within this discovery process, certain users deserve special attention: lead users or early evangelists. These are individuals or teams who feel the problem most acutely and have already attempted to solve it through improvised workarounds—cobbled-together toolchains, custom scripts, or elaborate manual routines. Their behavior signals both intensity of need and willingness to experiment. Studying their solutions reveals where existing products fail, which constraints matter most, and what minimum capabilities a new offering must provide to be meaningfully better. Moreover, lead users often indicate where broader markets may move next, making them valuable not only for validation but also for strategic direction.

Validate Demand Through Commitment (“Skin in the Game”)

Discovery alone does not establish demand; validation requires commitment. The most reliable indicator that a problem is worth solving is a user’s willingness to incur a non-trivial cost to address it. This “skin in the game” can take multiple forms. In consumer contexts, it may appear as pre-orders, deposits, or sustained usage despite friction. In business contexts, it may appear as pilot budgets, signed letters of intent, or the allocation of staff time to implementation. Importantly, commitment is not limited to money. Time is scarce, and users who repeatedly engage in deep-dive sessions, complete high-friction onboarding steps, or integrate a rough prototype into their workflow demonstrate seriousness. Reputation can be an even stronger signal in B2B settings: a champion who introduces a founder to decision-makers, procurement, or senior leadership is spending social capital and taking a personal risk. These behaviors are difficult to fake and therefore far more diagnostic than compliments or casual enthusiasm.

Design Tests That Filter for Real Demand

Founders can deliberately design tests that elicit commitment. Rather than optimizing early experiences for maximum sign-ups, they can introduce small hurdles that filter out superficial interest. A “high-friction MVP” might require a detailed intake process, a scheduled onboarding call, or a paid pilot. The purpose is not to create inconvenience for its own sake, but to measure whether the problem is sufficiently painful that users will overcome obstacles to reach a solution. When multiple users independently demonstrate this willingness, the founder gains credible evidence of demand.

Make Discovery a Continuous Discipline

User understanding is not a phase that ends at launch; it is a continuous practice. Markets evolve, organizations change, and products introduce new behaviors that reshape user expectations. A weekly rhythm of customer conversations and observation prevents “founder drift,” the gradual substitution of internal assumptions for external reality. Early-stage startups may lack large datasets, but they can still learn effectively by looking for behavioral consistency within small groups: repeated use, recurring pain points, and stable patterns of willingness to pay or invest time. As the product matures, quantitative analytics can complement qualitative insight, but it should not replace it. Numbers are most useful when interpreted in light of the lived context that produced them.

Conclusion: Evidence Over Validation

Uncovering true demand requires an investigative posture grounded in humility and rigor. The work begins with problems, not solutions; it relies on past behavior rather than hypothetical preference; it is strengthened by observation and structured by frameworks such as Jobs to Be Done; it focuses on lead users who reveal intense needs through workarounds; and it is ultimately confirmed through costly commitment—money, time, or reputation. When founders stop seeking validation and start seeking evidence, they dramatically increase the likelihood of building something users genuinely need and are willing to adopt.