Competitive analysis: lead with the advice, show the working

A short document that compares you with your rivals and says what to do about it.

2 live examples

The example: Hearth & Hound against four dog food rivals

A strategist's memo: verdict first, three moves

Hearth & Hound against four dog food rivals

Open the exampleThe names and numbers are made up.

What to notice

  • The headline is the advice, "Don't match the price cut. Win the big dog.", and the paragraph under it answers the question the client asked.
  • A bar chart draws the gap: nothing is on sale for a 90 lb dog between $3.10 and $8.96 a day, and the proposed plan sits there at $6.90.
  • The first two moves show their arithmetic in small type, down to 540 × $6.90 × 365 days = $1,359,990.

The prompt that starts one like it

Turn my notes into a competitive analysis as a single HTML page for [client]'s leadership team. They asked: [question]. Here is what I have on [three or four rivals]: [strengths, weaknesses, prices, sources]. Make my recommendation the headline, with three numbers that back it. Then each rival's strengths and weaknesses, a price table, a chart of the gap, three moves in order, what would change my mind, and the one decision I need. It should read well on a phone. Then publish it on sharable.link with a password.

The example: Cellarhand and three brewery software rivals

A feature matrix and positioning map for a product team

Cellarhand and three brewery software rivals

Open the exampleThe names and numbers are made up.

What to notice

  • Both axes of the map are scores from the matrix, so Cellarhand's spot at 5.5 for making beer and 1 for selling it can be checked row by row.
  • A half mark always has its reason under the feature name, such as "Cellarhand: a CSV file to upload by hand."
  • Three rows carry a Q2 tag, and the plan says what they add up to: selling the beer goes from 1 to 3 out of 6.

The prompt that starts one like it

Make a competitive analysis for my product team as a single HTML page. We make [product]; the rivals are [three products]. Notes from trying each: [features, prices, setup time]. Why we lost deals last quarter: [reasons and counts]. Mark every feature full, partial or none in one matrix grouped by job, naming the limit under each partial mark. Draw a positioning map from two of the group scores. End with what to build, leave and watch. It must fit a phone. Then publish it on sharable.link with a password.

A competitive analysis that stops at the comparison table hands the hard part back to the reader. The two linked from this page each end in a recommendation. One is a strategist's memo for a client's leadership team, the other a feature matrix a product manager made for her own team. Every company in them is invented, so take the structure and do your own research.

Who it's for

Consultants and strategists whose client has asked a pointed question, such as whether to follow a rival's price cut. Product managers and founders who want their team to agree on what to build next.

Keep the raw material elsewhere: screenshots of rival sites, the review spreadsheet, your call notes. Nothing on the page updates itself, so a rival's new price means a new version from you.

What a good one contains

  • The advice as the headline. The memo opens with "Don't match the price cut. Win the big dog." A leadership team may read no further.
  • Three or four rivals, and yourself. Each gets a line on who it is, what it's good at and what it's bad at. The memo calls its own client bad at price.
  • Prices in one unit. The memo's price table has one column each for a 20, 50 and 90 lb dog, per day, before discounts.
  • The gap, drawn. The memo's bar chart shows nothing on sale between $3.10 and $8.96 a day. The matrix page's map shows one rival alone in the top right corner, at 4.6 times the price.
  • Marks a reader can check. Each half mark in the matrix names its limit, and the map's two axes are sums of those marks.
  • Evidence from your own customers. 26 of the brewery software's 58 lost deals named keg tracking or wholesale orders. A rival's website can't tell you that.
  • What to do, and what to leave. The memo gives three moves in order. The matrix page lists three things to build and three to leave alone.
  • What would change your mind. The memo names three events, such as the price cut lasting past January.

Where these go wrong

The usual failure is a matrix in which your own column is all full marks. Nobody believes it, and the team learns nothing. Score yourself first and hardest: the product manager gives her own product 1 out of 6 for selling.

Say where each fact came from and when you checked it. A price read from a rival's site on a named date is evidence. "I heard they're cheaper" isn't. Both examples end with their sources and dates.

How to send it

With a password. It names rivals' weak points and carries your client's own loss figures. Only the people in the meeting should have it.

Every page you publish gets one link that opens in any browser. You choose who can open it: anyone with the link, anyone with the password, or only the people and company domains you name, who sign in with Google or Microsoft. Change the page later and the link stays the same.

Make yours in Claude

Add the connector once, then publish from any Claude conversation and get a link to send.

Add Claude Connector

Already have the file? Upload it here.

More in marketing

  • Landing page: A single page that makes one offer and asks for one thing, sent as a link before you have a website.
  • Infographic: A long scrolling page that explains one subject with numbers, one drawn chart at a time.
  • Newsletter: One issue of a group's news as a page: a lead story, short items, dates and who wrote it.
  • Portfolio: A page of your best work, each piece with its problem and outcome, to send with an application.
  • Market research report: Survey and interview results written up for the client who has a decision to make.
  • Press release: A news announcement written for journalists: the facts, two quotes and a contact on one page.
  • All use cases

Keep reading