Product guides

How to Validate an Idea Before Building

A practical checklist for validating a startup idea before you write code: measuring real pain, checking willingness to pay, and talking to buyers.

Last updated July 6, 2026

Quick answer

Validate an idea by confirming the pain is real (repeated, specific, and quantified in time or money), checking that people are already paying for a workaround, and talking to five potential customers before you build anything. If you cannot find ten people independently describing the same problem, the idea is not validated yet, it is a guess.

Step one: measure the pain, do not just notice it

Search for the specific complaint on Reddit, in review sites, or in forums for your target audience. Look for phrases like 'I waste X hours' or 'it costs us Y dollars'. When people quantify their own pain, they are telling you, unprompted, what a fix might be worth to them.

Step two: check what they already pay for

A workaround is proof of budget. If people are already paying a person, a spreadsheet consultant, or a clunky adjacent tool to deal with the problem, that spend is a signal you can displace. If nobody spends anything today, you are not just building a product, you are also creating a new spending habit, which is a much harder sell.

Step three: talk to five potential buyers

Find five people who actually have the problem, through Reddit DMs, LinkedIn, or communities where they already gather, and ask directly: would you pay $X a month for something that solves Y? Five honest conversations tell you more than a month of solo research, and they often surface a detail about the problem that changes what you build.

A simple checklist before you write any code

  • Ten or more independent people describe the same specific problem
  • At least some of them quantify the cost in time or money
  • There is an existing workaround people already pay for
  • Five real conversations confirm willingness to pay
  • You can scope a version small enough to ship in about two weeks

Frequently asked questions

How many complaints do I need before an idea counts as validated?

There is no fixed count, but ten or more independent people describing the same specific problem, ideally with a quantified cost, is a reasonable bar before investing serious build time.

Do I need to talk to real people, or is research enough?

Research finds the pain; conversations confirm willingness to pay. Five direct conversations with people who have the problem will tell you more than another week of reading, and often reveal a detail that changes the scope.

What if I cannot find any existing workaround?

That is a warning sign, not automatically a dead end. If nobody currently pays anything to solve the problem, you are also selling the idea of paying for a solution at all, which is a harder, slower sale than displacing an existing spend.

How does IdeaFast help with this process?

IdeaFast automates the first step: it scans a community, clusters recurring complaints, and scores each by how acute, frequent, and recent it is, with every claim linked to the original post, so you start step two and three with real evidence already in hand.

Related

Skip the manual digging

IdeaFast scans Reddit for you and scores real pain points with evidence. Run your first scan free.