How To Tell If A Business Idea Has Real Demand

Most founders validate ideas by asking people if they want them. This is the fastest way to build a product nobody buys. When you ask a friend, a colleague, or a stranger on the internet if your idea is good, they will usually say yes. Saying yes costs them nothing. It avoids social friction. It makes you smile. It is also completely useless data.

A business idea only has real demand if people are already spending time, money, or social capital trying to solve the exact problem you want to fix. If they are not actively trying to solve it right now, they will not pay you to solve it later.

The hierarchy of demand signals

Not all evidence is created equal. You can rank demand signals by how much friction a person had to overcome to create them.

At the bottom is the survey response. A user clicking a radio button to say they experience a problem is a weak signal. The friction is near zero.

One step up is the search query. A user opening Google and typing a specific phrase to find a solution shows intent. The friction is low, but it requires unprompted action. If a keyword tool shows 5,000 monthly searches for a highly specific problem, you have a baseline.

The next level is the public plea. This is a user going to Reddit, a specialized forum, or a Facebook group, writing a paragraph about their problem, and asking for help. They are spending time and risking public ridicule to find an answer. This is a strong signal.

At the very top is the cobbled together workaround. This is the holy grail of demand signals. A user who pays for a Zapier subscription to connect a Google Sheet to a clunky CRM just to track their freelance invoices is screaming for a better solution. They are spending money and time on a bad process. When you find this, you have found real demand.

Stop asking about the future

The human brain is terrible at predicting future behavior. When you ask someone if they would pay $10 a month for your proposed app, they imagine an idealized version of themselves. That version exercises daily, eats perfectly, and has plenty of disposable income.

To find real demand, you must only ask about the past.

Instead of asking if someone would use a meal planning app, ask them what they ate for dinner last night. Ask them how they decided what to cook. Ask them to show you the exact grocery list they used. If they say they just winged it and ordered takeout, they do not have a meal planning problem. They have a habit they are not actively trying to change. You cannot build a business on a habit someone is not trying to change.

Finding the bad workarounds

You do not need to interview people one by one to find these workarounds. The internet is a massive, searchable database of human frustration. You just need to know how to query it.

Look for specific phrases that indicate a user has hit a wall. People do not write that they have demand signals on the internet. They write how do I force, is there a way to bypass, or tired of manually.

If you want to build a tool for Shopify store owners, go to the Shopify community forums. Search for export to excel and. You will find hundreds of threads where store owners describe exporting their data to a spreadsheet, manually running a macro, and then importing it somewhere else. Every one of those threads is a validated demand signal. They are showing you the exact product you need to build.

You can do this manually across Reddit, Twitter, and niche forums.

The math of a viable problem

Once you find a workaround, you must quantify the pain. A problem is only worth solving if the cost of the workaround is higher than the price of your future product.

Let us look at a concrete example. You find a group of podcast editors who spend two hours per episode manually removing filler words. A freelance podcast editor charges roughly $50 per hour. Their bad workaround costs them $100 per episode in lost billable time.

If your software can automate this task, you are not selling a feature. You are selling $100. If you charge $20 per month, the arithmetic is undeniable. The editor saves $80 on their very first episode. This is an easy sale.

Many founders build tools that save users five minutes a week, then wonder why nobody subscribes. Five minutes a week is twenty minutes a month. Even if your user values their time at $100 an hour, you are only saving them $33. If your software costs $30, the margin of value is too thin. The user will just keep their bad workaround. You need overwhelming mathematical superiority to change human behavior.

Now consider a different scenario. You find gamers stating that a popular video game takes too long to load. The workaround is just waiting an extra 45 seconds. The cost of this workaround is 45 seconds of leisure time. The monetary value of that time is zero. No matter how many people highlight the loading screen, you cannot build a business selling a slightly faster loading screen. The math does not work.

Testing demand with a landing page

Sometimes you find a problem, but you cannot find a clear workaround. You suspect the demand is there, but people are just suffering in silence. In this case, you must force a transaction before you write a single line of code.

You build a landing page. You describe the problem exactly as your target audience describes it. You present your solution. You put a price tag on it. You add a buy button.

When the user clicks that button, you do not show them a waitlist form. A waitlist is just another way of asking if they would use this. It is a weak signal.

Instead, you ask for their credit card. You set up a Stripe checkout link. If they enter their card details and hit submit, you capture the payment intent. Then, and only then, do you show a message explaining that the product is still in development and their card has not been charged.

This is the ultimate test of demand. If you send 1,000 targeted visitors to that page and zero people attempt to pay, you do not have a marketing problem. You have a demand problem. The idea is dead. Move on.

What conversion rate should you look for? A standard conversion rate for a B2B SaaS product is around 1 percent. If 1,000 visitors yield 10 attempted purchases at $50 each, you have validated $500 in monthly recurring revenue. That is enough signal to start building.

Analyzing competitor reviews

Your competitors are doing you a massive favor. They are spending their own marketing budget to acquire users, and those users are leaving public reviews detailing exactly what the product lacks.

Go to the App Store, G2, or Capterra. Ignore the five star reviews. They are often generic and lack detail. Ignore the one star reviews. They are usually from people angry about a billing issue or a crash.

Read the three star reviews. A three star review is written by a pragmatist. This user liked the concept enough to try it, but found a specific, frustrating limitation. They will write things like:

The interface is great, but I cannot export my reports to PDF, so I have to take screenshots.

That is a pristine demand signal. The user has already proven they will pay for a solution in this category. They are telling you the exact feature that would make them switch. If you find twenty reviews across three different competitors all highlighting the lack of PDF exports, you have your wedge into the market.

You can also look at the language users employ in these reviews. When a user writes that they are frustrated, stuck, or losing money because of a missing feature, they are handing you a marketing script. You can use their exact words on your own landing page to attract other users who are experiencing the identical frustration.

The danger of the visionary trap

Founders love to quote Henry Ford saying that if he had asked people what they wanted, they would have said faster horses. They use this quote to justify building products with zero existing demand signals. They believe they are visionaries creating a new market.

You are probably not Henry Ford. Creating a new market requires millions of dollars in consumer education. As an indie developer or a bootstrapped founder, you cannot afford to educate the market. You must capture existing demand.

This trap is especially common among technical founders who want to play with a new technology. They build an artificial intelligence tool or a blockchain application first, and then go looking for a problem it can solve. This is a solution in search of a market. It always ends in failure because the technology itself is not a demand signal.

You want to build the car, but you must first verify that people are already spending money on faster horses, better saddles, and premium oats. The desire to travel faster is the demand signal. The car is just a better execution of the solution.

If you cannot find people spending money on horses, do not build the car.

Final validation checklist

Before you open your code editor, put your idea through this filter.

• First, can you point to a specific group of people who have this problem? If your audience is everyone, your audience is no one.
• Second, can you prove they are actively trying to solve it right now? You need links to forum posts, search volume data, or examples of bad workarounds.
• Third, does their current workaround cost them more in time or money than your proposed solution? Run the arithmetic. The numbers must be overwhelmingly in your favor.
• Fourth, if you put a buy button in front of them today, will they click it?

If you cannot answer yes to all four questions, do not build the product. Go back to the internet, look for the bad workarounds, and find a problem people are actually desperate to solve.