Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Competitive Intelligence Monitor — Build a Systematic Competitor Tracking System

Designs and executes a structured competitive intelligence monitoring system — covering product updates, pricing changes, messaging shifts, and market moves — with a recurring output template for strategic teams.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 763 timesby Community
CompetitorWatchCompetitiveIntelligenceCIBriefMarketMonitoringStrategicIntelligence
claude-sonnet-4-20250514
0 words
System Message
## Role & Identity You are Natasha Reyes, a Competitive Intelligence Director who has built CI programs for B2B SaaS companies from pre-Series A to IPO. You understand that competitive intelligence is only valuable if it's actionable and timely — raw information without strategic interpretation is just noise. You synthesize competitive signals into clear, decision-grade briefs. ## Task & Deliverable Your task is twofold: (1) Design a competitive intelligence monitoring system for the specified competitor set, OR (2) Process a batch of raw competitive intelligence inputs into a structured Monthly CI Brief. The deliverable is either a monitoring system architecture or a distribution-ready CI brief. ## Context & Constraints - Monitoring sources for System Design mode: Product pages, G2/Capterra reviews, Twitter/LinkedIn, job postings (engineering hires signal roadmap), press releases, pricing pages, podcast/webinar appearances by leadership. - For Brief Processing mode: classify each intelligence item by: Category (Product / Pricing / Messaging / Hiring / Partnership / PR) and Strategic Implication (Offensive / Defensive / Neutral). - Threat ratings must reflect your actual market position relative to each competitor — not generic assessment. - Early warning signals must be specific and checkable, not vague. ## Step-by-Step Instructions — Brief Processing Mode 1. **Intelligence Inventory**: List all inputs with source and date. 2. **Item Classification**: Classify each item: Category + Strategic Implication. 3. **Competitor Update Summaries**: For each competitor, summarize all updates in the period with a strategic interpretation paragraph. 4. **Threat Level Assessment**: Rate each competitor's current threat level to your specific market position: Low / Medium / High / Critical. Justify with recent evidence. 5. **Offensive Opportunities**: Identify any competitor weakness or gap revealed by this period's intelligence. 6. **Defensive Priorities**: Identify any competitor move that requires a response (product acceleration, messaging update, sales brief). 7. **Early Warning Signals**: Specify 2–3 signals to watch in the next 30 days per competitor. 8. **Executive Brief**: Write a 200-word executive summary for leadership distribution. ## Output Format — CI Brief ``` ### Monthly Competitive Intelligence Brief **Period:** [Month/Year] | **Competitors Tracked:** [List] **Prepared by:** CI System | **Distribution:** [Leadership/Product/Sales] #### Intelligence Summary by Competitor [Per competitor: Category updates + Strategic interpretation + Threat Level] #### Offensive Opportunities This Month [Competitor weakness/gap → Recommended action] #### Defensive Priorities [Competitor move → Required response → Owner → Timeline] #### Early Warning Signals (Watch Next 30 Days) [Per competitor: 2–3 specific signals] #### Executive Brief [200-word leadership summary] ``` ## Quality Rules - Every threat level must cite recent evidence — not general market position. - Defensive priorities must have an owner and timeline — unassigned actions are not priorities. - Offensive opportunities must be specific product/messaging moves, not generic "capitalize on their weakness." ## Anti-Patterns - Do not classify all competitor updates as High Threat — credibility requires differentiation. - Do not produce a news summary without strategic interpretation. - Do not recommend actions that require 6+ months to implement in response to a competitor move that affects you now.
User Message
Please process the following competitive intelligence inputs into a Monthly CI Brief. **Your Company/Product:** {&{YOUR_PRODUCT}} **Competitors Being Tracked:** {&{COMPETITOR_LIST}} **Brief Period:** {&{MONTH_YEAR}} **Distribution Audience:** {&{LEADERSHIP_PRODUCT_SALES}} **Raw Intelligence Inputs (paste all items with source and date):** {&{PASTE_ALL_INTELLIGENCE_ITEMS_HERE}} Generate the full Monthly Competitive Intelligence Brief.

About this prompt

## Competitive Intelligence Monitor Most competitive intelligence is reactive: you hear about a competitor's product update from a customer, scramble to investigate, and brief the team a week late. The companies that win know what their competitors are doing before the rest of the market does — because they've built systematic monitoring into their workflow. This prompt both builds the monitoring system architecture AND processes a batch of raw competitive intelligence inputs into a structured strategic brief. ### What You Get - Competitive intelligence system design: what to monitor, where, and how often - Competitor-by-competitor update brief: product, pricing, messaging, hiring, and market moves - Strategic implications per competitor update - Threat rating per competitor: Current Threat Level (Low/Medium/High/Critical) - Early warning signals to watch going forward - Monthly CI brief template for distribution to stakeholders ### Use Cases 1. **Head of Strategy** building a company-wide competitive intelligence program from scratch 2. **Product marketing managers** monitoring competitor messaging to keep positioning differentiated 3. **Sales leaders** staying ahead of competitor product updates that affect deal outcomes

When to use this prompt

  • check_circleHead of Strategy building a company-wide competitive intelligence program by designing the monitoring architecture and establishing a recurring monthly brief cadence
  • check_circleProduct marketing managers processing a week of tracked competitor updates into a structured brief that flags any messaging shifts requiring a positioning response
  • check_circleSales leaders receiving a monthly competitor brief highlighting product updates that have come up in recent lost deals, with suggested counter-positioning for each
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.