How to Validate a SaaS Idea Before You Build Anything: The Founder’s Checklist
The most expensive mistake a SaaS founder can make is building a product nobody wants. Validation before build is how you find out whether your idea has commercial potential before spending $10,000-50,000 on development. The specific validation activities that produce reliable answers.
The Pre-Build Investment
The most common reason early-stage SaaS products fail is not a technology failure or an execution failure but a market failure — the product solves a problem that is not painful enough, not frequent enough, or not specific enough for people to pay to solve it. Validation before build is the process of finding this out with 40-60 hours of founder time and zero development cost, rather than finding it out after $15,000-50,000 in development investment and 3-6 months of founder time. The goal of validation is not to confirm that your idea is good; it is to either confirm that a real market exists for the specific product you are planning to build, or to find out fast enough that you can adjust before committing resources.
What to Do and in What Order
1. Define the specific target user with uncomfortable specificity
Not ‘small businesses’ but ‘operations managers at UK marketing agencies with 5-20 employees who currently use Google Sheets for client reporting.’ The more specific the target user definition, the more reliable the validation results.
2. Write down your problem hypothesis in one sentence
‘[Target user] struggles with [specific problem] because [specific cause], and this causes [specific negative consequence] approximately [frequency].’ Write this down before any interviews. You are testing whether this hypothesis is true, not going into interviews to confirm it.
3. Find 10 target users to interview
Not friends, not family, not people who will be politely supportive. Find 10 people who exactly match the target user definition: LinkedIn outreach, community posts, warm introductions.
4. Run problem interviews (not solution interviews)
Ask about the problem, not about your solution: ‘How do you currently handle client reporting? What is the most frustrating part of that process? When was the last time that frustration caused a real problem?’ Do not describe your product idea until after you have heard their unprompted description of the problem.
5. Count how many of the 10 described the problem without prompting
If 7 of 10 interviews produced unprompted descriptions of the problem you hypothesised, the problem is validated. If fewer than 5 described it without prompting, either the target user definition is wrong or the problem hypothesis is wrong.
6. Ask about current solutions and willingness to pay
‘Have you ever paid for a tool to solve this problem? How much? Would you pay $X/month for a tool that solved it?’ Do not accept ‘maybe’ as validation. ‘Yes, I would pay $X for a tool that did Y and Z’ is validation; ‘it sounds interesting’ is not.
7. Build a one-page landing page and drive 200 targeted visitors to it
Create a landing page (Carrd, $19/year; 30 minutes to build) describing the product in outcome terms with an email sign-up. Drive 200 targeted visitors via LinkedIn posts, community sharing, and direct outreach. Measure the email capture rate: above 8% for cold traffic is a strong signal.
8. Offer a paid pre-sale or letter of intent to 5 interviewees
Approach the most enthusiastic interview participants: ‘We are building this product and I would love to offer you founding member access at [price] before we launch. Would you be willing to commit today?’ Three or more paid commitments from people found through cold outreach is the strongest pre-build validation signal available.
9. Check that no existing product already solves the problem perfectly
Search for existing solutions. If 3-4 well-funded, well-reviewed SaaS products already solve the specific problem at a similar price point, ask specifically: why will your product win users from well-established competitors?
10. Validate the price with 3 paid commitments or clear data
The only price validation that counts is a person’s willingness to commit money. Three paid commitments at the planned price point confirm that the market will pay the price.
11. Define the minimum viable product scope
After validation, define the smallest version of the product that delivers the core value validated in the interviews. SA’s Discovery Sprint is the structured process that converts interview insights into a buildable MVP specification.
12. Go/no-go decision
Apply the go/no-go criteria: 7 of 10 interviews validated the problem; at least 3 expressed willingness to pay at the planned price; the landing page converted above 5%; at least 1-3 paid commitments received. If all four criteria are met, commission the build.
🔗 Related reading on sasolutionspk.com
What Is a Discovery Sprint? The Smart First Step Before Building Your App
The structured process that converts a validated idea into a buildable product specification — the bridge between validation and build.
Bubble SaaS Product-Market Fit
How the validation activities in this checklist connect to the ongoing product-market fit measurement process.
Q: How long does validation take?
4-6 weeks is SA’s recommended validation timeline: 1-2 weeks to find and schedule 10 interviews; 2 weeks to run the interviews and collect the results; 1-2 weeks to build the landing page, drive traffic, and interpret the results. Founders who rush validation to get to the build phase faster consistently produce products that require significant rework or pivoting after launch.
Q: What if the interviews are positive but I cannot get paid commitments?
Positive interviews without paid commitments are weak validation. The two most common reasons: the problem is real but not painful enough to pay to solve at the planned price; or the target user believes the problem is worth solving but does not yet trust the founder to deliver a solution. Do not commission a build on interview enthusiasm alone.
Q: Should I do validation myself or hire SA to help?
Validation is the founder’s responsibility, not SA’s. The insights from validation interviews are the most valuable product intelligence a founder has and cannot be delegated without significant loss of nuance. SA’s role begins at the Discovery Sprint, after validation has confirmed a real opportunity.
Ready to Build Your MVP?
SA Solutions builds MVPs in weeks using Bubble.io. Start with a free audit or scope your build in 48 hours with a Discovery Sprint.
