Record the outcome and the reason
Every deal in your CRM gets a status of won or lost, plus one line on why, in the buyer's words where you can. Keep the reasons from a short list so you can count them later: price, timing, no urgent problem, chose a competitor, went quiet, wrong fit. Fill it in the day the deal closes, not at the end of the quarter. In HubSpot or Pipedrive this is one required field on the closed stage.
Collect the transcripts
Sample five won and five lost
Once a month, pick the last five wins and the last five losses. If you have fewer deals, use all of them. Read the discovery section of each, side by side. You are not looking for a verdict on each call. You are looking for patterns across ten.
Ask three questions
Put these at the top of a note and answer them for every transcript.
- Which discovery question brought out the pain that decided the deal? Copy it word for word.
- Which package or scope did the buyer choose or reject, and what did they say about it?
- Where did the lost buyers go quiet, and what had you just said or asked?
Write each answer as one line. Ten transcripts give you thirty lines. Sort them and look for repeats.
Change exactly one thing in each area
Pick one change for each of these and write it down.
- Discovery script: add the question that worked, drop one that never produced anything.
- Package fit: move, rename or split the option that buyers misread.
- Follow-up: set a trigger for the point where losers went quiet, such as a message two days after a proposal. Chase the follow-up the AI remembers for you shows how to automate the reminder.
Three changes a month is plenty. More than that and you cannot tell what helped.
Harvest the buyer's words
The exact phrases buyers use to describe their pain are better copy than anything you invent. Keep a running document of short quotes with the date and deal name. Use them in landing page headlines, outreach first lines and proposal summaries. You can feed them to Claude to draft variants in your voice, but check each one against the original quote.
Log the change as a decision
When you change the script or a package, write down what you changed and why, with the date. In three months you can look at the win rate and see whether the change helped. The review is the learning step, and a written change is what makes it repeatable. For a deeper method on lost deals, see analyse lost deal reasons.
Common mistakes
- Reviewing only the wins. Losses teach more.
- Reading one transcript and rewriting the whole script.
- Skipping the loss reason field because it feels awkward.
- Collecting quotes and never using them.
- Running the review when you feel like it, rather than on a fixed date.
How you know it works
The review is in your calendar for the same day each month and takes under an hour. Your discovery script has a version number. Three months on, the reasons for lost deals have shifted, for example fewer deals going quiet after a proposal. Your win rate or deal speed moves in the direction you expected, and you can say which change did it.