How to Validate a SaaS Idea Without Building Anything

The most expensive way to learn how to validate a SaaS idea is to build the product first and hope people show up. This guide walks through the opposite approach: proving demand exists before you write a single line of application code.

The fake-door test

A fake-door test is a landing page for a product that doesn't exist yet. It states the problem, states the solution, and asks for an email or a small payment — and that's it. If nobody clicks through, you've learned something valuable for the cost of an afternoon, not a quarter of development time.

• One page, one offer. No pricing tiers, no feature comparison — just the problem statement and a single call to action.
• Drive traffic from where the complaint lives. Post the link in the same community where you found the original pain point, not a cold audience.
• Measure click-through, not just page views. A visitor who reads the page and leaves without acting is a weaker signal than one who clicks "join the waitlist."

In summary, the key metric for how to validate a SaaS idea without building it is conversion on a real call to action, not traffic volume — a landing page that gets a thousand visitors and zero signups has told you the offer doesn't land, no matter how much attention it got.

The waitlist-with-a-deposit test

A plain email waitlist measures curiosity. Adding a small refundable deposit — even five or ten dollars — filters for people who are actually willing to pay, not just people who thought your headline was interesting. The drop-off between "gave an email" and "put down a deposit" is one of the most honest numbers you'll get before building anything.

The concierge MVP

Instead of building software, deliver the outcome manually for a handful of early customers — spreadsheets, manual emails, a human doing the work behind the scenes. It doesn't scale, and it isn't supposed to. It exists to answer one question: does anyone actually want the outcome enough to pay for it, before you spend months automating the delivery?

1. Find 3–5 people with the exact pain point. Ideally people who already complained about it publicly.
2. Offer to solve it manually, for a fee. Be upfront that it's a manual process for now — most people don't care how the sausage gets made if the outcome is right.
3. Only automate the parts that get repetitive. Let the manual process show you exactly which steps are worth turning into software first.

The main takeaway from analyzing indie trends is that a concierge MVP answers the willingness-to-pay question faster than any survey — someone handing over real money for a manually delivered outcome is a stronger signal than any amount of positive feedback on an idea.

Your next step

Pick whichever test matches how much friction you can tolerate: a fake-door landing page if you want the fastest possible signal, a deposit waitlist if you want to filter for real intent, or a concierge MVP if you want the strongest proof available before writing any code.