win-loss-analysis
Skill13 starsChanged 22 days agoMITView on GitHub
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.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- Insightful-Pipe/marketing-strategy-skillstheir own version, first seen Nov 1, 2026
- TahaSheikh12/ai-native-product-marketing-workspacetheir own version, first seen Oct 13, 2026
- poorvith-mp/skills-sales-supporttheir own version, first seen Sep 6, 2026
- sidchaudhary/gtm-skillstheir own version, first seen Aug 21, 2026
- matteotitta/genesys-skillstheir own version, first seen Jul 30, 2026
- growthack88/growth-marketing-ostheir own version, first seen Jul 3, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- growthack88/growth-marketing-os★ 117same name
- matteotitta/genesys-skills★ 46same name
- jbalbu01/sales-enablement-plugin★ 15same name
- whyashthakker/agent-skills-marketing★ 15same name
- the-nam-shub/e5-real-skills★ 10same name
- nandanosql/all_in_one_pm_skills★ 1same name
- sidchaudhary/gtm-skills★ 1same name
- TahaSheikh12/ai-native-product-marketing-workspace★ 1same name
- Insightful-Pipe/marketing-strategy-skills★ 0same name
- poorvith-mp/skills-sales-support★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository77 other files it gives its agents.
- AGENTS.mdAGENTS.md
- abm-account-planSkill
- account-research-briefSkill
- account-tieringSkill
- aeo-answer-optimizerSkill
- breakup-emailSkill
- buyer-persona-builderSkill
- buying-committee-mapperSkill
- buying-signal-scoringSkill
- call-coaching-scorecardSkill
- campaign-performance-analyzerSkill
- case-study-writerSkill
- churn-win-backSkill
- closed-lost-reactivationSkill
- cold-call-scriptSkill
- cold-email-sequenceSkill
- cold-email-writerSkill
- comparison-page-writerSkill
- competitive-battlecardSkill
- competitor-teardownSkill
- crm-hygiene-auditSkill
- customer-interview-guideSkill
- deal-qualificationSkill
- deliverability-auditSkill
- discovery-call-prepSkill
- domain-warmup-planSkill
- email-authentication-setupSkill
- email-copy-reviewSkill
- event-follow-upSkill
- expansion-opportunity-finderSkill
- first-line-personalizationSkill
- follow-up-email-writerSkill
- funding-signal-outreachSkill
- gtm-global-rulesSkill
- hiring-signal-outreachSkill
- icp-builderSkill
- job-change-playsSkill
- lead-list-builderSkill
- lead-magnet-builderSkill
- lead-scoring-modelSkill
- linkedin-comment-strategySkill
- linkedin-connection-noteSkill
- linkedin-message-sequenceSkill
- linkedin-post-writerSkill
- linkedin-profile-optimizerSkill
- list-cleaningSkill
- lookalike-account-finderSkill
- meeting-booking-replySkill
- messaging-matrixSkill
- multichannel-cadenceSkill
- mutual-action-planSkill
- negotiation-playbookSkill
- no-show-recoverySkill
- objection-handlerSkill
- outbound-ab-testSkill
- outbound-mathSkill
- outreach-compliance-checkSkill
- pipeline-reviewSkill
- post-engagement-outreachSkill
- proposal-follow-upSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Use this quarterly or after a run of losses.
- Distinctive: line 21
Call notes, emails and, ideally, 5-10 buyer interviews.
- Distinctive: line 66
MUST quantify before interpreting.
- Distinctive: line 67
MUST treat stated reasons as hypotheses until evidence supports them.
- Distinctive: line 68
NEVER single out individual reps in a team-wide report.
- Distinctive: line 69
NEVER share interview quotes with identifying details without the buyer's permission.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

