The most expensive mistake in building a SaaS product isn't a bad architecture decision or the wrong tech stack. It's spending months building something nobody actually wanted, discovered only after the thing is finished and launched to silence. Validation exists to catch that before it costs months instead of days.
Why Most Validation Advice Is Too Vague to Act On
"Talk to your customers" is technically correct and almost useless as actual guidance, since it doesn't say what to ask, who to ask, or what answer should actually change your plans. Real validation means gathering specific, honest signals that would genuinely change whether you build something, not just confirming what you already hoped to hear.
Start With a Problem, Not a Feature List
A SaaS idea framed as a list of features to build is already starting in the wrong place. A SaaS idea framed as a specific, painful problem a specific group of people already has, and are already spending time or money trying to solve badly, is a far stronger starting point. If you can't state the problem in one sentence without mentioning your own solution, that's worth revisiting before anything else.
Talk to People Who Have the Problem, Not People Who Like You
This sounds obvious and gets violated constantly. Friends, family, and people who generally support your ventures tend to respond encouragingly regardless of whether the idea is actually good, since the social cost of discouraging you feels higher than the cost of being politely vague.
What actually works: finding people who are strangers to you but not strangers to the problem. Communities, forums, and existing customers of an adjacent tool, people with no personal stake in being nice to you specifically, tend to give far more honest, useful signal.
Ask About Their Current Behavior, Not Their Hypothetical Interest
"Would you use a tool that does X" gets a yes from almost everyone, since agreeing costs nothing and imagining a hypothetical future is easy. The more reliable question is about what they're already doing right now.
What actually works: asking how they currently solve this problem, what they're using instead, and how much time or money that current (often bad) solution costs them. Someone already cobbling together a messy spreadsheet-and-email workaround for a real problem is a far stronger signal than someone politely agreeing your idea sounds cool.
Look for a Willingness to Pay, Not Just Enthusiasm
Enthusiasm is cheap. A genuine willingness to actually pay, even a small amount, before the product exists is a much stronger signal, since it requires the person to put something real at stake rather than just offering a compliment.
What actually works: a landing page describing the product clearly, with a real way to express commitment, joining a waitlist with payment information collected upfront, or a genuine pre-order, rather than just an email capture form that costs the visitor nothing to fill out.
Build the Smallest Possible Version of the Core Value
Before building the full product, the smallest version that delivers the actual core value, even manually behind the scenes, tests whether the value itself is real before investing in the infrastructure around it. A queue management tool might start as a shared spreadsheet with a simple form in front of it, testing whether people actually want the underlying workflow improved before any code gets written for a real dashboard.
What actually works: doing manually, or with the simplest possible tool, what your eventual product would automate. If people still find enough value in the manual, clunky version to keep using it, that's a strong signal the automated version is worth building. If they abandon even the simple version quickly, that's worth knowing before a real build starts, not after.
Signals Worth Trusting
People asking when it will be ready, unprompted, without you pushing for a timeline. People willing to pay something before it exists. People already spending real time or money on a worse alternative. Specific, detailed complaints about the current options, rather than vague dissatisfaction.
Signals That Quietly Mislead You
Polite interest with no follow-through. Someone saying "that sounds great" and never responding to a follow-up message is a much weaker signal than their initial enthusiasm suggested. Positive feedback from people who wouldn't actually be the paying customer. Feedback from someone who isn't the actual buyer, a friend, a colleague in an unrelated field, feels validating but doesn't reflect the market you're actually building for. A large total addressable market with no specific, findable first customer. A genuinely huge potential market with nobody specific willing to be customer number one is often a sign the idea is too broad and unfocused, not a sign of a big opportunity.
What Validation Actually Buys You
Not certainty, certainty doesn't exist at this stage regardless of how much validation happens. What real validation buys is a meaningfully reduced risk of spending months building something for an audience that was never actually there, replaced with early evidence that a specific group of people has a real problem, is unhappy with their current options, and would genuinely pay for something better.
Frequently Asked Questions
How many people should I talk to before starting to build? There's no universal number, but a common rough benchmark is somewhere around ten to twenty genuine conversations with people who actually have the problem, enough to start seeing real patterns rather than drawing conclusions from one or two data points that might just be noise.
Is a landing page enough validation, or do I need a working prototype? A landing page with a real commitment mechanism, a waitlist, a pre-order, is often sufficient for early validation, since the goal is testing demand for the underlying value, not proving the full product works yet. A working prototype becomes more valuable once initial demand signals are already positive and you're validating the specific execution, not just the core idea.
What if people say they love the idea but nobody actually signs up or pays? This is one of the clearest and most common signals that the idea needs rethinking, not more marketing. A gap between verbal enthusiasm and actual commitment usually means the problem wasn't painful enough to act on, or the specific audience being reached isn't the group that actually feels the pain most acutely.
If you're validating a SaaS idea and want a technical perspective on what a lean first version could actually look like, I help founders scope and build early-stage SaaS products.
Get in touch: https://pixelanas.com/contact
Anas, full-stack Next.js developer building SaaS products and premium templates. X: @ASheikh69751