To validate a SaaS idea before development, collect evidence that a specific group of people has the problem, cares enough to change their behaviour, and will pay. Practical methods include customer interviews, a landing page with a clear call to action, a clickable prototype test, a manual “concierge” version of the service, pre-sales or letters of intent, and a small paid pilot. Commitments such as time, money or data are stronger signals than compliments.
Validation does not prove an idea will succeed. It reduces the risk of building something nobody wants — which remains the most common reason new products fail.
What you are actually trying to learn
- Problem: do people in a specific segment have this problem, frequently and painfully?
- Current solution: what do they do about it today, and what does it cost them?
- Your solution: does your approach make sense to them?
- Willingness to pay: will they commit money, time or data?
Seven validation methods
1. Problem interviews
Talk to 10–15 people in your target segment about how they handle the problem today. Ask about past behaviour, not hypothetical future behaviour: “Tell me about the last time…” is better than “Would you use…”.
2. A landing page test
Describe the outcome your product delivers, add a clear call to action — join a waitlist, book a demo, pre-order — and send targeted traffic to it. The conversion rate from relevant visitors tells you more than social media likes.
3. A clickable prototype test
A clickable prototype lets people experience the product. Watch five to eight target users try to complete a task, then ask what they would pay and what they would stop using if they switched.
4. A concierge MVP
Deliver the outcome manually for a handful of customers — using spreadsheets, email and your own time. If customers value the outcome when a human provides it, software can make it scalable.
5. Pre-sales and letters of intent
For B2B products, ask prospects to commit: a discounted annual pre-payment, a paid pilot, or a letter of intent. Hesitation at this stage is valuable information.
6. Competitor analysis
Competitors are often a good sign — they show people pay to solve the problem. Read their reviews to find what users dislike, and look for underserved segments.
7. A paid pilot with a working prototype
A working prototype used by one or two real customers for a few weeks reveals whether the product fits into their actual workflow.
Reading the signals
| Weak signal | Strong signal |
|---|---|
| “That’s a great idea!” | “When can I start using it?” |
| Likes and shares | Waitlist sign-ups from your target segment |
| “I would probably pay for that” | A pre-payment, deposit or signed pilot |
| Interest from friends and family | Referrals from people you have never met |
Common validation mistakes
- Asking leading questions that invite polite agreement;
- testing with people outside the target segment;
- treating one enthusiastic prospect as market demand;
- skipping the willingness-to-pay question because it feels awkward.
When to move from validation to building
Move to an MVP when you can describe your target customer precisely, you have heard the same problem described consistently, and at least some prospects have made a meaningful commitment. Then build the smallest product that serves those people — see what to include in your first SaaS MVP.
Frequently asked questions
How many interviews are enough?
Continue until you stop hearing new things — often 10–15 conversations within a well-defined segment.
Is validation possible without a product?
Yes. Interviews, landing pages, concierge services and pre-sales all work before any software exists.
How much should validation cost?
Often little more than your time. A clickable prototype or discovery workshop is a modest additional investment that makes validation more concrete.
