competitor-tracking

Files (2)

• README.md
• SKILL.md

SKILL.md (first lines)

# Competitor Tracking

Systematic framework for tracking competitors in the developer tools space, from identification through ongoing monitoring and battlecard creation.

## Overview

Competitor tracking for developer tools requires monitoring multiple dimensions: product features, pricing, developer sentiment, content strategy, community growth, and funding/trajectory. Unlike consumer products, developer tools compete on technical merit, documentation quality, and community trust.

Effective competitor tracking helps you:
- Understand your competitive positioning
- Anticipate competitor moves
- Arm sales and marketing with accurate battlecards
- Identify market gaps and opportunities
- Learn from competitor successes and failures

## Competitor Identification

### Types of Competitors

**Direct Competitors:**
- Same category, same target developer
- Solve the same core problem
- Would appear in the same "best X tools" lists
- Example: If you're a CI/CD tool, other CI/CD tools

**Indirect Competitors:**
- Adjacent categories that overlap with your use case
- Might be expanding into your space
- Developers might use instead of your category
- Example: GitHub Actions competing with standalone CI tools

**DIY Alternatives:**
- Open source tools developers self-host
- Custom scripts and internal tooling
- "Just use bash scripts" or "build it yourself"
- Often your biggest competitor by volume

**Platform Alternatives:**
- Cloud provider native services (AWS, GCP, Azure equivalents)
- All-in-one platforms that include your functionality
- Enterprise suite solutions

### Competitive Landscape Mapping

Create a competitive landscape document with:

1. **Competitor profiles** - Company, product, target market, positioning
2. **Feature matrix** - Core features compared across competitors
3. **Pricing comparison** - Tiers, pricing model, enterprise pricing signals
4. **Strengths/weaknesses** - Honest assessment of each competitor
5. **Trajectory** - Funding, growth signals, strategic direction

## What to Track

### Product and Features

**Track weekly/monthly:**
- Changelog and release notes
- New feature announcements
- Pricing changes
- Integration announcements
- API changes
- SDK/library updates

**How to track:**
- Subscribe to competitor newsletters
- Follow their GitHub releases
- Monitor their Twitter/blog
- Set up monitoring alerts for "[competitor] launch" "[competitor] announces"

### Pricing and Packaging

**Key signals:**
- Pricing page changes (use archive.org to track history)
- New tier introductions
- Enterprise/custom pricing signals
- Free tier changes
- Usage-based vs seat-based shifts

**Competitive pricing intelligence:**
- What's included in free tier?
- Where are the upgrade triggers?
- How do they handle overages?
- What's the enterprise motion?

### Positioning and Messaging

**Track changes in:**
- Homepage headline and hero
- "Who it's for" positioning
- Primary use cases emphasized
- Comparison pages (how they position against others)
- Case studies and social proof

**Analyze:**
- What problem do they lead with?
- What audience are they targeting?
- What's their unique angle?
- How are they different from 6 months ago?

### Content Strategy

**Monitor:**
- Blog post frequency and topics
- Documentation quality and coverage
- Video/tutorial content
- Conference talks and sponsorships
- Developer education initiatives

**Look for:**
- SEO plays (what keywords are they targeting?)
- Content gaps you can exploit
- Successful content formats to learn from

### Community and Traction

**GitHub signals:**
- Stars/forks growth rate
- Issue volume and response time

From jonathimer/devmarketing-skills, MIT.

More from jonathimer/devmarketing-skills