Ask most teams to run a competitive analysis and you'll get the same deliverable back: a spreadsheet with competitor names down the left, feature names across the top, and a grid of checkmarks in between. It's thorough-looking, it's easy to build, and it answers a question nobody in the room actually asked.
A competitive analysis exists to change a decision. If it doesn't, it's not strategy work — it's a reference document that happens to mention competitors.
Start with the decision, not the competitor list
Before naming a single competitor, name the decision the analysis needs to inform. Pricing, positioning, market entry, product roadmap, a fundraising narrative — each of these needs an entirely different competitive question answered.
A pricing decision needs competitors' actual price points and packaging logic, not just published rate cards. A positioning decision needs their messaging and, just as importantly, who they're clearly not targeting. A market entry decision needs a read on how saturated and defended the space already is, and by whom.
If the decision the analysis needs to inform can't be stated in one sentence, the research isn't ready to start — the competitor list will just expand to fill the time available, without ever producing something actionable.
A feature matrix measures activity, not advantage
Feature comparison spreadsheets are seductive because they're easy to build and look thorough — every competitor gets a row, every feature gets a column, and checkmarks fill in the grid.
The problem: the presence of a feature doesn't mean advantage, or even usage. A checkmark treats a competitor's flagship, heavily-used capability the same as a feature that shipped once and shows up in nobody's actual workflow.
What matters more than presence is which features a competitor is actively messaging around — that signals what they believe is winning them deals. Where complaints cluster on review sites signals real gaps, not assumed ones. And where pricing reflects confidence versus where it reflects discounting signals which parts of the market are actually contested.
The best sources are the competitor's own words
Primary competitive data should come from a competitor's own public materials: website copy, pricing pages, release notes, job postings, and investor materials where they're public. Job postings in particular are underused — they reveal where a company is actually investing engineering and go-to-market effort well before that shows up in marketing.
Secondary sources — industry reports, analyst commentary — supplement but don't substitute. They're frequently outdated by the time they publish, and they rarely reflect the specific decision a given business is facing.
Customer reviews are one of the most underused primary sources available. Complaints on G2, Capterra, Trustpilot, or industry-specific review platforms reveal where a competitor is genuinely vulnerable. Praise reveals what's actually driving retention — which is often different from what the competitor's own marketing emphasizes.
What a strategy-grade competitive analysis produces
Not a spreadsheet. A short set of findings, each one tied directly back to the decision at hand: where competitors are strong enough that competing head-on there would be expensive and slow; where they're vulnerable and what specifically opens that gap; how they're priced and positioned relative to where a business is considering entering; and what's likely to happen if the move under consideration actually gets made — whether a competitor's existing customer base would even notice, or whether the move touches their core positioning closely enough to provoke a real response.
Each finding should end with an implication for the decision being made, not just a description of what was found.
This matters as much for a fundraising deck as it does for a go-to-market plan — a market research section built on descriptions instead of findings reads as due diligence theater, and investors who've seen enough pitch decks can tell the difference.
A quick gut check before you commission (or run) one
Two questions cut through most of the scoping conversation: Can the specific decision this needs to inform be named? And is this a reference document, or an input to a decision that has to get made in the next few weeks?
If the honest answer to the second question is "reference document," it's worth scoping down. Competitive landscapes move fast enough that a comprehensive reference build goes stale before anyone circles back to actually use it.
Bottom line
A competitive analysis is a strategy tool that happens to involve competitors — not a competitor-tracking exercise that happens to touch strategy. That distinction is what determines whether the output changes a decision or sits in a folder.