[Template: Competitive Teardown] [Intent] This is not an article, not a PRD, not a pitch deck. The goal is to turn messy materials on multiple competitors into a decision-ready product strategy report, helping the team answer: "Where exactly do we differ from them, and how should we fight next?"
[Suitable inputs]
- Competitor websites / pricing pages / changelogs / user reviews / sales feedback / internal research notes
- 2-6 competitors is most suitable; if the user provides only one competitor, output a single-competitor deep dive
- Can include tables, bullets, link excerpts, interview records, screenshot descriptions
[Required output structure]
- Header: market / product category / report date / one-sentence conclusion.
- Executive takeaway: the 3 most important judgments, each must include a "so what".
- Positioning map: use a 2×2 quadrant or coordinate chart to show competitor positioning. The axes must come from the user's content; do not apply template words.
- Competitor cards: one card per competitor, including target user, core promise, pricing signal, primary strength, visible weakness.
- Feature matrix: rows are key capabilities, columns are competitors + "Us / Opportunity"; use ✓ / △ / — to express coverage, and add short annotations.
- Pricing / packaging read: pricing tiers, free trials, limitations, enterprise sales motions.
- UX / messaging notes: extract 4-6 observable details from user materials; do not speak in generalities.
- Opportunity windows: 3 opportunity windows, each including why now, target segment, first move, risk.
- Recommended moves: near-term 30-day / 90-day / 180-day action recommendations.
[Design requirements]
- Strategy consulting + product war room style: high information density, fast to scan, clear charts.
- Use a restrained palette: ink / paper / muted blue / signal amber or similar professional colors.
- The feature matrix must be horizontally readable; on small screens it can become stacked cards.
- Do not make it a marketing landing page, and do not make it an ordinary article.
[Optional style templates — see assets/] Choose the one that best fits the user's content; do not mix the three:
assets/war-room-grid.html: default style. Light war room / consulting report, suitable for product teams, PMs, and general business readers.assets/radar-map.html: dark radar chart / market intelligence console, suitable for security, AI, developer tools, and platform-type competitors.assets/analyst-dossier.html: paper analysis dossier / investment research dossier, suitable for investment research, industry analysis, and formal strategy memos.
If the user does not specify a style, prioritize using war-room-grid; if the input emphasizes market landscape, technology radar, or offensive/defensive posture, use radar-map; if the input resembles research notes, an investment memo, or an industry report, use analyst-dossier。
[Content authenticity]
- Use only the competitors, prices, features, and reviews provided by the user. Mark missing information as "not found in source" or "unknown".
- Do not invent market share, ARR, customer names, or pricing numbers.
- If the user's materials are clearly insufficient, still output the report, but list the gaps in "Evidence gaps".