Read enough competitive analyses and a pattern appears. Under “competitor weaknesses” you will find entries like:

  • Smaller team than us
  • Less funding raised
  • Founded more recently
  • Lower revenue
  • Fewer customers

Each of these is a fact. None of them is a weakness. Treating them as one is the most common reasoning error in competitive analysis, and it is worth having a name and a test for it.

The test

Invert the claim. If the opposite would also read as a weakness, it is not a finding.

Apply it to headcount. “They have a smaller team” reads as a weakness — less capacity, slower shipping, thinner support. Now invert: “They have a larger team.” That also reads as a weakness — higher burn, slower decisions, more coordination overhead, more to justify at the next raise.

Both directions sound bad. That means the observation is carrying no information; the analyst is supplying the negative interpretation, and would have supplied it either way.

Run the same test on the rest:

  • Less funding → under-resourced. More funding → growth expectations they cannot meet, pressure to move upmarket.
  • Founded recently → unproven. Founded long ago → legacy architecture, aging customer base.
  • Fewer customers → unvalidated. More customers → support strain, slower to change.

Every one fails. These are not weaknesses; they are dimensions on which a company has a position, and the position alone tells you nothing.

Why it happens

Two reasons, both structural rather than careless.

The first is that comparison to yourself feels like analysis. If you have 200 people and they have 40, the difference is salient, and salience gets mistaken for significance. But you are not the benchmark for whether their team is adequate — their obligations are.

The second is that competitive analyses are usually read by people who would prefer the competitor to be weak. An analysis full of these entries is comfortable, gets approved quickly, and produces no uncomfortable follow-up questions. It is also useless, which is discovered later.

Turning a non-finding into a finding

The fix is not deleting the observation. It is doing the work the observation was standing in for.

“They have 40 people” becomes a finding when you connect it to an obligation:

They have roughly 40 employees, of whom public profiles suggest 6 are in support. They publish a one-hour response SLA on their top tier. At their stated customer count that ratio is unusually thin, and support response is the most frequent complaint in their recent reviews — which is consistent with a team stretched against a commitment they made when they were smaller.

That passes the inversion test, because the opposite would not read the same way. It is grounded in a specific commitment they made, evidence about whether they are meeting it, and a mechanism connecting the two.

The general form: a number becomes a weakness only when paired with a commitment it fails to meet.

The same error in reverse

It also runs the other way, as unearned strengths. “We have more engineers” is not a strength unless you can show it produces something — faster shipping, broader coverage, better reliability. Plenty of large engineering teams ship more slowly than small ones.

Apply the test symmetrically or you will produce an analysis where every difference happens to favour you, which is the tell of a report written to be approved.

Where it does the most damage

Three places, in increasing order of cost:

In battlecards. A rep who says “they're a smaller company” to a buyer who values responsiveness has just made the competitor's case. See proof points vs claims.

In strategic planning. A competitor dismissed on size grounds gets under-monitored, which is precisely how emerging competitors become established ones.

In investment decisions. Company assessments built on this error mistake stage for quality, in both directions.

The habit worth building

Before any entry lands in a weakness or strength column, invert it. It takes seconds and it removes a substantial fraction of a typical analysis — which is the point. What remains is shorter, defensible, and actually says something.

Our Competitive Intelligence report applies this test as a standing rule: a gap has to name the commitment it fails against, or it does not appear. It is why the weakness sections in those reports tend to be shorter than clients expect, and more useful.