agentleFS
darkweb19darkweb19/skills/competitive-intel/SKILL.md

competitive-intel

Skill0 starsChanged 27 days agoApache-2.0View on GitHub

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.

19 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask in natural language for the deliverable you need:

    line 23
  2. Distinctive:

    Update this quarterly. Who's moved quadrants?

    line 46
  3. Distinctive:

    Update battlecards with new intel

    line 99
  4. Distinctive:

    Add/remove companies from tracking list

    line 112
  5. Distinctive:

    Every lost deal >$50K ACV

    line 121
  6. Distinctive:

    Every churn >6 months tenure

    line 122
  7. Distinctive:

    Every competitive win (learn why — it may not be what you think)

    line 123
  8. Distinctive:

    NOT the AE who worked the deal (too close, prospect won't be candid)

    line 126
  9. Distinctive:

    Don't let them set your agenda

    line 161
  10. Distinctive:

    One source of truth: All competitive intel lives in one place (Notion, Confluence, Salesforce).

    line 176

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.