September 25, 2026 3 min read validate a saas idea

Validate a SaaS Idea Before You Write Any Code

How to validate a saas idea with public evidence, five customer conversations and a small demand test, so you build only what people want.

The most expensive way to validate a SaaS idea is to build it and find out. The cheapest way is to look for evidence in three places, in order, and stop as soon as the evidence tells you no.

Most founders skip to the last step — a landing page — before they have done the reading that would tell them what the page should say. Validation is not one test. It is a ladder, and each rung is cheaper than the one above it.

What validation actually means

Validation does not mean proving the future. It means reducing the biggest risk first.

For a new SaaS idea, the risks stack in a known order: does the problem exist, does it hurt enough to act, will people pay, can you reach them, can you build it. You validate from the top down, because a false answer at the top makes every test below it a waste.

Stage 1: evidence from public discussions

Before talking to anyone, read. You are looking for signs that the problem is real and recurring:

  • The same complaint from different people, in different threads, over months.
  • A current workaround that costs time or money — a spreadsheet, a freelance hire, a tool they pay for and resent.
  • Active searching: people asking for a tool, comparing options, or describing what they left and why.

If you find only excitement and no cost, you have a topic, not a problem. This is the core of evidence-based idea validation, and it is free.

Stage 2: five conversations

Now talk to five people who have the problem. Not to pitch — to reconstruct a recent event. Ask when it last happened, what they did, what it cost, and what they tried before. You will learn more from five of these than from fifty survey responses, because you can follow up on the interesting sentence.

Watch for these in what they say:

  • They describe the problem before you describe your solution.
  • They mention a cost without being prompted.
  • They have already tried to solve it, even badly.

Anything less is pleasant conversation. For the difference between a signal and a compliment, see idea validation red flags.

Stage 3: a small demand test

Only now put something in front of people. A simple page describing the outcome, with a real call to action — a waitlist, a pre-order, a “book a call”. Then send traffic to it from where the buyers already are.

The point is not the number of signups in isolation. The point is the ratio between people who see it and people who do something. A page that describes the problem in the buyer’s own words converts; a page that describes your features does not.

If you can, include a price. Real intent shows up when money is involved, which is why willingness-to-pay signals are the strongest evidence of all.

What a real signal looks like

  • People ask when it will be ready.
  • People offer to pay before you ask.
  • People introduce you to others with the same problem.
  • People push back on details because they are already imagining using it.

Weak signals look different: polite interest, “looks cool”, a long compliment with no mention of the current cost. If that is all you have, the honest move is to keep reading, not to start building.

FAQ

How long should validation take?

Weeks, not months. A focused pass is roughly a week of reading, a week of conversations and a week of testing. If it drags, you are usually avoiding a “no” you already found.

Is a waitlist enough proof?

No, but it is a useful step. A waitlist tells you the message resonates. It does not tell you people will pay. Pair it with conversations and, ideally, a price.

What if the evidence is mixed?

Mixed evidence usually means the problem is real but your segment is too broad. Narrow it until the signal is consistent, rather than averaging the noise.

Do I have to talk to strangers?

Yes. Friends are the worst sample because they want to be kind. If cold outreach is hard, start from people who already complained in public, then invite them.

What if I already started building?

Stop and run stage one now. Reading costs a week and can save months. If you want the public-discussion part done in minutes, run a report for 2.99 EUR and read validated signals with quotes, then move straight to conversations. For the full method, start with how to validate a startup idea.

Run your own

Name a problem you keep hearing about — or the market people are stuck in. The report comes back with the problems they described, the quotes behind them and what they already tried.

Two to four minutes. 2.99 € once, no subscription.

October 12, 2026 5 min read

GitHub Issues as a Source of Micro SaaS Ideas

Use GitHub issues to find micro SaaS ideas: filter the noise out of issue search, read reactions and wontfix threads, and turn an unmet need into a product.