Competitive intelligence

Competitive Intelligence Patterns

CI Program Architecture

CI Program Maturity Levels

Level	Characteristics	Output
Ad-hoc	Informal, reactive, person-dependent	One-off reports on request
Defined	Structured process, designated owner	Monthly competitor reports
Managed	Systematic collection, shared tools	Real-time alerting + quarterly deep-dives
Optimized	CI embedded in strategy, predictive	Early warning system, battle cards, deal support

CI Program Structure

Roles:
- CI Owner: coordinates, synthesizes, distributes
- Contributors: sales (win/loss), product (features), marketing (messaging)
- Consumers: product, sales, strategy, leadership

Cadence:
- Daily: automated alerts reviewed
- Weekly: signal triage and distribution
- Monthly: deep competitor profiles updated
- Quarterly: landscape report + strategy implications

OSINT Techniques

Legal Open Source Intelligence Sources

Source	Signal	How to Access
Job postings	Investment areas, tech stack, team growth	LinkedIn, Indeed, Greenhouse
Company blog	Product direction, culture, customer stories	RSS feed, Feedly
Developer docs/changelog	Feature releases, API changes	docs.competitor.com
GitHub repos	Engineering team, tech stack, open source	github.com/competitor
G2/Capterra reviews	Customer pain points, praise, churn reasons	Filter by recency
LinkedIn company page	Headcount growth, org changes	LinkedIn
Press releases	Partnerships, funding, launches	PR Newswire, Businesswire
Patent filings	R&D direction, future products	USPTO, Google Patents
SEC filings (public)	Revenue, growth, risks, customer count	EDGAR
Podcast appearances	Strategic messaging, founder worldview	Listen Notes search
Conference talks	Technical roadmap hints	YouTube, conference sites
Wayback Machine	Historical pricing and messaging	web.archive.org
Crunchbase/PitchBook	Funding, investors, headcount history	Crunchbase (free tier)

Job Posting Intelligence

Reading job postings for CI:

"Senior ML Engineer (NLP focus)" → investing in language AI
"Head of Enterprise Sales" → moving upmarket
"VP of Partnerships" → ecosystem/channel strategy
"Staff Security Engineer" → compliance push (SOC2, FedRAMP?)
"Localization Manager, APAC" → geographic expansion
"Director, Pricing Strategy" → pricing model change coming

Track velocity: how many postings, in which departments, over time

G2/Capterra Review Mining

Search filters:
- Most recent (last 90 days)
- Rating: 1-2 stars (find pain points) AND 5 stars (confirm strengths)
- Role filter: match your ICP

What to extract:
- Recurring complaints → their weaknesses to exploit
- Most-praised features → what customers value (match or exceed)
- "Switched from [competitor]" reviews → your churned users?
- "Compared to [alternative]" → how buyers position them

Quote extraction template:
Competitor: [name]
Source: G2, 3-star review, 2024-03
Segment: Mid-market, Operations Manager
Pain: "The reporting is powerful but the learning curve is steep—
      we had to hire a consultant to get it set up."
→ Insight: Training/onboarding is a weakness; we can exploit with better UX

Monitoring Infrastructure

Alert Setup

Google Alerts (free):
- "competitor name" new product
- "competitor name" funding
- "competitor name" review
- "competitor name" partnership
- CEO/founder name

Tools for broader monitoring:
- Crayon: automated CI platform, $$$
- Klue: battle cards + CI platform, $$$
- Mention.com: social + web monitoring
- Brand24: real-time brand monitoring
- Feedly + RSS: free, manual curation
- Talkwalker: enterprise social listening

CI Triage Matrix

When a signal comes in, ask:

Urgency   High           Low
─────────────────────────────
Impact   ┌─────────────┬─────────────┐
High     │ ACT NOW     │ PLAN FOR    │
         │ (same week) │ (next month)│
─────────┼─────────────┼─────────────┤
Low      │ MONITOR     │ LOG ONLY    │
         │ (track)     │ (archive)   │
         └─────────────┴─────────────┘

Examples:
- Competitor cuts price 30% (High urgency + High impact) → ACT NOW
- Competitor hires VP Marketing (Low urgency + High impact) → PLAN FOR
- Competitor blog post (Low urgency + Low impact) → LOG ONLY

Win/Loss Program

Win/Loss Interview Cadence

• Conduct within 2 weeks of deal close/loss (memory fades)
• Interview buyer, not just internal rep
• Aim for 20+ interviews per quarter for statistical validity
• Use neutral third party if possible (higher candor)

Win/Loss Interview Guide

Opening:
"Thanks for 20 minutes. We're trying to learn so we can improve.
 Your candor is more valuable than politeness. Ready?"

Questions for WINS:
1. "Walk me through your evaluation process."
2. "Who else did you consider?"
3. "What almost made you choose someone else?"
4. "What tipped it toward us?"
5. "What would have made the decision easier?"

Questions for LOSSES:
1. "Who did you end up going with?"
2. "What did they offer that we didn't?"
3. "Was price the deciding factor?" (If yes: "What would we have needed to be at?")
4. "If we'd addressed [specific gap], would that have changed things?"
5. "What would it take for you to revisit this in 12 months?"

For ALL deals:
"What was your biggest concern going in?"
"What surprised you (positively or negatively)?"
"Who else influenced the decision?"

Win/Loss Analysis Dashboard

Metrics (track monthly, trend quarterly):

Win rate overall: X%
Win rate vs. [Competitor A]: X%
Win rate vs. [Competitor B]: X%

Loss reasons (% of losses):
□ Price: X%
□ Missing feature: X%
□ Relationship/trust: X%
□ Poor sales execution: X%
□ Timing: X%
□ No decision: X%

Displacement rate: X% of wins came from displacing a competitor
Average days to close (won vs lost): Xd vs Xd

Battle Cards

Battle Card Template

COMPETITOR: [Name]  |  Updated: [Date]  |  Owner: [Name]

HEADLINE POSITIONING
"[One-line differentiation your reps should lead with]"

WHEN YOU'LL FACE THEM
[Segments/deal sizes where they compete most]

THEIR REAL STRENGTHS (don't dismiss — acknowledge first)
• [Genuine strength 1]
• [Genuine strength 2]

WHY WE WIN
• [Advantage 1] — Customer proof: "[Quote]"
• [Advantage 2] — Metric: [Data point]
• [Advantage 3] — Story: [Customer name] switched because...

HANDLING THEIR ATTACKS

When they say: "We're cheaper"
You say: "[ROI calculation showing total cost of ownership]"
Proof: [Customer who calculated this]

When they say: "We have more integrations"
You say: "We have the [N] integrations that 95% of teams need including..."
Trap: "Which integrations are critical for your workflow specifically?"

When they say: "We've been in the market longer"
You say: "We were built for [specific modern use case they weren't]"
Proof: [Customer who came from competitor]

QUALIFYING QUESTIONS
1. "How important is [your key differentiator] to you?"
2. "What happened last time [competitor's known weakness occurred]?"
3. "Are you in a competitive evaluation, or is this exploratory?"

DO NOT DO
• Don't trash talk — it backfires and makes you look insecure
• Don't dismiss their strengths — acknowledge then pivot
• Don't get into feature wars — focus on outcomes