How to know if your product idea already exists

The worst thing that can happen when you research a new idea isn't finding competition. It's not finding competition — and then launching to discover it everywhere.

Most founders search for their idea, find nothing obvious, and conclude the market is open. Then they launch and realize the competition was there all along, in places they didn't look.

Here's how to do the research properly.

The mistake: searching for products instead of problems

When founders look for competition, they search for products. "Invoice management SaaS." "AI writing tool." "Project tracker for freelancers."

This is backward. Products don't compete with each other. They compete for the same customer, solving the same problem.

Your real competition isn't just the other app with your features. It's also:

• The spreadsheet your customer built themselves
• The combination of two other tools they currently duct-tape together
• The manual process they do every Friday afternoon
• Doing nothing at all (the status quo)

If your idea already exists as a spreadsheet template with 10,000 downloads, that's competition. If your idea already exists as a Zapier integration that 5,000 people use, that's competition.

Search for how people solve the problem today — not just for your product.

The full search process

Search 1: Product Hunt (10 minutes)

Product Hunt is the best database of every software product that has ever launched.

Go to producthunt.com and search for:

• The core problem you're solving (not your solution)
• The main noun in your idea ("invoicing," "feedback," "scheduling")
• The combination your solution uses ("AI + [your domain]")

Look at launch dates. A product that launched 4 years ago and has 200 upvotes is very different from one that launched 6 months ago and has 2,000.

The 4-year-old product: either the market wasn't there, or it's been acquired/shut down. The 6-month-old product: the market exists, someone is executing.

Click through to every relevant result. Read the comments. What did users love? What did they criticize? What did they say was missing? The comments on a competitor's Product Hunt launch are gold.

Search 2: Google (10 minutes)

Search for these specific patterns:

• "[problem] software"
• "[problem] tool"
• "best [problem] apps"
• "alternatives to [tool you already know]"
• "[problem] for [specific segment, e.g. freelancers, agencies, startups]"

The "alternatives to" search is the most underused. If you already know of one player in the space, searching for their alternatives will surface the other 8-15 products competing for the same customer.

Also search Google for the problem itself, not the solution: "how to manage [thing]" will surface both tools and manual processes people use.

Search 3: GitHub (10 minutes)

Open source competition is real competition.

Search GitHub for your core concept. Look for repos with:

• Stars (50+ means real users, 500+ means a real community)
• Recent commits (active development = active market)
• Issues with feature requests that describe what your SaaS would do

An abandoned open source tool in your space with 300 stars from 4 years ago tells you: the demand was there, the free version wasn't enough to sustain it, a paid SaaS might work where the OSS couldn't.

Search 4: Reddit (10 minutes)

Search for "alternatives to [competitor]" and "best [tool category]."

Reddit will show you:

• The community's actual experience with existing tools
• Which gaps consistently come up ("I love X but I wish it had Y")
• Whether the market is mature (lots of sophisticated discussion) or nascent

The gap between "I love X but..." is your differentiation. Write those down. That's your feature list for v1. For a deeper dive into getting value from Reddit research, see how to use Reddit for market research.

Search 5: App stores (5 minutes)

If there's any mobile or desktop component to your idea, search app stores. The reviews on existing apps are your market research:

Filter by 1-star and 2-star reviews. Sort by recent. Read the specific complaints. "This app is perfect except it doesn't do X" is someone telling you exactly what to build.

What to do with what you find

Finding 1: No competitors at all

This is a bad sign, not a good one.

If nobody is building for this market, there are two explanations:

1. The market is too small or too hard to monetize
2. You searched wrong

Almost always it's the second one. Try broader searches, different terminology, adjacent problem spaces. Ask someone outside your industry how they'd describe the problem.

If you've done exhaustive research and genuinely found nothing: validate that the problem exists (Reddit, customer interviews) before assuming you found a gap. A gap with no market is just a void.

Finding 2: One or two competitors, not growing

This usually means the market exists but is still being discovered, or the existing players haven't found the right go-to-market.

Look at their reviews, their pricing, their marketing. Are they reaching the right customer? Are they priced correctly? Do their customers complain about the same specific things?

Sometimes one failing competitor means bad execution. Sometimes it means the market is genuinely small. The difference is in the customer research.

Finding 3: Several well-funded competitors

This is often treated as scary. It shouldn't be.

Well-funded competitors in a space mean: the market is real, customers exist, and the problem is worth solving.

The question isn't "is the market taken?" The market is never taken. The question is: what do customers hate about the current options?

Go read 1-star reviews on every competitor. Find the complaint that appears most often. Build the product that fixes exactly that thing.

You don't need to beat the market leader. You need to be the right choice for a specific segment the leader ignores.

Finding 4: Many indirect competitors (substitutes)

Spreadsheets, manual processes, Zapier automations, combinations of other tools — these are the hardest competition to identify and the most important to understand.

If people are solving your problem with a spreadsheet, ask: why haven't they bought a SaaS solution? Understanding why most SaaS ideas fail before launch helps you spot the patterns that keep customers stuck on workarounds. Three common answers:

1. Existing SaaS solutions are too expensive
2. Existing SaaS solutions are too complex (require onboarding, training, buy-in)
3. The problem isn't acute enough to justify switching from something that mostly works

Your job is to make switching obvious. That means: simpler than the spreadsheet, cheaper than the alternatives, and solving the exact gap the spreadsheet leaves open.

The question to answer

After all this research, you should be able to answer:

"Why would someone choose my product over what they already have?"

If you haven't yet confirmed that people are willing to pay for a solution, the next step is understanding how to find out if people will pay for your idea — because competitive research alone doesn't tell you that.

Not in abstract — with specifics. Not "because mine is better" — with evidence.

"Because the two main competitors [X] and [Y] both require a team plan starting at €100/month, and my core use case is solo founders who need one seat at €15/month. The Reddit posts [link] confirm this complaint is consistent and unaddressed."

If you can write that paragraph, you have your differentiation. If you can't, keep researching.

The last check

Once you've done all this, run your idea through the final lens:

• Does competition exist? (It should)
• Are people complaining about the competition? (They should be)
• Is your angle addressing the most common complaint? (It should)
• Is the market growing, flat, or shrinking? (Growing or flat — shrinking is trouble)

If yes to all four: you have a validated angle.

Validate your idea against live signals →