competitive-intelligence
Competitive intel research, battlecards, and win/loss programs
View on GitHubTable of content
Competitive intel research, battlecards, and win/loss programs
Installation
npx claude-plugins install @gtmagents/gtm-agents/competitive-intelligence
Contents
Folders: agents, commands, skills
Included Skills
This plugin includes 4 skill definitions:
battlecard-library
Template system for building, tagging, and distributing competitive battlecards.
View skill definition
Battlecard Library Skill
When to Use
- Creating/updating battlecards for new competitors.
- Packaging objection handling + differentiation guidance for field teams.
- Tracking adoption and freshness of competitive assets.
Framework
- Card Structure – overview, positioning, landmines, differentiation, trap-setting, proof, offer packaging.
- Metadata & Tagging – segment, persona, stage, product module, last updated, SME, confidence level.
- Enablement Hooks – talk tracks, snippets for sequences, asset links, CRM surfaces, content snippets.
- Review Cadence – SME assignments, refresh schedule, localization requirements.
- Analytics – usage tracking, win rate impact, prioritized backlog.
Templates
- Battlecard deck/Notion template with modular sections.
- Objection handling table (objection → talk track → asset → confidence).
- Update log spreadsheet capturing date, owner, change summary.
Tips
- Embed battlecards directly into CRM/workspace surfaces where reps already work.
- Flag trap-setting and landmines clearly to avoid disclosure mistakes.
- Pair with
build-battlecard-suitecommand to automate population.
executive-briefing-kit
Framework for packaging competitive updates into executive-ready narratives
View skill definition
Executive Briefing Kit Skill
When to Use
- Preparing board/ELT updates on competitive threats and market shifts.
- Summarizing key intel for quarterly business reviews or deal war rooms.
- Aligning cross-functional leaders on immediate actions + investments.
Framework
- Story Arc – context, signal summary, threat/opportunity framing, recommended plays.
- Evidence Layer – data, quotes, visuals, scorecards, customer anecdotes.
- Action Register – decisions required, owner, due date, confidence level, resource ask.
- Escalation Hooks – highlight urgent risks, exec sponsors, and escalation paths.
- Follow-up Cadence – timeline for progress updates, KPI tracking, and retrospectives.
Templates
- One-page exec brief + appendix outline.
- Slide template with signal cards, impact matrix, and action tracker.
- Decision log template for recording commitments + rationale.
Tips
- Lead with business impact before diving into tactical intel.
- Include “what we need from you” explicitly to unlock fast decisions.
- Use with
analyze-competitive-landscapeandbuild-battlecard-suitefor cohesive storytelling.
market-signal-tracker
Operating system for logging market/competitive signals with severity,
View skill definition
Market Signal Tracker Skill
When to Use
- Monitoring competitor launches, pricing moves, org shifts, funding, or partner announcements.
- Tracking analyst coverage, customer chatter, or social sentiment around competitors.
- Ensuring signals route to the right owners with context and deadlines.
Framework
- Signal Intake – capture source, timestamp, competitor, category (product, pricing, GTM, talent, regulation).
- Severity & Confidence – rate potential impact, confidence level, and affected product/segment.
- Routing – assign owners (product, enablement, comms, exec) with SLA + follow-up notes.
- Action Status – track planned/active/completed actions linked to each signal.
- Reporting – weekly digest summarizing net-new signals, escalations, and outstanding actions.
Templates
- Signal log spreadsheet or Notion database with views by competitor/category.
- Weekly digest template with highlights, escalations, and recommended actions.
- Action tracker with owner, due date, and dependency fields.
Tips
- Automate ingestion by connecting RSS, alerts, and social monitoring; maintain manual overrides for high-sensitivity items.
- Keep a rolling 90-day archive to reference trends and repeat patterns.
- Pair with
analyze-competitive-landscapeandrun-win-loss-programfor holistic perspective.
win-loss-dataset
Structure for capturing qualitative + quantitative win/loss insights
View skill definition
Win/Loss Dataset Skill
When to Use
- Running structured win/loss programs.
- Aligning qualitative interviews with CRM metrics.
- Sharing insights across product, sales, pricing, and marketing teams.
Framework
- Data Model – deal metadata (segment, region, product, stage), outcome, competitor, primary driver, secondary driver, confidence.
- Qualitative Tags – categories for pricing, product gaps, implementation, support, brand, relationships.
- Quotes & Evidence – key quotes, call clips, doc references with consent + access controls.
- Analytics Layer – dashboards for driver frequency, trendlines, influence on win rate, revenue impact.
- Action Tracking – link insights to backlog items, status, owner, and due date.
Templates
- Interview note template with pre-defined tags + drop-downs.
- Dataset schema (CSV/Sheet/BI) with validated fields.
- Dashboard layout for driver trends + revenue impact.
Tips
- Keep raw qualitative notes but publish sanitized, anonymized snippets for broader sharing.
- Standardize driver taxonomy every quarter to avoid drift.
- Pair with
run-win-loss-programcommand for automatic dataset updates.