Raw view: Competitive Landscape Brief
No invisible, zero-width, or bidi-control characters detected.
<research_notes>
{{RESEARCH_NOTES}}
</research_notes>
Write a competitive landscape brief from the research notes above. The reader is {{AUDIENCE}} (for example, "the product leadership team deciding next quarter's roadmap"). They will act on this, so every claim about a competitor must be sourced to the notes, and every gap you identify must be one the notes actually support.
<our_product>
{{OUR_PRODUCT}}
</our_product>
<competitors>
{{COMPETITORS}}
</competitors>
<dimensions>
{{DIMENSIONS}}
</dimensions>
<research_notes> should contain the raw material: pricing pages, feature lists, reviews, analyst excerpts, changelogs, job postings, each labeled with its source and date where possible. <dimensions> lists the axes to compare on (for example: target segment, pricing model, deployment, integration depth, support tier). If empty, derive 4-6 dimensions from <our_product> and the notes, and state them.
Rules:
1. Inventory the notes first. For each competitor in <competitors>, list which dimensions the notes cover and which they do not. Coverage gaps become explicit `[no data in notes]` cells, never guesses. If a competitor appears in the notes but not in <competitors>, mention it under "Also observed" without a full profile.
2. Every factual statement about a competitor carries a source reference from the notes (label or quoted fragment) and, if present, the date. Claims from your own knowledge are allowed only when labeled `[from model knowledge, verify]`, and never for pricing, headcount, funding, or feature availability, which change too fast to trust from memory.
3. Separate what a competitor says about itself (marketing copy, positioning) from what others say (reviews, analysts) and from what is observable (pricing page, changelog, documentation). Label each claim with its type; the three disagree more often than readers assume.
4. Build the positioning view on two dimensions from <dimensions> that most differentiate the field. Place each competitor and <our_product>, and explain each placement in one clause tied to evidence.
5. Identify gaps: combinations of dimension values that no competitor occupies and that the notes suggest customers want (reviews complaining, feature requests, analyst commentary). For each gap, state the evidence and the strongest reason it might be empty for a good reason.
6. Keep the brief honest about <our_product>: apply the same claim-type labeling and the same scrutiny. A brief that flatters the home team is not useful to the reader.
## Output format
**Field at a glance** - table: competitor (plus <our_product>) as rows, <dimensions> as columns, cells hold a 2-6 word value with a source reference or `[no data in notes]`.
**Positioning view** - the two axes chosen and why, then each player's position and the one-clause justification. Describe it as a 2x2 or a line; no image needed.
**Competitor profiles** - one short section per competitor: positioning in their words `[self]`, strengths and weaknesses from others `[external]`, observable facts `[observed]`, recent moves (dated), and the single thing they do that <our_product> does not.
**Gaps and opportunities** - numbered list; each: the gap, evidence from notes, why it might be empty for a reason, and what it would take to own it.
**Also observed** - competitors or substitutes in the notes not profiled above, one line each.
**Confidence and staleness** - which claims are oldest or weakest-sourced, and the three things to verify first before this brief is used in a decision.