How do I study my competitors without copying them?

A pre-launch founder came to us carrying a colour-coded spreadsheet. Every competitor feature mapped, ranked, and colour-coded by priority. It was genuinely impressive work. And it told us almost nothing about whether the product he was building would succeed. The spreadsheet showed what already existed. It showed nothing about what was missing, what was failing users, or where the genuine opening was. That is not a criticism of the founder. Competitive mapping feels like rigour because it is tangible. You can point to a cell and say "we have that". But the question that actually matters is whether having it means anything to the person you are building for.

The question that matters is not what competitors have built, but what they have chosen not to do.

Competitor analysis done well is one of the most useful things a product team can do. Done badly, it produces a copy of whatever already exists, with slightly different colours. The difference between those two outcomes is not how much you look at competitors, but what you are looking for when you do.

This article works through how to study a market without becoming a mirror of it, and how to turn what you find into design and positioning decisions that are genuinely yours.

What competitor analysis is actually for

The point of studying competitors is to understand the assumptions your market has made so you can decide which ones to accept and which to question. Every product in a category makes dozens of implicit decisions: about what users want, how much they know, what they are willing to do, what would frustrate them. Those decisions solidify over time. They start to look inevitable. Studying competitors well means noticing those decisions before they become invisible to you too.

There is a practical side too. Understanding what a competitor charges, how they structure onboarding, where users drop off, and what complaints appear in their reviews gives you a map of where the category is currently sitting relative to the people using it. That is useful starting data. The error is treating it as the end point.

Founders gravitate toward feature mapping partly because it offers immediate validation of what they already believe. Nothing in a spreadsheet can tell you the idea is wrong. User research can, which is exactly why it feels riskier. But a competitor audit that does not eventually connect to how real people feel about the category is an exercise in confirming your own assumptions by a different route.

Mapping what competitors have chosen not to do

Every product leaves something out. The more time you spend with a competitor's product, the more legible those omissions become. Some are gaps the company has not noticed. More often, they are deliberate tradeoffs: a fitness app that strips back social features to focus on pure tracking, a skincare brand that avoids personalisation to keep the proposition simple. The team made a call. You can disagree with it.

A useful exercise is to write down everything a competitor's product does not do, and then ask why. Three explanations tend to cover most cases.

• The team does not think users want it
• The team could not work out how to do it well
• The team decided it was out of scope for their positioning

Each of these creates a different kind of opening. A gap that exists because a team could not solve a design problem is a technical challenge. A gap that exists because of a positioning choice is a question about whether that choice was right. A gap that exists because the team underestimated what users want is the most interesting one, because it points to something the whole category is failing to give people.

For each competitor, list five things their product does not do. Then ask whether that omission is a weakness, a deliberate choice, or an assumption about users. The third category is where the most useful territory sits.

Reading the assumptions baked into competitor products

Every design decision is a bet on how users behave. The onboarding flow assumes users have a certain amount of patience. The pricing structure assumes they will stay long enough to justify a subscription. The navigation assumes they already understand the category. When those bets are wrong, users leave and teams rarely know why, because the assumption was never surfaced as a decision.

Reading a competitor product for its assumptions is a different skill from reading it for features. You are not asking what it does. You are asking what it expects of the person using it.

A common assumption we find baked into wellness and fitness products is that users arrive already motivated. The product is built for someone who has already decided to change. The onboarding is short, the friction is low, and the first session starts immediately. That works for the people who stay. It explains why so many people download and then disappear: the product was not designed for the version of them that actually showed up.

When clients say a competitor feels more intuitive, they are usually describing a product they already understand.

When clients tell us a competitor's product feels more intuitive, they are often also describing a product whose overall purpose they already understand. That understanding bleeds out into how individual features feel. Once a user grasps what a product is for and trusts it, the specific flows feel obvious within that established frame. Strip that context away and the same interaction design can feel confusing. You cannot lift a sequence of steps from a competitor and drop it into your product and expect the same clarity. The brand is different, the context is different, the use case is different, and all of that changes what "intuitive" means in practice.

Why feature parity is not a strategy

There is a meaningful body of research showing that matching a competitor's features does not produce equivalent results. A Bain & Company study across nearly 400 organisations found that 80% of companies believed they delivered a superior customer experience, while only 8% of customers agreed. The gap between what teams build and what users actually experience is rarely closed by adding more of what competitors already offer.

The deeper problem with feature parity as a goal is that it keeps you permanently behind. You are always reacting. The competitor launched something, you put it on the roadmap, you ship six months later into a market where that feature is now expected as standard. Meanwhile, the thing that would actually distinguish your product is sitting in your users' complaints and your competitors' negative reviews, unread.

Feature parity also assumes that context does not matter. Taking a feature from a product that operates in one scenario and implementing it in a product with a different user base, different emotional context, and different purpose will not necessarily produce the same outcome. A social sharing mechanic that works beautifully in an activewear community might feel invasive in a mental health app. The feature is not the thing. The fit between the feature and the specific context it lives in is the thing.

Before adding any feature that a competitor has, ask what job a user would hire it to do in your product specifically. If the answer is different from why it works in the competitor's product, the feature needs rethinking before it gets built.

Using adjacent markets when no direct comparison exists

Products that do something new often have no direct competitor to study. That does not mean competitive analysis is off the table. It means expanding the frame to find products that solve some part of the same problem, serve a similar emotional need, or operate in a similar relationship with their users.

We used this approach when working on a niche trading platform where no direct equivalent existed. To validate the revenue model, we identified products that performed some aspects of what the platform would do, examined their subscription structures and revenue figures, and built projections from there. Where a comparable product already had strong traction in the market, we scaled our projections down significantly to reflect the reality of launching a new product into the same space. The benchmarks were not direct, but they were far more grounded than working from nothing.

Adjacent market analysis works best when you are explicit about where the analogy holds and where it breaks down. A hospitality brand studying how a premium skincare brand handles personalisation is looking for the underlying logic: how does a high-consideration purchase work when the customer cannot touch or try the product before buying? That question transfers. The specific answer does not.

Where to look for adjacent reference points

Start with the emotional job the product does. A wellness supplement brand asking what adjacent products do the same emotional work will find references in premium food and drink, in fitness and coaching, and in medical devices. Each of those categories has solved different parts of the same problem. The useful question is not "what features do they have" but "what belief about their user does this product rest on."

What user research reveals that competitor mapping cannot

Competitor analysis tells you what teams have decided to build. It does not tell you whether those decisions worked, or whether the people using the products are actually satisfied. Those are different questions, and they require different methods to answer.

User research gets to the emotional texture of a category in a way that product audits cannot. What do people find frustrating about their current process? Where do they feel embarrassed, anxious, or confused? What workarounds have they built because no product has solved the problem properly? Those answers do not appear in a competitor's feature list. They appear in conversations with real users, and they are the source of the most defensible product decisions.

We ran into this dynamic on a project for a grassroots football product. The competitive mapping looked complete. The feature set was solid. But when we sat with users, we found that the emotional context around the product had been almost entirely missed: the anxiety about group dynamics, the social awkwardness of certain interactions, the moments where the product created friction precisely because it did not account for how people actually felt in the situation. None of that was visible from studying what competitors had built.

The reluctance to do user research before competitive analysis is understandable. Research takes time, costs money, and might tell you something you do not want to hear. But a competitor audit that runs without it is working from incomplete information, and the gap tends to surface later, at much greater cost.

Turning gaps into design and positioning decisions

Identifying a gap in the market is not the same as having a position. The gap is just the starting observation. The question that follows is whether the gap exists because there is genuine unmet demand, or because the demand is not there. Those are very different situations that look similar until you test them.

The workshop process we use to help clients translate gaps into decisions involves mapping what the brand actually is before auditing what competitors are doing. One of the exercises we run is what we call the dinner party: we ask clients to picture their product as a person. How does that person dress, how do they talk, are they the loudest voice in the room or the quiet one in the corner? Once that personality is defined, it becomes much easier to look at competitor positioning and ask whether your product would do it that way, or differently, and why. It gives you a concrete human benchmark to measure every positioning and design decision against.

From there, gaps become actionable in a structured way.

1. Name the gap precisely: what is the competitor not doing, and for whom does that matter?
2. Test whether the gap represents real demand or a deliberate tradeoff by the competitor
3. Ask whether your brand, as defined, is the right one to fill it
4. Translate the answer into a specific design or copy decision, not a general direction

Run the dinner party exercise before any competitive audit, so you have a clear picture of your brand's personality before you start comparing it to others. Without that anchor, competitor features and positions tend to pull the brief in directions that do not belong to you.

Conclusion

Competitive analysis is not the problem. The problem is treating it as a destination rather than a starting point. A thorough map of what competitors have built, what they have left out, and what assumptions sit beneath their decisions is genuinely valuable data. It becomes a liability when it replaces the harder work of understanding how real users feel about the category and what they are still not being given.

The founders and product teams who get the most from competitor research are the ones who use it to ask better questions of their users, not to avoid asking those questions altogether. The spreadsheet and the user interview are not in competition. The spreadsheet tells you where to look. The interview tells you what you are actually seeing.

The opening we worked through with the grassroots football product, and the approach we built for the niche trading platform, both came from combining a clear read of the competitive landscape with a direct understanding of how users were experiencing the problem. Neither was enough on its own. Together, they produced decisions we could actually defend, and a product position the market had not already claimed.

If you are in the process of mapping your market and want to make sure the analysis you are building from is complete, let's talk about your competitive strategy.

Frequently Asked Questions