HomeGuides › Competitor mapping

Competitor-mapping frameworks that survive an IC

Framework · ~8 min read · public-methodology

Most competitor slides are logo soups — a grid of names with no axes and no argument. An investment committee doesn't want to know who exists; it wants to know where the whitespace is, who you'd actually collide with, and why not just keep doing it the old way. A map that answers those survives the room. Here's how to build one deterministically, so the same players always land in the same place.

Step 1 — pick two axes that trade off

A 2×2 only means something if the two axes capture a real tension. Pick from a fixed vocabulary so the map is comparable across sectors:

The classic pairing is capability × scale: it separates "great product, small footprint" from "big footprint, ageing product," which is exactly the whitespace a new entrant argues for.

Step 2 — score each player 0–100 from public evidence

Every score is analyst-assigned from public evidence — disclosed funding, install-base statements in filings, product docs — and carries a citation slot. A player mapped without a source doesn't ship. Players above the 50 midpoint on an axis are "high"; below, "low." That splits the map into four quadrants:

High capability · High scale
Leaders
Established, hard to displace head-on.
Low capability · High scale
Specialists / incumbents
Big footprint, product ageing — displacement targets.
High capability · Low scale
Challengers
Strong product, small footprint — where you'd collide.
Low capability · Low scale
Laggards
Neither — usually not the real threat.

A composite rank (the mean of a player's provided scores) gives the "who to watch" ordering underneath the map — deterministic, so it's reproducible.

Step 3 — the mandatory status-quo row

This is the row that separates a real map from a logo soup. Every committee asks the same question: "why not just keep doing it the old way?" So the framework requires a "status quo / do-nothing / DIY" entry — manual process, incumbent conveyor, in-house spreadsheet — sized like any other competitor.

warehouse-robotics example: Global AMR incumbent — leader Fulfilment challenger $600M funding Piece-picking startup $250M funding Manual + conveyor (status quo) ← mandatory row

If the status-quo row is missing, the engine raises a warning and the map isn't considered complete. Half of all deals lose to "do nothing," and a map that pretends otherwise gets torn apart in the room.

The IC's real question isn't "who are the competitors." It's "where's the defensible whitespace, and what happens if the customer does nothing." A two-axis map with a status-quo row answers both on one slide — which is why the framework enforces both rather than trusting the analyst to remember.
Honest caveat. Funding and scale figures are only as good as their sources — disclosed rounds, filings, named-byline press. Private-company numbers are often stale or self-reported; a real report cites each and flags where a figure is a company disclosure rather than a filing. See sourcing citable market claims.

Get a scored competitor map for your sector

Every commissioned report includes a two-axis positioning map with the mandatory status-quo row and a cited attribute table.

See it in the sample → Commission a cited report