TL;DR: Searching Google and Product Hunt finds the products with marketing budgets, not the products with customers. Below are seven places competitors actually hide, plus the test that distinguishes "someone already does this" (usually fine) from "someone already does this for my exact customer, well" (the finding that should change your plan).
First, the reframe
"Has someone built this?" is the wrong question, and it produces the wrong reaction. Almost every worthwhile idea has been attempted. What you actually need to know is three things:
- Does something exist? — Establishes the category is real.
- Does it serve the customer you intend to serve? — Most competitors serve an adjacent segment.
- Do its users say it solves the specific job you care about? — This is where the answer usually is.
A "yes" to the first is reassuring. A "yes" to all three is the finding that should make you change plans. Founders who stop after question one either abandon good ideas or miss real competition — depending on which way the first answer went.
The seven places to look
1. App stores (iOS, Google Play). Search the job, not the product category. Many of the best small businesses are single-purpose mobile apps that no tech publication has ever covered. Filter by recent updates — an app not updated in two years is an artifact, not a competitor.
2. Browser extension stores. An enormous amount of quiet, profitable software ships as a Chrome or Firefox extension. These almost never appear in startup press and rarely rank in Google for category terms.
3. GitHub. Search for the problem in issues and READMEs, not just repository names. Two useful findings live here: an open-source tool that already does it (a competitor with a price of zero), and a long-running issue thread describing the problem with nobody solving it (the opposite).
4. Niche community forums. Every industry has a forum where practitioners recommend tools to each other. The recommendations in those threads are the real competitive landscape for that audience, and they routinely contain products with no marketing presence whatsoever.
5. Marketplaces and app directories. Shopify, WordPress, Slack, Notion, Figma, and similar platforms each host an app ecosystem. A product solving your problem inside one platform is both a competitor and evidence of demand.
6. The graveyard. Search for the idea plus "shutting down", "sunset", or "acquired". A company that tried this and failed is more informative than one currently succeeding, because post-mortems tend to be candid about why. Sometimes the answer is a fatal structural problem you would have hit too. Sometimes it is a fixable execution mistake or bad timing — which is a genuine opening.
7. Service providers. If people are paying agencies, freelancers, or consultants to do this manually, the demand is proven and unproductised. This is frequently the strongest possible signal, and it appears in none of the first six places.
The test that actually matters
Once you find something, run this:
| Question | If yes | If no |
|---|---|---|
| Does it serve my exact customer? | Real competition | Adjacent — likely your wedge |
| Do its reviews say it does the job well? | Real competition | Opportunity inside a proven market |
| Is it actively maintained? | Real competition | Possible opening |
| Can it serve my customer without breaking its own model? | Hard to displace | Structural opening |
That last row is the one people skip and the one that matters most. A product whose business model prevents it from serving your customer well cannot simply decide to compete with you. An enterprise tool with a required sales call cannot serve solo developers without dismantling its own economics. That is a durable position, and it is invisible from a feature comparison.
What "already exists" should change
- Nothing exists at all. Be suspicious before being excited. Verify people actually have the problem — the most common reason nobody has built something is that nobody needs it.
- It exists, serves a different segment. Usually the best case. Market proven, wedge available.
- It exists, serves your segment, users complain about the same thing repeatedly. Also good. The complaint cluster is your entry point.
- It exists, serves your segment, users are happy. Change something — the customer, the wedge, or the idea. This is the finding worth having early.
Doing this systematically
The manual version of this takes a day per idea and gets skipped under time pressure. The parts that reward automation are searching many platforms at once and — more importantly — reading complaints about existing products rather than their marketing.
PainHunt indexes complaints across dozens of platforms including app stores, GitHub, and community forums, and maintains a set of tracked products alongside them. The practical use here is the third question above: rather than reading a competitor's landing page, you can look at what its users say is still broken.
Related reading
- How to validate a startup idea — the step after this one
- How to find SaaS ideas in app store reviews — the same review-reading skill, applied to finding ideas
- The best startup idea validation tools in 2026 — a neutral map of the tooling
- Search existing complaints by product or category, or test your idea against them