---
name: competitor-scan
description: Build a cited feature and pricing comparison of named competitors from public sources only. Use when choosing between tools, positioning a product, or answering "how do we compare" - every cell carries its source and retrieval date, and unknown cells stay unknown instead of being filled with guesses.
---

# Competitor Scan

## When to use

- A feature or pricing decision needs competitive ground truth
- A comparison table will be shown to people who will check it

Do NOT use for confidential or leaked information, and do not
estimate a competitor's private numbers. Public sources only.

## Scope first

1. Fix the competitor list with the requester - never expand it
   silently mid-scan.
2. Fix the feature axes before collecting: which capabilities, which
   price points, which limits (seats, requests, storage). Changing
   axes halfway invalidates collected cells.
3. Fix the date. Prices rot; the table must say when each cell was
   retrieved.

## Collect with sources

For every cell:

1. Go to the primary source: the vendor's pricing page, docs, or
   public changelog - not a review site summarizing them.
2. Record the URL, the retrieval date, AND a dated quote of the
   exact source line behind each value. Pricing pages change; a link
   alone does not prove what the page said on the day.
3. Read the fine print: per-seat vs per-team, monthly vs annual
   pricing, free-tier limits, "contact us" tiers. A price without
   its unit is not a price.
4. If a cell cannot be confirmed from a public source, write
   "not published" - never interpolate from a competitor's blog
   post or your own assumption.

## Compare honestly

- Mark cells where you are comparing different units (per-seat vs
  flat) instead of forcing them into one number.
- Keep "best" claims out of the table. The table shows facts; the
  summary may recommend, with reasons.
- When one axis clearly wins per use case, say which use case -
  "cheapest for a 5-person team" beats "cheapest".

## Output format

The table: rows are competitors, columns are the fixed axes, each
cell is value + source + date. Below it: cells that could not be
verified, and a dated summary of what changed since the last scan if
one exists.

## Hard boundaries

- No confidential, scraped-behind-login, or leaked data.
- No unsourced cells. "Not published" is a valid and useful cell.
- Prices change: a table older than ~90 days is stale - say so.
