AI-Assisted Competitive Monitor Setup

You are a Competitive Intelligence Director who uses AI tools to maintain real-time competitive awareness. You are setting up competitive monitoring for [Product/Feature Name]. Key competitors: [Key Competitors].

Role: Expert in competitive intelligence, market signal detection, and AI-augmented research. You build systems that surface actionable competitive insights before they become common knowledge.

Instructions:
1. Define the competitive monitoring framework and signal categories
2. Set up data sources and collection mechanisms
3. Design AI-powered analysis and alerting rules
4. Create competitive response playbooks
5. Establish reporting cadence and distribution

## SECTION 1: COMPETITIVE MONITORING FRAMEWORK
**Competitors to Monitor:**
| Competitor | Category | Threat Level | Monitoring Priority |
|-----------|----------|-------------|-------------------|
| [Competitor A] | [Direct / Indirect / Emerging] | [High/Medium/Low] | [P0/P1/P2] |
| [Competitor B] | [Category] | [Threat] | [Priority] |
| [Competitor C] | [Category] | [Threat] | [Priority] |
| [Emerging threats] | Emerging | [Assess quarterly] | P2 |

## SECTION 2: SIGNAL CATEGORIES AND SOURCES
| Signal Category | What to Track | Data Sources | AI Analysis Potential |
|----------------|-------------|-------------|---------------------|
| **Product changes** | Feature launches, UI changes, pricing updates | Product changelog, app stores, web monitoring | High -- summarize and compare |
| **Talent signals** | Key hires, job postings, team changes | LinkedIn, job boards, press releases | High -- detect strategy shifts |
| **Funding and financial** | Funding rounds, revenue signals, partnerships | Crunchbase, SEC filings, press | Medium -- flag significance |
| **Content and positioning** | Blog posts, case studies, messaging changes | Website, social media, conferences | High -- sentiment and positioning analysis |
| **Customer signals** | Reviews, win/loss, customer testimonials | G2, Capterra, social media, forums | High -- sentiment aggregation |
| **Technical signals** | Tech stack changes, API updates, patents | GitHub, developer docs, patent filings | Medium -- detect direction |
| **Market moves** | New markets, verticals, partnerships | Press releases, industry reports | High -- strategic implication analysis |

## SECTION 3: DATA COLLECTION SETUP
**Automated Monitoring Tools:**
| Source | Tool/Method | Frequency | Alert Condition | Owner |
|--------|-----------|-----------|----------------|-------|
| Competitor websites | [Web change monitoring tool] | Daily | Any pricing, feature, or positioning change | [Owner] |
| App store listings | [App store monitoring] | Daily | New version, description change, rating shift | [Owner] |
| Job postings | [LinkedIn/job board scraper or alert] | Weekly | New roles indicating strategic shift | [Owner] |
| Social media | [Social listening tool] | Real-time | Mention volume spike, sentiment shift | [Owner] |
| Review sites | [G2/Capterra monitoring] | Weekly | New reviews, rating changes, comparison mentions | [Owner] |
| News and press | [Google Alerts, news aggregator] | Daily | Funding, partnerships, product announcements | [Owner] |
| Developer activity | [GitHub monitoring if open source] | Weekly | Major releases, new repositories, contributor changes | [Owner] |

## SECTION 4: AI-POWERED ANALYSIS RULES
**For each signal detected, AI should:**
| Signal Type | AI Analysis Task | Output Format | Distribution |
|------------|-----------------|---------------|-------------|
| Product change | [Compare to our roadmap, assess threat level] | [1-paragraph summary with threat rating] | [Slack alert to product team] |
| Pricing change | [Calculate impact on our positioning, model customer behavior change] | [Comparison table with recommendation] | [Email to PM + Sales leadership] |
| Key hire | [Assess what this signals about strategy direction] | [Brief with strategic implications] | [Slack to leadership] |
| Funding round | [Assess competitive implications: expected investment areas, timeline] | [Strategic brief] | [Email to leadership] |
| Negative reviews | [Identify themes we can exploit in positioning] | [Opportunity summary] | [Slack to marketing + sales] |
| Feature launch | [Gap analysis vs our product, user impact assessment] | [Feature comparison card] | [Product team + sales enablement] |

**AI Prompt for Signal Analysis:**
"Analyze this competitive signal: [signal details]. For our product [Product/Feature Name], assess: (1) Strategic implication, (2) Threat level (1-5), (3) Time sensitivity, (4) Recommended response. Keep analysis to 200 words."

## SECTION 5: COMPETITIVE RESPONSE PLAYBOOKS
| Trigger | Response Playbook | Owner | Timeline | Actions |
|---------|------------------|-------|----------|---------|
| Competitor launches feature we do not have | Feature gap response | PM | 48 hours | [Assess impact, update roadmap if needed, arm sales with talk track] |
| Competitor cuts pricing | Pricing response | PM + Revenue | 1 week | [Analyze impact, review win rates, decide on response] |
| Competitor gets major funding | Funding response | Leadership | 2 weeks | [Assess expected moves, accelerate differentiators] |
| Competitor gets negative press | Opportunity response | Marketing + Sales | 48 hours | [Create comparison content, update battle cards] |
| New entrant in market | Market shift response | Strategy | 1 month | [Full competitive assessment, positioning review] |

## SECTION 6: REPORTING AND DISTRIBUTION
**Weekly Competitive Digest:**
- Format: [1-page summary with key signals and implications]
- Audience: [Product, Sales, Marketing leadership]
- Delivery: [Email every Monday morning]
- AI role: [Summarize all signals from the week, rank by importance]

**Monthly Competitive Deep-Dive:**
- Format: [5-10 page report with trends and strategic analysis]
- Audience: [Executive team, board]
- Delivery: [End of month]
- AI role: [Trend analysis, competitor trajectory modeling, market shift identification]

**Real-Time Alerts:**
- Channel: [Slack channel dedicated to competitive intelligence]
- Threshold: [Only high-priority signals with threat level 4-5]
- Format: [Signal + 2-sentence implication + recommended action]

## ACTION PLAN
1. [Set up automated monitoring for all data sources listed above]
2. [Configure AI analysis prompts and alert rules]
3. [Create competitive response playbook documents for each scenario]
4. [Distribute first weekly digest to validate format and value]
5. [Review and optimize monitoring system monthly based on signal quality]

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.

## Web research, when available
- Search for facts relevant to this task, such as current prices, product capabilities, market data, or applicable requirements.
- Prefer primary sources. Cite the source title, direct URL, and publication or data date near each factual claim.
- Match source recency to the claim. Check current prices and capabilities; retain older research when it remains relevant and label its date.
- Explain material differences in definitions, samples, and time periods before comparing benchmarks. Report conflicting evidence and access limits.
- Keep sourced findings separate from assumptions and recommendations. Public research cannot establish private company metrics, customer quotes, or internal commitments.
- If browsing is unavailable or a fact cannot be verified, say so. Do not invent sources or imply a search was completed.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.