If you have no startup idea, you are not behind. You're probably in the same spot as most people who want to build something and can't decide what.
The usual advice is to brainstorm, follow your passion, or "scratch your own itch." That works if you already have an itch. If you don't, staring at a blank page makes it worse.
There's a better move. Stop trying to invent an idea. Go read what people are already complaining about, and pick a problem from there.
This article shows you how to do that, what separates a real problem from noise, and what to do in your first week.
Why brainstorming fails when you have no idea
Brainstorming asks you to produce something from nothing. Your head is the only source of input, and it's limited by what you've already seen and done.
That creates three problems:
- You come up with ideas you like, not ideas people need. Those are different things, and you often can't tell until you've spent weeks building.
- You judge ideas by how they feel. An idea feels exciting at 11pm and silly the next morning. Feelings are a poor filter.
- You have no one to check with. An idea in your notebook has no customers, no objections, and no evidence.
Starting from complaints flips this. The problem already exists, someone already feels it, and they've already described it in their own words. Your job changes from "invent" to "notice and verify." That's a much easier job when you feel stuck.
Start with complaints, not ideas
A complaint is a small piece of evidence that a problem exists. People rarely complain about things they don't care about.
You don't need a clever insight. You need to collect complaints, compare them, and see which ones are worth your time.
What makes a complaint worth building around
Not every rant is a business. When you read a complaint, check three things:
- Intensity. How much does it hurt? "This is slightly annoying" is different from "this is costing me clients."
- Frequency. Do many people say the same thing, or just one person on a bad day?
- Willingness to pay. Is there a sign that the person would spend money or time to fix it? Mentions of current workarounds, paid tools they've tried, hours lost, or money leaking are all good signs.
Those three signals are what you're sorting for. A problem that is intense, common, and tied to money is a better starting point than one that's merely interesting.
What to ignore
Skip complaints that are pure venting with no stakes, problems that only affect one unusual person, and anything where the "solution" is just "people should behave differently." You can't build a business around that.
Where to find real complaints
You have plenty of places to look. Pick one or two and go deep rather than skimming ten.
- Reddit communities for professions. People in r/sysadmin, r/webdev, r/entrepreneur and similar communities describe their work problems in plain language, often with detail.
- App store and software reviews. Read the one- and two-star reviews of tools in a category you find interesting. They list exactly what's broken.
- Job-related forums and Slack or Discord groups. Questions like "how do you handle X?" show where people lack a good answer.
- Your own work history. Even if you have no idea, you have a job or past jobs. The tasks you hated are leads.
Reddit is especially useful because people tend to be candid there. They're asking peers for help, not writing a polished review for a company.
Three real complaints and what you could do with them
Here are three examples of posts that show what a usable complaint looks like. Each one is a lead, not proof. A single post tells you a problem exists for one person. It becomes interesting when you find more like it and talk to people.
Example 1: repeating the same manual work
A poster in r/entrepreneur described how agency work piles up:
"Every time i took on a new client i was doing the same manual analysis over and over. Go through their website, check the SEO, read the copy, look at competitors, figure out where they're leaking money."
You can read the original thread on Reddit.
What stands out: it's a repeated task, it happens with every new client, and it's tied to money ("leaking money"). Repetition plus money is a good pattern.
Possible directions: a tool that automates part of the audit, a productized service that delivers the audit for a fixed price, or a template pack for agencies.
Example 2: a messy problem after a company merger
A poster in r/sysadmin wrote:
"8 months post-acquisition and we still have 200 people with active accounts in both tenants. Some line-of-business apps were never migrated."
Here's the original post.
What stands out: the problem has gone on for months, it has a clear owner (IT), and it carries security risk. Business buyers often have budget for problems like that.
Possible directions: software that reconciles duplicate accounts, a consulting offer for post-merger cleanups, or a checklist-based info product for IT teams.
Example 3: one failure that spreads
A poster in r/webdev described a cascade of account trouble:
"one of my client had his payment delayed... it affected my personal account as well. Mine also got deactivated/suspended."
The thread is here.
What stands out: a small billing issue caused a bigger loss of access. Freelancers and agencies who manage client accounts could share this fear.
Possible directions: a monitoring or alerting tool, a guide on separating client and personal accounts, or a service that sets up safer account structures.
Notice that none of these needed a flash of genius. You read a complaint, ask what's behind it, and list a few ways to help.
Turn a complaint into an idea
Once you have a promising complaint, work through four questions.
1. Who exactly has this problem?
Name the role and context. "Agencies" is vague. "Small marketing agencies that onboard several new clients a month" is specific. The more precise you are, the easier it is to find them and talk to them.
2. What do they do today?
Every problem has a current workaround, even if it's a spreadsheet or doing it by hand. Understanding that workaround tells you what you need to beat, and how much effort people already put in.
3. What's the smallest thing that would help?
You don't need a full platform. Think about the smallest useful piece. This is where it helps to consider three forms:
- Software (SaaS): an app that automates or simplifies the task.
- Productized service: you do the work for a fixed scope and price, using templates and checklists.
- Info product: a guide, course, or template set that teaches people to do it themselves.
If you're non-technical, a productized service or info product lets you test demand without writing code.
4. Would anyone pay?
This is the question that matters most, and you can only answer it by talking to people. More on that below.
Speed this up with a tool
You can do all of this by hand. It just takes time: reading threads, copying quotes, comparing posts, and trying to remember which complaints were more common.
SaasNiche is built for this workflow. It scans Reddit communities and surfaces pain points, each scored 0–100 for intensity, frequency and willingness to pay, and backed by verbatim user quotes. It also generates AI solution ideas in the SaaS, productized service and info product formats, and lets you message the original posters for customer discovery.
It isn't required. If you prefer a spreadsheet and a few evenings of reading, that works too. A tool mostly saves you the sorting.
Talk to people before you build anything
Reading complaints gets you to a hypothesis. Conversations get you closer to the truth.
When you find a poster whose problem fits, send a short, honest message. Keep it low-pressure:
- Say which post you read and why it caught your attention.
- Say you're exploring the problem, not selling anything.
- Ask for ten minutes, or even just a couple of written answers.
In the call or chat, ask about the last time the problem came up, what they did, what it cost them, and what they've already tried. Don't pitch. Don't describe your idea until the end, if at all.
Two cautions. First, follow each community's rules and Reddit's etiquette. Don't spam. Second, expect many people not to reply. That's normal. Contact several people, not one.
Your first-week plan
Here's a simple seven-day plan. It assumes you have a couple of hours a day.
Day 1: Pick a lane
Choose one profession or community you can understand reasonably well. It could be one you've worked in, or one you're curious about. Write down why. Don't overthink it. You can change lanes later.
Day 2: Collect 20 complaints
Read threads in that lane and save 20 complaints. For each, copy the exact quote, the link, and the date. Don't judge yet. You're gathering raw material.
Day 3: Score them
Rate each complaint from 0 to 100, or just low, medium and high, on intensity, frequency, and willingness to pay. Look for repeats. Cut the bottom half.
Day 4: Pick three and sketch options
Choose the three strongest. For each, write the target person, their current workaround, and one idea in each form: software, service, info product. Keep it to a few lines.
Day 5: Reach out
Send short messages to at least ten people connected to your top three problems. Be clear that you're doing research. Prepare five questions in advance.
Day 6: Have the conversations
Talk to whoever replies. Take notes using their exact words. Listen for money, time lost, and failed workarounds. Notice who says "I'd pay for that" without being asked, and who is only being polite.
Day 7: Decide
Review your notes and pick one of three paths:
- Go: one problem has clear pain and at least a few people who'd try a solution. Make a one-page offer and a simple landing page.
- Dig deeper: the signal is promising but thin. Spend another week on the same problem.
- Switch: nothing held up. Go back to Day 3 with a new batch of complaints.
Any of those is progress. You now know something you didn't a week ago.
Common mistakes to avoid
- Falling for one loud post. A single viral complaint isn't a market. Look for patterns.
- Building before talking. Writing code feels productive, but it's the most expensive way to learn that nobody cares.
- Choosing a problem you can't reach. If you can't find or contact the people who have it, selling will be hard.
- Waiting for the perfect idea. There isn't one. Your first idea mostly matters because it gets you into real conversations.
Ready to start?
You don't need a brilliant idea today. You need a place to look and a method for judging what you find.
If you'd like a head start on the reading and scoring, SaasNiche has a 7-day trial on its $19/month Starter plan. Try it at saasniche.com and use your first session to run Days 1 to 3 of the plan above.
FAQ
How do I find a startup idea if I have no ideas?
Start with problems instead of ideas. Read complaints in communities tied to a profession or topic you know a little about, collect the ones that show real cost or repeated frustration, and then explore ways to solve one. Conversations with the people who posted help you test whether it matters.
Do I need to be a developer to build a startup?
No. Many problems can be addressed with a productized service, an info product, or a no-code tool before any custom software is written. Starting with a non-code version is also a cheaper way to test whether people will pay.
How do I know a problem is worth solving?
Look for three signals: the problem hurts (intensity), it comes up repeatedly across different people (frequency), and there's evidence people would spend money or time to fix it (willingness to pay). Mentions of workarounds, lost hours, or lost revenue are useful clues. Direct conversations are the strongest check.
Is it okay to message people from Reddit posts for research?
It can be, if you do it respectfully. Keep the message short, say you're researching and not selling, reference their post, and make it easy to say no. Follow Reddit's rules and each community's rules, and don't send mass copy-paste messages.
How many people should I talk to before deciding?
There's no fixed number. A common approach is to speak with several people about the same problem and see whether the same themes keep coming up. If every conversation sounds different, or nobody seems to care much, the problem may not be strong enough.