Map Three Layers, Not One
Direct competitors solve the same problem the same way you plan to. If you are building project-management software, they are the other project-management tools. These are the obvious ones, and they are also the least useful to obsess over, because every founder already sees them.
Indirect competitors solve the same problem a different way. For a project-management tool, that includes shared spreadsheets, a Slack channel with pinned messages, or a weekly standup. They serve the same job-to-be-done with a different shape. Substitutes are even broader: the customer doing nothing, hiring a person, or duct-taping three free tools together. The status quo is almost always your biggest competitor, and it never shows up on a feature-comparison chart.
Write all three layers down explicitly. The reason matters: if you only beat the direct competitors but lose to 'a spreadsheet that is already good enough,' you have built something nobody switches to. Most failed products lose to the status quo, not to a named rival.
- Direct: same problem, same approach (the named rivals).
- Indirect: same problem, different approach (manual workarounds, adjacent tools).
- Substitute: doing nothing, hiring someone, or stitching free tools together.
Find Competitors the Way Customers Actually Do
Do not rely on your own knowledge of the market. You know the polished, well-funded players. Your customers find solutions through messier paths, and those paths reveal competitors you would never list from memory.
Search the exact phrases a frustrated customer would type. 'How do I track X in a spreadsheet,' 'best way to manage Y,' 'X alternative,' and '[big tool] is too expensive.' Read the Reddit threads, the Stack Overflow answers, the 'we switched from' blog posts. Check what tools appear in G2 and Capterra 'compared to' sections. Each one is a competitor your customers are weighing right now.
Pay special attention to the workarounds people describe with pride. When someone says 'I built a Notion template that does all this for free,' that template is your competitor, and the fact they are proud of it tells you the bar you have to clear.
- Search '[category] alternative' and '[incumbent] too expensive' to find who people compare.
- Read 'we switched from X to Y' posts for real switching triggers.
- Note every DIY workaround mentioned, that is your substitute competition.
Build a Comparison That Tells You Something
Feature checklists are mostly theater. Everyone has every feature, or claims to. Instead, compare the things that drive a buying decision: who exactly each competitor is built for, what they are priced for, where they are obviously strong, and what they have chosen to ignore.
The most useful column is 'who they are NOT for.' Every product makes tradeoffs. A tool built for 200-person enterprises is, by design, too heavy and too expensive for a solo freelancer. That deliberate exclusion is an opening. The customers a competitor has decided not to serve are the ones who might switch to you fastest.
Capture pricing tiers, the smallest plan, and what triggers an upgrade. Pricing reveals positioning more honestly than any marketing page. A tool with a $500 minimum is telling you who it does and does not want.
Mine Reviews for the Gaps Money Leaks Through
This is where competitor analysis stops being a chart and starts being a strategy. Pull the reviews from G2, Capterra, the App Store, Trustpilot, and Reddit, and read them for patterns, not stars. A four-star average hides the exact complaints that send customers looking for an alternative.
Sort by the lowest ratings and the 'most helpful' negative reviews. Look for the same frustration repeated by different people: 'support takes a week to reply,' 'the mobile app is unusable,' 'it does X but you have to pay three tiers up.' Repetition is signal. One angry review is noise. Fifteen reviews naming the same gap is a roadmap.
Distinguish two kinds of gap. A fixable gap (slow support, a missing integration) the incumbent can close any quarter, so it is a weak moat for you. A structural gap (too complex by design, priced for enterprises, locked into a legacy architecture) they cannot close without alienating their core customer. Structural gaps are the ones worth building on.
- Read the 1- and 2-star reviews first, that is where the switching reasons live.
- Count repeated complaints. Frequency is the signal, not severity.
- Separate fixable gaps from structural gaps. Build on the structural ones.
Turn the Analysis Into a Decision
The output of a competitor analysis is not a tidy grid. It is a single honest answer to one question: is there a specific group of customers who are underserved by everyone currently taking the money, and can you serve them better in a way the incumbents will not copy?
If the answer is 'the market is crowded but everyone ignores small teams and the reviews are full of small teams complaining,' you have a wedge. If the answer is 'every competitor is excellent, well-loved, and cheap,' that is a kill signal, and finding it now saved you a year of building. Olune's whole point is to reach that verdict before you write code, not after.
Write down the one gap you will attack and the evidence behind it. Then go talk to the people leaving those reviews and confirm they would actually switch and pay. Reviews tell you the wound. Conversations tell you whether it hurts enough to act on.