Written by Simon, founder who shipped 4 products nobody wanted.

Validate Before You Build: How to Estimate Real Demand Using Free Public Data

Ninety percent of startups fail. You already know that stat. What's less discussed is how many of those founders knew, somewhere deep down, that they were building on shaky ground but kept going anyway. Startup idea validation isn't a nice-to-have step you do when you have spare time. It's the difference between spending 8 months building something 120 people will ever want versus spending 4 weeks discovering that and saving your year. If you're reading this, you probably have an idea you're excited about. Good. Now let's figure out if anyone else cares. Validate your idea before you write a single line of code.

Part 1: Why Founders Skip Startup Idea Validation

The Bias Trap

Founders are optimists by nature. That's a feature, not a bug, until it causes you to mistake enthusiasm for evidence. Confirmation bias is the silent killer of early-stage companies. You post about your idea in a Slack group, three friends say "that's cool," and suddenly you've convinced yourself there's market demand. There isn't. Not yet. The "build it and they will come" mentality still runs rampant despite every piece of evidence against it. Passion for a problem is a good starting point, but it is not a proxy for market demand. According to CB Insights, 42% of startups fail due to no market need. Not competition, not funding, not bad timing. No market need. That's a validation failure, plain and simple.

The Time Cost of Ignoring Validation

Here's a real scenario, anonymized but true. A B2B SaaS founder spent 8 months building a compliance workflow tool. He hired a contractor, paid for infrastructure, wrote docs and onboarding flows. When he finally went to sell it, he discovered his total addressable market contained roughly 120 qualified prospects. Not 120,000. One hundred and twenty. The product wasn't bad. The market just couldn't support a business. Four weeks of validation work upfront would have revealed that. Instead, he lost 8 months and a meaningful amount of capital. Pivoting after 6 to 12 months of development is brutal. Pivoting after 2 to 4 weeks of validation work is just smart iteration.

Part 2: The Validation Framework

Step 1: Define Your Hypothesis and Target Customer

Vagueness kills validation. "Small businesses" is not a target customer. "Independent bookkeepers in the US earning $50K to $150K annually" is a target customer. The sharper your definition, the more accurate your demand signals will be. Use the Jobs-to-be-Done methodology as your starting frame. Your customer isn't buying software. They're hiring it to accomplish a specific job. Ask yourself what job they're trying to get done and what's standing in their way. Write your hypothesis in one sentence using this structure: "We believe [target customer] struggles with [problem] because [reason] and we can solve this with [approach]." If you can't write it in one sentence, you don't know what you're building yet.

Step 2: Extract Demand Signals from Free Public Data

This is where most founders either skip entirely or do superficially. Don't. Google Trends is your first stop. Search for keywords related to your solution and look at the trajectory. Is search volume trending up, flat or declining? Seasonal patterns matter too, especially for B2C ideas. Next, go to Reddit. Search relevant subreddits like r/entrepreneur, r/freelance or industry-specific communities. Count how many threads surface your exact pain point unprompted. That unprompted quality matters. If people are complaining about this problem on their own, without anyone asking, that's a real signal. LinkedIn searches tell you how many people carry job titles matching your ideal customer profile, which gives you a rough ceiling on your addressable market. YouTube is underrated for this. Search the problem category and look at view counts and comments. The comments section on a video with 200,000 views about a niche frustration is a goldmine of exact customer language. Free tiers of tools like Ahrefs and Ubersuggest show keyword difficulty and search volume estimates. SBA.gov and US Census data round out the picture with demographic and industry-level numbers. Spend four focused hours across three to five of these sources and document everything in a spreadsheet. You're building an evidence base, not a feeling.

Step 3: Run a 48 to 72 Hour Landing Page Experiment

You do not need a product to test demand. You need a one-page website that clearly describes the problem, hints at your solution and asks visitors to join an early access waitlist. Webflow, Carrd or even a basic WordPress install works fine. Your headline should name the problem, not your product. Drive traffic through relevant Reddit communities, LinkedIn posts, Twitter/X and Hacker News. If you have $200 to $500, a targeted Google Ads or Facebook campaign gets you cleaner data faster by putting your page in front of exactly the people you defined in Step 1. The metric that matters is signup rate, not pageviews. A 5% to 10% conversion from visitor to email signup indicates genuine interest. Below 2% means something is off, either the messaging, the audience or the problem framing. Don't confuse 1,000 visitors with validation. Ten signups from 1,000 visitors is a signal you need to rethink your angle.

Step 4: Conduct 10 to 15 Structured Customer Interviews

Quantitative signals show you that interest exists. Qualitative interviews show you what that interest actually means and whether it translates into money. Reach out to people who signed up on your landing page plus a fresh set of cold contacts who match your ICP. Each interview should run about 30 minutes. Start by asking how they currently solve the problem. Let them talk. Then go deeper: what's the annual cost or impact of this problem on their business? Would they use a solution like yours, and what would they pay? End by asking who else you should talk to. That last question is a commitment test. People who are genuinely interested give you referrals. People who are being polite dodge it. Red flags in interviews include phrases like "that's interesting" with no follow-up action, vague answers about cost or frequency and zero budget language. Green flags are specific metrics ("I spend five hours a week on this"), willingness to name a price without being pushed and unsolicited referrals. After 15 interviews, write a one-page synthesis. Look for themes that appeared in eight or more conversations. Those are your real product requirements, not your assumptions.

Step 5: Estimate Market Size Using Bottom-Up Analysis

Top-down TAM numbers pulled from industry reports are usually fantasy. Bottom-up math is what serious founders and investors actually trust. Start with how many people or companies fit your ICP. Use LinkedIn, industry directories and census data to get a real number. From your interviews, estimate what percentage of that population has the problem severely enough to pay for a solution. Usually that's somewhere between 5% and 15%. Multiply by your price point, then apply a conservative Year 1 penetration rate of 1% to 3%. Here's a worked example: 50,000 independent bookkeepers in the US, 12% with an acute version of the problem, $100 per month price point, 2% Year 1 penetration. That's $1.2M in potential Year 1 revenue. Is that enough to build a business on? Depends on your cost structure. But now you're talking about real numbers, not slides with hockey sticks drawn on them.

Part 3: The 30 to 90 Day Validation Roadmap

Weeks one and two are for hypothesis definition and data mining. Write your hypothesis on Day 1. By Day 10 you should have 20 to 30 documented data signals from Google Trends, Reddit, LinkedIn and keyword tools. Weeks three and four are for your landing page experiment. Build the page in a day. Spend the rest of the time driving traffic and collecting emails. Your target is 100 or more visitors and at least five to fifteen email signups. Weeks five through eight are for customer interviews. Aim for 15 completed conversations. Track pain severity, willingness to pay and how frequently the problem occurs. Weeks nine through twelve are for building your market size model. Run a sensitivity analysis. What happens if only 5% have the problem instead of 12%? What if pricing comes in at $60 instead of $100? Make a go or no-go decision based on the full body of evidence. Get started with this timeline this week, not next month.

Part 4: Common Pitfalls

Confirmation bias doesn't stop at the idea stage. It shows up when you interpret your data too. The fix is to document bullish and bearish signals side by side in your spreadsheet. Assign each signal a confidence score. Force yourself to look at the bearish column. Vanity metrics are a close second on the list of validation traps. A landing page with 1,000 visitors and 0 signups is a failure, not a near-miss. Always track conversion rates, not raw numbers. Interview questions that lead witnesses produce useless data. Never ask "don't you find it frustrating when X happens?" Ask "how do you currently handle X?" and then be quiet. The most underrated pitfall is ignoring customer acquisition cost reality early. Your landing page might convert at 8%, but if acquiring each customer costs $400 and they'll only pay $50 per month, you don't have a business. Model CAC before you get too excited about conversion rates.

Part 5: A Real Validation Story

A founder came to the table with a clear hypothesis: freelance accountants lack good invoicing software for compliance purposes, and they'll pay $50 per month for it. In Week 1 she searched Google Trends for "freelance accountant invoicing" and found modest, flat search volume. Nothing alarming, but nothing exciting. Week 2 she posted in r/accounting and r/freelance. Twelve people responded with genuine interest. Week 3 she built a landing page, pushed 250 visitors via LinkedIn outreach and collected 8 signups, a 3.2% conversion rate. Below the 5% benchmark, but not dead on arrival. Weeks 4 and 5 she interviewed 10 accountants. This is where everything shifted. Not one of them wanted new invoicing software. They were all using FreshBooks and happy with it. But every single one of them had a serious, painful, expensive problem with multi-state compliance tax reporting. Willingness to pay for that? $200 to $400 per month. She pivoted her entire angle, revalidated with 5 new interviews and went on to build a company now sitting at $2M ARR 18 months later. Validation isn't about proving your hypothesis is right. It's about discovering what the real problem actually is, as fast as possible.

Part 7: What "Validated" Actually Means

Validation is not a feeling. It has specific quantitative thresholds. You want 50 or more qualified leads from your landing page within four weeks. You want a 5% or better conversion rate from visitor to signup. You want at least 10 customer interviews completed with eight or more of them surfacing the same core problem without you naming it first. On the qualitative side, the strongest signal is when customers articulate your problem back to you more precisely than you described it. At least three customers willing to pay in a 30-day pilot is the gold standard. For your go or no-go decision: 70% or more of your signals pointing positive means proceed to MVP. Mixed signals mean refine your hypothesis and run 10 more interviews. Predominantly negative signals mean pivot or walk away. Walking away after 4 weeks of validation is not failure. It's the best possible return on that time.

Validation Is Your Competitive Advantage

Founders who run proper startup idea validation get to market faster because they're not rebuilding from scratch after 8 months of wrong assumptions. They raise better rounds because they walk into investor meetings with evidence instead of slides. They build better products because they know exactly what job the product needs to do. The framework in this piece takes 30 to 90 days. That is nothing against the cost of a year spent building the wrong thing. Your one job right now is to try to disprove your idea as quickly and cheaply as possible. If you can't kill it in 90 days of structured testing, you probably have something worth building. Read more on the Validate & Launch blog for frameworks that take you from validated idea to first paying customer.