Validation guides / SaaS
How to validate a SaaS idea before you build it
The worst way to learn if a SaaS idea will sell is to build it first. Here's how to get real proof of demand in an afternoon — measuring buy-intent, not vanity views — so you only build the ideas people actually want.
The 4-step fake-door test
- 1
Write the promise, not the product
Turn a SaaS idea into a single landing page: a headline, a subtitle, and a “buy” button. No app, no code — just the promise you'd make to a customer.
- 2
Put it in front of the right people
Share the link where this audience already is — r/SaaS, Indie Hackers, and SaaS-heavy X (Twitter). A sharp post or a small ad sends enough traffic to read a signal.
- 3
Measure intent, not curiosity
Track who leaves an email and, crucially, who clicks buy. The buy-click is the honest signal: someone clicking a plan/pricing button — for SaaS, price-tier intent beats a bare email every time.
- 4
Read the rate, then decide
Judge by rate (intent ÷ views), never raw clicks. A big channel inflates volume; the rate tells you if the idea itself has pull.
Why rate beats raw clicks
An idea with 2,000 views and 100 emails (5%) looks like it's winning over one with 80 views and 40 emails (50%) — but the second is 10× more promising. Volume rewards your biggest distribution channel, not your best idea. For a SaaS idea, always compare on rate.
What a good result looks like for saas
220
views
13%
email conv.
11%
buy-intent
A B2B SaaS with an 11% buy-intent rate on 220 targeted visitors is a strong go signal — SaaS converts on pain, not volume.
Common mistakes validating saas ideas
- ✕Confusing “this would be useful” replies with actual demand — nobody commits until money (or a click that stands in for it) is on the line.
- ✕Validating with other founders instead of the people who’d pay. Builders love tools; that’s not your market.
- ✕Shipping the whole app to “see if it sticks” instead of testing the promise with one page first.
Example ideas to test
Spin up a test page for each of these in minutes and let the rate pick the winner:
Stop guessing. Start knowing.
Get real proof for a SaaS idea before it costs you a weekend.
Questions about validating saas ideas
How many visitors do I need to validate a SaaS idea?
ProofBench measures a rate, not raw traffic, so even 50-100 targeted visitors give a real read. In the worked example above, 220 visitors were plenty to trust the 11% buy-intent rate.
What's the strongest signal that a SaaS idea will work?
Not an email — someone clicking a plan/pricing button — for SaaS, price-tier intent beats a bare email every time. A fake-door "buy" click is far closer to money than a signup.
Where do I send my first visitors?
For this category, r/SaaS, Indie Hackers, and SaaS-heavy X (Twitter). A single sharp post or a small ad is enough to start collecting signal.
Do I need to build anything to test a SaaS idea?
No. You create a test page in minutes — a headline, a subtitle, and a "buy" button — and measure who signs up and who clicks. You only build the product once the demand is proven.