SaaS validation should begin before the MVP
An MVP is a way to test particular product assumptions. It is not the starting point for every SaaS idea. If you do not yet know whose problem matters, how it is handled today or who controls the purchase, building software may simply make an untested assumption more expensive.
Before writing production code, you can investigate the customer, problem, workflow, consequences, alternatives, buying process, implementation constraints and access to the market. These questions often determine whether there is a commercially plausible SaaS opportunity at all.
Do not ask, “What is the smallest product we can build?” until you have asked, “What is the smallest credible test of the assumption that could stop us?”
Validation is not a request for approval
Positive feedback, email sign-ups and feature requests can be encouraging, but none is decisive without context. Stronger evidence connects the idea to actual behaviour: repeated problems, current spending or workarounds, a reason to change, a feasible buying route and a concrete next commitment.
Map the assumptions that can break a SaaS business
Customer
Can you define and reach a group with sufficiently similar needs, context and buying conditions?
Problem
Does the problem occur, matter and create consequences important enough to prompt action?
Alternative
What software, service, spreadsheet, manual process or inaction competes with the idea?
User and workflow
Where would the product fit, who would use it and what behaviour or data would need to change?
Buying process
Who owns the budget, defines requirements, approves security and signs the agreement?
Value and pricing
What measurable value could justify the price, switching cost and implementation effort?
Access
Can you reach prospects and create a repeatable path to sales at a viable cost?
Feasibility
Can the promise be delivered reliably within technical, legal, data and support constraints?
Rank assumptions by uncertainty and consequence. Test the ones that could invalidate the opportunity before polishing lower-risk features.
A step-by-step SaaS idea validation process
- Define the decision.Specify the development, funding or commercial commitment the evidence must inform.
- Choose a focused initial segment.A narrow test is easier to interpret than feedback from unrelated markets.
- Write falsifiable assumptions.State what must be true about the problem, buyer, workflow, value and access.
- Recruit relevant roles.Include users, buyers and technical or procurement stakeholders when their evidence differs.
- Run problem interviews first.Explore recent events, consequences, current alternatives and decisions before presenting the idea.
- Map the B2B purchase.Identify triggers, budget, criteria, blockers, integrations, security and approval stages.
- Test the smallest credible concept.Use a workflow sketch, prototype, concierge service or landing page matched to the question.
- Seek a proportionate commitment.Request time, data, access, a pilot, procurement review or payment when appropriate.
- Compare evidence against criteria.Separate recurring patterns, segment differences, contradictions and unresolved risks.
- Choose the next action.BUILD, CHANGE or KILL—and state the evidence required before the following investment.
Use the customer discovery interview guide to design the conversations and the B2B participant recruitment guide to reach the right people.
Match the validation method to the SaaS assumption
| Question | Useful test | Evidence to look for |
|---|---|---|
| Is the problem important? | Interviews and workflow observation | Recent examples, consequences, escalation and action |
| Is the segment coherent? | Compare interviews by role and company type | Recurring needs and buying conditions within the group |
| Would the solution fit? | Concept or prototype test | Comprehension, workflow fit, objections and required changes |
| Can it create value? | Concierge or manual pilot | Outcome achieved, implementation effort and repeat use |
| Will the organisation buy? | Concrete offer, paid pilot or procurement step | Budget access, approval progress and real commitment |
| Can prospects be reached? | Targeted outreach or landing-page experiment | Qualified response, meeting and conversion rates |
| Can users adopt it? | Prototype or limited product test | Task completion, continued use and switching barriers |
Evidence has levels
Earlier, weaker signals
- interest or praise;
- stated future intention;
- email sign-up;
- feature request;
- prototype preference.
Later, stronger signals
- time or data contributed;
- access to decision-makers;
- pilot participation;
- procurement progress;
- payment or signed commitment.
Weaker signals are not useless. They are appropriate for early questions, but they should not be presented as equivalent to purchase evidence. See how to test willingness to pay before you build.
Do not mistake a prototype for an MVP
A clickable prototype can test comprehension and workflow without production software. A concierge test can deliver the promised outcome manually. An MVP becomes appropriate when functioning software is required to test the next important uncertainty—such as repeated use, integration or technical performance.
Decide whether to BUILD, CHANGE or KILL the SaaS idea
BUILD
The focused segment shows a recurring important problem, a credible reason to change, a feasible buying route and sufficient commitment to justify the next bounded investment.
CHANGE
The evidence supports a need, but the customer, workflow, promise, pricing, sales route, implementation model or concept must change before development continues.
KILL
The intended market does not show enough problem importance, access, differentiation or commitment to justify the investment, and no credible adjustment resolves the weakness.
TEST AGAIN
A decisive assumption remains unresolved. Define the smallest next test and avoid expanding scope until its result is known.
The recommendation should name the evidence, limitations and next threshold. It is not a guarantee of commercial success; it is a disciplined way to reduce avoidable risk before more capital and time are committed.
Frequently asked questions
Questions about SaaS idea validation
How do you validate a SaaS idea before building an MVP?
Define the commercial decision and riskiest assumptions, interview relevant buyers and users about current behaviour, verify the problem and buying process, test the smallest credible concept, and seek a proportionate real commitment before expanding development.
Do you need an MVP to validate a SaaS idea?
No. You can investigate the problem, target customer, current alternatives, buying process and access to the market before software exists. A prototype, concierge test or paid pilot may later test solution-specific assumptions with less investment than a full MVP.
Who should you interview for B2B SaaS validation?
Interview the people whose experience or authority affects adoption. Depending on the sale, this may include users, managers, economic buyers, technical evaluators, security or compliance specialists and procurement. Do not treat these roles as interchangeable.
How do you test whether customers will pay for SaaS?
Start with current spending, costs, workarounds, budget ownership and approval criteria. Then test a concrete offer and seek a realistic next commitment, such as a paid pilot, pre-order, procurement review or agreed commercial next step. A hypothetical willingness-to-pay answer is weak evidence on its own.
What are the strongest signs that a SaaS idea is worth pursuing?
Relevant customers repeatedly describe an important problem, take action or incur costs today, can explain a feasible buying path, see a clear reason to change and accept a proportionate next commitment. Evidence should recur in the intended segment, not only among friendly contacts.
When should you change or stop a SaaS idea?
Change the idea when the problem is real but the segment, workflow, value proposition, pricing, buying path or implementation assumptions are wrong. Stop when the evidence shows insufficient importance, access, differentiation or credible commitment relative to the required investment.
Independent SaaS validation
Know what the market evidence says before you build the MVP.
The standard project includes target definition, approximately 30–40 suitable prospects for client approval, recruitment, 20 interviews, transcripts, evidence analysis, a written report, recommended changes and a BUILD, CHANGE or KILL recommendation.
Fixed price: €2,900 + VAT. Typical timeline: approximately 2–4 weeks. Larger and multi-segment projects can be scoped separately.
Submit your idea
About the author
Dr. Kari Jääskeläinen
Dr. Kari Jääskeläinen is an entrepreneur, business leader and consultant with experience in market validation, technology commercialisation, business development and sales. He has worked on around 200 commercialisation and consulting projects and has made approximately 2,000 sales calls a year.
Read about Dr. Kari Jääskeläinen’s experience →Sources and further reading
- Harvard Business School Rock Center for Entrepreneurship. Customer Discovery Basics.
- U.S. National Science Foundation. NSF I-Corps.
- Ries, E. (2011). The Lean Startup. Crown Business.
- Blank, S. and Dorf, B. (2012). The Startup Owner’s Manual. K&S Ranch.