Validation

How to validate a micro SaaS idea before writing code

Building software is the expensive way to find out nobody wants it. This guide walks through how to test a micro SaaS idea with real people, from the first interview to a landing page with a price, before you spend on development.

By the Twarx Micro SaaS Boutique team5 min read

Most software products that fail were not badly built. They were built for a problem that was not painful enough, for people who could not be reached, or at a price nobody would pay. The code worked. The idea did not.

Validation is the work of finding that out early and cheaply. It does not prove an idea will succeed, because nothing can. What it does is replace guesses with evidence on the three questions that decide most outcomes: is the problem real, who has it, and will they pay to have it solved?

Start with a problem, not a product

Ideas usually arrive as a product: an app that does this, a tool that connects that. Before testing anything, turn the idea back into the problem it solves and the person who has it. Write it as one sentence: this kind of person struggles with this task, and it costs them this much time, money or risk.

If you cannot write that sentence, the idea is not ready to test. If you can, you now have something specific to check. A micro SaaS works because it is narrow. A product for every small business is hard to sell. A product for one kind of business with one recurring headache is much easier, because you know exactly who to talk to and what to say.

Write down your assumptions too. Who exactly has the problem? How do they solve it now? What would they pay? These are the bets you are about to test, and writing them down stops you quietly moving the goalposts later.

Find the people who have the problem

Validation only works with the right people. Friends, family and other founders will be kind and supportive, which is exactly what you do not need. You need people who have the problem now and would be the ones to pay for a solution.

Look where they already gather: industry forums, professional groups, trade associations, online communities and your own customer or supplier list if you run a business. If you struggle to find even a handful of these people to talk to, take that seriously. It may mean the market is hard to reach, which will also make the product hard to sell.

  • Aim for people who make or influence the buying decision.
  • Talk to people at different sizes of business, not just the first type you find.
  • Keep a simple record of who you contacted, how, and who replied.

Run interviews that tell you the truth

The most common mistake in customer interviews is pitching. As soon as you describe your idea, most people will be polite and say it sounds useful. That tells you nothing about whether they would pay for it.

Instead, ask about their life, not your idea. Ask about the last time the problem happened, what they did about it, what it cost them and what they have already tried. Past behaviour is far more reliable than predictions about the future. Someone who has spent money or built a spreadsheet to work around the problem is a much stronger signal than someone who says they would definitely use your product.

Keep the conversations short and let the other person do most of the talking. Take notes in their words, not yours, because the language customers use to describe the problem is the language your landing page will need later. After each interview, write down the one or two things you learned and whether they support or weaken your assumptions.

  • Tell me about the last time this happened. What did you do?
  • What do you use for this today, and what do you dislike about it?
  • What does this problem cost you in time or money?
  • Have you looked for a better solution? What happened?

Study what they use today

Every problem worth solving already has a solution of some kind, even if it is a spreadsheet, an assistant or a general-purpose tool used awkwardly. Competitors are not a bad sign. They show that people spend money on the problem. No competition at all is often the warning sign, because it can mean nobody cares enough to pay.

For each alternative, note what it costs, who it is built for and what its users complain about. Reviews and support forums are full of honest feedback. You are looking for a gap that a focused product could fill: a group of customers the big tools serve badly, a step they make painful, or a price that is out of reach for smaller buyers.

Test whether anyone will pay

Interviews tell you whether the problem is real. They do not tell you whether people will pay. For that you need a test where people have to do something, not just say something.

The simplest version is a landing page that describes the product, shows a real price and asks visitors to join a waiting list, book a call or pre-order. Send people from the communities you found to the page and watch what they do. A visitor who leaves an email address after seeing the price has told you more than ten people who said it sounded interesting.

You can also ask your strongest interviewees directly whether they would pay for early access or commit to a pilot. Some will say no, and the reasons they give are often the most useful thing you will hear all week.

Decide: build, change or stop

Before you begin, decide what result would make you build, what would make you change direction and what would make you stop. Doing this up front protects you from reading what you hoped for into weak results.

A good result is people describing the problem in their own words without prompting, already spending money or effort on it, and acting when shown a price. A mixed result often points to a better version of the idea: a different customer group, a narrower problem or a different price. A clear no is not a failure. It is the cheapest lesson available, and it frees your budget for an idea that deserves it.

The short version

Validation turns a hopeful idea into a decision you can defend. Write down the problem and who has it, talk to those people about their past behaviour rather than your product, study what they already pay for and test whether they act when shown a real price. If the evidence says build, you start development knowing who it is for and what it must do. If it says stop, you have saved the cost of finding out the hard way.

Have an idea worth testing?

Tell us the problem and who has it. We will reply with how we would validate it and what an MVP could look like.