Systematic competitor tracking that feeds CMO positioning, CRO battlecards, and CPO roadmap decisions. Use when analyzing competitors, building sales battlecards, tracking market moves, positioning against alternatives, or when user mentions competitive intelligence, competitive analysis, competitor research, battlecards, win/loss, or market positioning.
cd ~/.claude/skills
git clone https://github.com/alirezarezvani/claude-skills.git claude-skills mkdir -p ~/.claude/skills/competitive-intel
curl -fsSL https://raw.githubusercontent.com/alirezarezvani/claude-skills/HEAD/.gemini/skills/competitive-intel/SKILL.md \
-o ~/.claude/skills/competitive-intel/SKILL.md Systematic competitor tracking. Not obsession — intelligence that drives real decisions.
competitive intelligence, competitor analysis, battlecard, win/loss analysis, competitive positioning, competitive tracking, market intelligence, competitor research, SWOT, competitive map, feature gap analysis, competitive strategy
Ask in natural language for the deliverable you need:
“Map our competitive landscape” — direct, indirect, and future competitors “Build a battlecard for [competitor]” — sales-ready battlecard “Run a win/loss analysis” — recent wins and losses by reason “What did [competitor] do recently?” — competitor update tracking “Build a competitive positioning map” — 2x2 positioning map
Direct competitors: Same ICP, same problem, comparable solution, similar price point. Indirect competitors: Same budget, different solution (including “do nothing” and “build in-house”). Future competitors: Well-funded startups in adjacent space; large incumbents with stated roadmap overlap.
The 2x2 Threat Matrix:
| Same ICP | Different ICP | |
|---|---|---|
| Same problem | Direct threat | Adjacent (watch) |
| Different problem | Displacement risk | Ignore for now |
Update this quarterly. Who’s moved quadrants?
Track these 8 dimensions per competitor:
| Dimension | Sources | Cadence |
|---|---|---|
| Product moves | Changelog, G2/Capterra reviews, Twitter/LinkedIn | Monthly |
| Pricing changes | Pricing page, sales call intel, customer feedback | Triggered |
| Funding | Crunchbase, TechCrunch, LinkedIn | Triggered |
| Hiring signals | LinkedIn job postings, Indeed | Monthly |
| Partnerships | Press releases, co-marketing | Triggered |
| Customer wins | Case studies, review sites, LinkedIn | Monthly |
| Customer losses | Win/loss interviews, churned accounts | Ongoing |
| Messaging shifts | Homepage, ads (Facebook/Google Ad Library) | Quarterly |
SWOT per Competitor:
Competitive Positioning Map (2 axis): Choose axes that matter for your buyers:
Feature Gap Analysis:
| Feature | You | Competitor A | Competitor B | Gap status |
|---|---|---|---|---|
| [Feature] | ✅ | ✅ | ❌ | Your advantage |
| [Feature] | ❌ | ✅ | ✅ | Gap — roadmap? |
| [Feature] | ✅ | ❌ | ❌ | Moat |
| [Feature] | ❌ | ❌ | ✅ | Competitor B only |
For Sales (CRO): Battlecards — one page per competitor, designed for pre-call prep.
See templates/battlecard-template.md
For Marketing (CMO): Positioning update — message shifts, new differentiators, claims to stop or start making.
For Product (CPO): Feature gap summary — what customers ask for that we don’t have, what competitors ship, what to reprioritize.
For CEO/Board: Monthly competitive summary — 1-page: who moved, what it means, recommended responses.
Monthly (scheduled):
Triggered (event-based):
Quarterly:
This is the highest-signal competitive data you have. Most companies do it too rarely.
When to interview:
Who conducts it:
Question structure:
Aggregate findings monthly:
Signs you’re over-tracking competitors:
Signs you’re under-tracking:
The right posture:
| Audience | Format | Cadence | Owner |
|---|---|---|---|
| AEs + SDRs | Updated battlecards in CRM | Monthly + triggered | CRO |
| Product | Feature gap analysis | Quarterly | CPO |
| Marketing | Positioning brief | Quarterly | CMO |
| Leadership | 1-page competitive summary | Monthly | CEO/COO |
| Board | Competitive landscape slide | Quarterly | CEO |
One source of truth: All competitive intel lives in one place (Notion, Confluence, Salesforce). Avoid Slack-only distribution — it disappears.
| Signal | What it means |
|---|---|
| Competitor’s win rate >50% in your core segment | Fundamental positioning problem, not sales problem |
| Same objection from 5+ deals: “competitor has X” | Feature gap that’s real, not just optics |
| Competitor hired 10 engineers in your domain | Major product investment incoming |
| Competitor raised >$20M and targets your ICP | 12-month runway for them to compete hard |
| Prospects evaluate you to justify competitor decision | You’re the “check box” — fix perception or segment |
| Intelligence Type | Feeds To | Output Format |
|---|---|---|
| Product moves | CPO | Roadmap input, feature gap analysis |
| Pricing changes | CRO, CFO | Pricing response recommendations |
| Funding rounds | CEO, CFO | Strategic positioning update |
| Hiring signals | CHRO, CTO | Talent market intelligence |
| Customer wins/losses | CRO, CMO | Battlecard updates, positioning shifts |
| Marketing campaigns | CMO | Counter-positioning, channel intelligence |
references/ci-playbook.md — OSINT sources, win/loss framework, positioning map constructiontemplates/battlecard-template.md — sales battlecard templateYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions