Competitive Intelligence Analyst Copilot

An agent for systematic competitive intelligence gathering covering market research, competitor analysis, SWOT frameworks, and strategic business intelligence to inform product and business strategy decisions.

When to Use This Agent

Choose Competitive Intelligence Analyst when:

• Conducting structured competitor analysis for strategic planning
• Building competitive landscape maps with positioning analysis
• Performing SWOT analysis on competitors or your own products
• Tracking market trends, pricing changes, and feature releases
• Preparing competitive battle cards for sales teams

Consider alternatives when:

• Doing academic research on market theory (use an academic researcher)
• Building marketing content (use a content marketing agent)
• Analyzing internal product metrics (use a data analytics agent)

Quick Start

Copy
# .claude/agents/competitive-intelligence-analyst.yml
name: Competitive Intelligence Analyst
model: claude-sonnet-4-20250514
tools:
  - Read
  - Write
  - Bash
  - Grep
  - WebSearch
prompt: |
  You are a competitive intelligence analyst. Conduct systematic
  market research and competitor analysis. Use SWOT, Porter's
  Five Forces, and positioning frameworks. Deliver actionable
  intelligence with sourced evidence, not speculation.

Example invocation:

Copy
claude --agent competitive-intelligence-analyst "Analyze the top
  5 competitors in the project management SaaS space. Compare
  pricing, key features, target market, and recent strategic moves.
  Create a battle card for our sales team."

Core Concepts

Intelligence Gathering Framework

Method	Purpose	Sources
Feature Tracking	Monitor product changes	Changelogs, release notes, product pages
Pricing Analysis	Track pricing strategies	Pricing pages, annual reports, reviews
Positioning	Understand market claims	Marketing sites, press releases, social
Technology	Identify tech stack choices	Job postings, engineering blogs, patents
Strategy	Predict strategic direction	Earnings calls, interviews, acquisitions
Sentiment	Gauge market perception	Reviews, social media, analyst reports

SWOT Analysis Template

Copy
## SWOT: {Competitor Name}

### Strengths
- {What they do well — features, brand, market share}

### Weaknesses
- {Where they fall short — gaps, complaints, limitations}

### Opportunities
- {Market gaps they could exploit}

### Threats
- {External risks — new entrants, regulation, technology shifts}

Battle Card Format

Copy
## vs. {Competitor}

### Quick Facts
- Founded: {year} | HQ: {location} | Employees: {count}
- Funding: {total raised} | Revenue: {estimated ARR}

### Where We Win
- {Our advantage 1 + supporting evidence}
- {Our advantage 2 + supporting evidence}

### Where They Win
- {Their advantage 1 + how to counter}
- {Their advantage 2 + how to counter}

### Pricing Comparison
| Tier | Us | Them |
|------|-----|------|
| Starter | $X/mo | $Y/mo |
| Pro | $X/mo | $Y/mo |

### Common Objections & Responses
- "They have feature X" → "We offer Y which solves the same problem better because..."

Configuration

Parameter	Description	Default
competitors	Tracked competitor list	Manual input
update_frequency	Intelligence refresh cycle	Monthly
frameworks	Analysis frameworks to use	SWOT, Porter's
output_format	Report format	Markdown
include_pricing	Track pricing data	true
include_features	Track feature changes	true
battle_cards	Generate sales battle cards	true

Best Practices

1. Base analysis on observable evidence, not assumptions. Use specific data points: changelog entries, pricing page screenshots, job postings, SEC filings, and customer reviews. "They're probably working on AI features" is speculation. "They posted 12 ML engineer roles in Q1 and their CEO mentioned AI at the last earnings call" is intelligence. Sourced claims are credible; unsourced claims are opinions.

2. Track changes over time, not just current state. A competitor's pricing page today tells you what they charge now. Tracking it monthly reveals their pricing strategy: are they moving upmarket? Adding a free tier? Increasing prices? Trends in hiring, feature releases, and messaging tell a strategic story that point-in-time snapshots miss. Maintain a time-stamped intelligence database.

3. Organize intelligence by decision it supports, not by competitor. Stakeholders ask "should we build feature X?" not "what is competitor Y doing?" Structure your intelligence to answer strategic questions: "Who offers real-time collaboration, and how?" rather than "Everything about Competitor A." Decision-oriented organization makes intelligence actionable rather than merely informational.

4. Validate competitor claims against user reviews. Marketing pages describe aspirational capabilities. User reviews describe reality. A competitor claiming "enterprise-grade security" might have G2 reviews mentioning security incidents. Cross-reference marketing claims with third-party reviews, social media complaints, and community forum discussions to build an accurate picture.

5. Update battle cards with feedback from lost deals. Sales teams learn the most about competitive strengths from deals they lose. Build a feedback loop where lost-deal analysis feeds back into battle cards. If three deals were lost because "competitor X has better API documentation," that becomes a competitive gap to address, not just a battle card talking point.

Common Issues

Intelligence becomes outdated before it reaches decision-makers. Shorten the cycle from collection to distribution. Automate competitor website monitoring for pricing and feature changes. Send weekly intelligence digests rather than quarterly reports. Flag material changes (new product launch, acquisition, major price change) immediately rather than including them in the next scheduled report.

Analysis lacks objectivity—either too favorable or too alarmist. Assign competitive analysis to someone who doesn't have emotional investment in the product (or use balanced frameworks like SWOT that force examination of both strengths and weaknesses). Have someone from a different team review the analysis for bias. The purpose of competitive intelligence is accurate understanding, not cheerleading or fearmongering.

Competitors' strategies are misinterpreted from surface-level signals. A competitor hiring Kubernetes engineers doesn't necessarily mean they're rebuilding their infrastructure—they might be backfilling departures. Triangulate signals: combine hiring patterns with product announcements, investor communications, and customer feedback before drawing strategic conclusions. Single data points suggest hypotheses; multiple correlated signals confirm them.