The SaaS Idea Validation Playbook: A Step by Step Guide for Founders
How to validate a SaaS idea before you build it: seven steps from the problem to the first payment, what counts as real evidence, and when to go ahead, change or stop.
By Suren, Founder & Growth Strategist at Gufy · Published · Last updated
To validate a SaaS idea, find out whether a specific group of people will pay to have a problem solved, before you build the product. An idea is validated when strangers commit money or time. It is not validated when people tell you it is a good idea.
This playbook covers seven steps, what counts as real evidence at each one, and how to decide whether to go ahead, change direction or stop.
What counts as evidence
Most founders collect the weak kind and treat it as the strong kind.
| Weak evidence | Strong evidence |
|---|---|
| Friends and colleagues like it | Strangers describe the problem without being prompted |
| "I would use that" | "Can I have it now?" |
| Survey answers | A payment, a pre-order or a signed commitment |
| Email sign-ups | People who turn up for a call or a pilot |
| "Let me know when it is live" | Someone introducing you to a colleague with the same problem |
| No competitors | People already paying for an imperfect alternative |
Step 1: Start with a problem, not a product
The ideas that work solve something painful, frequent and costly. Good sources:
- A problem you have lived with yourself
- Something you know from inside an industry that outsiders miss
- A job people already do badly with spreadsheets, email or manual effort
Write the problem down in one sentence without mentioning your solution. If you cannot, the idea is still a feature looking for a use.
Step 2: Choose one specific customer
You cannot test an idea on "businesses". Choose a group narrow enough that you could list twenty of them: a role, in a type of company, with this problem.
Check whether the person who would use the product is the person who would pay for it. In B2B they are often different, and you need to hear from both, because each has a different job to be done. If several groups could use the product, score them and pick one before you start interviewing.
Step 3: Check how they solve it today
Look at what your chosen customers use now. Read reviews of existing tools, especially the complaints.
Competition is good news. It shows people already spend money on the problem. An empty market is a warning, because it often means the problem is not worth paying to solve. What you need is a clear reason someone would switch.
Step 4: Talk to five people who do not know you
This is the step founders avoid, and it matters most.
A plan built on three conversations with people who like you is built on a biased sample. Contact potential customers with no connection to you, by direct message or email, and ask for twenty minutes.
On the call, do not pitch. Ask:
- How do you handle this today?
- When did it last come up, and what happened?
- What have you tried, and why did it not work?
- What does it cost you in time or money?
- Who else is involved in deciding what to buy?
Five conversations are enough to hear whether the same problem comes up in the same words. If the answers are scattered, your customer group is too wide.
Step 5: Describe the solution and make an offer
Now put the solution in front of people, without building it.
- A landing page that states who it is for, the outcome, and one action to take
- A clickable prototype or mock-up that shows how it would work
- A manual version, where you deliver the result by hand behind a simple form
Describe the outcome, not the features. Then send the people you interviewed, and others like them, to it.
Step 6: Ask for a commitment
A survey can confirm a problem exists. It cannot tell you whether anyone will pay.
Ask for something that costs the customer money or effort:
- A paid pilot
- A pre-order or deposit
- A signed letter of intent
- A scheduled onboarding session
How people react to a real price tells you more than any answer to "how much would you pay?" Willingness to Pay sets out the tests from weakest to strongest.
Do the arithmetic at this point too. Estimate what a customer is worth over the time they stay, and what it is likely to cost to win one. If winning a customer costs more than they are worth, the idea needs a different price, a different customer or a cheaper way to reach them.
Step 7: Build the smallest version that delivers the outcome
Only now build, and only the part that delivers the outcome your first customers committed to. Leave out everything else.
Then watch what people do, not what they say:
- Do they reach the first useful moment (the aha moment)?
- Do they come back without being reminded?
- Do they pay again?
What Is a Minimum Viable Product? covers how small that first version can be.
Go ahead, change or stop
| What you see | What to do |
|---|---|
| Strangers pay or commit, and the same problem comes up in the same words | Go ahead. Build the smallest version for that group. |
| The problem is real but people will not pay your price | Change the price, the customer or the scope, and test again. |
| Interest is polite and nobody commits | Change the problem or the customer. Do not build. |
| Every conversation describes a different problem | Narrow the customer group and repeat step 4. |
| Nobody will take the call | The problem may not matter enough. Consider stopping. |
Stopping early is a good result. It costs you weeks, not a year.
Common mistakes
- Building first and looking for customers afterwards
- Relying on friends and family for feedback
- Treating interest as commitment
- Hearing "let me know when it is live" as a yes
- Building far more than the first customers asked for
- Leaving price until after launch
After validation
Validation is the first step towards product-market fit, which is measured by whether customers stay and pay, not by whether they say they are interested.
Validation does not finish at launch. Each new feature, customer group, price and channel is another assumption to test in the same way.
When you are ready to plan the launch, see SaaS Go-to-Market Strategy. If you are still choosing between ideas, 25 Micro SaaS Ideas and Niche SaaS Ideas are starting points.
Common questions
How do you validate a SaaS idea?
Choose one specific customer, talk to at least five of them who do not know you, check how they solve the problem today, describe your solution on a simple page, and ask for a commitment such as a paid pilot or pre-order. An idea is validated when strangers pay or commit, not when people say they like it.
How long does it take to validate a SaaS idea?
A few weeks if you keep it simple: a week or two of customer conversations, a week to put up a page and an offer, and two or three weeks to see who commits. Building a full product to find out the same thing can take months.
How many customer interviews do you need to validate an idea?
Start with five people who do not know you. That is enough to hear whether the same problem comes up in the same words. If the answers are scattered, narrow the customer group and do five more.
Do you need to build an MVP to validate a SaaS idea?
No. Building is one of the more expensive ways to test an idea. A landing page with a real offer, a clickable prototype, or a manual service delivered by hand can show whether people will pay before any code is written.
Where Gufy fits
Gufy runs growth workshops and audience research for founders who want to test demand before they build or launch. The MyGigsters case study shows that work for an app before its market release.