Most SaaS products fail not because of bad code, but because nobody wanted them. The fix is simple in theory — validate demand before building — but most founders skip this step because it feels slower than just shipping.
Here's a practical framework for validating a SaaS idea in under a week, with zero code.
Step 1: Check If People Are Already Talking About It
Before you build anything, search for your idea in the places developers and founders hang out:
- Hacker News — Search for your problem keywords. Look for "Ask HN" and "Show HN" posts. If people are asking for solutions, there's demand.
- Reddit — Check r/SaaS, r/microsaas, r/indiehackers, r/SideProject. Look for complaints, feature requests, and "I wish there was a tool for X" posts.
- GitHub — Search for related repos. If open-source alternatives exist but have many open issues, there's a gap.
Or skip the manual search and browse our directory of 1,700+ ideas already extracted from these sources.
- Multiple people describing the same problem independently
- Existing solutions with vocal complaints
- "I'd pay for this" comments (even casually)
Red flag: If zero people are discussing the problem, you're either too early or too niche. Proceed with caution.
Step 2: Size the Audience
A great problem with 50 potential customers isn't a SaaS business. You need to estimate:
- How many people have this problem? Search job titles, company sizes, industry verticals.
- How often do they have it? Daily problems justify subscriptions. Yearly problems don't.
- What do they currently pay to solve it? If the answer is "nothing," you need to understand why.
Quick sizing hack: Search LinkedIn for the job title most likely to buy your tool. If there are 50,000+ people with that title, you have a market. If there are 500, you need a very high price point.
Step 3: Find 5 People Who Have the Problem
Don't ask "would you use this?" — that question always gets a yes. Instead:
- Find people who posted about the problem on Reddit, HN, or Twitter
- DM them with: "I saw your post about [problem]. I'm exploring building a tool for this. Could I ask you 3 quick questions about how you currently handle it?"
- Ask about their current workflow, not your idea
The questions that matter: 1. How do you solve this today? (Current behavior reveals real pain) 2. What's the most frustrating part? (Specificity = real pain) 3. How much time/money does it cost you? (Willingness to pay)
If 4 out of 5 describe the same painful workflow, you have a validated problem. If answers are scattered, the problem isn't focused enough.
Step 4: Pre-Sell Before You Build
The strongest validation signal is someone paying you before the product exists.
- Landing page + waitlist: Build a one-page site describing the solution. Use a clear CTA: "Join the waitlist" or "Get early access for $X/month." Track conversion rate.
- Paid pilot: Offer to solve the problem manually for 3-5 customers at a discount. If they'll pay you to do it by hand, they'll pay for software that does it automatically.
- Lifetime deal pre-sale: Offer a discounted lifetime plan to early believers. If 20 people pay $50 each, you have $1,000 and 20 committed beta testers.
Benchmark: A landing page with 5%+ email signup rate from cold traffic suggests real interest. Below 2% means your positioning needs work.
Step 5: Define Your MVP Scope
Validation isn't about building everything. It's about finding the smallest thing you can ship that solves the core problem.
- One user type. Not "teams and individuals." Pick one.
- One workflow. Not "project management." Pick "task assignment for 2-person teams."
- One pricing tier. Don't build a free tier yet. Charge from day one.
- Two-week build target. If it takes longer, you're building too much.
The Validation Checklist
Before writing code, you should have:
- [ ] 10+ independent mentions of the problem online
- [ ] 5 conversations with people who have the problem
- [ ] 3+ people describing the same core workflow pain
- [ ] A landing page with measurable interest (emails, pre-orders)
- [ ] A defined MVP scope you can build in 2 weeks
If you can check all five, build it. If you can't, keep validating.
Find Your Next Idea
Not sure what to build? We track the most-discussed SaaS opportunities across Hacker News, Reddit, and GitHub — updated daily.