Where Good Startup Ideas Come From: 8 Sources Worth Watching

Good startup ideas rarely arrive as a flash of inspiration. They show up as complaints, workarounds and half-finished tools scattered across the internet, usually written by people who have no plan to build a company around them. The trick is knowing where to look and what to look for.

Below are eight sources worth watching, how to mine each one for real pain, and a simple method for turning a raw signal into an idea you can actually evaluate.

What you are really looking for

Before the list, a filter. An idea source is only useful if it surfaces evidence of demand, not just clever concepts. The strongest signals are:

• Repeated complaints about the same problem from different people
• Workarounds: spreadsheets, scripts, Zapier chains, manual processes
• Money already being spent on a tool people dislike
• "Is there a tool that..." questions that get no good answer
• Timing shifts: a new API, regulation, platform or behavior that makes something newly possible

Keep a running note while you browse. One complaint is an anecdote; the same complaint in three places is a lead.

1. Hacker News

Hacker News is dense with technical founders and developers describing their daily friction in detail.

• Ask HN threads are gold. Search for "Ask HN: How do you..." and "Ask HN: Is there a tool for..." and read the replies. When the top answers are "I wrote a script" or "we use a spreadsheet," you have found a gap.
• Show HN launches tell you what others are building and, more usefully, the comments list what is missing. "This is great, but I need it to also do X" is a feature request from a market.
• Complaint threads around price increases, shutdowns or acquisitions of popular tools often contain hundreds of users looking for an alternative right now.

2. Niche subreddits

Big subreddits are noisy. The value is in small, specific communities where professionals talk shop: subreddits for accountants, landlords, freelancers, teachers, small e-commerce sellers, specific software platforms.

Search each one for phrases like "how do you handle," "I hate," "is there an app," and "what do you use for." Sort by top posts of the past year to find problems that keep resurfacing. Pay attention to the flair and job titles of posters; knowing exactly who has the problem is half the idea.

3. Product Hunt launches

Product Hunt shows what is being built, which is useful in two ways. First, a cluster of launches in one category signals that builders see an opportunity, and the comments show how users react. Second, launches reveal underserved adjacent niches: a general tool that gets many comments like "does this work for [specific industry]?" points to a vertical version nobody has built yet.

Read the critical comments, not the congratulations.

4. Y Combinator's Requests for Startups and launches

YC periodically publishes Requests for Startups, a list of problem areas its partners want founders to work on. These are useful as a map of where experienced investors think timing is right. YC company launches, meanwhile, show which specific wedges well-funded teams are attacking.

Use these as a starting point, not a destination. If a well-funded team is going after a broad market, there is often a smaller, specific segment they will ignore for years.

5. App store charts and 1–3 star reviews

The App Store, Google Play and the Chrome Web Store all publish category charts. Popular apps prove a market exists. Their low-star reviews tell you exactly what that market is unhappy about.

Pick a top app in a category and read its 1, 2 and 3 star reviews from the last few months. Look for patterns:

• "It used to do X, now it's behind a paywall"
• "Great, but missing Y"
• "Too complicated, I just want Z"

Three-star reviews are especially useful: the person likes the product enough to keep using it but is telling you what would make them switch. Chrome extensions with large user counts and stale update dates are another signal; users are stuck with something the author has stopped maintaining.

6. GitHub trending and issues

GitHub trending shows which open-source projects are gaining attention, which often reflects a new technical capability that is about to become mainstream. The issues tab of a popular project is even more useful: long-open feature requests with many upvotes, and repeated questions about hosting, setup or enterprise features, point to things users would pay for.

A common pattern: a popular open-source tool that is painful to self-host becomes a hosted product. Another: a library that developers love but non-developers cannot use becomes a no-code product.

7. Dev.to and Lobsters developer chatter

Dev.to and Lobsters are quieter than Hacker News but full of developers writing long posts about their workflows. Tutorials are a hidden signal: if many people write "how I automated X with a custom script," the underlying task is common and nobody has productized it well.

Look for posts describing tedious multi-step processes, especially ones that end with "I wish there were a better way."

8. Your own job and work

The source you know best is the one you live in. Every role has recurring annoyances: reports you assemble by hand, data you copy between systems, approvals that bounce around email. You have context no outsider has, you know who buys, and you can probably name ten people with the same problem.

Keep a list for two weeks. Every time something at work is tedious, confusing or slow, write it down. Ideas from your own work also tend to score well on founder fit, which is covered in choosing a startup idea that fits you.

Quick reference table

Turn a signal into an idea

A complaint is not an idea yet. Run each promising signal through four questions and write one line for each:

1. Problem. What exactly is painful, in the words people used? "Freelancers lose track of which invoices are overdue" is better than "invoicing is hard."
2. Who. Which specific person has this problem and would pay to fix it? Name the role, company size or situation.
3. Why now. What changed that makes this solvable or more urgent today? A new API, a price hike by the incumbent, a regulation, a shift in how people work.
4. How it earns. Subscription, usage fee, one-time purchase, marketplace cut? Who holds the budget?

If you cannot answer all four, keep the signal in your notes and move on. If you can, you have an idea worth scoring. Our guide on how to evaluate a startup idea gives you a weighted scorecard to compare candidates.

Let the sources come to you

Watching eight sources every day is a lot of reading. Ideas does this scan for you: every day it pulls from Hacker News, Reddit, Product Hunt, Dev.to, Lobsters, GitHub, Y Combinator and the App Store, Google Play and Chrome Web Store charts, then distills what it finds into one card per idea in a daily feed. The feed is free to browse, with or without an account, and you can like, save and rate cards as you go. Start with the idea library, or read how the daily feed works to see how cards are picked and ranked.

Whether you mine the sources yourself or let a feed do the first pass, the habit is the same: collect signals, look for repetition, and only get attached to an idea once real people keep describing the same pain.