How investors can read public demand signals
Public demand is cheap to read and easy to misread. What each signal tells you, and what it cannot.
At the earliest stage there is not much to look at. No revenue, few users, maybe a demo. What you can often find is evidence that the problem is real: people describing it in their own words, before anyone has sold them a solution. Read carefully, public demand is one of the few signals available before a company has numbers of its own.
Read carelessly, it misleads. A big vote count can mean a real market, or one enthusiastic WhatsApp group. This guide covers what each signal on Suggst tells you and where each one stops.
What public demand can show you
A problem post on Suggst is someone describing something hard or annoying that no product solves well. Other people vote on it and add detail. Together, that gives you three things a pitch deck cannot: the problem in the customer's words, a rough sense of how many people recognise it, and the workarounds they use today.
It cannot tell you the size of the market, whether a given team can build the fix, or whether anyone will keep paying after the first month. Treat it as evidence about the problem, not about the company.
Reading each signal
Votes
A vote, I want this too, means someone recognised the problem enough to click. It is the cheapest signal and the noisiest. Use it to notice a problem, not to size one.
Would pay
I'd pay for this is a mark on a vote. It is a stated intent, not a payment, but it asks the voter to think about money for a moment. The share of votes with a would-pay mark often says more than the vote count itself.
How often it happens
Posts ask How often does this happen to you? with daily, weekly, monthly and rarely as answers. Frequent problems can support habits and subscriptions. Rare problems can still be valuable if each one is costly, but the business looks different: fewer, larger sales and constant work to find new customers.
Pledges
On problems and ideas, people can pledge an amount: "I'd pay ₹X if someone builds this". Nothing is charged. Treat pledges as a guide to price range and seriousness, never as revenue. The spread of pledges tells you more than their total.
Who is building
Builders can mark I'm building this on a problem or idea, and the people who wanted it hear when the build launches. This shows you competition early. It also lets you check whether the founder in front of you is one of the builders, and how long they have been at it.
Comments
Comments, especially the ones marked helpful, are where people describe what they do today. A comment saying "we pay someone to do this by hand every month" can tell you more than a long list of votes.
Quick question
A problem has a lot of votes, but very few people marked "I'd pay for this" and most said it happens rarely. What is the most reasonable read?
Patterns worth a closer look
- Would-pay marks high relative to votes. Fewer people, but more of them thinking about money.
- Frequency weighted to daily or weekly. A problem people hit often is easier to build a habit around.
- Comments describing paid workarounds. People already spending money is the clearest sign there is.
- Several builders, no launches. Either the problem is hard or there is a barrier the builders ran into. Ask the founder which, and how they plan to get past it.
- The same problem in different words from different people. Independent descriptions are harder to manufacture than one popular post.
The Most wanted reports show the top requests in each category, a quick way to see where demand is gathering. If you want to work across many problems at once, Builder Pro (₹499 a month, see pricing) has a demand table across problems with votes, would-pay and frequency side by side, a CSV export, and a daily email of new problems matching your searches.
Where the signal breaks
Public demand has blind spots, and they are predictable. Keep them in mind every time a number looks good.
- The people on the site are not the whole market. Customers who are rarely online, or who do not write in public, will be missing from the count.
- Votes can come from one community. Group lists make it easy to share a post in a WhatsApp group, which is good for reach. It also means a jump in votes can be one housing society, one college or one founder's friends. Check back over the following weeks to see whether the post keeps collecting votes.
- Stated intent is not payment. Would-pay marks and pledges cost nothing to make. They are more useful for comparing problems with each other than for forecasting revenue.
- Some problems never get posted. Health, debt, family trouble and anything embarrassing tend to stay private. Few votes there may mean discretion, not a lack of demand.
- Business buyers may not post at all. A finance team with a painful process may never write it up in public, even if they would pay well to fix it.
- New posts have not had time. A week-old problem with few votes has not been tested yet.
Reading the same problem two ways
A quick read
This problem has the most votes in its category, so the market must be big.
Using it in diligence
Public demand works best as a set of questions to bring to a founder, alongside the conversations and numbers you would ask for anyway.
Questions to bring to a founder
0/6The public record helps here too. Every post carries a timestamp proof made with OpenTimestamps, so if a founder says they spotted a problem early, you can check when they posted it. And if you vote or comment as an investor, a verified work badge shows founders who you are: funds are confirmed by work email, and angel investors are reviewed by a moderator.
If you also build, or advise founders who do, finding a startup idea people will pay for covers the same signals from the builder's side.
Browse problems and the Most wanted reports to see where demand is gathering.
Browse problemsWritten by the Suggst team. Example requests about real apps are made up to show how to write them, not reports about those apps.