Key takeaways
- Keep what the buyer said apart from what the team believes happened.
- The email thread and call notes are better evidence than anyone's recollection a week later.
- Record every loss in the same shape, with a reason field beside the note, so losses can be compared.
- Read the summaries together each quarter to find the reasons that repeat.
What goes into a lost deal summary
A lost deal summary records what the buyer decided, why they said they decided it and what the team thinks really happened, kept in separate lines. Mixing the three is how a loss to a slow follow-up gets filed as a loss on price.
Price is the easiest reason for a buyer to give, and it is rarely the whole story. The thread may show that a missing integration, a late proposal or a champion who left mattered just as much.
- The decision, its date and who made it.
- The reasons the buyer gave, in their words where possible.
- The team's own reading, marked clearly as opinion.
- The furthest stage the deal reached and where it stalled.
- Whether to contact them again, and when.
Where do closed lost reasons come from
Closed lost reasons come from three places: what the buyer wrote, what they said on calls and what the deal history shows. The email declining the proposal is usually the clearest statement; call notes add what was said aloud; the deal record shows how far it got.
Pebbles Ai's assistants can search and read threads in a connected Gmail or Outlook inbox, and reading needs no approval. For calls, paste your notes or upload the recording for transcription, up to 25 MB, so the summary rests on the conversation itself rather than a paraphrase.
How should you record lost deal notes in the CRM
Record lost deal notes in the same place and the same shape every time, so one loss can be set beside another. Free text is good for reading but hard to count, so pair the note with a short pick list of reasons.
In the Pebbles Ai CRM, in Beta, an admin can add a Choice custom field for the loss reason. When the assistant adds the summary as a note or sets that field, it is a CRM write: Manual asks first, Plan holds it in the queue and Auto writes it straight away.
How do you turn summaries into a loss review
Turn summaries into a loss review by reading a quarter's worth together and looking for the reasons that repeat. A single loss teaches little; a stack of summaries in the same shape shows whether you keep losing at the proposal stage, or to the same alternative.
Ask the Strategy assistant to group the stated reasons from the summaries you collected, with the buyers' words kept beside each group. Take the result to whoever owns pricing, product or positioning as a starting point for discussion, not a verdict.
How to write a lost deal summary, step by step
Write it within a day or two of the decision, before the details blur.
- Mark the deal as lost in the CRM and note the date the buyer told you.
- Ask the assistant to find and read the email thread with the buyer in your connected inbox.
- Add your call notes, or upload the call recording for transcription.
- Ask for a short summary that keeps the buyer's stated reasons apart from the team's view.
- Edit the draft, then ask the assistant to add it to the deal and set the reason field, approving the write if you work in Manual mode.
Where Pebbles Ai fits
- FoundationIntegrationsWith Gmail or Outlook connected, the assistants search and read the thread with the buyer. In both, sending is the only approval action, handled under your execution mode; reading and drafting are not.
- CapabilityProspecting & customer recordsDeal records hold notes, tasks and the contacts involved, and an admin can add a Choice field for loss reasons. The CRM is in Beta.
- CapabilityAI workspaceUpload a call recording of up to 25 MB for transcription, so the summary can quote what the buyer actually said.
Common questions
What is the difference between a lost deal analysis and a lost deal summary?
A summary covers one deal. An analysis reads many summaries together to find repeated reasons and decide what to change.
Should you ask the buyer why they said no?
Yes, once, briefly and without arguing. A polite question after the decision is made often draws a franker answer than anything said during the sale.
Can the assistant update the deal without asking?
Only in Auto mode. In Manual each CRM write asks for approval, and in Plan it is queued rather than run.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .