Competitive Matrix

Competitors came up in every meeting, but each person had a different company in mind. The product manager pictures whoever ships similar features, sales pictures whoever they lost last week's deal to, and the CEO pictures whoever just showed up in a funding announcement. So "we're better" and "they're far cheaper" collide in the same room while neither statement is wrong. The two people are describing different companies.

One pricing discussion ran two hours and ended nowhere. Someone said a rival charged $9 a month and someone else said $19, and it turned out the first number was per seat and the second was the team minimum. Nobody had written down where either figure came from, so there was no way to settle it in the room.

A competitive matrix moves that conversation onto one surface. The reason it takes the form of a table isn't neatness — it's that a table exposes empty cells. If two of five companies have nothing in the price row, the fact that those two don't publish pricing is itself a finding. Comparing in your head, you never see the blanks. You only see the companies you happen to think about often.

Attributes run down the side, companies run across the top. Fill it only with features and half the table goes unused, so six rows make a reasonable starting set.

1. Entry price. The per-seat monthly figure of the cheapest plan, along with any minimum seat count. Record one without the other and you reproduce the $9-versus-$19 argument exactly.
2. What the free tier covers. Say whether the limit is on users, storage, or time.
3. The customer size they sell to. The company sizes in their published customer stories answer this.
4. The one-sentence claim. Copy the headline off their home page verbatim — paraphrasing erases the words they deliberately chose.
5. Features shipped in the last six months. This row shows direction, which matters more than the current feature list.
6. The five or six capabilities buyers actually compare. Pick these from what customers ask about, not from what you happen to do well.

Fill cells with what you saw, not what you heard. Prices come from the pricing page; scope comes from screens you signed up and clicked through yourself. Write the source and the date you checked next to each cell, so six months later you can re-verify the whole row in twenty minutes. A cell filled in from "someone in sales mentioned" is one that, a month on, not even the person who said it can source — and it drags the credibility of the table down with it.

Choosing who goes across the top is the harder half. List only same-category companies and every substitute drops out. A substitute is something in a different category that solves the customer's same problem. The way a small team keeps meeting notes is a long message in a chat channel, and since that costs nothing, the strongest competitor usually lives here. An indirect competitor deserves a row too — a company selling something different that takes the same budget from the same buyer. If a team adopts exactly one new tool this year, a project tracker and a document tool compete for that slot without overlapping on a single feature.

One person writes it, usually the product manager or product marketer covering that area. Split the work across several people and the same row gets filled to different standards — one column says "up to 5 users" under the free tier while another says "generous."

Three groups read it, and each looks at different rows.

1. Product. Reads the blanks in row six when deciding what to build. A blank is not automatically an opportunity, though. More often nobody built it because customers don't want it. The blanks worth acting on are the ones a buyer has already asked you about in a call.
2. Sales. Takes the answers used when a buyer hesitates mid-comparison. The table itself is too long for a meeting, so the counter-arguments get pulled into a one-page battlecard.
3. Executives and investors. Read rows three and four together to judge whether there is still room in this market.

The default refresh is quarterly, with individual cells corrected the same week a competitor changes pricing or ships something major. Rebuilding the whole table each time makes it heavy enough that nobody touches it. The dates written beside each cell pay off here: fix only the rows whose dates have gone stale and the job comes down to three or four cells.

"Where did this cell come from, and when was it checked?"

Verifying the value still holds before the table gets used as evidence.

"Shouldn't spreadsheets be a row on this?"

Pointing out that competitors are being counted only within the same product category.

"We have three blanks nobody else has, and customers have asked about exactly one of them."

Proposing that only the blanks customers ask about should be counted.

At Pagedeck, Mia revises this table every quarter. Last quarter it had six rows: four competing products plus spreadsheets and chat. What stood out once it was filled in wasn't the feature rows but the free-tier row. All four competitors capped by user count while Pagedeck capped by document count, and teams that pile up short documents like meeting notes hit the Pagedeck ceiling first.

Theo saw that cell, pulled the free accounts that had stalled, and found half of them sitting at the document limit. One feature came off that quarter's roadmap and a change to the free tier went on. The table didn't make the decision — it made a cell visible that nobody had been looking at. Everyone had been comparing feature rows because that's where the argument usually lives.

The most common mistake is reading it as a checkmark count. The grid invites counting. But whoever picked the attributes decided the count in advance. Choose six rows weighted toward your own strengths and your column comes out densest, and a plan built on that table spends engineers defending features no customer has ever asked about. Attributes should come from the questions buyers actually raise in comparison calls.

The second is treating it as finished once written. It looks like a document, so it looks complete. In practice price and feature cells change faster than anything else, and within six months about half of them no longer match reality. A stale table is worse than no table. Without one, people verify before the meeting. With one, they carry it in unverified.