Competitor Analysis

What it does

Tells you when a competitor makes a move that matters, not a weekly report to skim.

Each run it:

• reviews each competitor's configured pages in a real browser
• diffs positioning, pricing, packaging, features, and CTAs against the last snapshot
• separates material moves from cosmetic copy tweaks
• alerts your Slack channel only on a verified material change: what changed, before and after evidence, why it matters against your positioning, and a suggested response

Nothing material changed, nothing posted: it records a clean no-op and keeps the snapshot history for the next diff. It reads competitor pages but never submits forms or creates accounts.

Setup lives in SETUP.md.

Slack

The agent alerts through Slack. Connect Slack in Vercel so it can post, then pick the channel it alerts.

For the channel ID: in Slack, open the channel, click its name, then About, and copy the Channel ID. Set SLACK_COMPETITOR_ANALYSIS_CHANNEL_ID to that value.

Store the values

Local runs read .env.local (gitignored). Deployed and scheduled runs read Vercel project env: vercel env add SLACK_COMPETITOR_ANALYSIS_CHANNEL_ID production takes the value from stdin, so pipe it in.

Point it at your project

Fill in the <!-- project-config --> block at the top of agent/instructions.md:

• Competitors and pages: the competitor sites to track and, for each, the pages to review (homepage, pricing, product, feature, docs, changelog, blog, and CTA pages).
• Your positioning: a short summary of your own positioning. Every alert explains why a change matters against it, so this is required.
• Reporting preferences: emphasis, length, or audience for alerts and run reports. Leave unset to use the agent's default structure.

The first run establishes a baseline snapshot and posts nothing. The agent browses competitor pages read-only in its own sandbox; the sandbox installs the browser tooling on first run.