Skip to content
millionsaas

Founder guide · Founder tools

How to validate a SaaS idea before building anything

A practical, low-cost process: find the painful problem, talk to buyers, test willingness to pay with a landing page, and decide with clear thresholds.

3 min read

Some links on this page are referral links. If you buy through them we may earn a commission at no extra cost to you. It never changes our verdicts. Affiliate disclosure

How to validate a SaaS idea before building anything: the key steps covered in this guide
What this guide covers, step by step.

Short answer: Validation means finding evidence that a specific group of people has a problem painful enough to pay for. Talk to at least ten of them, put a priced offer on a landing page, and decide in advance what result means "build", "change" or "stop".

1. Write the problem, not the product

Write one sentence: "[Who] struggles with [problem] when [situation], and currently deals with it by [workaround]." If you can't name the workaround, you may not have found a real problem yet. Existing workarounds (spreadsheets, scripts, hiring someone) are the best sign that people care.

2. Find where those people already are

Look for communities, forums, subreddits, Slack groups and job boards where your buyers talk about work. Search for complaints about the workaround and existing tools. Save the exact phrases people use; they'll become your landing page copy.

3. Have ten problem conversations

Ask about the past, not hypotheticals:

  • "Tell me about the last time this happened."
  • "What did you do about it? What did that cost you?"
  • "What have you tried? Why did you stop?"

Avoid pitching. You're listening for frequency, cost and urgency. If most people shrug, that's an answer.

Signal vs noise

"That's a cool idea" is noise. "Can I use it next week?", "How much is it?" and "I'll introduce you to my boss" are signal.

4. Test willingness to pay with a landing page

Build a single page that states the problem in their words, the outcome, and a price. A Hostinger or static page is enough. Offer one of:

  • Pre-order or deposit (strongest signal).
  • "Join the paid beta at $X/month" with an email form.
  • Waitlist (weakest, but still useful when paired with interviews).

Collect emails with a free plan from a tool like Kit, and send traffic from the communities in step 2, without spamming them.

5. Decide with thresholds you set beforehand

Write these down before you look at results:

Result after 2-4 weeksDecision
People pre-pay or ask to payBuild the smallest version that delivers the outcome
Strong interview pain, weak page conversionChange the positioning or the audience, retest
Little pain in interviews, low signupsStop, or pick the next problem from your notes

6. Build the smallest thing that delivers the outcome

That might be a manual service, a spreadsheet template or a script you run for them. Charge for it. Automate only what you repeat.

Common traps

  • Validating with friends. They're kind, not customers.
  • Counting signups without price. Free interest doesn't predict paid use.
  • Building during validation. Every week of code makes it harder to admit the answer is no.

FAQ

How long should validation take?

Two to four weeks is usually enough to get ten conversations and a meaningful landing page test.

How many signups is enough?

There's no universal number. A handful of people who pay or pre-order beats hundreds of free waitlist signups.

Tools mentioned

HostingerFrom $1.99/mo

Cheap, beginner-friendly shared and cloud hosting with a free domain on longer plans.

Best for: Landing pages and marketing sites on a tight budget

KitFrom $39/mo

Email marketing for creators (formerly ConvertKit), with a free plan up to 10,000 subscribers.

Best for: Creators and founders selling courses or info products

Written by

The millionsaas editor · Founder, millionsaas

Runs millionsaas and writes most of the reviews. Focuses on the tools small software businesses actually pay for, and on what they cost after the first invoice. Replace this bio with your own name and background in data/authors.json.

Last updated . Spot something out of date? Tell us.

The SaaS deals digest

One email a month: verified discounts, price changes we spotted, and the reviews we published. No sponsored slots. Unsubscribe in one click.

Related reading

Tags:validationindie-hackerssaas