Competitor teardown
A deep read of a single rival from public evidence: filings, pricing, job ads, reviews, product pages. Slow, unglamorous, and consistently the highest-yield research a team does.
The printable canvas and the handoff into Claude Code are part of a paid plan. See what a plan includes. It needs the Claude desktop app on this machine, and your team and the prompt library already installed in that project — we cannot see your disk, so open it there.
What it is
A deep, evidence-based read of a single competitor built entirely from public material. Slower than profiling and much more useful, because it produces an exposure rather than a description.
- Filed accounts
- The only audited view of a competitor. Revenue, margin, employee count, borrowings, and the direction of all of them.
- Pricing and proposition
- The full cost to a customer, reconstructed including the parts not advertised. Buy it if you can.
- Hiring signals
- Job adverts reveal what is being built six to twelve months ahead of launch. Nearly free and almost nobody looks.
- Customer evidence
- Reviews, complaints, forums, case studies. Where they repeatedly fail is where they can be attacked.
- Cost structure inference
- What their model implies about their costs — headcount, property, sourcing, automation. Inferred, and labelled as inference.
- Exposure
- Where they are vulnerable and what it would take to exploit it. The output; everything above is input.
How you run it
- Start with the filingsAccounts, annual reports, any regulatory submissions. This is the only part of a competitor that has been audited.
- Read the job adsWhat they are hiring for tells you what they are building, six to twelve months before it ships. Nobody does this and it is nearly free.
- Price the proposition end to endBuy it if you can. Otherwise reconstruct the full cost to a customer, including the parts they do not advertise.
- Mine the reviews and the complaintsWhere they fail repeatedly is where a competitor could take customers. Look for the pattern, not the outlier.
- Write the exposure, not just the profileA teardown that ends in a description has done half the job. Name where they are vulnerable and what it would take to exploit it.
The prompt
Run this tool in your own Claude
The short prompt starts your partner against the library on your disk. The long one carries everything with it and needs nothing installed.
Your playbook
It lands in the earliest stage this tool suits. Move it on the Playbook page.
You’ll need
- The competitor named precisely, including which entity files accounts
- Access to their public pricing and product pages
- Any customers you share
You’ll end up with
- How they actually make money, with numbers where filed
- Their cost base and where it differs from yours
- Two things they are structurally better at, and two where they are exposed