How to find a startup idea people will pay for
Start with what people already complain about, then keep the problems they already spend money or hours working around.
The ideas that arrive in the shower tend to be solutions looking for someone to use them. The ones that turn into businesses usually start somewhere less exciting: a person annoyed by the same thing, again and again, to the point where they have already started paying for a bad fix.
So instead of hunting for ideas, hunt for complaints. Then sort the complaints by one question: is anyone already spending money or time on this?
Look for complaints, not ideas
A complaint is specific in a way an idea rarely is. It comes with a person, a moment and usually a workaround. "Our society secretary collects maintenance on UPI and then spends Sunday matching payments to flat numbers in a register" tells you who has the problem, when it bites and what they do now. "An app for housing societies" tells you none of that.
Complaints also give you the words people use. If you build for the society secretary, you will sell to them in their language, about their Sunday, and not in the language of your pitch deck.
A few kinds of complaint deserve extra attention:
- Ones people repeat. If the same frustration comes up from people who have never met, it is not one person's bad day.
- Ones with a workaround. A spreadsheet, a notebook, a WhatsApp group, a cousin who handles it. Every workaround means someone cared enough to do something.
- Ones tied to a job. Problems people hit while running a shop, a clinic or a class often have someone with a budget attached, because fixing them saves the business time or money.
Signs a problem is worth money
Plenty of real problems will never pay. Someone can be annoyed by a thing every day and still not spend a rupee on it, because the annoyance is small or the fix belongs to someone else. The problems that do pay tend to share a few traits, and you can check for them before writing a line of code.
Is this problem worth building for?
0/6A problem does not need every box ticked. Something that happens rarely but costs a lot, like a house move or a wedding, can still support a business, though you will keep having to find new customers because nobody needs you twice a month. What you want to avoid is a problem that ticks none of them: rare, cheap when it goes wrong, and owned by someone with no budget.
A vague problem and a sharp one
Vague
People need a better way to manage their money.
Where complaints show up
You do not need special tools to find complaints. You need to look where people already talk about their day.
- Your own work. The parts of your job you dread, or the spreadsheet your team keeps patching, are the problems you understand best.
- App store reviews. One-star reviews of apps in a category you know are a list of things people wanted and did not get.
- WhatsApp groups you are already in. Society groups, school parent groups and trade groups are full of people asking each other how to deal with the same things.
- People who do the job. Sit with a shop owner, a tuition teacher or a clinic receptionist for an hour and write down every time they sigh.
- Suggst. Problems are posts about things that are hard or annoying where no product solves them well, and ideas are products people wish existed.
On Suggst, each problem shows more than a vote count. You can see how many people marked I'd pay for this, how often it happens to the people who answered (daily, weekly, monthly or rarely), and any pledges, where someone writes "I'd pay ₹X if someone builds this". Nothing is charged for a pledge, but a number in rupees is still a stronger signal than a click. The Most wanted reports group the top requests by category, which is a quick way to see where demand is piling up.
If you do this every week, Builder Pro (₹499 a month) sends a daily email of new problems that match your searches, gives you a demand table across problems, and lets you export it as CSV.
Tell interest from intent
The most dangerous thing a friend can say about your idea is "that's a great idea". It costs them nothing, it feels like evidence, and it tells you very little about whether they will pay.
Interest is free: a like, a vote, a nod. Intent costs something: time, money, a referral, a promise to try it. When you sort problems, give much more weight to the second. A problem with fewer votes but more people saying they would pay can be a better bet than a popular one nobody would spend on.
Quick question
Which of these is the strongest sign that someone will pay for a fix?
Check who else is working on it
Finding out that someone is already building for your problem feels like bad news. Usually it is not. It means someone else saw the same demand, and the question becomes whether you have a different angle: a different customer, a lower price, a better way to reach people, or a language they do not serve.
On Suggst, builders can mark I'm building this on a problem or idea, so you can see who already has. If you mark it yourself, the people who wanted it hear when your build launches. That is a small launch list made of people who already said they have the problem.
If several people have marked it and nobody has launched, treat that as a question to answer before you start. The problem may be harder than it looks, or there may be a barrier, such as regulation or distribution, that the others ran into.
A routine you can repeat every week
- Read new problems in the areas you know, on Suggst or wherever your people talk.
- Pick three that pass most of the checklist above.
- For each one, talk to five people who have it. Ask what happened last time, what they did and what it cost.
- Drop any problem where nobody pays for a workaround or has tried to fix it.
- Post the one that survives as a problem on Suggst if it is not there yet, and share it with the people you spoke to.
- Watch what comes back: votes, I'd pay for this marks, how often it happens and pledges.
Then move from finding to testing. Validating a startup idea in India covers cheap ways to check demand before you build, from WhatsApp groups to small UPI pre-orders.
Browse the problems people have posted and see which ones they would pay to have fixed.
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.