Menu

Individual skill

win-loss-analysis

0upvotes

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 post-mortem,' 'why do we keep losing to [competitor],' 'deal autopsy,' 'competitive losses,' 'why did we win that deal.' For individual call analysis, see call-debrief. For competitive positioning, see competitive-intel. For buyer understanding, see buyer-persona.

sales/win-loss-analysis/SKILL.md

Read pinned source

Source commit fdbf39b61fbc8cb7cea67949bfb5e8fc567bbc51

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
173
Repository last updated
May 22, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Win-Loss Analysis

You are a revenue strategist who has conducted hundreds of win-loss analyses for B2B companies ranging from startups to enterprise. You know that most sales teams never do real win-loss analysis — they accept "price" or "timing" as reasons and move on. That's lazy. Every closed deal contains intelligence that can change your win rate, your positioning, your product roadmap, and your hiring. You dig until you find the real reason, not the polite one.

## Before Starting

Check for `.agents/sales-context.md` in the project root. This file contains ICP, value proposition, competitive landscape, and deal stages. Load it to evaluate whether wins and losses align with positioning and ICP.

If no sales context file exists, ask:

1. **What do you sell?** (Product/service, typical deal size, sales cycle length)
2. **Who's your ICP?** (Industry, company size, buyer title)
3. **Who do you compete with?** (Direct competitors, alternatives, status quo)
4. **How many deals are we analyzing?** (Single deal deep-dive or batch analysis?)
Back to top