win-loss-decoder
/win-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 losses, buyer interviews.
- Author
- varunk130 ↗
- Repository
- ai-gtm-skill-library ↗
- Licence
- MIT
- Last repository change
- 17.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 17.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
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 losses, buyer interviews.
Original author description
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 losses, buyer interviews.
How it works
- Core Principle
- The SIGNAL Framework
- Reason Taxonomy
- Process
- Output
- Tips
- Pairs With
SKILL.md preview
--- name: win-loss-decoder description: '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 losses, buyer interviews.' --- # Win-Loss Decoder (SIGNAL Framework) CRM loss reasons are picked by the rep in ten seconds, and "price" wins every time. Win-Loss Decoder rebuilds the reason from what the buyer said and did, codes it against a fixed taxonomy, and ranks patterns by revenue so product, marketing, and sales each get the fixes that are theirs. ## Core Principle **The buyer's words decide the code.** A reason without a quote or artifact from the buyer is logged as "unknown", not guessed. ## The SIGNAL Framework | Letter | Step | The Question | |---|---|---| | **S** | Sample | Which deals, and is the sample balanced across wins, losses, segments, and reps? | | **I** | Interview | What did the buyer say in a 20-minute conversation after the decision? | | **G** | Group | Which taxonomy code does each reason map to? | | **N** | Number | How much ARR sits behind each code, for wins and for losses? | | **A** | Assign | Which team owns the fix for each code? | | **L** | Loop | Did the fix change the rate of that code next quarter? | ## Reason Taxonomy | Code | Covers | Default owner | |---|---|---| | VALUE | Buyer could not see enough return or urgency | Marketing | | FIT | Missing capability, integration, or compliance need | Product | | TRUST | Proof, references, security, or vendor-risk concerns | Marketing / Security | | PROCESS | Lost the sales process: slow, no champion, wrong buyer | Sales | | PRICE | Price or packaging, after the above are ruled out | Pricing | | STATUS QUO | Buyer chose to do nothing | Marketing / Sales | ## Process 1. **Sample** - 15-30 recent decisions, at least one-third wins; exclude deals under the ACV floor 2. **Collect** - buyer interviews first, then call notes and emails; note the source of every reason 3. **Code** - up to two codes per deal (primary, secondary); PRICE only if VALUE and FIT are ruled out 4. **Weight** - sum ARR by code for wins and losses; compute `loss share - win share` per code 5. **Rank** - largest positive gap first; these are the reasons you lose more than you win on 6. **Route** - one fix per top code, with owner and the metric that will show it worked ## Output Save to `outputs/win-loss-decoder-[period]-[YYYY-MM-DD].md` | Artifact | Description | |---|---| | **Coded deal log** | Deal, outcome, codes, quoted evidence, source | | **Pattern table** | Code, ARR won, ARR lost, gap | | **Fix plan** | Top three codes with owner, action, and target metric | ## Tips 1. **Interview wins too** - you cannot tell a loss pattern from a market pattern without them 2. **Don't let reps interview their own deals** - buyers are more candid with a neutral party 3. **Rerun quarterly** - the Loop step is where the value compounds ## Pairs With - **deal-xray** - PROCESS losses usually show missing proof earlier in the deal - **competitive-battlecard** - competitor-named losses update the battlecard - **position-lock** - persistent VALUE losses signal a positioning problem
Versions
The database has no other skills named win-loss-decoder.
Database snapshot: 13.11.2026 · package version 45c5d775d903 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100win-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,… - 100win-loss-analysis
When the user wants to analyze why deals were won or lost, find patterns across closed deals, or extract competitive intelligence from deal outcomes. Trigger phrases: 'why did we lose that deal,' 'win-loss review,' 'analyze our closed deals,' 'what are we losing to,' 'deal… - 100win-loss-analysis
Use when the user wants to understand why deals are won or lost and turn it into patterns they can act on. Also use when the user mentions win/loss, win-loss analysis, why we lose deals, deal post-mortem, lost-deal reasons, competitive losses, sales feedback, or "why aren't we… - 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. - 90win-loss-analysis
AUTO-TRIGGER: Apply this skill when the user wants to run, structure, or improve a win/loss analysis program. Trigger phrases include: "win/loss analysis," "why are we losing deals," "why do we win," "lost deal analysis," "closed lost reasons," "competitive losses," "deal… - 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…