Business guides

How to Analyse Lost Deals and Improve the Next Conversation

A glowing coral structure with a broken branch sprouting many new branches in deep blue water.
On this page
  1. Define the decision before the workflow
  2. A practical method
  3. Worked example: from an idea to a defensible next step
  4. Working worksheet
  5. How to know whether it is working
  6. Mistakes that make the process look better than it is
  7. Putting the method to work with Dainin
  8. Related guides and reference material

The best approach to lost deals as information about market-fit produces a decision the organisation can explain, repeat and improve. It does not depend on one person's memory or a dashboard full of uninterpreted activity. Start by asking: What factors can be documented rather than guessed?

Define the decision before the workflow#

Write this question at the top of the working document: What factors can be documented rather than guessed? Establish the people who will make or be affected by the decision, the time horizon and the cost of being wrong. Then separate verified facts from reasonable hypotheses and genuine unknowns. An assumption is acceptable at the start; an assumption disguised as a verified finding is not.

For a practical example, consider a provider losing to an incumbent consultancy. The tempting move is to start producing collateral, buying tools or contacting a market. A disciplined approach first records the existing alternative, the evidence for the opportunity and the smallest commitment needed to test whether the offer or intervention is truly relevant.

A practical method

  1. Prepare the buyer and relationship context

    Working question: What is verified, inferred or still unknown?

    Create a concise pre-meeting evidence brief: buyer organisation, visible situation, relationship history, relevant offer, likely assumptions and gaps. Label unknowns; an AI-generated biography is not the same as verified customer context. A review should later be able to inspect loss-reason coverage and offer improvement without inventing the story afterwards.

    Output to retain: A buyer brief distinguishing observed facts, inferences and missing evidence.

  2. Agree the decision the interaction should support

    Working question: What outcome would make this meeting useful for both sides?

    Agree the decision the conversation can support. A discovery call may be intended to establish fit, identify a sponsor or decide whether a diagnostic is useful. Opening with a product tour often hides the real purpose of the meeting. In this step, lost deals as information about market-fit becomes a working question instead of a slogan.

    Output to retain: A written meeting objective co-owned by the participants.

  3. Explore causes, effects and existing alternatives

    Working question: What is the actual commercial or operational cost of the problem?

    Ask about recent examples, existing alternatives, ownership, consequences and attempts already made. Distinguish curiosity from urgency and authority. A useful question invites specific evidence rather than pushing the buyer towards the seller's preferred diagnosis. Use the decision what factors can be documented rather than guessed to determine whether the step is complete.

    Output to retain: A problem statement connected to consequence and existing alternatives.

  4. Match the right evidence to the concern

    Working question: What proof addresses the decision without overselling?

    Bring the right proof at the moment it resolves a real question. This may be a scoped case, transparent methodology or demonstration with known limitations. Never cover weak evidence with manufactured certainty or unrelated success stories. Record this step in the same working record that will later support a loss review with buyer-observed causes and actions.

    Output to retain: A proof plan that addresses the buyer decision without promising unverified outcomes.

  5. Define the authority and the next commitment

    Working question: Who can approve price, scope and the proposed next step?

    Clarify who can decide on budget, pricing, scope, privacy and implementation. Separate a meeting agreement from authority to sign. Commercial exceptions should follow the organisation's approved decision path rather than being improvised by an enthusiastic seller or agent. For the example of a provider losing to an incumbent consultancy, do not assume the answer is already known.

    Output to retain: A decision map showing approvers, commitments and the next legitimate step.

  6. Record what was learned and update the opportunity

    Working question: What new evidence warrants pipeline movement?

    Write down what changed: confirmed problem, unresolved questions, decision owner, agreed next action and date. Update pipeline only if the buyer decision warrants it. After delivery or loss, compare the prediction with the observed result and revise the method. Test the step against the failure you specifically want to avoid: blaming every loss on price without buyer evidence.

    Output to retain: A truthful opportunity update based on new evidence rather than calendar activity.

Worked example: from an idea to a defensible next step#

Imagine a provider losing to an incumbent consultancy. The team begins with the decision question: What factors can be documented rather than guessed? Its initial hypothesis is that lost deals as information about market-fit will materially improve the situation, but it has not yet established what the buyer, client or stakeholder would accept as proof.

First, the team documents the existing way of doing the work and what is unsatisfactory about it. It then collects a small number of relevant observations rather than an indiscriminate dataset. Contradictory observations are retained because they may reveal that the intended audience is too broad, the offer is mis-scoped or the problem is not urgent. The team prepares a loss review with buyer-observed causes and actions and asks an accountable person to review the assumptions.

The first implementation is deliberately bounded. After the work, the team examines loss-reason coverage and offer improvement. A positive signal is a reason to investigate expansion, not a licence to assume the same result will hold for every customer or market. If the evidence is negative, the correct outcome may be to narrow the audience, redesign the offer, revisit the method or stop.

Working worksheet#

FieldWhat to record
Decision to makeWhat factors can be documented rather than guessed
Central mechanismLost deals as information about market-fit
Evidence already availableLinks, observations, interviews and their dates
Key uncertaintyThe most consequential assumption that remains untested
DeliverableA loss review with buyer-observed causes and actions
Decision ownerThe person authorised to approve the next commitment
Evaluation signalLoss-reason coverage and offer improvement
Review dateThe point at which evidence will be inspected, not simply reported

How to know whether it is working#

Use loss-reason coverage and offer improvement as the main substantive signal, but do not read it alone. Compare the current period with a relevant baseline and ask whether the mix of buyers, work and conditions changed. Record both leading indicators, which suggest progress, and lagging indicators, which show whether the intended outcome occurred. Avoid attributing a commercial result to a single article, meeting, tool or message when several causes were involved.

Add a short qualitative review: What became clearer? Which assumption was disproved? Which person now has enough information to decide? What problem is still unresolved? Those answers make the method reusable rather than reducing it to a performance number.

Mistakes that make the process look better than it is#

Putting the method to work with Dainin#

Within an appropriate Dainin configuration, Lead Analysis, Meeting Planner and Sales Performance can help connect the relevant evidence and the ensuing work. The point is not to automate the judgement away: it is to preserve the context, show what informed the recommendation, route consequential actions through the appropriate authority and retain useful learning for the next iteration.

Next practical move: produce a loss review with buyer-observed causes and actions and use it to decide the smallest worthwhile follow-up. A reader who wants the supporting capability can explore Dainin Academy or the relevant CEOS capability.

See how Dainin connects the evidence, judgement and work behind this method.

Explore Meeting & Sales Performance

Found this useful? Share it with your team.

Written by

Dainin Research & Insights

Research team, Dainin

The Dainin research team writes about how organisations connect business understanding, judgement, decision authority and execution, and what that means for enterprise AI.

Dainin CEOS

See how your organisation could work as one.

Talk to us about connecting business understanding, judgement, decision authority and execution across your teams.