Twenty minutes. Six questions. One pattern worth keeping.
A short structured review of a deal you lost, using the same template every time so five reviews show you where you leak.
After a loss, most people either move on or tell themselves the story that hurts least: no budget, a cheaper competitor, bad timing. One story tells you nothing, and the same deals keep dying at the same point.
Lost Deal Review asks for the facts, labels each reason as known or a guess, traces the timeline to find where energy dropped, and checks four early signals. It drafts a two-line message to the buyer, writes a one-line pattern with a tag, and picks one change for the next deal.
What it produces.
- →A factual two-sentence account of the loss
- →A known-versus-guess list of reasons
- →A timeline marking where energy dropped
- →A tagged one-line pattern and one change to make
- ✦Founders who lose deals and move on without looking
- ✦Salespeople who want a consistent post-loss routine
- ✦Consultants tracking why proposals do not close
This Playbook is a short review for the pattern across deals. It does not include the deeper work in the What Actually Happened Tool: reconstructing what was knowable at the time and separating decision quality from luck. The What Actually Happened Tool is for learning the right lesson from a significant outcome, not just logging a pattern.
See the What Actually Happened Tool ($79) →- →lost-deal-review.zip: a native Claude Skill. Upload to Settings → Skills in Claude, or unzip to
~/.claude/skills/ - →lost-deal-review-skill.md: plain markdown. Works in ChatGPT Custom GPTs, Gemini, Claude Projects, agent system prompts, anywhere
- →A README inside the zip with install steps for Claude, ChatGPT, and Gemini
What it does with a real question.
We lost the Brightwater Logistics deal on March 14, a $48,000 annual contract for our dispatch software. After two demos and a pricing call, their ops director went with a competitor that came in about 15% cheaper. Our champion, the dispatch manager, went quiet three weeks before the decision. Can you run a lost deal review?
What happened, and what you know. You offered $48,000 a year for dispatch software, and after two demos and a pricing call, the ops director chose a competitor about 15% cheaper. That is the only firm fact. "We lost on price" is a guess until someone at Brightwater says so, and the timeline argues against it. Your champion went quiet three weeks before the decision, which means the deal was likely turning well before the ops director signed anything. Price usually gets named at the end because it is the easiest reason to say out loud.
My read. The leading explanation is a decision-maker problem. Your champion was the dispatch manager, and the ops director chose. If the ops director only appeared at the pricing call, you sold the value to someone who could not buy it, then asked the buyer to justify a premium with no one inside advocating for you. A 15% gap is also small enough that a champion with real authority or a strong case could have absorbed it. I would tag this "no decision-maker" provisionally, with price as the stated cause and champion drift as the early sign.
Next move. Send the ops director two lines: thank them, and ask what the deciding factor was, making clear you are not reopening the deal. Separately, find out whether your champion ever presented your case upward. Then change one habit: on the first call of the next deal, ask who signs off and get that person into the second demo.
The full Playbook runs the whole procedure and writes the complete deliverable, not this excerpt.
Written by claude-sonnet-5-5 with this Playbook loaded, 2026-10-11. Checked automatically for length and for copied framework text.
No subscription · free updates within v1.x
Works as a Claude Skill (.zip) and as a plain .md for ChatGPT, Gemini & every LLM
Delivered to your email within 60 seconds · Secured by Stripe
Price includes UK VAT where applicable
Before you buy.
How is this different from just asking Claude directly?
Asked cold, Claude offers a plausible explanation for why the deal was lost. This holds the same short template each time, separates what you know from what you guess, and records a tagged pattern you can compare across deals.
How is this different from a Tool?
Playbooks are systematically produced to a fixed template and priced accordingly ($12.99). Tools are hand-built, one at a time, and go deeper ($39 to $199). A Playbook gives you a reliable method for routine work; a Tool is for when the judgment matters more than the format. This Playbook is a short review for the pattern across deals. It does not include the deeper work in the What Actually Happened Tool: reconstructing what was knowable at the time and separating decision quality from luck. The What Actually Happened Tool is for learning the right lesson from a significant outcome, not just logging a pattern.
Will this work with ChatGPT, Gemini, and other LLMs?
Yes. You get a native Claude Skill (.zip) that auto-invokes in Claude, plus a plain .md you can paste into a ChatGPT Custom GPT, a Gemini system prompt, or any LLM. The procedure travels with the file.
Can I share this with my team?
It's licensed for your own personal and professional use. The output it produces is yours to circulate. To put the Playbook itself in the hands of a whole team, email hello@authority.md about team licensing.
What if it doesn't work for me?
If the file hasn't been delivered, or arrives defective or empty, we refund in full: see our refund policy.