Monitor competitor signals and surface strategic implications for your roadmap. Use when asked to monitor competitors, track the competitive landscape, produ...
Documents
Competitor Signal Tracker
Try itAnalyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing chan...
What it does
Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive intelligence report. Produces a categorised signal analysis with reactive-vs-proactive assessment, threat ratings, specific roadmap implications, and recommended responses with owners. For a recurring whole-market briefing use competitive-intelligence-monitor instead.
The skill document
Competitor Signal Tracker Skill
Turn scattered competitor information into structured strategic intelligence — not just "what they did" but "what it means for us."
Required Inputs
Ask the user for these if not provided:
- Competitor name(s) and the signals/updates to analyse
- Your product's current roadmap or strategic priorities (to assess relevance)
- Time period the signals cover (this week, this month, etc.)
Signal Categories to Track
- Product signals: New features, removals, UX changes, beta programmes
- Pricing signals: Changes to tiers, free limits, enterprise terms
- Hiring signals: Job postings that reveal strategic bets (e.g., hiring ML engineers = AI investment)
- Partnership signals: Integrations, acquisitions, ecosystem moves
- Messaging signals: Changes in positioning, target audience, value proposition
Process
- For each competitor update provided, categorise the signal type
- Assess: Is this reactive (responding to market) or proactive (setting direction)?
- Rate strategic threat level: High / Medium / Low / Watch
- Connect to your roadmap: does this accelerate, validate, or challenge any of your bets?
- Recommend a response: Accelerate existing initiative / Deprioritise / Monitor / Investigate further
- Validate — Confirm every High threat has a specific recommended response with an owner. "Monitor" is not an acceptable response for High-rated threats.
Output Structure
Competitive Intelligence Report — [Date]
[Competitor Name]
Signal: [What they did] Signal Type: [Product / Pricing / Hiring / Partnership / Messaging] Reactive or Proactive: [assessment] Threat Level: [High / Medium / Low / Watch] Implication for Us: [Specific connection to our roadmap or strategy] Recommended Response: [Action + owner + timeline]
Strategic Summary
[2-3 sentences on the overall competitive landscape shift this period]
Anti-Patterns
- Do not rate a signal as High threat without explaining the specific roadmap item or customer segment it threatens — unjustified threat ratings lose credibility over time
- Do not treat a hiring signal as definitive proof of a strategic bet — hiring signals require corroboration from product, messaging, or pricing signals before acting on them
- Do not conflate a competitor's announcement with a competitor's shipped capability — press releases and blog posts often describe aspirations, not production features
- Do not recommend "accelerate existing initiative" for every High signal — sometimes the right response is to differentiate harder in an adjacent area rather than race the competitor directly
Quality Checks
- Every signal is categorised (not just described)
- Threat level is justified — not assigned arbitrarily
- High-threat signals have specific recommended responses (not "monitor")
- Implications connect to specific roadmap items or strategic bets
- Strategic summary gives a landscape-level view, not just a list of individual signals
Related skills
Evidence-backed competitor and market analysis
1 installs
Technology-sector competitive landscape analysis with player tiering, route differentiation, and white-space identification. Use when the user asks for player mapping, sector competitor analysis, technology-track player comparison, domestic-vs-overseas player comparison, or any multi-player competitive assessment in a defined technology domain.
1 installs
Competitive landscape analysis, market sizing, and positioning research. Use for "who are the competitors", TAM/SAM/SOM sizing, go-to-market input, or positi...
3 installs
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
1 installs
Research one company before a meeting and hand back a briefing, powered by Cargo — what it does, what it publicly says is hard right now, and who it names as competition, each line traceable to where it came from. Triggers: "research this company", "brief me on this account", "prep me for this meeting", "what should I know about them", "write me a one-pager on", "what are they struggling with", "who do they compete with". Meeting prep, briefing, dossier, talking points. Skip when: you want many companies filtered rather than one understood — use build-tam-list; or you want the people to contact there — use find-stakeholders.
1 installs