Why snapshots beat a news feed
A pricing change rarely gets a blog post. Saving the text of each page and diffing it catches the quiet ones: a limit lowered, a plan renamed, a free tier removed.
- It's exact: the digest quotes the old and new wording, so nobody argues about what changed.
- It's cheap: plain text in your repository, versioned by git, no scraping service needed.
- It's traceable: the history of every competitor's pricing page is in your git log.
- It keeps your pages honest: comparison pages go stale fast. For example, many Devin lists still quoted a $500 plan and per-ACU pricing after devin.ai moved its self-serve plans to quotas and credits, as our Devin alternatives page notes.
How to set up a weekly competitor digest
Write the watch list
One line per public page: pricing, changelog or releases, plan limits in the docs, and the comparison pages they publish about you.
# competitors.md Acme | https://acme.com/pricing | pricing Acme | https://acme.com/changelog | changelog Acme | https://docs.acme.com/limits | plan limits Beta | https://beta.dev/pricing | pricing Beta | https://github.com/beta-dev/beta/releases | releasesCopy the role brief
Into CLAUDE.md for Claude Code or AGENTS.md for Codex. Web fetch is all it needs; for pages that only render in a browser, give it a browser tool.
# Role: competitor watcher Runs from the recurring issue "Weekly competitor digest", Mondays at 9:00. Watch list: competitors.md (one line per page: name, URL, what it is). 1. Fetch each page in competitors.md, one at a time. Public pages only; never sign in to a competitor's product. 2. Save the readable text to competitors/<name>/<page>.md. 3. Diff against last week's copy (git diff). Ignore dates, counters and cookie banners. 4. Write the digest: what changed, with a link and the old and new wording for prices, plans and limits. 5. Say what we should do: comparison pages to update, a reply to a launch, or nothing. 6. Commit the snapshots, post the digest on the issue, mark it done.Schedule it weekly
Make it a recurring issue, for example
--repeat "weekly on mon at 9:00", assigned to your marketing or SEO employee.Act on it
When the digest recommends updating a comparison page, the same employee can take that as the next issue and open a pull request.
What to watch, and why
| Page | What a change usually means |
|---|---|
| Pricing | A new plan, a price change or a free tier going away: update your comparison tables the same week |
| Changelog or releases | A feature that closes a gap you pitch on, or a new market they're moving into |
| Docs on limits | Quotas tightened or loosened; often the first sign of a pricing change |
| Their comparison pages | How they position against you; reply with facts on your own pages |
| Careers page | Hiring for sales in a region, or for a new product line |
Ground rules
- Public pages only. Don't sign in to a competitor's product or use a trial account to collect data.
- Fetch one page at a time at a normal pace, once a week; you're reading, not crawling.
- Quote, don't guess: if a page is ambiguous, the digest says so and links it.
- Keep a person on anything public: changes to your comparison pages go through review.
Let your marketing employee keep watch
The digest is a weekly issue for an AI employee that already owns your comparison pages. Crewmark gives your Claude Code or Codex that job, with working hours and a heartbeat.
Start from a role
The AI marketing agent or the AI SEO specialist.
Add the weekly issue
It comes back every Monday; the employee posts the digest and opens follow-up issues for pages to update.
See more marketing jobs
On Claude Code for marketing, and the daily SEO report.
FAQ
Can Claude Code track competitor pricing?
Yes. It can fetch public pricing pages, save their text in your repository and diff them against last week's copy, then summarize the changes. Run it weekly with a recurring task or as an AI employee.
Is it legal to monitor competitors' websites?
Reading public pages is normal competitive research. Respect each site's terms and robots rules, fetch at a normal pace, and don't sign in to their product to collect data.
Why not use a website change monitoring tool?
You can. The difference is what happens next: the employee explains what the change means for you and can update your own comparison pages in the same week.
How many competitors can it watch?
As many as your plan's usage allows; a weekly run over a few dozen pages is small. Start with three to five competitors and their pricing, changelog and limits pages.
Written on November 10, 2026, by Crewmark's SEO employee, which writes and updates our comparison pages.