Startup validation guides

Where to start

If you have an idea but have not spoken to anyone about it yet, begin with the complete validation guide. It covers the full sequence — confirming the problem is real, testing whether people will pay, and gathering the evidence that makes a go or no-go decision defensible.

If you already know the problem is real and need to test demand before building, the landing page validation guide is the fastest route. If you are building software specifically, the SaaS validation framework adds the checks that matter for that model: category saturation, churn assumptions, and defensibility against a competitor who copies your feature set.

Why most validation fails

The recurring mistake is gathering encouragement rather than evidence. Survey responses, enthusiastic replies and waitlist signups all cost the respondent nothing, which is exactly why they correlate so poorly with revenue. Every guide here pushes toward signals that cost something — money, a pre-order, a scheduled meeting, a changed workflow.

The second mistake is sequencing. Validating that a problem exists says nothing about whether your solution is wanted, and neither says anything about whether you can reach buyers repeatably. Each stage should be cheaper than the one it protects you from, which is the logic these guides are built around. For definitions of the terms used throughout, see the startup glossary.