本文へ移動
cccskills
無料GitHub で公開

win-loss

Analyses sales call transcripts (and churn or renewal calls) to find why deals are won, lost, kept or churned. Reads each call across six dimensions (product, messaging, sales process, pricing, competition, customer context), pulls verbatim quotes with the speaker named, counts how often each pattern appears, and writes findings with recommendations. Works with any recorder export or pasted text. Triggers: "win/loss analysis", "why do we lose", "why do we win", "analyse these sales calls", "lost deals", "churn analysis", "objection patterns". Feeds /positioning and /messaging. Not for general meeting summaries or competitor research (use /competitor-research).

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Win-loss

Turn sales calls into evidence about why people buy and why they don't. The quotes are the main product; the summary is secondary. Every pattern you report has to trace back to something a person said on a call.

When to use it

  • After 5 or more closed deals with recordings or notes.
  • Before positioning or messaging work, to replace opinions about objections with evidence.
  • When win rate drops, or a competitor starts showing up in losses.
  • Monthly, as a standing review for a team with steady deal flow.

Don't use it for one-off meeting notes, for researching competitors from the outside (/competitor-research), or for picking an ICP on its own (feed the findings into /icp-research).

Inputs

Required: transcripts, each with the customer (or a code name) and the outcome: win, loss, retention or churn. If the outcome isn't given, ask. Only infer it when the call itself states it.

Optional: deal size and stage, competitor names to watch for, context/icp/ and context/competitors/ for cross-referencing.

Paths. Write to context/win-loss/MMYY-win-loss.md. Keep a short context/win-loss/win-loss-strategy.md across runs: decisions made, definitions agreed, things to stop doing. Read it first on every run. Agency or consultant? Swap context/ for clients/<client>/context/ throughout.

Tools. None needed beyond the transcripts. If a call recorder or CRM is connected, pull from it; otherwise the user pastes or uploads files.

Before you analyse

  • Normalise the format. Recorder exports, subtitle files, JSON and pasted text all become one shape: speaker-attributed turns, with timestamps where they exist.
  • Redact personal data. Mask end-customer names, emails, phone and account numbers. Keep roles, company type and deal context.
  • Bind every claim to a quote. A finding without a quote and a named speaker role doesn't ship.

The six dimensions

DimensionWin signalsLoss signals
Product"Exactly what we need""It doesn't do X"
Messaging"Now I see why this matters""What does it actually do?"
Sales process"You understood our problem""The demo missed our use case"
Pricing"Fair for what we get""Over budget", "too expensive"
Competition"Chose you over Y""Going with Y"
Customer context"We need this by Q2""No rush, maybe next year"

Steps

  1. Read the strategy file if one exists, and apply its locked definitions.
  2. Process each call. Classify the outcome, tag speakers (buyer, champion, rep), and pull quotes against the six dimensions. Produces: a per-call evidence table.
  3. Aggregate by outcome. Group wins, losses, retention and churn. Count how many calls support each pattern ("4 of 7 losses").
  4. Rank patterns. Three or more mentions is a pattern. Two is emerging. One is a single mention, labelled as unconfirmed.
  5. Cross-reference by segment, deal size or competitor where the data allows. Look across at least three cuts, not just competitor.
  6. Separate product gaps from sales execution. They go to different teams.
  7. Write insights. For each: the pattern, the evidence with frequency and quotes, the confidence, and what to do about it.
  8. Update the strategy file with new decisions and definitions.
  9. Hand off to /positioning and /messaging.

Output shape

Open with a 3-line TLDR and the sample size, stated once. Then: an executive summary, top win drivers, top loss drivers, objection themes with suggested responses, competitor mentions, a per-dimension breakdown, recommendations split into product, messaging and sales, and an appendix of quotes by call.

Confidence: high is 3 or more consistent calls, medium is 2 or strong indirect signals, low is a single mention.

What good looks like

  • Every finding has a frequency and at least one verbatim quote with a speaker role.
  • Patterns are described as "associated with", not "caused by".
  • Small samples are flagged clearly. Under 5 wins and 5 losses, findings are directional.
  • Dimensions with no data say "not discussed in transcripts".
  • A seller could use the objection section on their next call.

Mistakes to avoid

  • Summarising what buyers said instead of quoting them.
  • Treating one memorable call as a pattern.
  • Mixing up what the rep said with what the buyer said.
  • Reading cause into correlation ("long cycles lose deals").
  • Keeping customer names or emails in the saved file.

Chain

Step 4 of the suggested chain: /company-context → /icp-research → /competitor-research → win-loss → /expert-pov → /tov-guidelines → /brand-kit → /positioning → /messaging → /funnel-strategy → /goals.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

brand-kit

無料

Extracts a company's visual identity from screenshots (best) or its website (fallback) and writes a DESIGN.md brand file: machine-readable tokens for colours, typography, spacing, corner radius and logo usage, plus short prose explaining how and when to use each, and a list of do's and don'ts. Any later page, deck, carousel or ad can read the tokens instead of guessing. Triggers: "brand kit", "brand guidelines", "extract our brand", "design tokens", "colours and fonts from", "visual identity", "DESIGN.md". Not for tone of voice (use /tov-guidelines) or messaging (use /messaging).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

Researches a company from its website and public sources and writes a company profile: what it sells, who buys it, traction, funding, team, hiring, tech stack, key people, red flags and the gaps you still need to fill, every claim tagged with a source and a confidence level. Use it as the first file in a marketing context folder, or to prep a discovery call or qualify a prospect. Triggers: "company research", "company background", "company context for", "qualify this prospect", "discovery call prep", "account brief", or a company URL handed over for research. Not for competitor analysis (use /competitor-research) or customer profiles (use /icp-research).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

Researches one B2B SaaS competitor across 13 dimensions (company, product, ICP, pricing, reviews, content, launches, search and AI visibility, tech stack, hiring, go-to-market, social, paid ads) and writes a sourced dossier with an executive summary, a threat level, strengths and weaknesses, and a data gaps section. Run it once per competitor, then compare. Triggers: "competitor analysis", "competitor research on", "what is [competitor] doing", "compare us to", "competitive landscape", "battlecard prep". Run after /company-context and /icp-research. Not for researching your own company (use /company-context).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

Draws out a founder's or expert's point of view: what they believe about their market that others don't, the hot takes they'd defend, the stories behind them, and their taste. Generates interview questions, works from answers, a live call or existing content, and ends with ranked One Big Idea candidates for thought leadership and positioning. Triggers: "expert POV", "founder POV", "one big idea", "OBI", "contrarian beliefs", "what makes our founder different", "thought leadership foundation", "founder interview questions". Feeds /positioning and /tov-guidelines. Not for writing posts or articles, and not for brand voice rules (use /tov-guidelines).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

Works out a company's go-to-market motion (product-led, sales-led or hybrid) from its website and pricing, then maps the funnel stage by stage: a definition, strategy, leading inputs the team controls, lagging outputs with targets, cadence and owner for each stage, MQL, SQL and PQL criteria, post-sale stages, closed-lost re-entry paths and backward funnel maths from a revenue target. Triggers: "funnel strategy", "funnel stages", "pipeline stages", "PLG vs SLG", "lead qualification criteria", "map our sales process", "how do leads flow". Feeds /goals. Not for setting the target itself (use /goals).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

goals

無料

Turns a target someone has already committed to (a board plan, an annual plan, a contract) into a plan the team can measure: KPIs in three tiers with a guardrail for each, a baseline from real data, monthly pacing with lag and seasonality, and two or three channels chosen from how your ICP actually searches and buys. Writes context/goals/MMYY-scope.md and context/goals/measurement.md. It never invents the target. Triggers: "set our goals", "what are our KPIs", "revenue target and pacing", "which channels and what targets", "write the scope file", "are we on track". Run after /funnel-strategy. Not for designing funnel stages (use /funnel-strategy).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

matteotitta のスキルをすべて見る

このスキルの問題を報告する