Competitive Matrix: Free Template, Grid & Examples
A competitive matrix is a table that compares you against rivals on the dimensions that decide deals. Below: what it is, the three types most teams use, and a free, ungated template you can copy, with a worked B2B SaaS example built only from public sources.
By Naveed Ratansi · 6 min read · Live as of 13 October 2026
A pricing question, answered three ways
A rep asks what a rival costs. “Enterprise pricing” isn’t an answer, it’s a missing cell. Here is one slice of a competitive matrix, checked on 5 October 2026. It compares pricing evidence, not overall product quality.
| Company | What the record supports | What to ask next |
|---|---|---|
| Klue | Its pricing page offers a demo; no numeric plan price is published there. | Get a quote for the coverage and users you need. Keep the quote date. |
| Crayon | Its pricing-inquiry page describes tailored pricing and asks visitors to request an estimate. No numeric plan price is shown. | Ask what your estimate includes before comparing it with another plan. |
| IndustryLens | Growth is £149/month for 10 tracked companies, billed monthly. See current pricing. | Count the companies you need to track, then compare the relevant plan. |
An undisclosed price is not proof that a product is expensive. Keep it as a question until you have a quote.
What is a competitive matrix?
A competitive matrix is a structured table that compares your product against competitors across a fixed set of dimensions, typically positioning, pricing, key features, strengths and weaknesses. Each competitor is a row, each dimension a column. You read across a row to size up one rival, and down a column to see where the whole market clusters (and where there is open space). The discipline of the format is the point: every cell has to be filled from a real source, which is what turns a hunch about a competitor into something you can put in front of sales and a board.
Competitive positioning matrix vs. feature grid vs. win-loss matrix
Three formats cover almost every use. They answer different questions, so most teams keep more than one.
Feature-comparison matrix
The most common. Competitors as rows, capabilities as columns, cells marked present/absent or scored. It is the right tool for a sales battlecard or a "why us" page, but only when the cells are sourced. A checkmark you cannot back up from a public page is the fastest way to lose credibility in a deal, so treat every cell as a claim that needs evidence.
Positioning matrix (2x2)
Plots competitors on two axes (for example price versus breadth, or ease-of-use versus depth) into four quadrants. It is about market perception rather than a checklist, and its payoff is spatial: it shows the crowded quadrant to avoid, the empty one you might own, and whether your differentiation is real or just claimed.
Win-loss matrix
Built from your own deal outcomes: competitors as rows, with columns for win rate, the reasons you win and the reasons you lose against each. It is the only matrix grounded in what buyers actually did rather than what either vendor claims. That makes it the one most worth keeping current, and the one most teams never start.
Competitive matrix template
Here is the feature/positioning template, ungated. Copy it and swap in your own competitors. The example rows are filled from the competitive intelligence category itself, using only public information; the prices and gaps shown are what each vendor publishes (or, in the demo-only case, does not). Cells illustrate the method — swap in your own competitors and your own evidence.
| Competitor | Positioning | Starting price | Key features | Strengths | Weaknesses |
|---|---|---|---|---|---|
| Enterprise CI suite (e.g. Klue / Crayon) | Enterprise competitive enablement; sales-team focus | Demo-only / "contact sales", no public price | Battlecards, win-loss, digests, integrations | Deep sales workflows, large card libraries | Gated pricing; enterprise-weight setup; assets often behind a form |
| Manual CI (ChatGPT + spreadsheet) | DIY; no dedicated tool | Effectively free (analyst time) | Ad-hoc prompts, hand-maintained sheet | Zero software cost, fully flexible | No monitoring, goes stale fast, no citations or audit trail |
| IndustryLens | Cited, monitored CI in one weekly briefing | £149/month for 10 tracked companies, billed monthly (published) | Cited insights, battlecards, weekly change tracking across 350+ sources | Every claim sourced; published pricing; weekly cadence | Newer category entrant; built for change-tracking over bespoke services |
Notice the price column does the most work: enterprise CI suites publish no number (demo-only), while IndustryLens publishes its price: £149/month for 10 tracked companies, billed monthly. That “same buyer, very different transparency” contrast only shows up when you actually compare the pricing pages — a fact you can cite, drawn straight from each one.
The blank version, ready to paste
The block below is the same structure with the cells emptied, tab-separated. Select it, copy, and paste into Google Sheets, Excel or Numbers and it lands as real columns. No email wall, no download.
Two rows most matrices are missing are included on purpose. You belongs in the table, because a matrix you are not in is a market map, not a competitive one. Status quo / do nothing belongs there because in B2B it is often the option that actually wins the deal.
Competitor Positioning Starting price Key features Strengths Weaknesses Source + date checked You Direct rival 1 Direct rival 2 Direct rival 3 Strongest indirect Status-quo / do nothing
Add the last column (source and date checked) even if you fill nothing else. It is what lets someone challenge a cell in a deal review and settle it in thirty seconds instead of re-doing the research.
A worked 2x2 positioning matrix
The feature table answers “what does each one do.” The 2x2 answers a different question: where is the market crowded, and is there space left. Pick two axes that a buyer actually weighs against each other. Here, price transparency against breadth of coverage, using the competitive intelligence category as the worked example.
High price · broad scope
Enterprise CI suites and research platforms
Demo-gated pricing, analyst-assisted, built for a dedicated CI function. Crowded, and the hardest quadrant to enter.
High price · narrow scope
Point tools sold enterprise
The weakest position in any category: premium price without the breadth to justify it. Usually a staging post, not a destination.
Low price · narrow scope
Alerts, single-source monitors, DIY prompts
Cheap and easy to start, but covers one surface. Teams outgrow it the first time a competitor changes something it does not watch.
Low price · broad scope
Published-price automated CI
The quadrant a challenger wants: multi-source coverage at a number the buyer can see without a sales call.
Two rules keep a 2x2 honest. Choose axes a buyer would actually trade off: “quality” against “price” is not a real axis pair, because nobody claims the low-quality end. And place yourself last, from the same public evidence you used for everyone else, or the exercise just confirms what you already believed.
How to fill each column from public sources
The matrix is only as trustworthy as the sources behind it. Fill each column from the competitor’s own public footprint, and note where the figure came from so anyone can re-check it.
| Column | Where to source it |
|---|---|
| Positioning | The competitor’s own homepage hero and "for [who]" copy. Quote how they describe themselves. |
| Starting price | Their public pricing page. If there is no published price, write "demo-only". That absence is a real, citable data point, not a gap to guess at. |
| Key features | Their features/product pages and changelog. List what is actually shipped and visible today. |
| Strengths | G2/Capterra review themes and analyst coverage: patterns several customers repeat, with the source noted. |
| Weaknesses | Recurring complaints in those same reviews, plus anything the pricing or feature pages quietly omit. |
Why your matrix goes stale (with numbers)
The hard part is not building the matrix; it is keeping it true. Across 197 B2B SaaS competitors and 2,900+ weekly comparisons (December 2025 – October 2026), in a given week about 4 in 10 of competitors changed a pricing page (~40%), 50.6% rewrote messaging, and 43.5% shipped a product change. Any single one of those edits a cell in your matrix, so a table built once is already drifting by the time it is saved.
Method: week-over-week diffs across the B2B SaaS competitors IndustryLens monitors. Figures refresh as new data lands.
Common questions
What is a competitive matrix?
A competitive matrix is a structured table that compares your product against rivals across a fixed set of dimensions, typically positioning, pricing, key features, strengths and weaknesses. Each competitor is a row and each dimension is a column, so you can read across to see how any one rival stacks up and down a column to spot where the whole market clusters. Its value is that it forces you to fill every cell from a real source rather than from memory or assumption.
What should a competitive matrix include?
At minimum: the competitors you actually meet in deals (direct, and the strongest indirect ones), and a column for each decision-driving dimension: positioning, starting price, key features, strengths and weaknesses. Each cell should be backed by a public source (a pricing page, a homepage hero, a review theme) so the matrix is defensible. The single most-skipped column is price overlap, because some competitors publish a number and others only offer a demo, and that contrast is often the most useful cell in the whole table.
What is a competitive positioning matrix (2x2)?
A positioning matrix, or 2x2, plots competitors on two axes (for example price against breadth of capability, or ease-of-use against depth) and places each rival in one of four quadrants. Unlike a feature-comparison matrix, it is about perception and market space rather than a checklist: it shows where the market is crowded, where there is an empty quadrant you could own, and where your own position is genuinely differentiated versus merely claimed.
How often should I update a competitive matrix?
More often than most teams do. A matrix built once and saved to a drive is stale within weeks, because competitors change pricing pages, rewrite messaging and ship features on their own cadence, not yours. Treat it as a living document reviewed at least monthly, and ideally fed by ongoing monitoring so a competitor’s move updates the relevant cell automatically rather than waiting for someone to notice.
How do you build a competitive matrix?
Start from the competitors you actually meet in deals (a few direct rivals plus the strongest indirect ones) and give each one a row. Then add a column for every decision-driving dimension: positioning, starting price, key features, strengths and weaknesses. Fill each cell from a public source (a pricing page, a homepage hero, a review theme) rather than from memory, and note where a price is simply not published. Finally, review it on a set cadence, because the moment it is saved it starts drifting out of date.
Where do you get the data for a competitive matrix?
From each competitor’s own public surfaces: their pricing page for the price (or a “demo-only” note where there isn’t one), their homepage and “for [who]” copy for positioning, their features and changelog pages for what is actually shipped, and G2 or Capterra review themes for strengths and recurring complaints. The rule is one citable source per cell. An absence, like a hidden price, is itself a real data point rather than a gap to guess at.
What is the difference between a competitive matrix and a feature comparison grid?
A feature comparison grid answers a narrow question (which product has which feature), usually as a checklist of yes/no cells. A competitive matrix is broader: it adds the dimensions that actually decide deals, such as positioning, starting price and the strengths and weaknesses behind the features. A positioning matrix (2x2) is different again: it maps perception and market space rather than a checklist. Most teams need the full matrix; the feature grid is one column-set inside it.