win-loss-analysis
/win-loss-analysis
Use this skill when you want to learn why deals are won and lost: \"run a win-loss analysis\", \"why are we losing to competitor X\", \"analyse last quarter's closed deals\", \"prepare win-loss interviews\". Analyses closed-won and closed-lost deals and buyer interviews, separates stated reasons from real ones, finds patterns by segment, competitor, deal size and stage, and turns them into specific changes for targeting, messaging, product and sales process.
- Author
- prosyo-ai ↗
- Repository
- gtm-skill ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use this skill when you want to learn why deals are won and lost: \"run a win-loss analysis\", \"why are we losing to competitor X\", \"analyse last quarter's closed deals\", \"prepare win-loss interviews\". Analyses closed-won and closed-lost deals and buyer interviews, separates stated reasons from real ones, finds patterns by segment, competitor, deal size and stage, and turns them into specific changes for targeting, messaging, product and sales process.
Triggers from the description
Original author description
Use this skill when you want to learn why deals are won and lost: \"run a win-loss analysis\", \"why are we losing to competitor X\", \"analyse last quarter's closed deals\", \"prepare win-loss interviews\". Analyses closed-won and closed-lost deals and buyer interviews, separates stated reasons from real ones, finds patterns by segment, competitor, deal size and stage, and turns them into specific changes for targeting, messaging, product and sales process.
How it works
- Inputs
- The play
- Output format
- What good looks like
- Rules
- Example prompts
SKILL.md preview
---
name: win-loss-analysis
description: "Use this skill when you want to learn why deals are won and lost: \"run a win-loss analysis\", \"why are we losing to competitor X\", \"analyse last quarter's closed deals\", \"prepare win-loss interviews\". Analyses closed-won and closed-lost deals and buyer interviews, separates stated reasons from real ones, finds patterns by segment, competitor, deal size and stage, and turns them into specific changes for targeting, messaging, product and sales process."
license: MIT
metadata:
title: Win-loss analysis
category: deals
tags: "Sales Leaders, Marketing, Founders, RevOps"
author: prosyo
version: "1.0.0"
keywords: "win loss analysis template, why we lose deals, win loss interview questions, claude win loss skill, closed lost analysis"
inputs: "Closed deals with reasons, Call notes or interviews, Competitor data"
outputs: "Win and loss patterns, Real vs stated reasons, Recommendations by team, Interview guide"
---
Use this quarterly or after a run of losses. It replaces anecdotes ("we always lose on price") with patterns and specific changes.
## Inputs
- Closed-won and closed-lost deals for the period with stage lost, reason, competitor, amount, segment and cycle length.
- Call notes, emails and, ideally, 5-10 buyer interviews.
- Rep notes on why they think deals went the way they did.
## The play
### 1. Quantify first
Win rate by segment, deal size, lead source, competitor, rep and stage lost. The stage where deals die says more than the reason field: losses after the demo are fit or value problems; losses after the proposal are price, champion or competitor problems.
### 2. Separate stated from real reasons
"Price" is the most common stated reason and often not the real one. Look for evidence: was the economic buyer engaged? Was value quantified? Did the champion go quiet? Real reasons usually fall into: no quantified value, wrong buyer, competitor better fit, poor timing, weak process, product gap.
### 3. Interview buyers
Short calls with won and lost buyers, run by someone other than the rep. Ask about their process and alternatives, not about the rep. A guide:
- What problem were you trying to solve, and why then?
- What alternatives did you consider, including doing nothing?
- What mattered most in the decision?
- Where did we fall short, or stand out?
- What almost made you choose differently?
### 4. Find patterns
A pattern needs 3+ deals pointing the same way. Group into: targeting, messaging, product, pricing, sales process, competition.
### 5. Turn patterns into changes
Each pattern gets one recommended change, an owner and how to measure it next quarter.
## Output format
```
Period: <dates> | Deals: N won, N lost | Win rate: X% (vs X% last period)
Where we win: <segments, use cases, competitors>
Where we lose: <same, with the stage deals die>
Stated vs real reasons: <table>
Patterns (3+ deals each): <pattern - evidence - change - owner - metric>
Quick wins: <changes that can start next week>
```
## What good looks like
- Losses are explained with evidence from the deal, not from the reason picklist.
- Wins are analysed too; knowing why you win tells you where to aim.
- Recommendations name a team and a metric.
- The common mistake is concluding "we need to be cheaper" from picklist data when the losses show no economic buyer was ever met.
## Rules
- MUST quantify before interpreting.
- MUST treat stated reasons as hypotheses until evidence supports them.
- NEVER single out individual reps in a team-wide report; give rep-level findings privately to managers.
- NEVER share interview quotes with identifying details without the buyer's permission.
## Example prompts
- "Here are 80 closed deals from last quarter. Run a win-loss analysis."
- "Why do we keep losing to Acme in mid-market? Notes attached."
- "Write a win-loss interview guide and a request email to lost buyers."
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · prosyo-ai/gtm-skill | 100 | MIT |
| Insightful-Pipe/marketing-strategy-skills | 100 | MIT |
| sarojkjha/aaj-marketing-skills | 100 | MIT |
| thecraighewitt/skills | 100 | MIT |
| modest-curator478/claude-skills | 90 | MIT |
| LeadMagic/gtm-skills | 90 | MIT |
| matteotitta/genesys-skills | 85 | MIT |
Database snapshot: 13.11.2026 · package version ba8907a5dff2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90win-loss-decoder
Turns closed-won and closed-lost deals into ranked, evidence-backed reasons (not rep-selected dropdowns) and routes each pattern to the team that can fix it. Use when: win loss analysis, why did we lose, why do we win, closed lost review, loss reasons, churned deals, competitive… - 100gtm-win-loss
When the user wants to explain why deals were won or lost — win/loss analysis from closed deals and interview notes. Use for 'win loss analysis', 'why do we lose deals', 'review closed deals', 'win loss interview', 'why did we win'. Interview evidence is user-supplied, never invented. - 90competitive-win-loss-analysis
Explain repeated competitive outcomes - why deals are won or lost against a competitor or across a period - from buyer and deal evidence rather than rep folklore, with the cohort defined, buyer-stated reasons separated from rep-entered ones, patterns counted without erasing the… - 100win-loss-review
Explain why a closed monday CRM deal was won or lost. Reads the deal's stage history, Emails & Activities timeline, notes and column changes, compares it with other closed deals on the same board, and writes a short evidence-based review. Use when someone asks "why did we… - 82arrows-win-loss-analysis
Win-loss analysis from Sales Skills by Arrows. A deep read of closed deals (every won and lost deal counted, about 25 wins and 25 losses read end to end, call transcripts and email) that answers why the team wins and why it loses: which segments win (size, source, industry, new… - 100win-loss
Synthesise why deals were won and lost this period from closed deals and call transcripts, by competitor, segment and reason. Use when "why did we lose Acme", "quarterly win/loss".