AI skill · Volume 1 · Workflow W10

How do you run a win/loss debrief on a TIC deal?

It runs a short debrief with a seller when a deal closes, or turns a quarter's debriefs into a pattern report.

It is workflow W10 of the twelve in The AI-Augmented TIC Sales Machine, sold on its own as one AI skill file (.zip) with a two-page start-here guide. Everything it writes is a draft for a person to check.

By Allen Chen, Deep Dive Reports, Wellington, New Zealand · Published 23 September 2026 · The skill carries the workflow and its prompts word for word from the report; it was adapted with AI assistance under a fixed method, and Allen Chen holds editorial responsibility. How the research is done

What you give it, and what comes back.

You attach: the closed deal's CRM summary, or a quarter's debriefs.

You get back: A structured debrief record, and a quarterly pattern report.

It does not: read your CRM by itself. You give it the records.

The CRM summary of the closed deal. For the quarterly report, also the quarter's debriefs, the CRM records and the previous report.

One run, start to finish

What it looks like when you use it.

Run in Claude (Opus 5, high effort), in our own Claude account with the skill installed on 20 September 2026. The deal and its CRM summary are invented for this example, and the run is shown as it came back, unedited. This skill interviews the seller, so the first output is questions, not a report. Your assistant's wording will differ: AI answers change between assistants and between runs.

input · what was given to the skill

The closed deal, invented. KettleExample SA. Value EUR 18,000, electrical safety and EMC for a new kettle range. Lost. Decision last month, to the incumbent laboratory. Enquiry in January, quote in February, two technical calls, revised quote in April, no decision until August. The seller's note in the CRM says: "price".

output · what came back

Debrief, internal only.

The record says "price". It also shows four months of silence between the revised quote in April and the decision in August. Those two things do not sit together comfortably. A price loss is usually quick. Here are the three questions. Answer them one at a time.

Question 1. Between the revised quote in April and the decision in August, what was actually happening on their side? Who did you speak to, and what did they tell you was holding it up?

Question 2. Did you ever see or hear the incumbent's number, from the customer or any other route? If not, what made you write "price" in the CRM?

Question 3. Who made the final call, and had you spoken to that person directly at any point in the deal?

I will ask at most one follow-up after your answers, then produce the structured record.

what to notice

This skill is an interviewer, so a short output is the correct output. It read the CRM summary, noticed that a four-month silence does not look like a price loss, and asked three questions aimed at the gap between what the seller wrote and what the record shows.

Question 2 is the one worth the money. "Price" is the most common thing written in a lost-deal field and often the least examined; the skill asks whether anyone actually saw the competitor's number. Question 3 goes after the other usual cause: never having spoken to the person who decided. The structured record comes after the seller answers, not before.

The skill, or the report?

This workflow is not sold on its own. It comes with The AI-Augmented TIC Sales Machine, which sets out the method and the evidence for all twelve of its workflows, and every licence includes all twelve as ready-made skill files at no extra cost.