TranskribatorTranskribator
Reviewing why a sale fell through: a table for signals and checks
Sales analytics

Reviewing why a sale fell through: a table for signals and checks

Use calls and correspondence to analyze why a prospect declined. Separate the customer’s words, deal stage, events, interpretation, category and follow-up test.

The Transkribator team5-minute read
SOURCEWHY THE DEAL FELL THROUGHInterest: the needis confirmedSignal: migration questionReply: discussion of a discountStop: no next stepagreedFROM WORDS TO RESULTS
Working with a real recordingIllustrated training exampleTemplate to copy
Sales analytics

A final remark may just be a polite way to end the call

A customer may say “we’ll think about it” after an implementation question goes unanswered. If your CRM stores only that remark, the team may fix the wrong thing. Trace the events from initial interest to the end of the discussion.

Transcripts make conversations comparable. A category remains a hypothesis until words, events or further checks support it. Contact the customer again only if you have a lawful basis and an agreed process.

Workflow

Trace the decline through the sequence of events

  1. Identify where the deal stopped

    Record the last agreed step and what should have happened next. Distinguish an explicit refusal, no response and a postponed decision.

  2. Find earlier signals

    Review questions, doubts, delays, changes in participants and promises that weren’t kept. Keep timestamps alongside the final label.

  3. Separate facts from interpretation

    Fact: the customer asked about moving data, and the recording contains no answer. Interpretation: implementation risk may still have concerned them. Keep those in separate fields.

  4. Choose an action that can test the hypothesis

    Match the action to the signal: check demo materials, coach the team on a question, change qualification or collect more interviews. Compare outcomes before promising an improvement.

Worked example

A lost deal recorded as “too expensive”

This is a fictional training example. The names, circumstances and outcomes are included solely to explain the method.

Excerpt from a training recording · 12:40
The price is above our budget, but the main question is who will move our archive and how long staff will have to work in two systems.

The customer raised both price and implementation. If the seller answered only with a discount, operational risk may still have been the sticking point. Record both factors until there’s evidence to isolate one.

To test it, look for a clear migration plan, compare similar won and lost deals and check whether migration came up before price. The scenario is fictional.

Interest: the needis confirmedContextSignal: a questionabout migrationRiskReply: discussionof a discountGapStop:no next stepagreedOutcome
The timeline shows when the signal appeared and whether it was addressed before the customer declined.
FieldExample entryStatus
Direct signalQuestion about moving the archiveConfirmed in the recording
Additional factorPrice above budget expectationsStated by the customer
InterpretationImplementation risk remainedHypothesis
ChecksCompare responses and deal outcomesNext action
Ready-to-use template

Lost deal review table

Use consistent fields so you can compare cases without changing the categories to fit each one.

Template for your workSelect and copy
Deal / anonymized ID:
Stage and stop date:
Last agreed step:
Customer’s exact words:
Questions and signals before the decline:
Seller’s responses:
Unfulfilled promises:
Factors mentioned:
Analyst’s interpretation:
Confidence level and basis:
Timestamps / sources:
Category from the reference list:
What to verify:
Action and owner:
Review date:
Check the result

Check the quality of the categories

  • Explicit refusals are distinct from silence and delays.
  • Direct quotes are separate from interpretation.
  • The category is based on events.
  • The action tests a hypothesis without promising growth.
ConversationRemarks and eventsTimelineTurning pointCodingFact and hypothesisActionProcess check
A review of lost deals should lead to an improvement you can test.
Frequently asked questions

A closer look

How does a lost deal differ from churn?

A lost deal is a prospect that never closed. Churn is when usage stops or shrinks after purchase, so it requires different context and data.

Can we count reasons?

Yes, if categories and coding rules are stable and cases are comparable. Check the categories first, and keep assumptions separate from confirmed causes in the count.

Keep working with the recording