Before You Code: Validate Startup Demand with Three Signals

Demand validation is not a vote on whether your idea sounds clever. It is a search for independent evidence that a specific buyer has a current problem and a reason to act. These three signals give you a fast pre-code filter. None is sufficient alone; together, they tell you whether to build, reframe, or stop.

1. Search Volume: Is the Problem Active?

Search volume is useful only when you inspect the language behind the number. Start with phrases a person uses when they need help, not your proposed product name. “How do I reconcile invoices?” reveals more than “best fintech app.” Look for repeated problem queries, recent discussions, and results that show people comparing solutions. A large keyword with vague, entertainment, or academic intent may be curiosity rather than demand. A smaller set of specific, recurring searches can be a stronger starting point.

2. Willingness to Pay: Is There a Cost?

Searches establish attention, not revenue. Next, find evidence that the problem already consumes money, time, or risk. Current subscriptions, paid agencies, contractors, preorders, deposits, and paid pilots are direct proof. Costly workarounds count too: a spreadsheet maintained every Friday, a manual process spread across three tools, or a founder spending hours stitching together a result.

Talk to people who match your target customer profile and ask what they do today and what it costs. A promise to buy later is weaker than a deposit, a pilot agreement, or a specific budget. You are measuring sacrifice, not enthusiasm.

3. Market Trajectory: Is the Opportunity Moving?

A real problem can still be a poor bet if the category is shrinking or the buyer is disappearing. Compare the direction of search interest, competitor activity, hiring, budgets, regulation, and customer conversations over time. Then separate category growth from buyer-problem growth: a popular category can hide a declining segment, while a stable category can contain a newly urgent workflow.

Classify the trajectory as growing, stable, or shrinking, and write down the evidence for your label. Growing is not automatically good—it can mean crowded competition. Stable is viable when the pain and spending are durable. Shrinking demands a narrow, defensible wedge or a different idea.

A Practical Decision Rule

Score each signal as strong, mixed, or absent, and compare the quality of evidence rather than counting mentions. Strong search intent plus existing spend but a shrinking trajectory suggests a focused cash-flow opportunity, not a venture-scale market. Growing trajectory plus curiosity but no current spend means keep testing the buyer and offer. Strong evidence across all three is a reason to build the smallest test that can earn a commitment.

Before you write code, put the evidence in one place and make the next decision explicit. A structured free market research report can help you map the category, competitors, pricing, and risks before you commit to a build.