Competitor Intel
What it does
It answers not “what did the competitor do?” but “what does it mean for us, and what do we do first?” The reader is a brand, marketing, or e-commerce lead.
Typical flow
- Triage — decide whether this round is a move-by-move review, a single attribution question, or a full competitor report.
- Gather — facts about you and the competitor on four surfaces: price and assortment (price tiers, SKUs, sizes), claims and ingredients, content and creator playbook, and recent moves. Data comes from the benchmark dashboard and change events, plus marketplace listings, rankings, and industry and social signals; first-party wherever possible, with second-hand reports used as leads only.
- Attribution — confirm a change is real (metric definition, base period, promotion effects) before explaining it; list the possible explanations and soften the wording to match the evidence. Leads are never written up as conclusions. Moves are ranked by money and urgency, not by when they were found.
- Write-up and audit — draft to the fixed section template and run the machine audit; significant moves can also push an alert.
What it delivers
- A competitor report: price and assortment, ingredient and claim gaps, content playbook, and recommended moves for you;
- Evidence grades and sources for the key conclusions, plus the snapshot time points;
- The benchmark dashboard and change events (in the workbench);
- Slides or a Word/PDF version when you want one.
Limits
- It does not do category-level research (use Market Insight) or write new-product proposals (use Product Proposal).
- Snapshots are discrete points in time, not a continuous series — say what the inference rests on.
- Rankings and marketplace data each use their own definitions (China rows are daily snapshots, global rows are 30-day totals), so they cannot be used to validate each other.
Orphic