As of 13 August 2026, AI can analyse your won and lost deals.
Most people should hand this to a purpose-built tool.
Can you do it?
15 minutesto a draft.
1 hourto something you’d act on.
Cost, all in£0
Skill neededchat-fluent
Who has to check ita colleague
What the alternative costsA specialist sales analyst is the alternative, but no price is supplied in the available tool information.
If this goes wrong: you mistake a correlation in your deal history for a sales cause and change a process that was working.
What to actually do
Use a tool built for this
The route this page recommends
Do it yourself
Second choiceA chat interface, chat-fluent skill, and roughly 1 hour until you can act on the result.
How to actually do it
- Export the relevant won and lost opportunities from your CRM, including outcome, close date, value, stage history, lead source, customer type, salesperson and recorded loss reason where available.
- Remove personal contact details and any customer information you are not allowed to share, then keep a consistent row for each deal and label the date range and currency.
- Open a chatbot and paste the prompt followed by the cleaned deal table, adding call notes or transcripts only where you have permission to use them.
- Ask the model to flag missing fields, duplicate deals and inconsistent labels before it interprets any pattern.
- Check every count, percentage, deal example and stated reason against the CRM export, correcting the analysis when the source data does not support it.
- Give the analysis to your sales manager or another colleague who knows the deals, and ask them to challenge the proposed explanations before changing the sales process.
- Test one or two evidence-backed changes in your next deal reviews or qualification process, then compare later outcomes with the same fields recorded consistently.
Prompt
Analyse the won and lost deal data below as a sales operations analyst. Business context: [describe the product, target customer, sales cycle and sales team] Date range: [insert range] Won deals: [paste a table or CSV] Lost deals: [paste a table or CSV] Optional call notes or transcripts: [paste only material you are allowed to share] Use only the information provided. Do not invent missing values, reasons or customer motives. First check the data for missing fields, duplicate deals, inconsistent outcome labels and incomparable time periods. Then: 1. Compare won and lost deals by stage reached, deal size, sales cycle length, customer type, lead source, product or package, stated loss reason and salesperson where those fields exist. 2. Show the counts and percentages used for each comparison, and say when the sample is too small to support a conclusion. 3. Separate observed patterns from possible explanations. Do not claim that one factor caused an outcome unless the data supports that claim. 4. Identify the strongest repeatable signals associated with wins and losses, with three representative deal examples for each signal. 5. Produce a short action plan covering qualification, discovery, follow-up, proposal, pricing and deal review, but mark each recommendation with the evidence behind it. 6. List the additional CRM fields or customer questions that would make the analysis more reliable. Present the result under these headings: Data quality, Executive summary, Won versus lost comparison, Evidence-backed patterns, Possible explanations, Recommended actions, Examples, Limitations and Questions to investigate. Keep the tone direct and suitable for a UK sales manager.
Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.
Hand it to a person
The distant thirdA person who owns the outcome does this end to end, worth it when the failure is dear.
What it gets wrong
- It cannot know that a recorded loss reason was a polite explanation rather than the real reason the buyer chose another supplier.
- It cannot recover missing deal context such as an internal champion leaving, a procurement freeze or a competitor relationship unless you provide it.
- It can mistake a small or uneven sample for a reliable sales pattern, especially when deal values, segments or salespeople are not comparable.
- It cannot decide whether a recommended change fits your market, team capacity or current commercial strategy.
- It cannot turn messy CRM records into trustworthy evidence without you checking the source rows and definitions.
Even on a YES, the friction has a name: judgement under ambiguity, context depth and stakes of error.
How we scored this
Five axes, each scored nought to two by hand: ten means AI carries the task cleanly, and the thresholds that turn a total into YES, PARTLY or NO are published in the methodology. Each axis name links to its definition.
| Axis | Score (0–2) |
|---|---|
| Output | 2 |
| Inputs | 2 |
| Verification | 1 |
| Liability | 2 |
| Effort delta | 2 |
| Total | 9 / 10 |
The methodology and its thresholds are published in full.
FAQ
- Can ChatGPT analyse my sales pipeline?
- Yes. Give it a cleaned CRM export with deal outcomes and ask it to show the calculations, separate patterns from explanations and flag weak evidence. You still need to check the rows and have a sales colleague challenge the conclusions.
- What data does AI need to analyse won and lost deals?
- Useful fields include outcome, close date, value, stage history, lead source, customer type, salesperson, sales cycle length and stated reason for winning or losing. Call notes can add context, but remove unnecessary personal data and share them only when you have permission.
- Can AI tell me why I lose sales?
- It can identify repeated signals in the reasons and fields recorded in your CRM. It cannot reliably know a buyer's unrecorded motive, so treat its explanations as hypotheses and test them with your team or customers.
- Is AI analysis of my sales data accurate?
- It can calculate and summarise the data accurately when the export is clean, but the conclusions are only as reliable as your fields, sample and deal notes. Check every figure against the CRM and do not change pricing or qualification rules from one unexplained pattern.
Nearby answers
Assessed by gpt-5.6-luna (gpt-5.6-luna) on 2026-08-13, second-checked by an independent model. Wrong somewhere? Email [email protected] and it gets re-checked.
The newsletter
AI news, new answers and product picks, straight to your inbox.