Skip to content

competitive-intel-watch-prompt.md

Latest commit

 

History

History
184 lines (140 loc) · 6.15 KB

competitive-intel-watch-prompt.md

File metadata and controls

184 lines (140 loc) · 6.15 KB
Raw

competitive-intel-watch-prompt.md

Purpose

Monitor a competitive landscape for material shifts since the last run. Diff the world against the previous snapshot; report only what changed, with evidence; flag which downstream artifacts need updating.

Mode

Baseline mode: if no previous snapshot is provided, produce one using the Competitive Research Snapshot structure and stop — the delta value begins next run.

Delta mode (default when a snapshot is provided): diff and report.

Before You Start

Ask at most 2 questions:

  1. Do you have the previous snapshot, or should I create a baseline?
  2. Anything specific you are watching for this cycle?

If unanswered, proceed with labeled assumptions.

Search Plan First

Before researching, show a 3-bullet plan: what you will check per competitor, source types, and how you will separate facts from inferences. Then continue unless asked to revise.

Materiality Bar

Report a change only if a sales rep, pricing owner, or roadmap owner would plausibly act on it:

  • Pricing or packaging changes
  • Product launches, major features, deprecations
  • Positioning or messaging shifts
  • Leadership changes, funding, M&A
  • Major customer wins or losses
  • Credible roadmap signals (hiring patterns, announcements)

Below the bar: cosmetic site changes, routine content marketing, minor releases. When nothing clears the bar, say so plainly.

Source + Trust Rules

Real, checkable URLs with dates. Mixed sources: company sites, pricing pages, release notes, press, investor materials, credible news, review sites, job postings. Do not invent competitors, features, pricing, market share, customer wins, roadmap items, or product claims. Label: Fact (source-supported), Inference (evidence-based interpretation), Assumption (working guess).

Competitive Watch Report

1. Run Header

Scope (from prior snapshot): Prior snapshot date: This run date: Competitors checked:

2. Changelog (Material Shifts Only)

For each material shift:

[Competitor] — [4 to 8 word change summary]

  • What changed: [1-2 bullets, labeled Fact/Inference]
  • Evidence: [URL, date]
  • So what: [why it clears the materiality bar]
  • Confidence: [high / medium / low]

If nothing cleared the bar: "No material shifts this cycle." List anything on the watchlist for next run.

3. Update Flags

Downstream artifact Sections needing update Driven by
Battle card
Positioning statement
Pricing/packaging analysis
Roadmap assumptions

Only rows with real updates; omit the rest.

4. Watchlist for Next Run

  • [Signals below the bar but trending]
  • [Open questions this run could not resolve]

Assumptions to Validate

  • [Assumption 1]
  • [Assumption 2]
  • [Assumption 3]

Final Step

Offer exactly 4 options:

  1. Update the battle card sections flagged above
  2. Deep-dive the most significant change
  3. Produce the refreshed full snapshot (new baseline)
  4. Adjust the materiality bar or competitor list for next run

Ask me to reply with 1, 2, 3, 4, 1 and 2, Verbose Mode, or a custom path.