MVP & building2 min read

How to Validate a SaaS Idea Before Development

Validate a SaaS idea by checking three things before you write production code: the problem is frequent and costly, the user has tried to solve it already, and the buyer will spend money or time on a solution. A waitlist alone proves curiosity. Interviews plus a commitment signal prove something more useful.

Interview the buyer, not only the user

In B2B SaaS the person who uses the product and the person who pays for it are often different. Interview both. Ask the user what the work looks like day to day. Ask the buyer what the problem costs the business, who would have to approve a tool, and what they tried before.

Keep the interview about the past. 'When did this last happen?' gives better answers than 'Would you use this?' People are poor predictors of their future behaviour, but good reporters of what they did.

Build a clickable test

A clickable prototype of the core workflow can test understanding without any backend. Give five target users a task and watch them try to complete it. Count how many finish without help, and note the step where they hesitate. A prototype that fails this test should not become a product.

Use a commitment signal

Choose one action that costs the user something: a paid pilot, a signed letter of intent, an onboarding call booked in their calendar, or data they are willing to share. A signup alone is cheap. A pilot fee or a calendar slot with a named colleague is a real signal.

Set the decision rule before you test

Write the threshold before you see the data. For example: 'Continue if at least five of twenty interviewed buyers agree to a paid pilot within four weeks, and at least three of those pilots name a budget.' Without a rule, every outcome can be explained as encouraging.

Common validation mistakes

  • Asking friends and family, who are kind rather than honest
  • Testing a feature instead of a workflow
  • Counting waitlist sign-ups as demand without any follow-up
  • Changing the target market after the first weak result, without rerunning the test

What a failed validation looks like

A failed validation is useful if it changes the next decision. Maybe the problem is real but the buyer is different. Maybe the buyer agrees but the workflow must be narrower. Write the lesson down. Several good SaaS products started as a narrower version of an earlier idea that failed the first broad test.

When to start building

Start building when the problem is confirmed by the buyer, the core workflow passes the clickable test, and at least one commitment signal exists. Then build only the piece that the commitment depends on. The rest of the product can wait for paying users to ask for it.

Next step

Get help improving conversion

Send me the page or flow that loses people. I will tell you where the friction is and what to change first.

Open the conversion page