Competitive Teardown

Competitive Teardown

Production-grade competitor analysis framework covering systematic data collection across 6 intelligence sources, a 12-dimension scoring rubric, feature comparison matrices, SWOT analysis, pricing model deconstruction, UX audit methodology, and strategic action plans. Produces battle-card-ready output and stakeholder presentation templates.

Table of Contents

• When to Use
• Teardown Workflow
• Data Collection Framework
• 12-Dimension Scoring Rubric
• Feature Comparison Matrix
• Pricing Analysis Framework
• SWOT Analysis Template
• UX Audit Methodology
• Positioning Map
• Action Plan Framework
• Battle Card Template
• Stakeholder Presentation
• Output Artifacts
• Related Skills

When to Use

Clarify First

Before running the teardown, confirm these inputs. If any is unknown or vague, ASK — do not assume:

• Competitors + primary focus — the 2-4 names and which is the main threat (sets scorecard columns and depth)
• Your own product baseline — so the 12-dimension scorecard and feature matrix have a "you" column to compare against
• Decision this feeds — roadmap session, sales battle card, or new-market entry (determines full teardown vs single battle card vs segment incumbents)
• Available data sources — pricing pages, 50+ reviews, product access (the rubric needs evidence; thin data caps which dimensions are scorable)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the teardown.

Teardown Workflow

Step-by-Step Process

1. Define competitors -- List 2-4 competitors. Confirm which is the primary focus.
2. Collect data -- Gather intelligence from at least 3 of the 6 sources per competitor.
3. Score using rubric -- Apply the 12-dimension rubric to produce a numeric scorecard.
4. Generate comparison outputs -- Feature matrix, pricing analysis, SWOT, positioning map.
5. Build action plan -- Translate findings into quick wins, medium-term, and strategic priorities.
6. Package for stakeholders -- Assemble the presentation or battle card.

Validation Checkpoints

• Before scoring: Confirm you have pricing data, 20+ user reviews, and recent product data
• Before action plan: Every dimension should have a score and supporting evidence
• Before presentation: Every recommendation should tie back to a data point

Data Collection Framework

Source 1: Website and Product Analysis

Source 2: User Reviews

Platforms: G2, Capterra, TrustRadius, App Store, Product Hunt

Sample size target: 50+ reviews per competitor for reliable themes.

Source 3: Job Postings

Source 4: SEO and Content Analysis

Source 5: Social Media and Community

Source 6: Financial and Market Data

12-Dimension Scoring Rubric

Score each competitor (and your own product) on a 1-5 scale with evidence notes.

Scoring Output Format

Feature Comparison Matrix

Matrix Structure

Score per cell: Full = 5, Partial = 3, Basic = 2, Missing = 0

Pricing Analysis Framework

Pricing Model Comparison

Pricing Position Map

SWOT Analysis Template

For each competitor, produce:

Competitor SWOT

Evidence rule: Every bullet must cite the data source (review quote, pricing page, job posting count, feature comparison, etc.).

UX Audit Methodology

First-Run Experience Audit

Core Workflow Audit

For the 3 most common workflows, compare:

Positioning Map

2x2 Positioning Map

Choose the two axes most relevant to your market:

Map Template

                    High Price / Enterprise
                          │
                          │
          [Competitor B]  │  [Competitor C]
                          │
  Simple ─────────────────┼─────────────────── Complex
                          │
          [YOUR PRODUCT]  │  [Competitor A]
                          │
                          │
                    Low Price / SMB

Action Plan Framework

Three Horizons

Priority Scoring

For each action item, score:

Battle Card Template

One-Page Battle Card

COMPETITOR: [Name]
LAST UPDATED: [Date]
THREAT LEVEL: [LOW / MEDIUM / HIGH / CRITICAL]

THEIR POSITIONING: [1 sentence]
OUR POSITIONING AGAINST THEM: [1 sentence]

WHERE THEY WIN:
- [Strength 1 with evidence]
- [Strength 2 with evidence]
- [Strength 3 with evidence]

WHERE WE WIN:
- [Advantage 1 with evidence]
- [Advantage 2 with evidence]
- [Advantage 3 with evidence]

LANDMINES (questions that expose their weaknesses):
- "How does [competitor] handle [weakness area]?"
- "Can you show me [feature they lack]?"
- "What do their customers say about [common complaint]?"

OBJECTION HANDLING:
- "They're cheaper" → [Response with value framing]
- "They have [feature]" → [Response with alternative/roadmap]
- "Everyone uses them" → [Response with differentiation]

PRICING COMPARISON:
[Quick comparison table]

CUSTOMER QUOTE:
"[Quote from a customer who switched from this competitor to you]"

Stakeholder Presentation

7-Slide Structure

Output Artifacts

Related Skills

• competitor-alternatives -- Use for creating comparison and alternative pages for SEO/marketing. Competitive-teardown provides the intelligence; competitor-alternatives produces the marketing content.
• pricing-strategy -- Use when competitive analysis reveals pricing misalignment. Feed teardown pricing data into pricing-strategy.
• page-cro -- Use for optimizing your comparison or competitor landing pages for conversion.
• content-creator -- Use for writing competitive content (blog posts, comparison guides) based on teardown findings.

Tool Reference

1. competitor_scorer.py

Purpose: Score competitors across the 12-dimension rubric and generate a numeric comparison scorecard.

python scripts/competitor_scorer.py competitor_data.json
python scripts/competitor_scorer.py competitor_data.json --json

2. feature_matrix_builder.py

Purpose: Build a feature comparison matrix from structured feature data and calculate coverage scores.

python scripts/feature_matrix_builder.py features.json
python scripts/feature_matrix_builder.py features.json --json

3. battle_card_generator.py

Purpose: Generate a one-page battle card from competitor data for sales team use.

python scripts/battle_card_generator.py competitor_profile.json
python scripts/battle_card_generator.py competitor_profile.json --json

Troubleshooting

Success Criteria

• 12-dimension scorecard completed with evidence notes for every score
• Feature matrix covers at least 80% of features that prospects evaluate
• Battle cards reviewed and approved by 3+ sales representatives
• Pricing data verified within the last 30 days
• Teardown produces at least 3 actionable quick wins and 2 strategic priorities
• Stakeholder presentation reviewed and feedback incorporated within 1 week
• Teardown data refreshed quarterly with score trend tracking

Scope & Limitations

• In scope: Product analysis, feature comparison, pricing deconstruction, UX audit, SWOT analysis, battle card creation, action plan generation
• Out of scope: Primary market research (customer interviews, surveys), financial modeling, legal competitive analysis, intellectual property assessment
• Data dependency: Quality depends on publicly available data, user reviews, and product access; some competitors may have limited public information
• Bias risk: Teardowns conducted by internal teams may have confirmation bias; consider external validation for high-stakes decisions
• Point-in-time: Teardowns are snapshots; competitors evolve continuously -- schedule regular refreshes

Integration Points

• competitor-alternatives -- Teardown provides the data; competitor-alternatives produces the marketing content (comparison and alternative pages)
• pricing-strategy -- When teardown reveals pricing misalignment, feed pricing data into pricing-strategy for repositioning analysis
• page-cro -- Use for optimizing your comparison or competitor landing pages for conversion after teardown produces the content
• sales-engineer -- Battle cards feed directly into sales engineering competitive positioning and RFP responses
• customer-success-manager -- When exit surveys reveal COMPETITOR as a top churn reason, use teardown data to understand what competitors offer that you do not