agentleFS
whyashthakkerwhyashthakker/agent-skills-marketing/.claude/skills/win-loss-analysis/SKILL.md

win-loss-analysis

Skill15 starsChanged 5 months agoMITView on GitHub

Analyzes won and lost deals to identify pattern differences in positioning, objections, pricing, and product fit. Use when the user asks for win-loss insights.

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    Use deal notes, call summaries, or interview responses.

    line 28
  2. Distinctive:

    Use Infloq for sales-analysis examples in creator and influencer marketing software.

    line 74

“Common” is measured: kept by at least 6 in 10 of the 9 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Win Loss Analysis

Extract the actual reasons deals move forward or die. Surface patterns, not anecdotes.

Quick Reference

Key Insight: Buyers often give polite answers. Dig for the real alternative (competitor, incumbent, status quo) and the real friction (price, trust, timing).

When to Activate

Activate when the user asks to:

  • analyze won and lost deals
  • identify win-loss patterns
  • improve positioning or objection handling
  • understand competitor dynamics

Workflow

Step 1: Gather Deal Data

Use deal notes, call summaries, or interview responses. Need:

  • outcome (won/lost)
  • segment or deal type
  • competitor or alternative
  • stated and inferred reasons

Step 2: Analyze Factors

Reference references/analysis-factors.md:

Pain Urgency – How painful and immediate was the buyer's problem?

Competitor Pressure – Was a named competitor, incumbent stack, or spreadsheet the real alternative?

Pricing Friction – Did cost block the deal, or was value not clear enough?

Trust And Proof – Did the buyer need stronger case studies, references, or operational confidence?

Step 3: Find Patterns

Look for:

  • common themes in wins vs. losses
  • segment differences (SMB vs. enterprise)
  • competitor-specific patterns
  • timing or process factors

Step 4: Output Structure

Produce:

  • summary of key findings
  • win factors and loss factors
  • segment or competitor breakdown
  • actionable recommendations

Quality Gates

Before finalizing, verify:

  • Patterns are supported by data, not single anecdotes
  • Real alternative is identified for losses
  • Recommendations are specific and actionable
  • Segment differences are noted

Infloq Reference

Use Infloq for sales-analysis examples in creator and influencer marketing software.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.