How to Validate a SaaS Idea Before You Build It
SaaS · 8 min read · Updated 2026-03-15
Most SaaS products fail not because the code was bad, but because nobody wanted what was built. Validation is cheaper than rebuilding. Here is the playbook we run with founders before quoting them an MVP.
Validate the problem before the product
Talk to at least 20 people in your target segment before you write a single line of code. Not "would you use this?" — that is useless. Ask them how they solve the problem today, how much it costs them, and what they have already tried and abandoned.
Charge before you build
A landing page with a real "buy" button — even if all it does is collect a deposit — tells you more about willingness to pay than 100 hours of user interviews. People lie in conversations. They do not lie with their credit card.
Pick a niche, not a market
Generic SaaS competes with a thousand others. A niche SaaS — "invoicing for dental clinics in Germany" — has a defensible position, clear marketing channels, and 10x easier sales conversations.
The minimum viable validation stack
A 1-week validation sprint costs almost nothing:
- A one-page landing site with clear positioning and a real CTA.
- A Stripe pre-order or paid waiting list.
- A short Loom video showing the proposed solution.
- Outreach to 50 hand-picked prospects in your niche.
- A spreadsheet tracking responses, objections, and conversions.
Frequently asked questions
How long should SaaS validation take?
A full validation sprint — landing page, outreach, conversations, and pricing test — should take 2 to 4 weeks. Longer than that and you are building.
How much does an MVP SaaS cost to build?
A properly scoped MVP from a boutique agency is priced per scope and varies with complexity. Beware of anyone quoting a fixed number without seeing your spec.
B2B or B2C SaaS — which is easier?
B2B is usually easier to validate and monetize early. Higher contract values and clearer buyer pain. B2C wins on scale but requires deep distribution.