What do I need to use Win/Loss Analysis?

Deal data; Feedback source; Time window and any segmentation; Primary competitors; The decision.

Is Win/Loss Analysis free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Win/Loss Analysis

Q: How do I know the Win/Loss Analysis output is good?

The skill verifies itself against its own quality checks: Every reason is backed by counts, not vibes; Losses are split into controllable vs structural; Each major theme has a real quote or an explicit `[quote to add]`; Actions name an owner and the highest-leverage single move.

🔵 Stable🕐 updated 2026-07-08 🔷 SkillSpec L3 pm-pmm

Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

🗣 Say this to your agent

“Run a win/loss analysis on last quarter's closed deals”“Why are we losing enterprise deals to [Competitor]?”“Summarize these win/loss interviews into themes and actions”“Turn our CRM closed-lost reasons into a report for the QBR”

What to give it

▸Deal data — a list of closed-won and closed-lost deals, ideally with amount, segment, competitor, and stage lost

▸Feedback source — win/loss interview notes, CRM `closed_lost_reason` fields, survey responses, or call transcripts

▸Time window and any segmentation — you care about (segment, region, product line)

▸Primary competitors — to track explicitly

▸The decision — this feeds — a QBR, a roadmap review, a messaging refresh, an enablement push

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Every reason is backed by counts, not vibes

✓Losses are split into controllable vs structural

✓Each major theme has a real quote or an explicit `[quote to add]`

✓Actions name an owner and the highest-leverage single move

✓Competitor findings are specific enough to change a battlecard

⚠️ What it refuses to do

Do not treat "price" as a root cause without checking whether it's really value perception

Do not average away segment differences — a 60% overall win rate can hide a 20% enterprise rate

Do not fabricate buyer quotes or inflate sample size; state the n

Do not list 15 actions — rank ruthlessly and name the top few

Do not blame sales or product reflexively; let the data assign the theme

📚 Ships with

references/buyer-interview-craft.md — the interview craft that defeats buyer politeness — who calls, when, and the questions that get truth

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="win-loss-analysis"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Win/Loss Analysis is one of 599 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog