How to assess the competition before you build a product
Published · By Daily Product Idea · Our methodology
The short answer
List every way your customers can solve the problem today: direct competitors, free and open-source tools, features of the platforms they use, add-ons, free content and the manual workaround. For each, note what it does and where it stops, then state in one sentence what is left. If you cannot name that gap, do not build. If you can, make it the first thing you test.
Expect to find competition
A real problem attracts solutions. If you have found good evidence that people struggle with something, assume someone has already tried to fix it, and go looking. In the research behind Daily Product Idea, this is the dimension that most often lowers an idea's score. Of the 11 researched ideas published by 1 October 2026, differentiation was the lowest of the six scores for 10. Their median differentiation score is 30 out of 100, against a median of 66 for the strength of the problem evidence.
That is not a reason to give up. It shows how early in the process to look. Most of those ideas are still worth testing, but only in the narrow gap the competition leaves.
Look beyond direct competitors
Customers compare you with everything that solves the problem well enough, not just with products like yours. List them all:
- Free and open-source tools. For Flight Deck, a control panel for running several AI coding agents at once, the research found five existing tools covering most of the proposed product, most of them free and open source. For Dropbox for Agents, an existing tool already stores agent knowledge as version-controlled notes across several AI coding tools.
- Features of the platform itself. Flight Deck's research also found reports of the agent tool adding built-in support for one half of the idea, which would turn that half into a standard feature rather than a product.
- Marketplace add-ons. For ReconSheet, which merges recurring CSV exports into one spreadsheet, existing add-ons already watch a folder and merge new files into a master sheet on a schedule.
- Adjacent software that does part of the job. For Deal Floor, trade quoting software already shows the margin on each quote, and free online calculators cover margin, markup and effective hourly rate.
- Free content. For Trade Reality Dossiers, free published guides already overlap two of the seven proposed report sections, so those sections cannot be what people pay for.
- The manual workaround. A spreadsheet, a freelancer or simply putting up with the problem. Often this is the strongest competitor of all, because it costs nothing new.
Compare on the job, not the feature list
For each alternative, write down what it actually does for the customer and where it stops. Then state what is left: the part of the job nobody covers. Be specific and short. If the gap takes a paragraph to explain, it is probably not there.
- LedgerLine: at least seven extraction tools compete, so what is left is remembering how each supplier's invoices are coded, and the review screen. Neither has been tested.
- ReconSheet: merging files is commoditised, so what is left is saved recipes for each client and an exceptions tab that catches a missed or duplicated export.
- Deal Floor: what is left is the whole stack of discounts, fees and unpaid time assembled into one walk-away price.
Evidence or hypothesis?
Competitors are evidence too
A crowded field cuts both ways. It weakens differentiation, but it also shows the problem is real and that people pay to solve it. Explain-Before-Merge's research found a vendor already marketing a near-identical mechanic, which lowered its differentiation to 28. The same finding shows that someone else judged the problem worth building for. Record both effects, rather than letting one cancel out the other.
Turn the gap into the first test
Once you have named what is left, that is what to build and test first. Everything the competition already does well, you can borrow or integrate. Flight Deck's research left one defensible part: reliably telling an agent that needs you from one that has finished. So its first test builds only that, and stops if it cannot beat the existing behaviour. See how to validate a product idea for designing tests like this.
A short checklist
- Search for competitors as soon as the problem looks real, not after you have designed the product.
- List free tools, platform features, add-ons, adjacent software, free content and the manual workaround.
- For each, write what it does for the customer and where it stops.
- State the remaining gap in a sentence. If you cannot, do not build.
- Record what the competition shows about demand as well as what it takes away.
- Make the gap the first thing you test.
Every researched idea on Daily Product Idea records the competitors its research found, and scores differentiation from them. See how ideas are researched and assessed or browse the researched ideas.
Related guides
- How to evaluate a product idea before you build it
Evaluate a product idea by scoring the evidence rather than your enthusiasm: six dimensions, a written reason for each score, the assumptions it rests on and the cheapest test to run first.
- How to choose between two product ideas
Choose between product ideas by comparing their scores dimension by dimension, the evidence behind them, the cost of each first test and your own fit, not their overall totals.
- How to find product ideas worth building
Find product ideas by starting from problems people describe in their own work, not from brainstorms. A practical method with real examples, from the research behind Daily Product Idea.
- How to find problems worth solving
A problem is worth solving when specific people repeatedly have it, it costs them something, they already work around it and you can reach them. How to check each, with examples.
