competitive-intel-watch

Competitive Intel Watch — Competitive Intelligence Delta Monitoring Skill

Skill Overview

Competitive Intel Watch is a competitive intelligence delta-monitoring skill: it uses the previous competitive research snapshot as a baseline, periodically scans competitor activity, reports only entries with material changes, and identifies which sales battlecards or product positioning sections need to be updated accordingly. It can be connected to scheduled tasks and run unattended.

Use Cases

Periodic comparison of competitive snapshots: Run this skill using the competitive research snapshot from the previous quarter or month to quickly determine “what exactly changed among competitors during this period.” It compares differences rather than rewriting a weekly report with largely repetitive content.

Scheduled unattended monitoring: Connect the skill to a recurring or scheduled workflow to automatically inspect competitor websites, pricing pages, release notes, news coverage, job postings, and other sources weekly or monthly. It can continue producing results without anyone watching; in scheduled mode, reports are archived directly, with operational options left to human operators.

Keeping battlecards and positioning documents current: When a competitor makes changes such as pricing adjustments, product launches, or positioning shifts, the skill automatically flags which sales battlecards, positioning statements, pricing analyses, and roadmap assumption sections are outdated, reminding the appropriate owners to update them promptly.

Core Features

Delta Monitoring: First read the previous snapshot in full, then compare it with the results of the current scan and output only entries that have changed. Each change is labeled as a fact or inference and includes a source link and date for direct verification and easier comparison in the next cycle. When there is no baseline on the first run, the skill falls back to “baseline mode” and generates a complete competitive research snapshot.

Materiality Bar: The built-in “materiality threshold” means that only changes likely to prompt action from sales, pricing, or roadmap owners are reported. Examples include pricing and packaging changes, product launches or discontinuations, positioning shifts, executive changes, funding or acquisitions, major customer wins or losses, and credible roadmap signals. Content marketing and minor updates are filtered out as noise, preventing the monitoring system from losing reader trust by over-reporting.

Empty Reports and Update Flags: When competitors have made no material changes, the skill explicitly outputs an empty report stating “No material changes this cycle,” while recording below-threshold but noteworthy developments in the watchlist for the next cycle. An empty report is also a valid conclusion. Every change that clears the threshold is mapped to downstream documents that need updating—battlecards, positioning statements, pricing analyses, and roadmap assumptions—so intelligence leads to action.

Frequently Asked Questions

What should I do if this is the first use and there is no historical snapshot?

You can run it directly. The skill will enter “baseline mode,” generate the first baseline snapshot according to the standard structure for a competitive research snapshot, and then stop. Delta-monitoring mode begins with the second run. If the monitoring scope itself changes—for example, you enter a new market segment or transform the product—you should establish a new baseline rather than continuing to compare against the old scope.

What will be output when competitors have made no material changes?

The skill will output an empty report stating “No material changes this cycle,” while also recording below-threshold but potentially developing trends—such as a competitor publishing content marketing on a particular topic at unusual volume or a previously unseen technology stack appearing in job postings—in the “Watchlist for Next Cycle.” An empty report is a first-class result of this skill: a well-supported finding of “no changes” demonstrates that the monitoring system is operating properly. There is no need to manufacture a report merely to appear productive.

What kinds of changes are considered “worth reporting”?

The default threshold is a change that might prompt action from a sales representative, pricing owner, or roadmap owner. This includes pricing and packaging changes, product launches and discontinuations, positioning shifts, leadership changes, funding or acquisitions, major customer wins or losses, and credible roadmap signals. Website redesigns, routine content marketing, and minor version updates do not qualify. Every reported change must include both a source URL and a date. Without a date, the change cannot be verified or compared in the next cycle. This threshold can be tightened or relaxed as needed.