41 lines
1.3 KiB
Markdown
41 lines
1.3 KiB
Markdown
# Competitor Tracking
|
|
|
|
Systematic competitor analysis for developer tools. Track features, pricing, positioning, content strategy, and developer sentiment across your competitive landscape.
|
|
|
|
## What This Skill Covers
|
|
|
|
- Competitor identification (direct, indirect, DIY alternatives, platforms)
|
|
- What to track: features, pricing, positioning, content, community signals
|
|
- GitHub/npm/PyPI monitoring for traction signals
|
|
- Developer sentiment monitoring
|
|
- Building and maintaining competitive battlecards
|
|
- When and how to respond to competitor moves
|
|
|
|
## Recommended Tools
|
|
|
|
- **Social listening tools** — Monitor competitor sentiment across developer platforms
|
|
- **GitHub/npm monitoring** — Track competitor traction signals
|
|
|
|
## Quick Start
|
|
|
|
1. Map your competitive landscape (direct, indirect, DIY, platform)
|
|
2. Set up monitoring keywords for each competitor
|
|
3. Create initial battlecards for top 3-5 competitors
|
|
4. Establish review cadence (monthly for major, quarterly for minor)
|
|
5. Build response playbooks for common scenarios
|
|
|
|
## Battlecard Template
|
|
|
|
1. Competitor Overview
|
|
2. When We Win (scenarios, customer types, proof points)
|
|
3. When We Lose (watch-outs, mitigation strategies)
|
|
4. Common Objections + Responses
|
|
5. Competitive Differentiation
|
|
6. Landmines to Set
|
|
|
|
## Related Skills
|
|
|
|
- developer-listening
|
|
- alternatives-pages
|
|
- positioning
|