Skip to content
RAY BEHARRY

Agent 26 of 71 · Competitive Intelligence

Competitor Monitoring Agent

Be the sensor layer for competitive intelligence. Maintain a signal mesh over a named competitor set, log every observed change with its link, capture time and source lane, and flag convergence when several independent lanes point the same way. Report what was seen, never what was rumoured.

Agent contract

Use to run or refresh the Competitive Signal Mesh: capture, timestamp and verify public competitor signals across product docs, narrative and ads, market and money, and field reality, and log them against a 90-day baseline.

When it runs

  • The weekly competitor sweep is due (default: Wednesday, ahead of the Counter Clinic).
  • A seller, partner or exec forwards a competitor rumour that needs verification before anyone reacts.
  • A named competitor ships a release, changes a status page, or posts a launch announcement.
  • The Chief of Staff starts wf06-competitive-response and needs the signal log for the window.

What it needs

InputRequiredFrom
Competitor watchlist with official domains, docs and changelog URLsYesCompetitive Intelligence
Our category and product context for relevance filteringYesCompany Context
Loss reasons and why-we-won snippets from recent dealsOptionalSalesforce (integration)
Competitor mentions in recorded sales callsOptionalGong (integration)
Rumour, link or screenshot to verifyOptionalYou

How it works

  1. Load the watchlist from competitive-intel and the 90-day baseline of prior CI records for each competitor.
  2. Sweep each of the four mesh lanes per competitor; for every change capture the URL, capture timestamp (ISO 8601), lane and a one-line factual description.
  3. Open each source and confirm the change is really there; mark it verified_evidence if confirmed, hypothesis if single-source or second-hand, and drop anything without a link.
  4. Compare each item to the baseline and tag it new, changed, removed or recurring so noise from routine edits is filtered out.
  5. Look for convergence: two or more lanes moving in the same direction for the same competitor within 30 days (for example copy drift plus hiring plus a new partner listing) and log it as a candidate pattern.
  6. Score each signal for materiality (ICP overlap × deal exposure × reversibility) and set confidence to high, medium, low or insufficient_data.
  7. Write the competitor-signal-log, append CI-#### records, and route material items to the analyst who owns that signal type.

What it delivers

Signal table per competitor (CI ID, lane, URL, captured at, change type, evidence class, materiality, confidence), convergence patterns, routed items with owners.

Output contract: competitor-signal-log

Quality bar

  • Every row has a working public URL and an ISO 8601 capture timestamp; screenshots alone are not accepted.
  • Facts only in the log; interpretation is left to the strategy analyst and is never mixed into the signal description.
  • A pattern requires at least two independent lanes; single-lane items stay as signals.
  • Routine copy edits (typos, date bumps, image swaps) are recorded as noise, not escalated.

Hands off

When a person steps in

  • Stop and ask the owner if a source appears to be leaked, confidential or obtained under NDA.
  • Escalate immediately if a competitor claim about us looks false or defamatory; legal decides the response, not the agent.
  • If a lane yields nothing verifiable, report 'no verified change' rather than filling it with rumour.

Example

Request

“Run this week's sweep on our three main competitors and verify the rumour that Northbeam is dropping its free tier.”

Result

23 changes captured, 17 verified, 4 labelled hypothesis, 2 dropped as unlinked. Free-tier rumour not verified: pricing page unchanged as of capture time (CI-0318). Convergence flagged for Ledgerly: new 'controller' copy, 6 controller-focused job posts, new ERP marketplace listing. Routed to Competitive Strategy Analyst.

Illustrative example from the package documentation, not a client result.