Watch these competitors: [names]. Check [official product pages, help pages, release notes, and other named sources] at [times]. Compare each check with the last recorded version. Treat [specific changes] as material and ignore cosmetic edits. At [time], send me a brief under [word limit] with the change, source link, checked time, and what remains unconfirmed. If a material change calls for a message to [person], draft it and hold it for my approval. Do not send a message on my behalf without approval.
Competitor change watch with a sourced morning brief
Set a competitor change watch that checks selected sources, separates material changes from noise, and sends a sourced morning brief.
Copy-ready brief
Example output
Example output, for an illustrative check: Checked 3 named sources at 01:00, 04:00, and 06:30. Material: One official release note describes a new export option. Source: [release note URL]. First seen at 04:00; confirmed at 06:30. Minor: A help page headline changed. The instructions beneath it did not. Unconfirmed: A third-party post mentions a channel change, but the official page has no matching update. Hold this item for the next check. Draft to co-founder: Prepared and waiting for approval. Nothing has been sent.
Trigger and cadence
- A scheduled check reaches its start time.
- Three overnight checks and one morning brief, or a schedule chosen by the reader.
Inputs
- Competitor names and exact pages to check.
- A definition of material changes and cosmetic edits.
- Check times, delivery time, brief length, and recipient of any draft.
Steps
- Open each named source and record its current state and checked time.
- Compare the relevant facts with the previous checked version.
- Verify material findings against an official source where possible.
- Write the brief with source links and clearly marked unknowns.
- Draft any proposed message and hold it for approval.
Approval boundary
A message to another person waits with its exact text and recipient visible.
Stop conditions
- A source cannot be reached or its identity cannot be confirmed.
- Sources conflict on a material point.
- The proposed action exceeds the instruction or lacks a recipient.
Expected output
A short morning brief covering material changes, minor edits, unknowns, and held drafts.
Receipt fields
- Check times and source URLs.
- Comparison decisions and verification status.
- Failed checks, draft text, approval decision, and any send time.
Recovery when it fails
- Mark failed sources and retry at the next scheduled check.
- Keep unconfirmed claims out of the material count until verified.
On this page
What a competitor change watch should report
A competitor change watch should report a verifiable change, its source, and the check time. A useful brief also says when nothing material changed.
OperatorNest can carry out recurring checks, prepare the brief, and hold a proposed message for your approval. The example below is an illustration of the workflow, not a record of a live run.
Start with three to five competitors and a short source list for each. Official pages and release notes provide a baseline. A news article can point to a change, but the brief should distinguish an announcement from a reporter’s inference.
Set the threshold before the first check
Write down what would change a decision you make at work. A founder may care about new channels, approval controls, export options, or a launch in a region where they sell. A sales lead may care about a new integration or an altered service promise. Those are different watch lists.
For example, Sam watches three companies. They classify a new supported channel as material, a revised help article as worth checking, and a changed homepage sentence as minor. The rule gives the operator a way to sort findings without pretending every page diff matters.
Keep a separate category for unknowns. A social post without a matching official update should stay unconfirmed.
Give the watch a repeatable schedule
Choose checks around the decision you need to make. If you want a 7:00 brief, a check at 6:30 leaves time to verify and write. Three overnight checks might fit an active launch week; one daily check can be enough for a slower category. The schedule belongs in the instruction so a missed check is visible.
Record each page’s URL and what to look for there. If access fails, name the source and time. A broken page is not evidence that a feature was removed.
Save the last checked version or a record of relevant facts. Compare it with the next pass and name the difference.
Read the brief as a decision aid
The morning brief works best in four parts:
- The count of material changes, minor edits, and unresolved claims.
- Each material change in one or two sentences, with a link and checked time.
- A short explanation of why the change meets your rule.
- Any draft action, clearly marked as waiting for your decision.
Say Sam’s watch finds an export option on a release page at 04:00 and confirms it at 06:30. The brief should cite the page and identify those as observation times. A note to Sam’s co-founder can be drafted, then held for approval.
The competitor monitoring use case covers the broader task. This workflow is the narrow operating instruction: sources, thresholds, check times, and the shape of the result.
Check the receipt before changing the watch
The receipt should list checks, pages reached, failures, sources for reported changes, and the status of any proposed message.
If briefs contain only minor edits, reduce the check frequency or tighten the source list. If an item arrived late, adjust the next check time.
Run it on a schedule
Plan the timing and missed-run behavior with the recurring task planner. For documented schedule controls across assistants, read scheduled AI tasks compared.
Related tools
- Recurring task planner
Map repeat work to a week or month, estimate monthly hours, decide what to delegate, and download calendar events with recurrence rules.
- AI agent receipt template
Make a task receipt with the request, actions, sources, approvals, uncertain steps, result, model usage, and cost. Copy or download it.
- AI agent approval policy
Set clear approval rules for an AI agent. Choose systems and risk limits, then copy a policy that says what waits and what can run.
Common questions
What if a source changes between scheduled checks?
The next check records the change as first seen at that time. The brief should not claim the change happened at the check time unless the source says so.
How do I stop the brief from filling with cosmetic edits?
List the changes you care about, such as supported channels or approval controls, and explicitly exclude copy, layout and image changes. Review the criteria after a few briefs.
What happens when two sources disagree?
Keep both links, state the disagreement, and mark the point unconfirmed. Do not turn a single report into a product fact.
Keep reading
- An AI competitor monitoring assistant that watches the market for youIt checks competitor pricing and product pages on a schedule and sends a brief only when something changes.
- Recurring tasks that run on their own scheduleSet a standing order once, on a schedule you choose, and it runs on its own from then on.
- A receipt for everything your operator doesEvery task keeps a receipt: what was asked, what ran, which model did it, what it cost, and every approval.
- Set up overnight AI competitor monitoringSet up AI competitor monitoring that runs overnight, checks the right pages on schedule, and brings a sourced brief with one action drafted for approval.
Hand off your first task tonight.
Tell us your email and what you'd hand off first. We'll send your access details and help you set up your operator.