How to Validate Your Idea Before You Pay a Developer

Building software is how we make a living. So it probably seems strange that the first thing I try to work out on a discovery call is whether the thing in front of me should be built at all.

There is a reason for that. I have seen what happens when it should not have been.

The most expensive sentence in software

"Of course this is a cool idea. Why wouldn't anyone like it?"

I knew a founder who built on exactly that. No research, no conversations, no evidence. He had decided the idea was cool, and to him that settled the question.

He was building a social app. His competitors were X and Facebook. He was going into an industry that already had a settled way of working, where users had few real complaints about the existing options, and he was going to be the change.

Social apps are among the hardest products you can attempt, and not for technical reasons. The difficulty is adoption. A social product is worthless until enough people are already on it, which means you are asking strangers to leave something that works and where their friends already are. That is a brutal ask, and it needs a very good reason behind it.

He did not have one. What he had was a monetisation plan. The idea had been built around how it would make him money rather than around what a user would actually gain by switching. Those are not the same thing, and users can tell the difference immediately.

A couple of weeks of research would have surfaced all of it. Not months. Weeks. He would have found out that his target audience was not looking to move, that the complaints he assumed existed were not really there, and that the thing he was excited about was the concept rather than the problem.

Feeling the pain does not mean the market feels it

Most good ideas start with a personal frustration, and that is a legitimate place to begin. The mistake is treating it as the finish line.

You are one person. Your frustration is one data point. It tells you the problem exists for you, and it tells you nothing about how many other people feel it, how badly they feel it, or whether they have already found something that solves it well enough.

It is also worth checking whether a solution already exists. Founders often assume that because they have not come across one, there is not one. Usually there is, and usually the interesting question is why the existing one is not good enough, rather than why nobody has thought of this.

"Oh, it's cool" is not feedback

This is the sentence I repeat more than any other, because it is the trap almost everyone falls into.

You describe your idea to people around you. They say it sounds great, they say it's cool, they say they would definitely use it. You walk away feeling validated. You were not validated. You were being encouraged.

The people close to you are protecting the relationship, not evaluating the business. They do not want to be the person who told you your idea was weak, and most of them do not have enough context to judge it anyway. Their enthusiasm costs them nothing and tells you nothing.

The feedback worth having comes from strangers, because a stranger has no reason to spare your feelings.

The questions I ask on a first call

When a founder brings me an idea, I ask what the inspiration behind it was. Was it a personal pain? Was it a pain you watched other people have? Was it something you think would make life easier for the people you are building for?

Any of those is a reasonable starting point. Then I ask the harder one: has it been validated? Have you spoken to anyone outside your own circle, and what did they actually say?

If the honest answer is no, I say so. I would rather someone spend two weeks finding out than six months building.

Two questions, not one

Here is the distinction that catches people out. There is demand, and there is willingness to pay, and they are not the same question.

Plenty of problems are real, widely felt, genuinely annoying, and worth nothing. People will complain about them at length and will not pay a dollar to make them go away, because the annoyance is small enough to live with or because a free workaround already exists.

So do not stop at "yes, people have this problem". Keep going until you know whether it is a problem people are already spending money on. That is a much higher bar and a much more useful answer.

Where to actually look

If you have the means, run a small survey in your target market. Real questions, real people, people you are not related to.

If you do not have the means, you still have everything you need. Go where your market already talks. Reddit, Quora, the forums and groups specific to your niche. Read what people complain about, in their own words, when nobody is asking them to be nice about it.

What you are looking for is people describing your problem without being prompted. Better still, people describing the thing they currently pay for and why it frustrates them. Someone already paying for a bad solution is the strongest signal you will find, because the willingness to pay is proven and only the quality is in question.

Do not ask AI whether your idea is good

This is where a lot of founders now begin, and it is the wrong room to be in.

An AI will tell you your idea is interesting. It will help you sharpen how you describe it, list competitors, and produce a tidy plan. What it cannot tell you is whether a single human being will pay for it, because it is not the market and it has never been your customer.

You are not building for AI. You are building for people. So go and ask people. Use the tools to move faster once you know what you are building, not to decide whether to build it.

What this means before you hire anyone

When someone comes to us without validation, we say so, and we usually suggest they go and do that work first. That is not us turning away business. It is that a build starting from an unvalidated idea tends to go one of two ways: it gets rebuilt halfway through when reality arrives, or it ships to silence.

We would rather help you get to the point where we are both confident. That is also why our discovery calls exist: to break an idea down to its simplest form and look at it honestly before anyone writes a line of code.

If you have done that work and you know what you are building, we build websites and web apps, and you can see what we have shipped.

The short version

An idea is not a nudge and it is not a feeling. It has to meet a demand that exists outside your own head.

Find out whether that demand is real before you spend your money, and before you spend the thing you cannot get back, which is your time. Talk to strangers. Look for people already paying. Treat "that's cool" as the non-answer it is.

Then build.