lost-deal-analysis

$npx mdskill add Significant-Gravitas/skills-catalog/lost-deal-analysis

Use this for closed-lost deals over a stated period, from a dated export.

SKILL.md

.github/skills/lost-deal-analysisView on GitHub ↗
---
name: "lost-deal-analysis"
description: "Analyse lost deals by recorded reason, stage, segment, and age, with gaps in the reasons shown."
triggers: ["lost deals", "win loss", "why are we losing", "closed lost", "loss reasons"]
version: "1"
---

# Lost deal analysis

Use this for closed-lost deals over a stated period, from a dated export.

## Check reason quality

Count lost deals and their value. Then count how many have a loss reason, how
many use "other" or a free-text note, and how many reasons were added long
after the close date. If more than a quarter lack a usable reason, say so
first; the breakdown will be weak.

## Break down the losses

Break losses down by:

- recorded reason;
- stage at loss;
- segment, region, and deal size;
- age at loss and days since last activity;
- owner, only where the count is large enough to mean something.

Compare with won deals over the same period where you can. Quote rep notes or
customer words only as written, with the deal id.

## What the data cannot say

State what the records cannot show: reasons picked from a short list, deals
lost before they were entered, and reps who log reasons differently. Suggest
the smallest next check, such as five calls with lost buyers.

Never fill a blank loss reason with a guess or infer one from the amount. Do
not edit deals in the CRM; propose changes to the reason list for approval.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.