How to Validate Your SaaS Idea Before You Build It

You have an idea. You can already picture the dashboard, the logo, maybe even the launch post. So you open your code editor and start building.

Three months later, you launch. And almost nobody signs up.

This happens to a lot of indie makers, and it's not because they're bad at building. It's because they skipped one small step: checking if people actually want the thing before building it.

That step is called validation. The good news? It doesn't take months, and you don't need to write a single line of code.

Quick answer: To validate a SaaS idea, write down the exact problem you want to solve, find 10 to 15 people who have that problem, and talk to them about how they deal with it today. Then put up a simple landing page and see if strangers sign up. The strongest proof is when someone pays or pre-orders before the product is ready.

What does "validating an idea" really mean?

Validating an idea means getting real proof that:

1. A specific group of people has the problem you want to solve
2. The problem bothers them enough that they want it fixed
3. They will pay, or at least sign up, for your fix

It's not about proving your idea is good. It's about finding out fast if it isn't, before you spend months on it.

Which signals actually count?

Not every "yes" means the same thing. Here's how to read the signals you get, from weakest to strongest:

The goal of validation is to get as far down this table as you can before you build.

Step 1: Write down the problem, not the solution

Most makers start with the solution: "an AI tool that does X." Start with the problem instead.

Fill in this line:

"[Who] struggles with [what problem] because [why], and today they deal with it by [current workaround]."

For example: "Freelance designers struggle to get paid on time because they send invoices by hand, and today they deal with it by sending awkward reminder emails."

If you can't fill in the "current workaround" part, that's a warning sign. People usually already do something about problems that really bother them.

Step 2: Find 10 to 15 people who have this problem

Not friends. Not other founders, unless founders are your users. Real people who fit your "who."

Good places to look:

• Reddit communities and niche forums where your users ask questions
• LinkedIn, by searching for job titles that match your users
• Facebook groups, Slack and Discord communities in your niche
• Indie Hackers, if your users are founders or builders

Don't pitch anything yet. Just say you're researching a problem and ask for 15 minutes of their time. If you're new to posting in communities, read our guide on how solo founders get their first users on Reddit and Indie Hackers without getting banned.

Step 3: Ask about their past, not your idea

This is where most people go wrong. If you ask "Would you use an app that does X?", almost everyone says yes just to be polite. That answer means nothing.

Ask about what they've actually done instead:

Listen more than you talk. Write down the exact words people use. Those words will later become your landing page copy.

What you're listening for: people who have already tried to fix the problem, spent money on it, or hacked together their own workaround. That's real pain.

Step 4: Put up a simple landing page

After your conversations, make a one-page site that explains the problem and your fix. You don't need the product yet.

Include:

• A headline that uses your users' own words
• Three short benefits
• A "Join the waitlist" or "Get early access" button

Then share it in the places where you found those 10 to 15 people. Watch two numbers: how many people visit, and how many sign up. If lots of people visit but nobody signs up, your message probably isn't clear yet. Our post on what to fix when you get visitors but no signups goes deeper on this.

Step 5: Ask for money

This is the scary step, and it's also the most useful one.

Go back to the people who were most excited and offer them something like:

• A "founding member" deal at a lower price, paid now
• A pre-order with a full refund if you don't ship
• A small paid pilot where you solve their problem by hand first

If even a few strangers pay before the product exists, you have something real. If everyone says "I'd love it, but not right now", listen to that too.

A simple 2-week validation plan

Signs your idea passed (or needs a rethink)

Common validation mistakes

• Only asking friends. They'll be nice, not honest.
• Pitching instead of listening. If you talk about your idea for 10 minutes, you'll only hear polite agreement.
• Counting likes as proof. Likes are free. Signups and payments aren't.
• Building "just a small MVP" first. Small MVPs still take weeks. Talk first, build second.
• Ignoring a "no". A clear "no" early saves you months. That's a win, not a failure.

Frequently asked questions

How long does it take to validate a SaaS idea?

About two weeks is enough for a first round. You can go faster if you already know where your users hang out.

Can I validate an idea without building anything?

Yes. Conversations, a landing page and a pre-order offer are enough to test most ideas. You only need a product once people show they want it.

How many people should I talk to?

Ten to fifteen conversations is a good start. When you keep hearing the same problems in the same words, you've talked to enough people.

What if someone has already built my idea?

That's often a good sign. Competition means people already pay to solve this problem. Your job is to find what users dislike about the current options and do that part better.

Is validation the same as building an MVP?

No. Validation checks if the problem is worth solving. An MVP is the first simple version of your solution. Validate first, then build the MVP.

Final thoughts

Validation isn't about killing your idea. It's about making sure you build something people are already waiting for. Two weeks of conversations can save you months of building in the dark.

Once your idea passes and your product is ready, go through our SaaS launch checklist, then see where to submit your startup in 2026. And when you're ready to put it in front of makers and early users, launch it on IndieNeed.