Agent Skillsmohitagw15856/pm-claude-skills › win-loss-analysis

win-loss-analysis

GitHub

分析赢单与输单原因,生成结构化报告。通过量化数据、提取买家证言和竞争动态,识别可控因素,为产品、营销和销售团队提供优先级排序的改进行动建议。

exports/openclaw/win-loss-analysis/SKILL.md mohitagw15856/pm-claude-skills

Trigger Scenarios

请求运行赢/输分析 审查已关闭的赢单或输单交易 了解团队为何输给特定竞争对手 将销售反馈总结为模式

Install

npx skills add mohitagw15856/pm-claude-skills --skill win-loss-analysis -g -y
More Options

Non-standard path

npx skills add https://github.com/mohitagw15856/pm-claude-skills/tree/main/exports/openclaw/win-loss-analysis -g -y

Use without installing

npx skills use mohitagw15856/pm-claude-skills@win-loss-analysis

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill win-loss-analysis -a claude-code -g -y

安装 repo 全部 skill

npx skills add mohitagw15856/pm-claude-skills --all -g -y

预览 repo 内 skill

npx skills add mohitagw15856/pm-claude-skills --list

SKILL.md

Frontmatter
{
    "name": "win-loss-analysis",
    "homepage": "https:\/\/mohitagw15856.github.io\/pm-claude-skills\/skill\/win-loss-analysis.html",
    "metadata": {
        "openclaw": {
            "emoji": "📣"
        }
    },
    "description": "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."
}

Win/Loss Analysis Skill

Turn raw deal outcomes and buyer feedback into a clear picture of why you win and lose — and what to do about it. The output should let a product marketer or revenue leader act on patterns, not anecdotes.

What This Skill Produces

  • A win/loss report with the top reasons deals were won and lost, ranked by frequency and deal value
  • Win/loss rates cut by segment, deal size, competitor, and source where the data allows
  • Representative buyer quotes that make each theme concrete
  • A prioritized action list mapped to product, marketing, sales, and pricing owners

Required Inputs

Ask for these if not provided:

  • 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

If the data is thin, say so and analyze what exists rather than inventing outcomes.

Process

  1. Normalize the reasons — collapse free-text loss reasons into a consistent taxonomy (price, product gap, timing/no-decision, competitor, champion left, poor fit, etc.).
  2. Quantify — count wins and losses per reason; weight by deal value; compute win rate overall and by cut.
  3. Separate controllable from structural — a missing feature is controllable; a genuine no-budget is not. Focus action on the controllable.
  4. Pull evidence — attach 1–2 real quotes per major theme. Never fabricate quotes; mark [quote to add] if none is available.
  5. Isolate competitor dynamics — where you lose to each competitor and on what basis.
  6. Recommend actions — for each top theme, the single highest-leverage move and who owns it.

Output Format


Win/Loss Analysis — [Period]

Scope: [N won · N lost · total value] · Segments: [list] · Source: [interviews / CRM / survey]

Headline

[2–3 sentences: overall win rate, the biggest swing factor, and the one thing to fix first.]

Why We Win (ranked)

# Reason % of wins Notable in
1 [Reason] [%] [segment/competitor]

Evidence: "[buyer quote]"

Why We Lose (ranked)

# Reason % of losses Controllable? Est. value at stake
1 [Reason] [%] Yes/No/Partly [$]

Evidence: "[buyer quote]"

Win Rate by Cut

Cut Win rate Read
[Segment / competitor / deal size] [%] [what it means]

Competitive Read

  • vs [Competitor]: [where and why we win/lose, and the counter]

Actions

Theme Recommended action Owner Effort Expected impact
[Theme] [Specific move] [Product/PMM/Sales] S/M/L [win-rate or deal-value effect]

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
  • Competitor findings are specific enough to change a battlecard

Anti-Patterns

  • 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

Example Trigger Phrases

  • "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"

Version History

  • 54fad50 Current 2026-07-19 12:38

Same Skill Collection

exports/openclaw/360-feedback-template/SKILL.md
exports/openclaw/401k-plan-decoder/SKILL.md
exports/openclaw/ab-test-planner/SKILL.md
exports/openclaw/ab-test-readout/SKILL.md
exports/openclaw/accessibility-audit/SKILL.md
exports/openclaw/account-plan/SKILL.md
exports/openclaw/acquirer-red-team/SKILL.md
exports/openclaw/ad-copy/SKILL.md
exports/openclaw/aeo-optimizer/SKILL.md
exports/openclaw/agenda-or-cancel/SKILL.md
exports/openclaw/agent-design-review/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/ai-ethics-review/SKILL.md
exports/openclaw/ai-eval-plan/SKILL.md
exports/openclaw/ai-feature-prd/SKILL.md
exports/openclaw/ai-product-canvas/SKILL.md
exports/openclaw/air-quality/SKILL.md
exports/openclaw/altitude-shifter/SKILL.md
exports/openclaw/ambiguity-resolver/SKILL.md
exports/openclaw/analyst-relations-brief/SKILL.md
exports/openclaw/announcement-card/SKILL.md
exports/openclaw/api-docs-writer/SKILL.md
exports/openclaw/api-test-plan/SKILL.md
exports/openclaw/api-versioning-strategy/SKILL.md
exports/openclaw/apology-letter/SKILL.md
exports/openclaw/architecture-decision-record/SKILL.md
exports/openclaw/architecture-diagram/SKILL.md
exports/openclaw/archive-strategy/SKILL.md
exports/openclaw/assumption-bounty/SKILL.md
exports/openclaw/assumption-mapper/SKILL.md
exports/openclaw/async-update-format/SKILL.md
exports/openclaw/auto-repair-estimate-decoder/SKILL.md
exports/openclaw/autopilot-charter/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-minutes/SKILL.md
exports/openclaw/board-pre-read/SKILL.md
exports/openclaw/bom-cost-review/SKILL.md
exports/openclaw/bookkeeping-categorization/SKILL.md
exports/openclaw/boolean-search-builder/SKILL.md
exports/openclaw/brag-doc/SKILL.md
exports/openclaw/brainstorming/SKILL.md
exports/openclaw/brief-builder/SKILL.md
exports/openclaw/briefing-note/SKILL.md
exports/openclaw/budget-builder/SKILL.md
exports/openclaw/budget-variance-analysis/SKILL.md
exports/openclaw/bug-diagnosis/SKILL.md
exports/openclaw/bug-report/SKILL.md

Metadata

Files
0
Version
471c606
Hash
d81b515c
Indexed
2026-07-19 12:38

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-30 18:11
浙ICP备14020137号-1 $방문자$