How to Validate Your SaaS Idea Before Writing Any Code

The most expensive mistake in building a SaaS product is spending six months building something nobody will pay for. Validation is how you compress that feedback loop from months to weeks.

The goal of validation is not to prove your idea is good. It is to find one person willing to pay for it before you build it.

Start With the Problem, Not the Solution

Most founders start with a solution ("I want to build a tool that does X") and then try to validate it. A better approach: start with the problem and work backwards.

The validation question is not "Will people use my product?" It is "Is this problem real, frequent, and painful enough to pay to solve?"

Talk to potential users before you have a product. Ask:

• How do you currently handle [the problem]?
• How much time does it take? How much does it cost?
• What have you tried? Why did that not work?
• What would a perfect solution look like?

If people cannot articulate the problem clearly, or the current workaround is "I do not bother with that," the problem may not be real enough.

The Landing Page Test

Build a landing page in one day. Describe the product you intend to build as if it exists. Include a clear CTA — either "Join the Waitlist" or "Pre-Order" if you are willing to take pre-sales.

Drive 200-500 targeted visitors to it. Sources:

• Post in relevant Reddit communities (honestly — introduce the problem, link to your landing page)
• Post on X with relevant hashtags
• Run a small paid ad ($50-100) targeting the exact audience

Benchmark:

• Waitlist conversion rate above 10% = strong signal
• Pre-order conversion rate above 2-3% = very strong signal
• Below 2% = either the audience is wrong, the landing page is unclear, or the product does not have a market

A low conversion rate is not automatically a death signal — it might mean the landing page copy is weak. Before concluding the idea is bad, test two different headlines and CTAs.

Pre-Sales

Pre-sales are the gold standard of validation. If someone pays you for a product before it exists, you have proof of demand. Not interest — demand.

Setting up pre-sales:

• Create a landing page with a clear "Pre-Order at $X — ships in [date]" CTA
• Use Stripe, Gumroad, or Polar.sh for payment processing
• Be honest: tell buyers this is a pre-order and give them a clear expected delivery window

The price matters. Pre-ordering at $9 is much weaker validation than pre-ordering at $49. Charge something close to your intended launch price to validate willingness to pay at the real level.

If you collect five pre-sales from strangers (not friends or family), you have enough validation to build a first version.

Customer Interviews

Five to ten customer interviews will teach you more than any amount of web analytics. The goal is not to pitch your idea — it is to understand the problem deeply.

Rules for useful interviews:

• Talk to people who already experience the problem (not people who might experience it)
• Ask about past behaviour, not hypothetical future behaviour ("Have you ever tried to solve this?", not "Would you use a tool that did X?")
• Do not pitch during the interview — you will contaminate the data
• Record the interview (with permission) and review the transcript for exact language — this language becomes your marketing copy

Listen for: frequency ("I deal with this every week"), pain ("I wasted three hours on this last month"), workarounds ("I built a spreadsheet but it keeps breaking"), and budget ("I pay $200/month for [competing solution] that partially solves this").

The Fake-Door Test

A fake-door test means presenting a feature or product that does not yet exist and measuring click intent. The classic example: a pricing page with a "Buy Now" button that leads to a waitlist page instead of a payment form.

This is more aggressive than a simple landing page test but provides cleaner data on purchase intent. Use it for specific features within an existing product ("Would our users pay for this feature?") or for pricing tiers you are considering.

Caveat: be honest with users who hit the door. "This feature is coming soon — we are measuring interest. Join the waitlist to be first in line." Do not leave them confused.

The Standard You Are Aiming For

Before writing your first line of product code:

• You have spoken to at least five people who have the problem
• You have built a landing page and driven real traffic to it
• Conversion rate is above 5% (waitlist) or you have at least one pre-sale from a stranger
• You can articulate the problem in one sentence using language the customers themselves used

If you cannot reach this bar after two weeks of genuine effort, the idea needs to change. Either the problem is not real enough, the audience is wrong, or the positioning is off.

Validation is not a box to check before building. It is information that shapes what you build.

---

Submit your product to LaunchBuff → — free listing + fortnightly tournament.