How to validate a SaaS idea before you write a single line of code

Validation has a reputation problem. It sounds like something consultants sell, it produces no visible progress, and it delays the enjoyable part. So most founders skip it: roughly 60% run no formal validation at all.

The arithmetic is hard to argue with. Validation costs something like 5 to 10% of what you would spend building. If spending that could tell you whether the rest is worth spending, skipping it is not efficiency — it is a bet.

What validation is not

Not validation	Why
Friends and family liking it	They are responding to you, not to the product
"That sounds useful"	Politeness costs nothing. Only money counts.
Waitlist signups	Free interest is weak signal. Better than nothing, far from proof.
A competitor existing and doing well	Proves the market exists. Says nothing about whether they will switch to you.
Your own certainty	Every founder of every failed startup had this too

The bar is demonstrated willingness to pay. Everything softer than that is a hypothesis wearing evidence's clothes.

A 30-day sequence

Week 1 — Define the buyer precisely

Write one sentence: "[Job title] at [type of company] with [size] who currently [does the workaround]."

If you cannot fill in every bracket, stop here. A vague buyer produces vague research, which produces false confidence.

Then find where those people are. A subreddit, a LinkedIn group, an industry association, a trade event, a Slack community. If you cannot find them anywhere, distribution will be your real problem and it will not improve after you build.

Week 2 — Have ten problem conversations

Not pitches. Conversations. Your job is to listen, and the questions are about the past rather than the future:

• "Walk me through how you handle [the process] today."
• "When did you last have a problem with it? What happened?"
• "What did you do about it?"
• "Have you looked for a tool? What happened?"
• "What does it cost you when it goes wrong?"

Never ask "would you use a tool that does X?" People are consistently bad at predicting their own future behaviour and consistently good at describing what they actually did last month.

What to listen for: money already being spent, hours being consumed, a workaround somebody built, and emotion. Irritation is data.

Week 3 — Read the market's own complaints

Free and underused. Go to G2, Capterra and Trustpilot, find the incumbents in your space, and read the one and two-star reviews.

People describe precisely what is broken, which features they needed and did not get, and what made them cancel. Do the same on Reddit and in industry forums, searching for the tool names plus words like "alternative", "frustrating" or "switching from".

A market with strong competitors and still-frustrated customers is often more interesting than an empty one. No competition usually means no demand.

Week 4 — Test willingness to pay

This is the part that separates validation from research. Three options, in increasing order of strength:

1. A landing page with real traffic. Describe the product as though it exists, state a price, and drive a small amount of paid traffic to it. A few hundred dollars of search ads gives you a signal in a weekend. Measure clicks on the pricing button, not email signups.
2. Pre-sell it. Offer a founding-customer rate for a product shipping in three months. Take actual payment, with a full refund guarantee if you do not deliver. Someone handing over money is a different species of evidence.
3. Sell the service manually first. Deliver the outcome by hand for three customers, charging for it. Slow, unscalable, and the strongest proof available — because you have learned the workflow properly and been paid to do it.

That third option is the one experienced founders recommend and beginners dislike, because it feels like the wrong business. It is the fastest route to knowing whether the real business works.

Reading the results honestly

What happened	What it means
Someone paid before it existed	Build it. This is as good as pre-launch signal gets.
Strong interest, nobody paid	The problem is real; your solution or price is not right yet
People struggled to describe their current process	The problem is not painful enough to have a process
Everyone gave different answers	Your buyer definition is too broad. Narrow it and repeat.
You could not find ten people to talk to	Distribution problem. It will not improve after launch.

The uncomfortable outcome is the second row, because it looks like success. Enthusiasm without payment is the single most common way founders talk themselves into building.

The mistakes that make validation useless

• Pitching instead of asking. The moment you describe your solution, the conversation stops producing useful information.
• Talking to the wrong people. Tech-savvy early adopters will validate almost anything. Talk to your actual target market.
• Skipping price. Validating that people want a solution is not validating that they will pay yours.
• Stopping at the first yes. One enthusiastic prospect is a coincidence.
• Validating once. Product-market fit is not permanent, and markets move faster than they used to.

What this is worth

Roughly 45% of SaaS failures occur between months 18 and 24 after launch — the point at which founders who built first discover what validation would have told them in month one.

Four weeks and a modest budget against twelve to eighteen months and a six-figure build. That is the entire argument, and it does not require believing anything about methodology.

We will happily scope and build a product for you. We would rather do it after this process than before it, because a build with a validated buyer behind it is a project that succeeds — and one without is a project that becomes a difficult conversation in month fourteen.