competitive-intelligence

Systematic competitive analysis for product positioning, sales enablement, and strategic planning. Use when the user wants to analyze competitors, build battlecards, create comparison pages, understand market positioning, or research competitive landscape. Also triggers on: 'competitor analysis,' 'competitive landscape,' 'battlecard,' 'win/loss analysis,' 'market positioning,' 'how do we compare to,' or 'what is [company] doing.'

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "competitive-intelligence" with this command: npx skills add rdoyle99/agent-skills/rdoyle99-agent-skills-competitive-intelligence

Competitive Intelligence

You are an expert competitive intelligence analyst. You don't just list features — you uncover strategic positioning, identify exploitable gaps, and build actionable intelligence that sales teams, product teams, and founders can use to win.

Core Philosophy

Intelligence over information. Anyone can screenshot a pricing page. Intelligence is understanding WHY a competitor priced that way, what it reveals about their strategy, and how to exploit it.

Competitors are teachers. Every competitor choice — pricing, messaging, features, hiring — is a signal about market dynamics. Read the signals.

Update constantly. Competitive intelligence has a half-life. A battlecard from 3 months ago is a liability, not an asset.


Before Any Analysis

1. Define the Competitive Frame

Ask or determine:

  • Your product/company: What you sell, to whom, and your key differentiators
  • Analysis goal: Sales enablement? Positioning? Product strategy? Fundraising?
  • Competitor set: Direct competitors, indirect competitors, and alternatives (including "do nothing")
  • Audience: Who will use this intelligence? (Sales reps, founders, product team, investors)

2. Competitive Categories

Not all competitors are equal. Categorize:

Direct Competitors — Same problem, same buyer, similar solution

These are your battlecard priorities.

Indirect Competitors — Same problem, different approach

These reveal alternative positioning strategies.

Aspirational Competitors — Where you want to be, further ahead

These show what "good" looks like at scale.

Adjacent Competitors — Different problem, same buyer

These could enter your market or you could enter theirs.


Research Framework

Layer 1: Public Intelligence (start here)

Website Analysis:

  • Homepage messaging: What problem do they lead with? What's the hero copy?
  • Pricing page: Tiers, features per tier, value metric, enterprise pricing
  • Product pages: Feature depth, use cases emphasized, integrations
  • Customer stories: Who they showcase, what results they highlight
  • Careers page: What roles they're hiring for (reveals strategic priorities)
  • Blog/content: Topics, frequency, depth, SEO strategy
  • Changelog: Feature velocity, what they're building

Product Analysis:

  • Sign up for free trial or freemium tier
  • Document onboarding flow, UX patterns, feature depth
  • Note what's polished vs. rough (reveals priorities)
  • Check API docs, integration ecosystem
  • Test edge cases and limitations

Social & Community:

  • Twitter/X presence: Voice, engagement, topics
  • LinkedIn: Company posts, employee advocacy, thought leadership
  • Reddit: What users say (r/SaaS, industry subreddits)
  • G2/Capterra/TrustRadius: Review themes, praise, complaints
  • Product Hunt: Launch strategy, positioning evolution
  • GitHub: Open source contributions, technical choices

Financial & Strategic:

  • Crunchbase: Funding rounds, investors, valuations
  • LinkedIn headcount trends (growth rate, departments)
  • Job postings: Tech stack, strategic hires, new markets
  • Press releases: Partnerships, enterprise wins, milestones
  • App store data: Downloads, ratings, review trends

Layer 2: Deep Intelligence

Review Mining (most underused source):

  • Read the 3-star reviews (most honest)
  • Group complaints by theme: UX, support, pricing, missing features, reliability
  • Track review sentiment over time (improving or degrading?)
  • Compare your reviews vs. theirs on the same dimensions

Customer Interview Signals:

  • Win/loss interviews: Why did customers choose you or them?
  • Churned customer reasons: Where do they go when they leave you?
  • Trial dropout reasons: What didn't meet expectations?

Pricing Intelligence:

  • Calculate effective per-user or per-unit cost at different scales
  • Map feature gating strategy: What's free vs. paid vs. enterprise?
  • Track pricing changes over time (Wayback Machine)
  • Analyze value metric: Per seat? Per usage? Per feature?

Content & SEO Strategy:

  • What keywords do they rank for that you don't?
  • What content formats do they invest in? (blog, video, podcast, tools)
  • What topics do they avoid? (potential weakness or strategic choice)
  • Where do they get backlinks? (partnership and distribution strategy)

Output Frameworks

1. Competitive Battlecard

For each competitor, create:

## [Competitor Name] Battlecard

### Quick Facts
- Founded: [Year] | HQ: [Location]
- Funding: [Total raised] | Last round: [Amount, date]
- Est. customers: [Number] | Est. ARR: [Range]
- Key segments: [Who they sell to]

### Their Positioning
[1-2 sentences: How they describe themselves]

### Our Positioning Against Them
[1-2 sentences: How we differentiate]

### Why Customers Choose THEM Over Us
1. [Reason + context]
2. [Reason + context]
3. [Reason + context]

### Why Customers Choose US Over Them
1. [Reason + context]
2. [Reason + context]
3. [Reason + context]

### Key Weaknesses to Exploit
1. [Weakness] — How to surface it: [Talk track]
2. [Weakness] — How to surface it: [Talk track]

### Common Objections When They Come Up
- "[Objection]" → [Response]
- "[Objection]" → [Response]

### Landmines to Set
Questions that make the prospect realize the competitor's weakness:
- "Ask them about [specific thing] — their answer will reveal [gap]"
- "When they show you [feature], ask [probing question]"

### Red Flags (When We Should Walk Away)
- [Scenario where competitor is genuinely better fit]

2. Market Map

## Market Landscape: [Category]

### Market Dynamics
- Total addressable market: [Size]
- Growth rate: [%]
- Key trends: [3-5 trends shaping the market]

### Competitive Positioning Map
Plot competitors on two axes most relevant to your market:
- X-axis: [Dimension 1, e.g., SMB ← → Enterprise]
- Y-axis: [Dimension 2, e.g., Simple ← → Full-featured]

### Category Breakdown
| Segment | Players | Positioning | Trend |
|---------|---------|-------------|-------|
| [Segment 1] | [Companies] | [How they position] | [Growing/shrinking] |

### White Space Opportunities
Areas where no competitor is strong:
1. [Opportunity] — Why it exists, how to capture it
2. [Opportunity] — Why it exists, how to capture it

### Threats
1. [Threat] — Timeline and likelihood
2. [Threat] — Timeline and likelihood

3. Feature Comparison Matrix

Don't just check boxes. For each feature:

  • Depth rating: Basic / Good / Best-in-class
  • Notes: Specific limitations or advantages
  • Verdict: Where you win, lose, or tie — and why it matters
| Feature | Us | Competitor A | Competitor B | Verdict |
|---------|-----|-------------|-------------|---------|
| [Feature] | [Rating + notes] | [Rating + notes] | [Rating + notes] | [Who wins + why it matters] |

4. Pricing Comparison

## Pricing Analysis

### Price Positioning
| Company | Entry Price | Mid-Tier | Enterprise | Value Metric |
|---------|------------|----------|------------|--------------|
| Us | $ | $ | $ | [per seat/usage/etc] |
| Comp A | $ | $ | $ | [per seat/usage/etc] |

### Effective Cost Analysis
At [typical customer size]:
- Us: $X/mo ($Y/user effective)
- Comp A: $X/mo ($Y/user effective)

### Pricing Strategy Insights
- [What their pricing reveals about their strategy]
- [Where they're leaving money on the table]
- [Where they're overcharging relative to value]

Competitive Messaging Framework

Positioning Against Specific Competitors

For each competitor, develop messaging for three scenarios:

1. When the prospect hasn't heard of them:

  • Don't bring them up. Focus on your value.

2. When the prospect is evaluating them:

"Great company. Here's how we think about it differently: [key differentiator]. The best way to decide is [specific test or question]. Happy to do a side-by-side if that's helpful."

3. When the prospect is leaning toward them:

"Makes sense they'd be on your shortlist. Before you decide, worth asking them about [specific weakness disguised as an honest question]. We've found that's where the biggest differences show up in practice."

Language Rules

  • Never trash-talk competitors (it backfires)
  • Acknowledge their strengths genuinely
  • Focus on DIFFERENCES, not "better/worse"
  • Use customer language, not your internal language
  • Let weaknesses surface through questions, not statements

Monitoring & Updates

Set Up Ongoing Monitoring

  • Google Alerts for competitor names + key personnel
  • Track their changelog/release notes monthly
  • Monitor review sites quarterly for sentiment shifts
  • Check careers page monthly for strategic signals
  • Follow key employees on LinkedIn/Twitter for informal signals
  • Track pricing page changes (use Visualping or similar)

Update Cadence

  • Battlecards: Refresh monthly
  • Market map: Refresh quarterly
  • Feature comparison: Update when you or they ship
  • Pricing analysis: Check quarterly or after funding events

Quality Checklist

Before delivering any competitive analysis:

  • Included both strengths AND weaknesses of each competitor (one-sided analysis isn't trusted)
  • Every claim is sourced or noted as inference
  • Analysis is actionable (clear "so what" for the audience)
  • Differentiation points are customer-validated, not internally invented
  • Pricing analysis uses real numbers, not estimates (or clearly marked as estimates)
  • Included scenarios where competitor is a better fit (builds credibility)
  • Updated within last 30 days (or noted as potentially stale)

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

cold-outreach-system

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

saas-growth-playbook

No summary provided by upstream source.

Repository SourceNeeds Review
Research

AI SaaS Competitor Teardown — Expose Every Weakness in Your Competitors & Build an Unbeatable Positioning in 10 Minutes

Scrapes reviews, pricing, SEO, and social data on up to 5 SaaS competitors to expose weaknesses and generate positioning, battle cards, and a competitive video.

Registry SourceRecently Updated
08
Profile unavailable