How to Validate a SaaS Idea Before Building

The expensive mistake

The wrong way to validate is to build a thing, launch it, and see if anyone uses it. That takes 3 to 6 months and costs real money. By the time you find out it does not work, you have burned through your budget and your patience.

The right way takes 2 weeks and costs almost nothing. You skip the build entirely until you have evidence the idea is real.

The 4 levels of validation

Validation is not one thing. It is a sequence. Each level is stronger evidence than the last.

• Level 1: People say it sounds interesting.Almost worthless. People are polite.
• Level 2: People sign up for a waitlist.Slightly better. Costs them nothing.
• Level 3: People give you a deposit or pre-order.Real signal. They are putting money on the line.
• Level 4: People are paying you for a manual version.The strongest signal. They have a problem painful enough that they are paying you to solve it without software.

Most founders stop at level 1 and start building. That is the mistake. Get to at least level 3 before you build.

Step 1: Define who you are building for

The first failure mode is “everyone who has this problem.” That is not a target audience, it is a wish.

You need a specific person. A title, a company size, a context. Not “small businesses” but “agency owners with 5 to 20 employees who manage clients in spreadsheets.”

The narrower, the better. You can expand later. Starting narrow gives you a real audience to talk to.

Step 2: Talk to 10 to 20 of them

Find them on LinkedIn, Reddit, in Slack communities, at meetups. Reach out and ask for 20 minutes of their time. Be specific about what you want to learn.

In each conversation, ask:

• How do you handle X today?
• What is the most frustrating part of that?
• What have you tried? Why did it not work?
• If you could wave a magic wand and fix it, what would that look like?
• How much time or money does this currently cost you?

Listen for emotional intensity. People who have a real problem get emotional describing it. People who do not have it stay flat.

Step 3: Pitch the solution and see what happens

After you have heard the problem clearly from 10 people, pitch your specific solution to them. Watch their reaction.

• If they get visibly excited and ask when they can use it, that is signal.
• If they say “that sounds interesting” and change the subject, that is not signal.
• If they offer to pay you for it before you have built it, that is the strongest signal possible.

You are not trying to convince anyone. You are trying to find the people who already have the problem and are waiting for someone to solve it.

Step 4: Pre-sell

Once you have a clear pitch and people who light up when you describe it, try to sell it before you build it.

• Build a landing page that describes the product clearly.
• Add a “Get early access” or “Reserve your spot” button.
• Ideally, charge for early access. Even $1 deposits filter serious buyers from polite ones.
• Drive a small amount of traffic to the page. LinkedIn posts, Reddit comments, direct outreach. See what converts.

If you cannot get 5 people to give you money for a thing that does not exist yet, you probably will not get them to buy it once it does. That is useful information.

Step 5: Manual MVP (the strongest validation)

The best validation: do the work manually for your first customers. No software. Just you doing the thing your future software would do.

• If you are building a scheduling tool, schedule things by hand for 3 customers.
• If you are building a reporting dashboard, build the report in a spreadsheet and email it.
• If you are building a CRM, manage their pipeline in Notion or Airtable.

This sounds slow. It is the fastest possible validation because you learn what they actually need before you write code. The features they end up wanting are often different from what you assumed.

Signs the idea is not real

• People say “cool” and forget about you.
• You cannot find people willing to talk for 20 minutes about the problem.
• Nobody will commit money even at a deeply discounted price.
• The people who do commit cannot articulate a current cost for the problem.
• You hear “just build it and we will see” from everyone you talk to.

Any one of these is a yellow flag. Two or more, and you probably have the wrong idea or the wrong audience.

When you are ready to build

You are ready to build when:

• You have 5+ people who have committed (paid or pledged) to use the product.
• You have a specific scope that solves a specific problem for a specific audience.
• You can describe the product in two sentences and see people light up.
• You have a clear path to your first 10 customers.

How FinishLine AI handles this

We work with founders who have validated their idea and are ready to build. If you are not sure whether you are at that stage, the $100 Quick Audit is a useful sanity check. We will tell you if your idea is ready for a build or if you need more validation first.