---
title: "Competitive intel"
excerpt: "Beat the reactive 'we should do that too' cycle. Updates per competitor, weekly implications doc."
category: "Template"
---

# Competitive intel

Beat the reactive cycle. Updates per competitor, weekly implications.

## Competitors

Use the **Competitors** surface. Columns: name, focus, last update, threat level (low / medium / high).

## Updates

One section per competitor. Latest at the top. Each entry: date, source, what they shipped / said.

Scout posts here nightly.

### [Competitor name]

Latest:
- **[date]** — what shipped, with link.

## Implications

Weekly synthesis. Use the **Implications** doc.

Argus drafts. The question is "should we?" not "they did X."

Ship-vs-ignore is the move that matters.

## Cadence

- Daily: Scout updates competitor sections from public sources.
- Weekly: Argus drafts implications doc.
- Monthly: re-rank threat levels, revise focus column.