win-loss-dataset

Structure for capturing qualitative + quantitative win/loss insights with consistent tagging.

⭐31stars🔀7forks📁View on GitHub🕐Updated Dec 23, 2025⬇️4downloads

When & Why to Use This Skill

The Win/Loss Dataset skill provides a comprehensive framework for capturing and analyzing qualitative and quantitative insights from sales cycles. By standardizing deal metadata, competitor tracking, and qualitative feedback, it enables organizations to align interview data with CRM metrics, identify revenue-impacting trends, and bridge product gaps through structured data models and actionable analytics dashboards.

Use Cases

  • Sales Performance Analysis: Standardize how sales teams record deal outcomes to identify patterns in winning and losing streaks across different regions and segments.
  • Competitive Intelligence: Build a robust database of competitor strengths and weaknesses based on direct feedback from prospects to refine market positioning.
  • Product Strategy & Backlog Prioritization: Use qualitative tags to highlight recurring product gaps or implementation hurdles that lead to lost deals, providing data-driven evidence for the engineering roadmap.
  • Cross-Functional Insight Sharing: Generate sanitized, anonymized reports and dashboards to share 'Voice of the Prospect' insights with marketing, pricing, and executive teams without compromising data privacy.
namewin-loss-dataset
descriptionStructure for capturing qualitative + quantitative win/loss insights

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

  1. Data Model – deal metadata (segment, region, product, stage), outcome, competitor, primary driver, secondary driver, confidence.
  2. Qualitative Tags – categories for pricing, product gaps, implementation, support, brand, relationships.
  3. Quotes & Evidence – key quotes, call clips, doc references with consent + access controls.
  4. Analytics Layer – dashboards for driver frequency, trendlines, influence on win rate, revenue impact.
  5. 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-program command for automatic dataset updates.