Guide

How do I validate my SaaS idea before building it?

Define the problem and a narrow target customer, interview 15–30 potential users, study competitors and search demand, then publish a landing page with a real call to action. Finally, ask for money — pre-orders, deposits, or signed letters of intent. Build only when strangers show willingness to pay, not just polite interest.

Why validate before building?

Direct answer: because the single most common reason startups die is building something nobody needs. CB Insights' analysis of startup post-mortems found “no market need” cited in roughly 35% of failures — ahead of running out of cash, team problems, or being outcompeted. Validation is how you avoid joining that statistic.

The economics are simple. A few weeks of interviews and a landing page cost almost nothing. Building the wrong product costs months of your life and, if you outsource development, tens of thousands of dollars. Eric Ries' Lean Startup methodology frames every product idea as a set of untested hypotheses: the job of validation is to test the riskiest one — usually “does anyone care about this problem enough to pay?” — with the cheapest possible experiment.

Validation is not about proving your idea is good. It's about trying hard to disprove it and failing. If your idea survives honest attempts to kill it, you can build with confidence.

7 steps to validate a SaaS idea

Direct answer: move from a written hypothesis, to conversations, to demand tests, to money — in that order. Each step is cheap enough that a “no” costs you days, not months.

1. Write a one-sentence problem hypothesis. “[Specific person] struggles with [specific problem] and currently solves it by [workaround].” If you can't name the current workaround, you haven't found a real problem yet.
2. Define a narrow target customer. Not “small businesses” — something like “solo bookkeepers with 10–40 clients who still send invoices from Excel.” Narrow segments give consistent interview signals; broad ones give noise.
3. Run 15–30 problem interviews. Follow the principles in Rob Fitzpatrick's The Mom Test: talk about their life, not your idea; ask about past behavior (“when did this last happen? what did it cost you?”), never hypotheticals; and treat compliments as noise.
4. Study competitors and search demand. Existing competitors are a good sign — they prove people pay for this. Check search volume with a keyword tool, read competitor reviews on G2 and Capterra, and mine the one-star reviews for unmet needs you could own.
5. Publish a landing page with a real call to action. One page: the problem, your promised outcome, pricing, and a concrete CTA — “join the waitlist” at minimum, “pre-order at 50% off” if you're serious. Measure visitor-to-signup conversion.
6. Drive a small batch of targeted traffic. A few hundred dollars of ads, or posts in the communities where your segment already hangs out (subreddits, Slack groups, LinkedIn). You need strangers, not friends — friends convert out of loyalty, which teaches you nothing.
7. Ask for money. Pre-orders, refundable deposits, or signed letters of intent for B2B. Willingness to pay is the only validation signal that reliably predicts a business. Everything before this step is a filter; this step is the test.

How many customer interviews do you need?

Direct answer: plan for 15–30 interviews inside one narrow segment. In practice, patterns stabilize after 15–20 conversations — you start hearing the same pains, the same workarounds, the same words. If you're at 30 interviews and the answers still contradict each other, the problem usually isn't the sample size; it's that your segment is too broad. Split it and restart.

Quality matters more than quantity. Five interviews where you dig into what someone actually did last month beat twenty where people politely agree your idea sounds nice. Keep a simple scorecard per interview: Did they describe the problem unprompted? Do they have a workaround today? Have they spent money or meaningful time on it? Three yes answers is a strong conversation.

Signs your idea is validated (and red flags)

Direct answer: validation looks like commitment — money, time, or reputation put on the line. Anything that costs the other person nothing (compliments, “I'd definitely use that”) is noise.

When is an MVP itself the validation tool?

Direct answer: when the remaining risk is behavioral, not conceptual. Interviews and landing pages tell you the problem exists and people say they'll pay. They can't tell you whether users will actually change their workflow, return every week, or keep paying after month one. At that point the cheapest honest experiment is a small, working product in real hands.

The key word is small. In Lean Startup terms, an MVP is the fastest way through one build–measure–learn loop — not a discount version of your five-year vision. Cut scope to the single workflow that delivers the core promise, instrument it, charge for it, and set a decision date. If a first version takes six months, it isn't a minimum viable product; it's a bet.

This is where speed becomes strategy. At ZeusInLabs we build validated ideas into launched MVPs in 21 days, precisely because a validation experiment loses value the longer it takes to run. If you've done the steps above and the signals are green, the next move is getting a real product in front of real users as fast as responsibly possible — see our guide on how long it takes to build a SaaS MVP and what MVP development costs. If you're weighing who should build it, we compare the options in agency vs. freelancer vs. in-house.