Open almost any product review meeting and you will hear the same sentence: "Competitor X has it, so we need it too." It feels like rigour. It is usually the opposite, a quiet decision to let a rival set your priorities for you. Done well, competitive and feature-gap analysis is one of the sharpest tools a leader has. Done badly, it turns a strategy team into a copying machine.

The quick version

  • Two different jobs. Competitive analysis asks where the profit and power sit in your market; feature-gap analysis asks which specific gaps in your offer actually matter to customers. Don't confuse them.
  • Map the structure, not just the rivals. Porter's Five Forces (1979) reminds you that suppliers, buyers, substitutes and new entrants shape your fate as much as the competitor across the street.
  • Sort gaps by satisfaction, not by checklist. The Kano model (1984) shows that features fall into very different buckets, basics, performance and delighters, and treating them the same wastes your roadmap.
  • A matched feature is not an advantage. Porter's later warning still holds: copying rivals on the same dimensions converges everyone toward the same place. The move that pays is being deliberately, defensibly different.

The idea in depth

"Competitive analysis" gets used as a catch-all, but it bundles together two jobs that need different lenses. The first is structural: understanding why your market makes money the way it does, and who has the power to take that money away from you. The second is comparative: lining up your product against rivals, feature by feature, to find the gaps. Most teams jump straight to the second and skip the first, which is how you end up with a beautifully detailed feature spreadsheet that answers the wrong question.

Start with the structure: Porter's Five Forces

The most durable tool for the structural job is still the oldest one. In his 1979 Harvard Business Review article "How Competitive Forces Shape Strategy," Michael Porter argued that an industry's long-run profitability is governed not by your direct rivals alone but by five forces: the threat of new entrants, the bargaining power of suppliers, the bargaining power of buyers, the threat of substitute products, and the rivalry among existing competitors. Value created in an industry, in this view, can be drained away by rivalry, bargained away by powerful customers or suppliers, or constrained by substitutes and new entrants (Porter, HBR, 2008 update).

So the move is: before you compare a single feature, spend an hour mapping the five forces around your product. If your buyers can switch in a click, low switching costs, high buyer power, a fancy new feature won't hold them. A structural lock-in might. And if a free substitute is one search away, matching a paid rival's feature is fighting the wrong war. The forces tell you where a feature can earn its keep, and where it can't.

The honest limitation: Five Forces was written for relatively stable, well-bounded industries. It is weaker at capturing fast-moving software markets, platform and network effects, and complements (the iPhone's value comes partly from its app ecosystem, which the original model doesn't name). Use it as a structured way to ask good questions, not as a forecast. It tells you the terrain; it does not tell you the weather.

flowchart TB
  NE(["New entrants
(threat of)"]) --> R
  SUB(["Substitutes
(threat of)"]) --> R
  SUP(["Suppliers
(bargaining power)"]) --> R
  BUY(["Buyers
(bargaining power)"]) --> R
  R(["Rivalry among
existing competitors"])
Porter's Five Forces: rivalry sits at the centre, but four other forces decide how much profit is left to fight over. Leaders Loop

Then sort the gaps: the Kano model

Once you know the terrain, the feature comparison becomes useful, but only if you stop treating every gap as equal. Here the canonical tool is the Kano model, set out by Noriaki Kano and colleagues in their 1984 paper "Attractive Quality and Must-Be Quality" (Journal of the Japanese Society for Quality Control, vol. 14). Kano's insight was that the relationship between a feature and customer satisfaction is not a straight line. Features fall into distinct categories: must-be qualities (basics whose absence enrages people but whose presence earns no credit, a hotel room that locks), one-dimensional / performance qualities (more is linearly better, battery life, page-load speed), and attractive qualities (delighters customers didn't expect and won't miss if absent, but love when present).

What to do with that: tag every gap your competitive analysis surfaces with a Kano category before you rank it. A missing must-be is a fire. Close it now, but know it only buys you the right to compete, not a lead. A performance gap is a dial; invest where customers actually feel the difference. An attractive feature is where genuine differentiation lives, but it ages: today's delighter becomes tomorrow's expectation (in-flight wifi went from wow to assumed in a decade). That decay is why "we matched them on delighters last year" is not a durable position.

The honest limitation: Kano relies on surveying customers with paired functional/dysfunctional questions, and people are unreliable narrators of delight, they often can't name a delighter they've never seen. Treat the categories as a thinking aid that forces the question "what kind of gap is this?", not as a precise measurement. The value is in the sorting, not the decimal place.

The trap: matching is not strategy

The deepest warning comes from Porter again, in his 1996 HBR essay "What Is Strategy?" His argument: operational effectiveness is not strategy. Doing the same things as rivals, only a bit better or with the same features, is easy to imitate and pushes every competitor toward an identical frontier, what he called competitive convergence, where firms become indistinguishable and compete the profit away. A company outperforms, Porter wrote, "only if it can establish a difference that it can preserve" (Porter, HBR, 1996).

A feature you added because a rival had it is, by definition, not a difference you can preserve.

This line should hang over every gap-analysis spreadsheet. Closing must-be gaps keeps you in the game, but a roadmap built entirely from "they have it, we don't" is a roadmap to the industry average. The complementary discipline, choosing what to not do, comes from the Blue Ocean work of W. Chan Kim and Renée Mauborgne (Blue Ocean Strategy, 2005), whose strategy canvas plots your value curve against rivals' so you can see where you are a copy and where you are distinctive. So here is the discipline: for every gap you decide to close, name one dimension where you'll deliberately do less, and one where you'll do dramatically more. A gap analysis that only ever says "add" is a backlog, not a strategy.

A worked example

Consider a mid-market project-management SaaS, call it Cadence (illustrative; figures below are made up to show the method, not real data). Sales keeps losing deals to a louder rival, BigGrid, whose website lists 40 features Cadence lacks. The instinct is to build all 40. Here is the toolkit version instead.

Structure first. A quick Five Forces pass reveals the real pressure isn't BigGrid, it's a substitute: half of lost prospects didn't buy BigGrid, they went back to spreadsheets and a group chat (free, good-enough). Buyer power is high because switching costs are low. That reframes the whole exercise: the job isn't to out-feature BigGrid, it's to give people a reason to leave "free and good enough."

Sort the 40 gaps with Kano. Tagging them: 6 are must-be (single sign-on, mobile app, data export, table stakes that lost-deal notes show prospects assumed and Cadence half-supported); roughly 28 are performance gaps of marginal value (yet more chart types); 3 look attractive (an AI status-summary that drafts the weekly update a manager hates writing). The 28 are the trap, most of the spreadsheet, almost none of the value.

Decide with the convergence test. Cadence fixes the 6 must-be gaps (cost of entry, non-negotiable), ignores the 28, and bets its differentiation budget on one delighter aimed squarely at the substitute, not at BigGrid: making the weekly-update grind disappear. That is a difference it can preserve and a reason to abandon the group chat, which 38 copied features never would have been.

flowchart LR
  G(["Every gap from
the comparison"]) --> K{"Kano
category?"}
  K -->|Must-be| M(["Close it now
(cost of entry)"])
  K -->|Performance| P(["Invest only where
customers feel it"])
  K -->|Attractive| A(["Your differentiation
budget lives here"])
  M --> T{"Does it create a
difference you
can preserve?"}
  P --> T
  A --> T
  T -->|No| X(["Don't build
just to match"])
  T -->|Yes| B(["Build"])
The decision path: a gap earns a place on the roadmap only after it passes both the Kano sort and the "can we preserve this difference?" test. Leaders Loop

Frequently asked questions

How often should we redo a competitive analysis?

The structural pass (Five Forces) ages slowly, once or twice a year, or when something big shifts (a new entrant, a substitute technology, a supplier consolidation). The feature comparison ages fast and is cheap to keep warm; a lightweight running log of rival releases beats a heavyweight annual deck nobody reads. Match the cadence to how fast the thing you're tracking actually changes.

Isn't this just an excuse to ignore what competitors are doing?

No, it's the opposite of ignoring them. You track rivals closely precisely so you can choose consciously which gaps to close and which to leave. Must-be gaps you ignore will sink you. The discipline is refusing to let the comparison auto-generate your roadmap; tracking is input, not instruction.

We're a small team with no analysts. Is this realistic?

Yes, and arguably more important for you, because you can't afford to build the wrong 28 features. The minimum viable version is one afternoon: a one-page Five Forces sketch, a list of rival gaps from your last ten lost-deal notes, and a Kano tag on each. No software, no analyst, just the two questions, asked honestly.

How do I tag a feature as must-be vs attractive without a full Kano survey?

Use your existing evidence before commissioning research. Must-be features show up in lost-deal notes and churn reasons as dealbreakers ("you don't even have X"). Attractive features rarely appear in those notes at all, because customers don't ask for what they can't imagine, they surface in user interviews as "oh, that would save me an hour." If you genuinely can't tell, that's the signal to run the paired-question survey for that item.

What's the single most common mistake?

Treating feature parity as the goal. Parity on must-be features is the cost of entry; parity on everything else is convergence, which Porter showed competes the profit away. The most common failure is a roadmap that is entirely "catch up," with no line item for "be different."

Related in the Toolkit

Where to go next