Agent use case / Strategy and research
Know what your competitors changed since yesterday
ZeroTwo checks competitor changelogs, product docs and positioning on a schedule, compares each page with its last snapshot and posts the changes that matter to Slack, with a dated log in Notion. A page it could not read is reported as such, never as no change.
One morning's feed. Illustrative, with fictional competitors.
- ChangelogMon 07:02
Acme
New release note: audit log export added for admins.
- PositioningMon 07:04
Contoso
Homepage headline changed from team-focused wording to enterprise-focused wording.
- Product docsMon 07:05
Initech
New Webhooks section appeared in the API documentation.
- Product docsMon 07:06
Contoso
Could not check: the page did not load. Will retry on the next run.
Four signals, one feed
A competitor rarely announces a strategy change. It shows up as a release note, a new docs section, a rewritten headline or a plan that moved. This feed watches all four and keeps pricing as a branch, so it does not repeat the pricing brief.
- Product
Changelogs and release notes
The most direct record of what a competitor shipped. Every new entry counts as a change, with the entry text kept verbatim in the log.
- Product
Product docs
New sections, endpoints and integration pages often show up in docs before they reach marketing.
- Positioning
Positioning copy
Homepage headlines, subheads and the customer segments a competitor names. A rewritten headline is a strategy signal that no price tag will show.
- Branch
Pricing and packaging
Detected here, interpreted elsewhere. This feed flags that a pricing page changed and links to the dedicated pricing brief, which normalises plans and works out what the change means for you.
Pricing and packaging analysis
How ZeroTwo monitors competitor changes
Runs every day at 7:00 AM. Output: Alerts in #competitive-intel on Slack, with every change logged in Notion. The log in Notion is the archive of record, and Slack carries the alerts.
Step 1
Snapshots changelogs, product docs and key pages on a schedule
Each tracked page is read as it is publicly visible and stored as a dated snapshot, ready to compare with the previous one.
Step 2
Compares snapshots and filters out cosmetic changes
Only substantive differences are kept: new features, removed features, changed positioning and new sections. Dates, counters and rotating content are ignored by rule.
Step 3
Logs each change with before and after text
A timestamped row in a Notion change log records the competitor, the page, what changed and the previous wording, so you can see how each competitor moved over months.
Step 4
Posts a dated summary to #competitive-intel
The team sees which competitor changed what, with a short note on why it matters to your positioning.
What counts as noise
Substantive-change filtering is a rule you write, and the list grows as you meet noise. A sensible starting ignore list:
- Dates and copyright years
- Counters and live statistics
- Rotating testimonials and logos
- Cookie and consent banners
- A/B test copy that flips back within the day
One change, from page to alert to log
A hypothetical positioning change at a fictional competitor, shown so you can see what a useful alert and log row contain. The wording is invented for illustration and is not a measured result.
1. The page, before and after
- Previous snapshot
- Contoso homepage headline: "The project tool for fast-moving teams."
- Today's snapshot, Mon 07:04
- Contoso homepage headline: "The project platform for enterprise delivery."
2. The alert in #competitive-intel
Contoso changed its homepage positioning (Mon 07:04). Before: fast-moving teams. After: enterprise delivery. Why it matters: they are now naming enterprise buyers directly. Log: row added in Notion.
3. The row in the change log
| Competitor | Contoso |
|---|---|
| Page | Homepage headline |
| Detected | Mon 07:04 run |
| Signal | Positioning |
| Change | Team wording replaced by enterprise wording |
| Review | Open: owner to confirm and update battlecard |
Where monitoring can miss, and what to do about it
Any crawler-based monitor has blind spots. These are the ones to plan for, and the behaviour to ask the run for in each case.
| Situation | What the run does | What you check |
|---|---|---|
| A page fails to load or blocks automated access | Reported as Could not check, with the time and reason. It is never reported as no change. | Look for the same page failing run after run; some sites block automated readers. |
| A page builds its content with scripts | The run reads what is publicly visible; content that needs interaction may be missed. | Compare the first snapshot of each page with the live page when you set it up. |
| Gated or contact-sales pricing | Only publicly listed tiers and features can be monitored. | Add manual intel to the log yourself and let the feed track the public pages around it. |
| A change lands just after a run | It is caught at the next scheduled run. With a 7:00 AM schedule that is up to about a day later, plus the time the run takes. | Give your most important pages a tighter schedule if a day is too slow. |
| A growing list of competitors and pages | Each added page lengthens the run. Pages are checked on every run, and failures are listed. | Start with a short list of direct competitors, then add pages in steps and watch run time. |
| Pages in other languages | ZeroTwo can read and summarise pages in many languages. | Spot-check the extracted text for each language that matters to you before relying on it. |
Battlecards stay human-reviewed
A detected change says what a page now says. It does not say whether the claim holds up in a deal. ZeroTwo drafts the suggested edit to your battlecard in Notion and marks it for review, and a person approves it before sales relies on it.
Current battlecard line
Contoso: positioned for fast-moving teams.
Suggested edit, pending review
Contoso: now positioned for enterprise delivery. Confirm with a customer call before using in a deal.
Illustrative wording for a fictional competitor.
What changes compared with checking by hand
The usual way to learn about a competitor's move is a prospect mentioning it on a call, weeks after it shipped. A schedule turns that into a morning habit.
Detection method
Manual checks, or a customer mentions it
Scheduled snapshots compared with the previous one
Detection speed
Often weeks later, if anyone notices
At the next scheduled run, for example the next morning, if the page loaded
Coverage
A few competitors, checked when someone remembers
Every tracked page on every run, with failures listed
Effort
Hunting for changes by hand
Reviewing a short list of dated alerts
Where this feed stops and other workflows start
This page owns continuous product and positioning change detection. Pricing analysis and one-off market landscapes have their own pages.
Set it up in one prompt
Name the competitors and pages, say what to ignore, and say what a failure looks like. The schedule is part of the same request.
Example prompt
Every morning at 7:00 AM, check the changelog, product docs and homepage for Acme, Contoso and Initech. Compare each page with the last snapshot and ignore cosmetic changes such as dates, counters, rotating testimonials and cookie banners. For every substantive change, post the competitor, the page, the before and after text and the time to #competitive-intel, and add a row to the competitor change log in Notion. If a page cannot be loaded, post it as Could not check with the reason, not as no change. If a pricing page changed, link it to the pricing brief instead of analysing it here.
Schedule
Runs every day at 7:00 AM.
The team channel gets the alerts and the Notion log keeps the history. Slack and Notion are the example destinations. Check which connectors you can use.
Frequently asked questions
How many competitor pages can ZeroTwo monitor?
We do not publish a fixed limit. Start with a short list of direct competitors and a few pages each, then add pages in steps. Every added page lengthens the run, so check how long a run takes after each addition.
What does it count as a change worth alerting on?
You decide. A run compares each page with its previous snapshot and keeps substantive differences such as new features, removed features and rewritten positioning, while ignoring cosmetic ones like dates, counters and rotating content. Write the ignore list into the prompt and extend it whenever noise gets through.
What happens when a page cannot be loaded?
Ask the run to report it as Could not check, with the time and the reason, and to retry on the next run. A failed crawl should never appear as no change, because that is how a competitor's move gets missed.
What if a competitor uses dynamic or gated pages?
ZeroTwo reads what is publicly visible. Content that needs interaction may be missed, and gated or contact-sales pricing can only be tracked through whatever tiers and features are listed publicly. Compare the first snapshot of each page with the live page when you set it up, and add manual intel to the log where needed.
Can ZeroTwo update our sales battlecards?
It can draft the suggested edit to the relevant battlecard section in Notion, but we recommend a person reviews and approves it before sales sees it. A detected change tells you what the page says, not whether it holds up in a deal.
Does it work on pages in other languages?
ZeroTwo can read and summarise pages in many languages. Spot-check the extracted text for each language that matters to you before relying on it for alerts.
Where do pricing changes go?
This feed flags that a pricing page changed and logs the before and after. For normalised plan comparisons, trend analysis and what a change means for your own pricing, use the dedicated competitive pricing monitor.
Pick three competitors and let tomorrow morning's run show you what moved
The Free plan starts with 100 credits, and Work agent access is listed from Plus at $14.99/month. Plan limits are on the pricing page.