Skip to content
OperatorNest

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

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.

Illustrative example

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

Trigger
A scheduled check reaches its start time.
Cadence
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

Decide what earns a line

A competitor change watch reports a change you can verify, its source and when you first saw it. Give OperatorNest the exact pages and the changes that would affect your next decision: a new channel, an export format or a region where you sell. A changed headline can stay out of the morning brief.

For example, Sam watches three companies and treats a new supported channel as material. A social post without a matching official update stays in a separate unconfirmed section, with both links so Sam can check it. The example output illustrates that rule.

Set checks around the decision

For a 7:00 brief, a 6:30 check leaves time to verify and write. Three overnight checks can suit an active launch week; one daily pass may cover a slower category. Put the check times, delivery time and time zone in the instruction.

Save the last checked version or relevant facts for each page. If access fails, record the page and time, then retry on the next pass. A failed check means the page was unread, not that its product stayed unchanged.

Read findings, then held drafts

Put the count of material changes first, followed by each change and its source. Explain which threshold it crossed and keep minor edits and unresolved claims below it.

Say Sam’s watch finds an export option at 04:00 and confirms it at 06:30. Those are observation times, not a launch date. OperatorNest can prepare a note to Sam’s co-founder, but the recipient and exact draft wait for approval.

Use the competitor monitoring use case to define the broader job. After the first week, tighten noisy sources or adjust a check that arrived too late; keep the missed checks and any approval decisions in the receipt.

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.

  • 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.

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.