Every founder has one. A tab called Competitor Comparison, last touched seven weeks ago, with green dots and red dots that no longer match what's on the competitor's pricing page. The cells list internal feature names — "SSO v2", "Slack integration beta" — that mean nothing to the people who lost the last deal.
The matrix isn't the problem. A product team needs to know what competitors offer vs. what they offer. The problem is that most matrices are built to be filled in rather than used. They die within a quarter because nothing in them drives a decision.
of internal feature comparison spreadsheets become shelf-ware inside 60 days of creation
Not because the data is wrong — because it never produced a decision. The matrix is treated as documentation, not as an input to a build/match/ignore choice.
The matrix that works — the one a road-mapping conversation actually opens — has four properties. It is structured around the buyer, not the codebase. It scores on what matters, not what is easy to count. It is small enough to read in five minutes. And it terminates in an action that has an owner and a date.
1. Why Spreadsheets Fail: The Four Failure Modes
Before redesigning the matrix, it helps to name the failure modes that make the current one useless. They show up everywhere — across every company I've reviewed — and they're diagnostic.
- Row drift. The competitor added a feature. The matrix doesn't have a row for it. Or the row exists but is six weeks stale. The matrix lies about the present, so the team stops trusting it.
- Internal naming. Rows are written in engineering language ("onboarding flow v3 with retry logic") instead of buyer language ("set up a new workspace in under 10 minutes"). Buyers don't recognize these names on calls.
- Resolution at the wrong level. A green dot vs. a red dot hides whether the competitor's feature actually solves the buyer's problem. Your "AI assistant" and theirs can both be live and still be 18 months apart in capability.
- No terminal action. The matrix ends at the cells. It never connects to a build, a match, an ignore, or a de-prioritize decision — so there's no reason to keep it current.
2. What a Good Matrix Looks Like
The single highest-leverage change is to flip the orientation: rows are buyer capabilities, not internal features. Competitors sit as columns, and your product sits as one column among them. Every row is a sentence a buyer would say on a sales call.
Buyer-capability rows do three things internal names can't. They're stable across release cycles (a "report export" capability is the same thing your v1 export and your v4 export both do). They're comparable across competitors without translation. And — most importantly — they map directly to win/loss data, so you can validate the gap with real deal evidence.
What does the buyer get done?
The buyer-facing outcome the capability produces. "Get a new team member productive in under an hour." Phrased in prospect language. The single highest-leverage row category.
What gets in the way?
The setup, integration, or learning-curve friction the buyer experiences. "Requires admin credentials to install." Differs sharply between products even when outcomes match.
How deep does the capability go?
The dimension of the capability that matters: scale, customization, automation. "Custom rules per workflow" is depth; whether the workflow exists at all is coverage.
How does pricing fit the buyer's usage?
Whether the cost scales linearly, plateaus, or has cliffs — and at what threshold. Often the cell that decides a deal even when no feature gap is present.
A 12-row matrix (3 of each type) covers more strategic ground than a 180-row feature checklist. Each row maps to a deal-level question a buyer actually asks; each row is in prospect language, so sales recognizes it; and each row is verifiable against the competitor in 30 minutes — not three hours.
3. The Scoring Framework: Demand × Differentiation × Defensibility
A green dot / red dot tells you who has the feature. It tells you nothing about whether the gap matters. The scoring framework is the second half of the redesign: once rows are in buyer language, score each cell on three axes.
- Demand. How often does this row actually come up in real deals? Validated by win/loss reasons, recorded sales calls, and review-site complaints. A capability nobody asks about is not a gap — it's a luxury.
- Differentiation. How uniquely does your product solve this row compared to competitors? Two products solving the same row at parity is not a moat. This is where the value of keeping the matrix ends up being highest.
- Defensibility. How easily could a competitor close this gap in the next 6 months? Cheap-to-build features are weak moats. Capabilities tied to data, integrations, or switching costs are stronger.
Multiply the three scores (each 1–3) to get a gap score per row, per competitor. Anything in the red zone — Demand × Differentiation = points on a competitor that you can't defend — is what deserves a build decision this quarter.
| Score | Demand (D) | Differentiation (Δ) | Defensibility (Df) | Gap Score (D × Δ × Df) | Implication |
|---|---|---|---|---|---|
| High | Asked in > 30% of deals | Only us (or 1 competitor) | Hard to replicate (data, network) | 9–27 (rare) | Compete aggressively. Don't ship a parity alternative — defend the lead. |
| Medium | Asked in 10–30% of deals | 2 of 3 competitors on par | Replicable in 6+ months | 4–8 (typical) | Match or anchor on adjacent value. Avoid a pure build race. |
| Low | Asked in < 10% of deals | Industry commoditized | Easily cloned in < 90 days | 1–3 (frequent) | Ignore or de-prioritize. Build only if vision demands it, not because the matrix is red. |
The gap score is what the matrix is for. A row scored 9–27 is a strategic asset; a row scored 1–3 is a tactical check-box. Treating them the same is the most common mistake — and the reason most matrices end up driving no decision at all.
Scoring is only useful if it survives contact with the buying committee. To turn gap scores into deal-ready positioning, the rest of the message lives in the competitive battlecard framework — the one-pager reps open mid-call.
4. The Downloadable Template: Buyer-Capability Rows Pre-Filled
Most founders can produce the framework above in their head; the work that doesn't get done is filling in the rows. The competitor analysis template at /resources ships with a buyer-capability matrix section — 12 pre-filled rows across the four categories from section 2, a Demand × Differentiation × Defensibility scoring grid with cell formulas, and the example-block scoring sheet from section 5 below.
The template is the same one the free assessment at /assess is built from — pull two competitor URLs in, get a starter matrix populated against your industry. From there, score the cells yourself; the scoring is the part that needs a human in the loop, and no AI is a substitute for a 30-minute conversation with sales about what buyers actually asked for this quarter.
For the upstream signal loop that lets you keep the matrix current — without manually re-checking competitor pages every week — see the competitor feature tracking guide.
5. Acting on the Findings: The 4-Week Decision Cadence
A matrix without an action cadence is documentation. The cadence that holds the matrix accountable is a 4-week loop. Every row above gap-score 6 gets a destination inside that loop; every row below 6 gets an explicit ignore-with-reason logged in the template.
| Decision | When | Owner | Ship By | Measurement |
|---|---|---|---|---|
| Build (close the gap) | Gap score ≥ 9, and defensibility is feasible | Head of Product | 8–12 weeks | Win/loss at affected tier · Review-site complaints fading |
| Match (parity surface) | Gap score 4–8, parity surfaces common to deals | PM + Eng Lead | 4–6 weeks | Sales-call objection rate · Deal velocity on mids |
| Anchor (reframe the value) | Gap score 4–8, but differentiator exists on adjacent capability | Marketing + Sales Enablement | 1–2 weeks | Battlecard use rate · New objection recurrence |
| De-prioritize / ignore | Gap score ≤ 3, or build/clone cost > deal impact | Founder + Head of Product | Filmed in template, no timeline | Reviewed quarterly — any spike in Demand reopens |
Where a feature gap overlaps with a pricing move — a competitor slashes prices on the same week they ship the feature you're matching — the two playbooks interlock. Pricing and feature moves together signal a strategic pivot, not a routine product update. For the pricing side of that combination, see the competitor pricing response playbook from two weeks ago.
The team that filled a 180-row matrix — and still missed the row that lost three deals
A mid-market SaaS spent four weeks building a 180-row feature comparison. Every cell green-dot or red-dot. They had it pinned in their road-mapping channel.
Six weeks of deals later, they realized the row that mattered — "give a buyer the outcome in under an hour without admin credentials" — wasn't in the matrix at all. It was three different internal rows collapsed into one buyer-facing outcome. They had scored parity on each separate row and missed the buyer-perceived gap entirely.
Build / match / ignore / de-prioritize is the loop. Every cell above gap-score 6 enters the loop with an owner and a date. Every cell below 6 enters the ignore log with the reason. Both halves of that — the active list and the ignore log — are kept in the same template at /resources, so the matrix doesn't drift back into shelf-ware after the first 60 days.
For the closed-loop partner — turning scoreboard rows into one-pagers reps actually open mid-call — see the competitive battlecard framework. For the upstream signal feed that keeps the matrix current without manual re-checks every week, the competitor feature tracking guide is the upstream input.