How to Do Competitor Analysis

When many people hear “competitor analysis,” they immediately think of opening several similar product websites, taking screenshots, copying the feature lists, and making a table: Product A has this, Product B has that, Product C has something else. The final conclusion is usually vague: this product has complete features, that one is expensive, another one has a nicer interface. It looks like research, but when it is time to build, you still do not know what to do.

The problem is not that competitor analysis is useless. The problem is that most people analyze the wrong thing. What you really need to analyze is not what features competitors have. You need to understand why users choose them, why users keep paying, why users complain, and why users still search for alternatives. Features are only the surface. The opportunity is underneath. A button, a template, an export format, or an automation flow matters only because it reduces a specific cost for a specific user.

So competitor analysis is not about proving that others are already strong, and it is not about finding a product to copy. Its purpose is simple: in a market where demand has already been validated, find users, scenarios, and entry points that are still underserved. After reading this lesson, you should be able to turn “looking at what others built” into “judging where I can still enter.”

Start by Separating Three Types of Competitors

Beginners often analyze only direct competitors. If they want to build an AI resume tool, they search for AI resume builders. If they want to build an SEO tool, they look at Ahrefs, Semrush, and Ubersuggest. If they want to build an image compression tool, they only compare similar websites. This is necessary, but it is not enough.

You should separate competitors into at least three groups. The first group is direct competitors: products that solve the same problem, serve similar users, and use a similar delivery format. They tell you the current market standard: core features, common pricing, landing page structure, acquisition messaging, and user expectations.

The second group is indirect competitors. These products may not look like yours, but users use them to solve the same problem. A user may not use a dedicated AI resume builder. They may use ChatGPT, Notion templates, Google Docs templates, job search courses, or a human resume editing service. Indirect competitors are often more important because they reveal real substitute behavior.

The third group is manual-work competitors. These may not be products at all. They may be spreadsheets, screenshots, copy-paste workflows, outsourcing, group chats, browser bookmarks, or internal SOPs. Many indie product opportunities hide here. Users are already solving the problem, but the current method is slow, clumsy, or error-prone. If you only look at software competitors, you will miss these real needs.

For example, if you want to build a cover image generator for Xiaohongshu creators, direct competitors are similar cover tools. Indirect competitors are Canva, design template sites, and Figma templates. Manual competitors may be users duplicating an old design file and manually changing text every time. The opportunity may not be building a larger design platform. It may be making the small workflow of choosing a template, changing a title, exporting the right size, and batch-generating covers much faster.

Do Not Look at Features First. Look at Who It Serves

The same product can mean very different things depending on who it serves. If a competitor’s homepage says “AI writing assistant,” do not only record that it has rewriting, summarizing, translating, and expanding features. Ask a deeper question: who is it really for? Students, marketers, ecommerce sellers, lawyers, developers, teachers, or content teams? Is it solving writing quality, efficiency, conversion, or compliance risk?

When judging target users, do not rely only on homepage slogans. Look for stronger evidence. The pricing page reveals whose money the product wants. Case studies reveal what kinds of customers it already serves. Template libraries reveal frequent use cases. Blog posts and SEO pages reveal which keywords it wants to capture. User reviews reveal what people actually use it for.

Many products look general on the surface, but revenue often comes from a few high-value scenarios. A screenshot beautification tool may be used occasionally by casual users, but the users who keep paying may be developers, product managers, course creators, or marketing teams. If you only copy the features, you will build a generic tool. If you understand the paying audience, you may find a more vertical entry point.

The first table in competitor analysis should not be called a feature comparison table. It should be a user and scenario table. Useful fields include product name, target user, core task, why the user needs it now, promised result, main paying audience, and most frequent use case. Once you fill this table, you will often find that many competitors are not fighting for exactly the same users.

Pricing Pages Are More Valuable Than Homepages

A homepage is designed to attract attention. A pricing page reveals business logic. How a product charges is often more honest than how it describes itself. Seat-based pricing suggests team collaboration. Usage-based pricing suggests cost or value grows with volume. Pricing by projects, exports, contacts, keywords, or credits tells you which metric the product treats as the core unit of value.

When reading a pricing page, record at least four things. First, what does the free plan restrict? Restricted features are usually the parts the product believes are most valuable and most likely to drive upgrades. Second, what is the lowest paid price? This helps you judge user purchasing power and market expectations. Third, what appears in higher tiers? Advanced features often reveal the needs of high-value users. Fourth, is there an enterprise plan? If yes, the product may already serve more complex organizational scenarios.

Pricing pages also help you judge whether an indie builder has room to enter. If leading competitors start at a high price, are feature-heavy, and require a sales process, individuals and small teams may be underserved. A lightweight, lower-priced entry point may exist. But if leading products already have a free plan, low-cost plan, templates, plugins, APIs, team features, and very detailed segmentation, you need to be more cautious.

For example, if an SEO tool starts at $129 per month, that may be too expensive for solo site owners and early indie builders. If these users only need long-tail keyword tracking, basic site checks, or content update reminders, you do not need to build a full Ahrefs clone. You can build a narrower, cheaper tool for small sites. The opportunity is not “more features than the competitor.” It is “serving users the competitor’s price and complexity do not cover well.”

User Reviews Reveal the Real Gaps

A competitor’s website tells you what it wants you to believe. User reviews tell you what users actually experience. Look at Product Hunt, Reddit, G2, Chrome Web Store, App Store, Google Play, YouTube comments, Twitter, niche communities, and blog comments. Do not only read five-star reviews or one-star complaints. Look for repeated concrete phrases.

High-value reviews often fall into several patterns. The first is “too expensive, is there a cheaper alternative?” This may reveal a price entry point. The second is “too complicated, I only need one feature.” This may reveal a lightweight product opportunity. The third is “it does not support this platform or language.” This may reveal a platform, localization, or integration opportunity. The fourth is “I have tried many tools, but none fit my use case.” This may reveal an underserved niche scenario.

The most important part of review analysis is not collecting a few quotes. It is counting repetition. One complaint may be an individual case. Ten people on different platforms complaining about the same thing in different words is a signal worth studying. You can split reviews into problem, frequency, impact, current workaround, user identity, and willingness to pay. Then you are no longer looking at emotions. You are looking at opportunity clues.

Many product ideas do not come from inventing new demand. They come from translating complaints into products. If users say “this tool is too bloated,” translate it into “solve one frequent action.” If users say “the export format does not fit my platform,” translate it into “build platform-specific export.” If users say “I have to manually change this every time,” translate it into “automate the repeated step.” Products are not imagined from nothing. They are extracted from user dissatisfaction.

Break Competitors Into Acquisition, Conversion, and Retention

Many people analyze only the product itself and ignore how the competitor gets users. For indie builders, acquisition can matter more than features. A product may not be technically complex, but if it already has stable traffic through SEO, template libraries, free tools, marketplaces, affiliate marketing, or a content engine, you cannot only ask “Can I build this?” You also need to ask “Can users find me?”

The first line is acquisition. Where does traffic come from: Google keywords, Product Hunt, Reddit, YouTube, Twitter, Chrome Web Store, App Store, template directories, tool directories, partners, or word of mouth? If it relies on SEO, study the long-tail keywords it covers. If it relies on a marketplace, study review count and ranking. If it relies on content, study topics and publishing frequency.

The second line is conversion. How does it turn visitors into trial users? Does it offer a free tool? Does it require signup? Can users preview templates? Can they experience the result before paying? Does it use case studies, comparison pages, alternative pages, or price anchors? A strong competitor guides users from “I am just looking” to “I will try it.” Analyze this path to understand user decision-making, not to copy it blindly.

The third line is retention. How does it make users come back? Does data accumulate? Is the workflow frequent? Does it include reminders, reports, collaboration, history, automation, integrations, or team permissions? Many products look easy to build but have weak retention because users leave after one use. If a competitor charges continuously, it is usually not because the homepage looks good. It is because the product is embedded in a repeated workflow.

End With an Opportunity Judgment Table

At the end of competitor analysis, you should not be left with only screenshots and links. You should produce an entry judgment. Use one table to bring the information together:

Competitor name
Target user
Core scenario
Main pricing model
Common user complaints
Existing solution gap
Possible entry point
Acquisition channel
Entry difficulty
Worth validating further?

The point of this table is not to choose the easiest product to copy. It is to identify where there is still room. You may find that many competitors serve large teams, while individuals find them expensive. Many products may be complete but too hard to start using. Many tools may serve the English market well, but local users struggle. Many products may be platforms, but none handles one frequent action extremely well. These are the entrances indie builders should care about.

You can also score each direction: user pain, willingness to pay, competitor strength, differentiation room, acquisition difficulty, and development difficulty. The scores are not meant to create fake precision. They are meant to keep intuition under control. Some directions look attractive but have strong competitors, expensive acquisition, and high switching cost. Other directions look small but have clear pain, clumsy substitutes, and users willing to pay.

Good competitor analysis should end with one specific sentence: I am not building a generic similar product. I am serving this user, in this scenario, solving this gap competitors have not handled well, with a lighter way to enter. If you cannot write this sentence, your analysis is still too shallow.

Do Not Turn Competitor Analysis Into Self-Discouragement

Competitor analysis has one common side effect: the more you look, the more you feel everyone else is too strong and there is no chance left. You see polished websites, complete features, beautiful screenshots, customer stories, and funding news. Then you decide the market is already over. But this is not analysis. It is being intimidated by surface scale.

Mature products have mature-product problems. They serve more people, so it is harder for them to go deep for one small group. They have more features, so it is harder to stay simple. They charge more, so they often ignore low-ticket users. They have larger organizations, so they respond more slowly to niche requests. An indie builder’s opportunity is not to beat a big product head-on. It is to find a small scenario the big product cannot do deeply, quickly, or cheaply enough.

But do not become blindly optimistic just because you find a few complaints. User complaints do not automatically mean users will pay. A missing feature does not automatically mean you should build it. A large market does not automatically mean you can acquire customers. Competitor analysis is a filter, not a conclusion. The real next step is low-cost validation: post in communities, interview users, build a landing page, collect emails, run small ads, or manually deliver the service to see whether real users take action.

Summary

Competitor analysis is not copying features or making a screenshot report. Its core purpose is to understand how users currently solve the problem, why they pay, why they remain unsatisfied, and whether you can enter with something lighter, more specific, and closer to the real scenario.

If you only look at features, you will become more and more like everyone else. If you look at users, scenarios, pricing, reviews, acquisition, and retention, you may find your own position. Valuable competitor analysis does not simply tell you “someone is already doing this.” It tells you “which small group of users is still underserved inside this market.”

Homework

• Choose 1 direction you want to build and find 10 direct competitors, 5 indirect competitors, and 5 manual-work alternatives.
• For each competitor, record target user, core scenario, pricing model, free-plan limits, and main acquisition channel.
• Collect at least 50 user reviews and classify repeated complaints by price, complexity, platform support, use case, export format, and service experience.
• Write 3 possible entry points. For each one, explain in one sentence who it serves, what gap it solves, and why existing competitors have not solved it well.

Next Lesson

Is a Project Worth Copying? The question is not whether you can replicate the product, but whether you can handle the acquisition, delivery, and payment conditions behind it.