Skip to content
cccskills
FreePublished on GitHub

competitive-intel

Track competitors’ products, pricing, and customer wins or losses, then turn findings into sales comparison sheets, market positioning updates, and feature gap summaries that inform product planning and leadership decisions.

OriginalShow the original description

Systematic competitor tracking that feeds CMO positioning, CRO battlecards, and CPO roadmap decisions. Use when analyzing competitors, building sales battlecards, tracking market moves, positioning against alternatives, or when user mentions competitive intelligence, competitive analysis, competitor research, battlecards, win/loss, or market positioning.

Works withLinkedIn
See how to install

Good for

  • Mapping direct, indirect, and emerging competitors
  • Preparing competitor comparison sheets for sales calls
  • Analyzing why deals were won or lost
  • Reviewing competitors’ pricing and product changes

Files included (3)

  • SKILL.md8.1 KB
  • references/ci-playbook.md9.7 KB
  • templates/battlecard-template.md3.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Competitive Intelligence

Systematic competitor tracking. Not obsession — intelligence that drives real decisions.

Keywords

competitive intelligence, competitor analysis, battlecard, win/loss analysis, competitive positioning, competitive tracking, market intelligence, competitor research, SWOT, competitive map, feature gap analysis, competitive strategy

Quick Start

Ask in natural language for the deliverable you need:

"Map our competitive landscape" — direct, indirect, and future competitors "Build a battlecard for [competitor]" — sales-ready battlecard "Run a win/loss analysis" — recent wins and losses by reason "What did [competitor] do recently?" — competitor update tracking "Build a competitive positioning map" — 2x2 positioning map

Framework: 5-Layer Intelligence System

Layer 1: Competitor Identification

Direct competitors: Same ICP, same problem, comparable solution, similar price point. Indirect competitors: Same budget, different solution (including "do nothing" and "build in-house"). Future competitors: Well-funded startups in adjacent space; large incumbents with stated roadmap overlap.

The 2x2 Threat Matrix:

Same ICPDifferent ICP
Same problemDirect threatAdjacent (watch)
Different problemDisplacement riskIgnore for now

Update this quarterly. Who's moved quadrants?

Layer 2: Tracking Dimensions

Track these 8 dimensions per competitor:

DimensionSourcesCadence
Product movesChangelog, G2/Capterra reviews, Twitter/LinkedInMonthly
Pricing changesPricing page, sales call intel, customer feedbackTriggered
FundingCrunchbase, TechCrunch, LinkedInTriggered
Hiring signalsLinkedIn job postings, IndeedMonthly
PartnershipsPress releases, co-marketingTriggered
Customer winsCase studies, review sites, LinkedInMonthly
Customer lossesWin/loss interviews, churned accountsOngoing
Messaging shiftsHomepage, ads (Facebook/Google Ad Library)Quarterly

Layer 3: Analysis Frameworks

SWOT per Competitor:

  • Strengths: What do they do well? Where do they win?
  • Weaknesses: Where do they lose? What do customers complain about?
  • Opportunities: What could they do that would threaten you?
  • Threats: What's their existential risk?

Competitive Positioning Map (2 axis): Choose axes that matter for your buyers:

  • Common: Price vs Feature Depth; Enterprise-ready vs SMB-ready; Easy to implement vs Configurable
  • Pick axes that show YOUR differentiation clearly

Feature Gap Analysis:

FeatureYouCompetitor ACompetitor BGap status
[Feature]✅✅❌Your advantage
[Feature]❌✅✅Gap — roadmap?
[Feature]✅❌❌Moat
[Feature]❌❌✅Competitor B only

Layer 4: Output Formats

For Sales (CRO): Battlecards — one page per competitor, designed for pre-call prep. See templates/battlecard-template.md

For Marketing (CMO): Positioning update — message shifts, new differentiators, claims to stop or start making.

For Product (CPO): Feature gap summary — what customers ask for that we don't have, what competitors ship, what to reprioritize.

For CEO/Board: Monthly competitive summary — 1-page: who moved, what it means, recommended responses.

Layer 5: Intelligence Cadence

Monthly (scheduled):

  • Review all tier-1 competitors (direct threats, top 3)
  • Update battlecards with new intel
  • Publish 1-page summary to leadership

Triggered (event-based):

  • Competitor raises funding → assess implications within 48 hours
  • Competitor launches major feature → product + sales response within 1 week
  • Competitor poaches key customer → win/loss interview within 2 weeks
  • Competitor changes pricing → analyze and respond within 1 week

Quarterly:

  • Full competitive landscape review
  • Update positioning map
  • Refresh ICP competitive threat assessment
  • Add/remove companies from tracking list

Win/Loss Analysis

This is the highest-signal competitive data you have. Most companies do it too rarely.

When to interview:

  • Every lost deal >$50K ACV
  • Every churn >6 months tenure
  • Every competitive win (learn why — it may not be what you think)

Who conducts it:

  • NOT the AE who worked the deal (too close, prospect won't be candid)
  • Customer success, product team, or external researcher

Question structure:

  1. "Walk me through your evaluation process"
  2. "Who else were you considering?"
  3. "What were the top 3 criteria in your decision?"
  4. "Where did [our product] fall short?"
  5. "What was the deciding factor?"
  6. "What would have changed your decision?"

Aggregate findings monthly:

  • Win reasons (rank by frequency)
  • Loss reasons (rank by frequency)
  • Competitor win rates (by competitor, by segment)
  • Patterns over time

The Balance: Intelligence Without Obsession

Signs you're over-tracking competitors:

  • Roadmap decisions are primarily driven by "they just shipped X"
  • Team morale drops when competitors fundraise
  • You're shipping features you don't believe in to match their checklist
  • Pricing discussions always start with "well, they charge X"

Signs you're under-tracking:

  • Your AEs get blindsided on calls
  • Prospects know more about competitors than your team does
  • You missed a major product launch until customers told you
  • Your positioning hasn't changed in 12+ months despite market moves

The right posture:

  • Know competitors well enough to win against them
  • Don't let them set your agenda
  • Your roadmap is led by customer problems, informed by competitive gaps

Distributing Intelligence

AudienceFormatCadenceOwner
AEs + SDRsUpdated battlecards in CRMMonthly + triggeredCRO
ProductFeature gap analysisQuarterlyCPO
MarketingPositioning briefQuarterlyCMO
Leadership1-page competitive summaryMonthlyCEO/COO
BoardCompetitive landscape slideQuarterlyCEO

One source of truth: All competitive intel lives in one place (Notion, Confluence, Salesforce). Avoid Slack-only distribution — it disappears.


Red Flags in Competitive Intelligence

SignalWhat it means
Competitor's win rate >50% in your core segmentFundamental positioning problem, not sales problem
Same objection from 5+ deals: "competitor has X"Feature gap that's real, not just optics
Competitor hired 10 engineers in your domainMajor product investment incoming
Competitor raised >$20M and targets your ICP12-month runway for them to compete hard
Prospects evaluate you to justify competitor decisionYou're the "check box" — fix perception or segment

Integration with C-Suite Roles

Intelligence TypeFeeds ToOutput Format
Product movesCPORoadmap input, feature gap analysis
Pricing changesCRO, CFOPricing response recommendations
Funding roundsCEO, CFOStrategic positioning update
Hiring signalsCHRO, CTOTalent market intelligence
Customer wins/lossesCRO, CMOBattlecard updates, positioning shifts
Marketing campaignsCMOCounter-positioning, channel intelligence

References

  • references/ci-playbook.md — OSINT sources, win/loss framework, positioning map construction
  • templates/battlecard-template.md — sales battlecard template

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

a11y-audit

FreeSummary

Audit web applications for accessibility issues against WCAG 2.2 Level A and AA, the web accessibility standards. Get framework-specific code fixes, contrast checks, verification steps, and reports, with options for automated checks in development pipelines.

  • Audit a web application before release
  • Fix contrast and keyboard navigation issues
  • Prepare accessibility reports for stakeholders
alirezarezvani/claude-skills28.4KUpdated Aug 30, 2026

ab-test-setup

FreeSummary

Plan A/B tests that compare page variations, from headlines to pricing layouts. Define a hypothesis, choose success metrics, calculate sample size and duration, and prepare launch checks and results reports to support decisions.

  • Comparing landing page headlines
  • Testing signup button changes
  • Planning pricing page experiments
alirezarezvani/claude-skills28.4KUpdated Aug 30, 2026

ad-creative

FreeSummary

Create paid ad headlines and body copy tailored to each platform's character limits. Use existing performance data to develop variations, explore new messaging angles, and check copy for length, quality, and potential rejection risks.

  • Creating Google RSA headlines
  • Writing Meta and LinkedIn ad copy
  • Developing variations of successful ads
alirezarezvani/claude-skills28.4KUpdated Aug 30, 2026

Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.

  • Reviewing a pull request before merging
  • Getting a second opinion on AI-written code
  • Checking authentication or data access code
alirezarezvani/claude-skills28.4KUpdated Aug 30, 2026

aeo

FreeSummary

Audit and improve content intended for citation in AI answers. Review evidence, author information, and structure, generate revised content and structured metadata, and keep a local record of observed citations across AI services.

  • Audit existing articles for evidence and credibility gaps
  • Revise article structure and references for AI answers
  • Record citations observed across AI services
alirezarezvani/claude-skills28.4KUpdated Aug 30, 2026

Create signed records for consequential agent actions such as deployments, deletions, and payments. Decide which actions need evidence, record the agent, action, target, and policy, then verify the resulting certificate offline to detect later changes.

  • Creating signed records for production deployments
  • Preserving evidence of deletions and payments
  • Recording access grants for later review
alirezarezvani/claude-skills28.4KUpdated Aug 30, 2026

See all skills by alirezarezvani

Report a problem with this skill