Contents

Chapter 1

Competitive Intelligence Process Guide

Purpose: Build a sustainable competitive intelligence program that keeps your team informed without consuming all your time. This guide covers sources, cadence, distribution, and how to get organizational buy-in.


Why You Need a CI Program

Most companies do competitive analysis as a one-time project — "the big competitive review" — that becomes outdated within 3 months. A CI *program* is different: it's a continuous, lightweight process that keeps competitive knowledge current and distributed.

Without a CI program, you will:

  • Lose deals because sales reps don't know about a competitor's new feature
  • Build features that competitors already ship better
  • Get surprised by competitor funding rounds, pivots, or pricing changes
  • Waste time with ad-hoc "can someone tell me about Competitor X?" requests

With a CI program, you will:

  • Equip sales with current battlecards that reflect this month's competitive reality
  • Make informed product bets based on real competitive gaps
  • Spot market shifts early (new entrants, pricing trends, feature convergence)
  • Build organizational muscle around competitive awareness

CI Program Components

1. Intelligence Sources

#### Primary Sources (Highest Signal)

SourceWhat You LearnCadenceEffort
Win/loss interviewsWhy buyers choose (or don't choose) youOngoing (2-8/month)High
Customer conversationsHow customers perceive you vs competitorsEvery CS call (tag insights)Low (if systematic)
Sales call recordingsWhat competitors say about you; what buyers ask aboutWeekly review of tagged callsMedium
Competitor product trialsFirst-hand experience with competitor UX, features, performanceQuarterly deep diveHigh
Industry events / conferencesCompetitor messaging, roadmap hints, partner announcements2-4 events/yearHigh

#### Secondary Sources (Good Coverage)

SourceWhat You LearnCadenceEffort
Competitor websites / blogsPositioning changes, feature announcements, case studiesWeekly scanLow
Press releases / funding newsStrategic moves, financial health, executive changesAs they happen (set alerts)Low
Job postingsWhere they're investing (hiring ML engineers? sales reps? compliance staff?)Monthly scanLow
Review sites (G2, Capterra)Customer sentiment, feature gaps, satisfaction trendsMonthly scanLow
Social media / communitiesDeveloper sentiment, user complaints, feature requestsWeekly scanLow
Patent filingsTechnology direction, innovation areasQuarterly scanLow
Analyst reportsMarket landscape, vendor positioning, growth projectionsAs publishedLow

#### Setting Up Automated Monitoring

Google Alerts (free, immediate):

  • Create alerts for each competitor name
  • Create alerts for "[competitor] + review"
  • Create alerts for your product category + "comparison"
  • Deliver to a shared inbox or Slack channel

Review site monitoring:

  • Set up G2 and Capterra alerts for your competitors
  • Track star ratings over time — a declining trend signals opportunity

Job posting monitoring:

  • Check competitor career pages monthly
  • Look for new roles that signal strategic shifts (e.g., a B2C company hiring enterprise sales reps means they're moving upmarket)

Social monitoring:

  • Follow competitor founders and product leads on LinkedIn and Twitter/X
  • Monitor relevant subreddits and Hacker News
  • Join industry Slack communities where your buyers congregate

2. Intelligence Processing

Raw intelligence is noise. Processing turns it into signal.

#### Weekly CI Triage (30 minutes)

Every week, one person (CI owner) reviews the collected intelligence and answers three questions:

1. What changed? — New product launch, pricing update, executive hire, funding round, customer win/loss, messaging shift

2. So what? — Does this change anything about how we compete? Does it affect our positioning, pricing, or product roadmap?

3. Now what? — Is there an action to take? Update a battlecard? Alert the sales team? Brief the product team?

#### Processing Template

=== WEEKLY CI TRIAGE: Week of [DATE] ===

## What Changed
- [Competitor A]: [Change description]
- [Competitor B]: [Change description]

## Impact Assessment
- [Change 1]: Impact = [High/Medium/Low]. Affects: [Sales/Product/Marketing]
- [Change 2]: Impact = [High/Medium/Low]. Affects: [Sales/Product/Marketing]

## Actions Required
- [ ] [Action description] — Owner: [Name] — Due: [Date]
- [ ] [Action description] — Owner: [Name] — Due: [Date]

## No Action Needed (Awareness Only)
- [Item] — Reason: [Why it doesn't require action right now]

3. Intelligence Distribution

The best CI in the world is worthless if it doesn't reach the people who need it.

#### Distribution Matrix

AudienceWhat They NeedFormatFrequency
Sales / AEsBattlecards, objection handling, competitive landmines, pricing comparisonsOne-page battlecards + Slack alerts for urgent changesBattlecards: monthly updates. Alerts: real-time
Sales leadershipWin rates by competitor, deal trends, competitive loss reasonsDashboard or quarterly reportMonthly metrics, quarterly deep dive
Product teamFeature gaps, customer-requested capabilities, competitor roadmap signalsFeature comparison matrix + quarterly CI briefingMonthly matrix update, quarterly briefing
Product marketingPositioning shifts, messaging changes, new competitor narrativesMessaging docs + positioning mapsAs messaging shifts occur
Executive teamMarket landscape, strategic threats, investment themesQuarterly strategy briefQuarterly

#### CI Communication Channels

Slack/Teams Channel: #competitive-intel

  • Purpose: Real-time intelligence sharing
  • Rules: Anyone can post a competitive insight; CI owner tags with priority and category
  • Format: "[COMPETITOR] [CATEGORY] — [One-line summary]. Details: [link/details]"
  • Example: "[AlphaFlow] [PRODUCT] — Launched AI-powered workflow builder. Positions against manual configuration. Details: [link to their blog post]"

Monthly CI Newsletter (Internal)

  • Send on the first Monday of each month
  • Sections: Top 3 Competitive Moves, Updated Battlecards, Win/Loss Highlights, Market Trends
  • Keep it to one page — executives won't read more

Quarterly CI Briefing (Meeting)

  • 30-minute presentation to product + sales + marketing
  • Focus on: What changed, what we learned, what we should do differently
  • End with 3 specific recommendations and assigned owners

4. CI Roles and Ownership

RoleResponsibilityTime Commitment
CI Owner (typically Product Marketing)Run the program: collect, process, distribute4-6 hours/week
Product ManagersProvide feature comparison data; consume CI for roadmap decisions1-2 hours/week
Sales RepsShare field intel (what competitors say in deals); consume battlecards30 min/week (field reports)
Customer SuccessShare customer-reported competitive mentionsOpportunistic (tag in CRM)
Executive SponsorChampion CI program; ensure organizational investment1 hour/quarter (review + mandate)

5. Building Organizational Buy-In

CI programs fail when they're seen as "nice to have" rather than essential. Here's how to get and keep buy-in:

Start small, show value fast:

1. Pick your #1 competitor

2. Conduct 3 win/loss interviews this month

3. Build one battlecard

4. Share it with the sales team

5. Track whether it gets used and whether it influences a deal

6. Use that success story to justify expanding the program

Speak the language of your stakeholders:

  • To sales leadership: "We lost $1.2M in ARR to [Competitor] last quarter. Here's why, and here's what we can do about it."
  • To product leadership: "Our #1 feature gap — cited in 40% of lost deals — is [feature]. Here's the competitive data."
  • To executives: "Our win rate against [Competitor] dropped from 55% to 40% this quarter. I have a plan to reverse that."

Make it easy to contribute:

  • Create a simple form or Slack workflow for sales reps to submit competitive intel
  • Don't make people write essays — bullet points are fine
  • Publicly recognize people who share valuable intel

CI Program Maturity Model

Level 1: Reactive (Most Companies Start Here)

  • CI happens when someone asks "what do we know about Competitor X?"
  • No systematic collection or distribution
  • Battlecards are outdated or nonexistent
  • Win/loss analysis is anecdotal

Level 2: Structured (Target Within 3 Months)

  • Automated monitoring is set up for key competitors
  • Weekly CI triage happening
  • Battlecards for top 3-5 competitors, updated monthly
  • Win/loss interviews happening regularly (2-4/month)
  • Monthly CI newsletter to sales team

Level 3: Strategic (Target Within 12 Months)

  • CI informs product roadmap decisions with data, not opinions
  • Sales team actively uses battlecards and reports competitive intel
  • Quarterly CI briefings for cross-functional leadership
  • Win rate tracked by competitor with trend analysis
  • Positioning validated through ongoing market feedback

Level 4: Predictive (Advanced)

  • Anticipating competitor moves before they happen (based on job postings, patent filings, partner signals)
  • Scenario planning: "If Competitor X does Y, we will respond with Z"
  • CI integrated into strategic planning and budgeting cycles
  • External CI network (industry contacts, former competitor employees)

Quick Reference: Monthly CI Cadence

WeekActivityTime
Week 1Send monthly CI newsletter. Review and update battlecards.2 hours
Week 2Conduct 1-2 win/loss interviews. Weekly triage.3 hours
Week 3Scan competitor websites, job postings, review sites. Weekly triage.2 hours
Week 4Prepare monthly summary. Update feature comparison matrix. Weekly triage.3 hours

Total: ~10 hours/month — a manageable investment for one person, and the ROI from improved win rates and product decisions will far exceed the cost.


*The best competitive intelligence program is the one that actually runs. Start with Level 1, make it a habit, and expand from there. Consistency beats comprehensiveness every time.*

Chapter 2

Quick Start: Get Value in 30 Minutes

Skip the theory. Follow these steps and you'll have a usable competitive analysis within one focused half-hour.


Minute 0-10: Competitor Tracker

1. Open spreadsheets/competitor-tracker.csv in Google Sheets, Excel, or Notion

2. Delete the sample data rows (keep the header row as reference)

3. Add your top 3 competitors — just fill in these columns for now:

  • Competitor Name
  • Website
  • Primary Product (one-line description)
  • Target Market
  • Pricing Model and Starting Price
  • Key Strengths (2-3 bullets)
  • Key Weaknesses (2-3 bullets)
  • Threat Level (1-5)

Don't try to fill every column. You can come back and add Funding, Employee Count, etc. later.

Minute 10-20: Feature Comparison

1. Open spreadsheets/feature-comparison-matrix.csv

2. Replace competitor names in the header with your actual competitors

3. Pick the 10 features that matter most to your buyers (delete the rest for now)

4. Rate each competitor 0-3 on those features:

  • 0 = Doesn't have it
  • 1 = Has it, but basic
  • 2 = Solid implementation
  • 3 = Best-in-class

5. Set Priority Weight (1-5) for each feature based on how important it is to your customers

6. Look at the weighted scores — where are your biggest gaps?

Minute 20-30: Your First Battlecard

1. Open templates/battlecard-template.md

2. Copy it and fill it in for your most dangerous competitor (highest Threat Level from step 1)

3. Focus on these sections:

  • At a Glance — basic facts
  • Where We Win — 2-3 advantages with proof points
  • Where We Lose — 2-3 disadvantages with mitigation strategies
  • Top 3 Objection Responses — the objections your sales team hears most

4. Share the battlecard with your sales team. Today. Don't wait until it's perfect.


What's Next?

Now that you have the basics:

When You Have...Do This
1 more hourComplete templates/swot-analysis.md for your own product
2 more hoursFill in templates/porters-five-forces.md for your market
A lost dealUse frameworks/win-loss-interview-guide.md to debrief
A strategy meeting coming upBuild a templates/market-positioning-map.md
A team to trainShare guides/competitive-intel-process.md and set up the CI program
A worked example to referenceRead examples/sample-competitive-analysis.md

*The goal isn't a perfect analysis — it's a useful one. Start with what you know, share it with your team, and refine it over time as you learn more.*

Competitive Analysis Framework v1.0.0 — Free Preview