How to Validate a SaaS Idea Before You Build Anything
The most common mistake first-time SaaS founders make is building before validating. They spend weeks or months coding a product, launch it, and hear silence. The problem was never technical — it was that nobody wanted what they built, or at least not enough to pay for it.
Validation is the process of testing whether real people have a real problem they'd pay real money to solve. It happens before code. Before design. Before naming your LLC. Here's how to do it systematically.
The 5 Validation Signals That Matter
Not all validation is equal. A friend saying 'cool idea' is not validation. Here are the five signals that actually predict whether your SaaS will work.
- Problem frequency: People experience this problem regularly (weekly or daily), not once a year.
- Current spending: People are already paying for a workaround — even if it's cobbled together from spreadsheets, freelancers, or competing tools.
- Urgency: The problem is painful enough that people would try a new solution this week, not 'someday.'
- Reachability: You can identify and contact these people through specific channels (communities, job titles, industries).
- Willingness to pay: At least some prospects would pay before the product exists — via pre-order, letter of intent, or deposit.
Step 1: Define the Problem in One Sentence
Write a single sentence that describes the problem you're solving, who has it, and why current solutions fall short. This forces clarity.
Example: 'Solo SaaS founders struggle with validating their ideas before building because existing frameworks are too academic, which costs them months of wasted development time.'
Step 2: Find 10 People Who Have This Problem
You need to talk to real humans who experience the problem you're solving. Not your friends. Not your family. People who match your target audience and have no social obligation to be nice to you.
Where to find them
- Reddit & forums: Search for posts describing the problem. People complaining = demand signal.
- LinkedIn: Find people with the job title that matches your target user. Send a short, respectful DM.
- Communities: Indie Hackers, Twitter/X builder communities, Discord servers for your niche.
- Competitor reviews: Read 1-star and 3-star reviews of competing products. These reveal unmet needs.
Step 3: Run Problem Interviews (Not Solution Pitches)
The goal of early conversations is to understand the problem, not pitch your solution. If you lead with your idea, people will be polite and say it sounds great. That's not validation — that's social courtesy.
Questions that reveal truth
- Tell me about the last time you dealt with [problem]. What happened?
- What do you currently use to solve this? How much does it cost?
- What's the most frustrating part of your current approach?
- If this problem disappeared tomorrow, what would change for you?
- Have you tried other solutions? Why did they fall short?
Step 4: Test Willingness to Pay
The strongest validation signal is money. Before you build anything, test whether people would pay. There are several ways to do this without a product.
- Landing page + waitlist: Build a simple page describing the value proposition. Track signups. If you can get 100+ signups with basic promotion, demand exists.
- Pre-sale page: Offer early access at a discount. Even 5 purchases proves willingness to pay.
- Manual delivery: Offer the service manually before automating it. If people pay you to do it by hand, they'll pay for software that does it automatically.
- Letter of intent: For B2B, ask prospects to sign a non-binding letter saying they'd pay $X/month for a solution that does Y.
Step 5: Analyze and Decide
After 10+ conversations and a landing page test, you have data. Not opinions — data. Use it to make a clear go/no-go decision.
Go signals
- Multiple people described the same problem unprompted
- They're currently paying for workarounds
- Your landing page converted at 5%+ to waitlist or 1%+ to pre-sale
- At least 2-3 people asked 'When can I use this?'
No-go signals
- People acknowledge the problem but don't care enough to try a new solution
- Everyone's 'solution' is free and good enough
- Your landing page got traffic but zero signups
- Nobody can articulate the pain clearly
Common Validation Mistakes to Avoid
- Asking friends and family: They'll say they love it. They're being kind, not honest.
- Building a survey instead of talking to people: Surveys give you data. Conversations give you insight. Start with conversations.
- Validating the solution instead of the problem: Don't ask 'Would you use an app that does X?' Ask 'How do you currently handle X?'
- Treating a waitlist as proof: A waitlist shows interest, not commitment. Test with money when possible.
- Giving up after 3 conversations: 10 is the minimum. Patterns emerge around conversation 7-8.
Frequently Asked Questions
How long should SaaS validation take?
1-2 weeks if you're focused. You need 10+ problem interviews, a landing page, and basic traffic. Don't let validation become a reason to not build.
What if my idea is too new for people to understand?
Validate the problem, not the solution. Even if your solution is novel, the underlying problem must already exist. If people don't recognize the problem, your idea may be too early.
Can I validate a SaaS idea without a landing page?
Yes. Conversations alone can validate demand. But a landing page with a waitlist adds quantitative data to your qualitative insights. Together they're much stronger.
How many pre-sales do I need to validate?
There's no magic number, but 5-10 pre-sales from strangers (not friends) is a strong signal for a solo founder. The point isn't the revenue — it's proof that someone will pay.