How to Validate Your SaaS Idea Before Writing a Single Line of Code

Why Validation Is the Most Valuable Week You Will Spend

Building the wrong product is the most expensive mistake in software. A working codebase nobody wants is worth nothing, and you only learn that after months of work and tens of thousands of dollars. A couple of weeks of validation costs almost nothing by comparison and can save the whole budget. If you take one idea from this article, it is to find out whether people will pay before you build.

The 5-Step Validation Playbook

Define the problem clearly. Write who has it, what it costs them, and how they cope today.
Find ten people who have this problem.
Talk to them, and listen more than you pitch.
Build a simple landing page describing the solution.
Ask for a commitment: a waitlist signup, a pilot agreement, or a pre-payment.

How to Find Your First 10 Potential Customers

LinkedIn: search for the job title that has the problem and send short, specific messages.
Communities: Reddit, Slack groups and forums where your customers already ask for help.
Your network: ask for introductions, even to people two steps away.

A message that works: "I am researching how [role] handle [problem]. I am not selling anything. Could I ask you three questions for fifteen minutes?" Be honest and be brief.

How to Run a Customer Discovery Interview

Use the approach from the book The Mom Test: ask about their life and past behavior, not your idea. Good questions are "How do you handle this today?", "What was the last time it went wrong?", and "What have you tried to fix it?" Bad questions are "Would you use this?" because people are polite and will say yes. Listen for how often the problem happens, how much it hurts, and whether they have already spent time or money on it.

Building a Validation Landing Page in a Day

You can use Framer, Webflow, or even a simple Notion page. Include a headline that states the outcome, three short benefits, and one clear button, such as "Join the waitlist." Send real people to it, and measure how many take the action. Ten signups from a small targeted group is a stronger signal than a thousand visits.

The Signals That Mean You Should Build

People share your page or introduce you to others without being asked.
They offer to pay, pre-pay, or commit to a pilot.
They book follow-up calls themselves.
They describe the problem with specific, recent stories.

The Signals That Mean You Should Pivot

Polite interest but no action.
Vague descriptions of the problem, with no recent examples.
No urgency: "sounds great, maybe someday."
Everyone says they would use it, but nobody will pay.

Pivoting at this stage costs a few conversations. It is the cheapest time to be wrong.

From Validation to MVP Scope

Turn your interview notes into a one-page spec: who the user is, the single problem that hurt the most, and the one feature that solves it. That feature and the steps to reach it are your MVP. Continue with how much an MVP costs and how long it takes.

Ready to Validate and Build?

I help startups in the US and Europe plan and build SaaS products. Book a free 30-minute call, or read more about SaaS MVP development.