Competitor Monitoring Pipeline
Most PMs do competitor monitoring reactively — someone mentions something in Slack, you Google it, you move on. A pipeline flips this: you define what you care about once, and a structured system surfaces the relevant signals on your schedule. This skill has two modes: setup (build the pipeline) and run (process the week's signals).
---
Context
Two modes:
---
Mode 1: Setup — Build the Pipeline
Step 1 — Define the competitor set
Direct competitors, adjacent competitors, and aspirational benchmarks. Maximum 8 competitors.
Step 2 — Define the signal categories
For each competitor, select which signals to track: pricing changes, new feature launches, job postings, leadership changes, funding/M&A, customer reviews, partnership announcements, SEO/content strategy, user community signals, outages/trust events.
Step 3 — Set up tracking sources
Minimum viable: Google Alerts, RSS feeds, LinkedIn notifications, and monthly G2/Capterra review checks.
Step 4 — Build the weekly review template
20-minute weekly review covering: raw signals, signal triage table, high-significance deep analysis, patterns, roadmap implications, and team update.
Mode 2: Weekly Run — Process This Week's Signals
Step 1 — Receive raw signals
Step 2 — Parse each signal (competitor, type, what happened, source, date)
Step 3 — Assess strategic significance using four questions:
Step 4 — Output the weekly review
Deep analysis for high-significance signals with response options including "do nothing."