The graveyard of software products is full of well-built things nobody needed. Founders spent months and significant money building a product, only to find out at launch that the problem was not painful enough, the audience was too small, or the market already had a better solution.
Validation is the work you do to find that out before you invest in building. It is not glamorous. But it is the most important thing you can do before writing a single line of code.
Start With the Problem, Not the Solution
The first question to answer is not will people pay for my product. It is do people actually have this problem. These sound similar but they lead to very different conversations.
Talk to ten people in your target market. Do not pitch your idea. Ask about their workflow, their frustrations, and what they currently do to solve the problem you are thinking about. If they do not bring up anything close to your idea, that is important information.
Find Out If They Are Already Paying for a Solution
If someone is already spending money to solve a problem, that is a strong signal the problem is real. It could be a competitor product, a freelancer, a spreadsheet and hours of manual work, or an agency retainer.
The fact that existing solutions are imperfect is not a blocker. It is an opportunity. Your job is to understand what is wrong with what they use today and whether your idea solves that specific gap.
The Fastest Validation Tool: a Landing Page
Build a simple landing page that describes the product, who it is for, and what it does. Include a clear call to action, whether that is joining a waitlist, booking a demo, or paying a deposit to reserve early access.
Drive traffic to it through your network, LinkedIn, relevant communities, or even a small ad spend. The conversion rate will tell you more than any survey. People clicking away cost you nothing to learn from.
Charge Money Before You Build
The most credible form of validation is a customer who pays before the product exists. This is uncomfortable to pursue but incredibly revealing.
Offer a founding member deal. Tell them the product is in development and you are taking on a small number of early customers at a discounted rate. If nobody pays, that is feedback. If ten people pay, you have validation and early revenue to fund the build.
Manual First, Automated Later
Another approach is to deliver the outcome of your product manually before you build the technology to automate it. This is sometimes called a Wizard of Oz MVP.
If your product would automate report generation, generate the reports manually for your first customers. If it would match buyers and sellers, do the matching yourself. You are testing whether the outcome creates real value, not whether your code works.
Look at Search Volume and Community Conversations
If your target customers are looking for a solution, they will leave traces. Check Google search volume for the problem terms you are targeting. Look in Reddit threads, Slack communities, and forums where your audience spends time.
Are people frustrated? Are there threads asking whether anyone knows a tool that does a specific thing? That is demand signal. Are those threads quiet or years old? That might mean the market has moved on or was never that large.
Be Honest About Your Own Biases
Every founder thinks their idea is good. That is not a useful filter. You need external signal from people who have no reason to be polite about whether your idea is worth their money.
Friends and family will often tell you what you want to hear. Strangers on the internet and potential customers with real budgets will tell you the truth. Seek out the people who might say no, because their hesitation is more valuable than encouragement from people who want you to succeed.
What You Are Looking For
You are not looking for certainty. Validation does not prove your product will succeed. It reduces the risk that you build something nobody wants.
You are looking for consistent signals: people who describe the problem without being prompted, people who ask when they can buy it, and people who part with money or time to engage with an early version. Three to five of those signals from unrelated sources is enough to move forward.
When to Stop Validating and Start Building
Validation has a point of diminishing returns. At some stage you need to ship something real so customers can react to the actual product rather than a description of it.
If you have spoken to real potential customers, seen genuine interest, and ideally collected either money or strong commitments, you have done enough. Build the smallest version that delivers the core value and get it in front of those same people.
If you have validated a SaaS idea and are ready to build, talk to us at Cystall. We help founders turn validated ideas into working products without wasted time or budget.