INT-02 · SEC. 09 Competitive Intelligence

Competitor Watch Loop

A weekly check that flags only what changed on a competitor's public pages, not the whole page again.

FORMAT: loop
DIFFICULTY: beginner
TIME: 5 min
TOOLS: universal
MODELS: any
COPIES: 0 so far

When to use this

You want to track a competitor over time without re-reading their entire site every week. Run this once, save the output, then run it again next week and diff it yourself, or feed last week's snapshot back in as context.

The pattern

Pastes as plain text

Visit the competitor site I name at the bottom of this prompt (and its /pricing and /changelog pages if they exist). This is a recurring weekly check, not a first-time scan.

Compare the current state of the pages against last week's snapshot, pasted at the bottom. If no snapshot is pasted, treat this as the first run: skip the diff and just produce the baseline snapshot. Report only:
1. Anything new: new pricing tier, new feature, new page, new messaging
2. Anything changed: price moved, a feature description changed, a plan was renamed or removed
3. Anything removed: a feature, tier, or page that was there before and isn't now

If nothing changed in a category, write "No change" for it, don't restate the old content. End with an updated snapshot block I can paste in next time, covering current pricing tiers and feature list in short bullet form.

Competitor URL:
Paste last week's snapshot below this line (leave blank on first run):

Real example output

New: Added a "Teams" tier at $49/mo between Starter and Growth.
Changed: Growth tier price moved from $99/mo to $89/mo (annual discount now shown by default).
Removed: No change.

Updated snapshot:
- Starter: $29/mo, 3 seats, 10k API calls
- Teams: $49/mo, 8 seats, 40k API calls (new)
- Growth: $89/mo, 15 seats, 100k API calls
- Enterprise: custom, unlimited seats, SSO

Why it works

Feeding last week's snapshot back in turns a full re-read into a diff. The model only has to report deltas, which keeps output short enough to actually skim weekly instead of skipping it. The snapshot block at the end is what makes the loop self-sustaining, no separate tracking system needed.