Is my idea already taken cannot be acted on either way, which is why the answers are useless
Is my idea already taken is the question everyone asks and it cannot be acted on either way, which is why the answers you get are all so useless.
A no tells you nobody wanted it enough to try. A yes tells you nothing about whether there is room. Half the results reassure you that competition is validation; the other half sell you a tool that counts competitors.
The reassurance is empty rather than wrong — competition proves somebody believed in the market, which is a weak claim once you notice how many crowded markets are crowded with unprofitable companies. The count is worse: twelve competitors in a market you can reach beats two in a market you cannot, and no tally distinguishes those.
The answerable question is narrower. Are the incumbent's own users complaining about one specific thing, and is it something the incumbent will not fix rather than has not fixed yet.
That produces 3 decisions rather than a yes or a no. Take them on where they are. Narrow to a slice they are not built to serve. Or leave it.
The middle one is the answer most often available to one person, and it costs something real: you give up the market you were imagining for the market you can actually win. A tool that never delivers that answer is flattering you.
And the trigger for leave it is usually not a strong competitor. It is silence — you went looking for complaints and found none, which usually means the problem is not painful enough to write about. That is a finding about the market, not about the incumbent.
The rule that decides whether any of this is worth anything is not about the verdict, it is about the evidence under it. You can produce all three verdicts from imagination, and most competitor analysis is exactly that: plausible weaknesses attributed to a company nobody checked.
So sort complaints into will not fix and has not fixed yet — an enterprise-first incumbent will never build what your slice needs, which is durable, while a missing feature on a public roadmap is a countdown. And write down what you could not find, because that is the part people delete from their notes.
The three decisions and the worked teardown: https://whittleos.com/guides/is-my-startup-idea-already-taken
“Will not fix” is the valuable distinction, but I reckon it needs stronger evidence than the complaint itself.
A durable opening usually exists because fixing it would conflict with the incumbent’s pricing, architecture, sales model or main customer segment. If the problem is merely absent from the roadmap, they can copy it. If solving it would upset their best customers or weaken their economics, the wedge is much safer.
I’d also be careful with silence. Some painful problems produce workarounds rather than public complaints. The stronger signal is probably: users repeatedly complain or spend time and money compensating for it, and the incumbent has a structural reason to leave it unresolved.
Both corrections I'd take. On the first: the structural test has an advantage I under-sold in the post — a conflict is visible somewhere the complaint is not. You don't find it in the thread, you find it on the pricing page, in the seat minimum, in the sales motion, in who the case studies are about. That makes it checkable rather than inferable, which is exactly the difference between a wedge you can defend and a plausible story about a company nobody looked at.
On silence you've landed on my own filter's worst failure mode, and I can put a number on it: the single most common reason my pipeline drops a candidate is no documented problem behind it — roughly six in ten drops. That's the filter reporting on my own sourcing and filing it as a verdict about the market. Your workaround point is why it isn't harmless. The cases where someone built a spreadsheet, hired a VA or wrote a script are precisely the ones where the pain was already worth paying to avoid — and what those people published is a description of their workaround, not a grievance. Cheap problems get complained about; expensive ones get routed around quietly.
So the artifact to go looking for is the workaround rather than the complaint, and it reads differently enough that a sweep tuned for complaint language misses it. That's a gap in what I search for, not just in how I weigh what comes back.