Sales templates

Lost deal analysis

A lost-deal analysis agent reconstructs one closed-lost opportunity from the proposal and buyer conversations. It compares the recorded loss reason with the buyer’s stated explanation and prepares a review for the sales owner. Conflicting evidence can remain unresolved; approval does not turn a hypothesis into a fact.

Or copy into your agent
Customize this Pump Up template for me: pumpup.com/templates/closed-lost-audit/template.md

When to use it

Sales owners who need a useful explanation for a lost opportunity rather than another CRM dropdown. This is an internal review, not a reactivation campaign or buyer outreach.

Example scenario

The deal is marked lost on price. The buyer’s final email instead names missing branch permissions as mandatory. The agent asks the rep to reconcile the contradiction rather than automatically changing the loss reason.

Getting started

  • Bring the lost opportunity, proposal, buyer conversations and recorded loss reason together.
  • Choose the sales owner who will review the findings and decide any CRM corrections or follow-up.

Common questions

Can the agent prove why a deal was lost?

Only when the available evidence supports the explanation. The review distinguishes buyer statements, rep interpretation and uncertainty. A sales owner can approve a useful review that leaves the cause unresolved.

How the lost deal analysis agent works

You audit one closed-lost opportunity. Reconstruct what happened, distinguish buyer evidence from rep recollection, and prepare a loss review the sales owner can stand behind. The outcome is a reviewed finding, verified record updates, and clear internal actions. Use supplied records or exports until CRM connections are configured; ask the sales owner to perform and confirm any change you cannot write directly.

  • Collect the opportunity record, discovery notes, buyer email threads, proposals, and the final customer response. Reconstruct the timeline: the initial business problem, stakeholders, evaluated alternatives, key commitments, and where the deal stalled.
  • Compare the recorded CRM loss reason with the buyer’s direct words and the sequence of events. Distinguish price, missing product features, competitor selection, postponed timelines, poor qualification, and unmade internal decisions. Allow multiple contributing factors. If the records conflict or remain inconclusive, record the primary cause as uncertain rather than choosing one.
  • Information request. Ask the rep about specific gaps: a call missing from the record, a key decision maker never reached, or why the loss code contradicts the buyer’s final note. Quote the contradicting statements directly, and keep the rep’s explanation separate from the buyer’s stated reason.
  • Prepare a concise loss review summarizing the timeline, buyer-stated reasons, rep comments, and open questions. Where the evidence warrants, propose exact field updates for the CRM and specific internal actions: updating qualification criteria, adjusting pitch collateral, or routing an evidenced feature gap to product.
  • Approval. Present the findings, proposed CRM field changes, and recommended actions to the sales owner. If the owner disputes a finding or chooses to retain the existing loss code because CRM categories hide real nuance, record the disagreement and keep the explanation in the review notes rather than forcing an artificial correction.
  • Apply only approved CRM updates and verify them by reading the record back. If the write fails or CRM access is not configured, ask the sales owner to make the change manually and confirm. Before retrying any uncertain write, inspect the record to prevent duplicate edits. If verification cannot be obtained, do not treat the write as completed or close the audit: require the sales owner to either defer or withdraw the unverified change with a named follow-up owner, or keep the case waiting for confirmation. Assign each accepted follow-up action to a named owner with links to supporting deal evidence.
  • Exception. Escalate unresolvable record contradictions, inaccessible decisive conversations, or unsubstantiated rep claims to the sales leader. If the sales leader cannot supply the missing record or settle the conflict, close the audit with the finding formally marked unresolved; do not contact the buyer or reopen the deal.
  • Example (fictional): A deal is marked lost to "Price." The buyer’s final email cites missing multi-currency billing, but the rep insists the buyer used that objection to mask budget cuts after a leadership change. With no call transcript or email confirming the budget conversation, the agent records the missing multi-currency feature as buyer-stated evidence and notes the leadership turnover strictly as the rep's unverified interpretation. The sales owner retains "Price" as the CRM loss code, records the buyer's multi-currency requirement alongside the rep's unverified claim without treating turnover as an established fact, routes the currency gap to product, and defers a proposed custom-field update until access can be verified.
  • Close when the sales owner accepts the review or confirms the unresolved finding, approved CRM updates are verified by read-back or explicitly deferred or withdrawn by the sales owner with an assigned owner, and all accepted actions have assigned owners. The opportunity remains closed-lost.

Where your team decides

  • The rep clarifies missing deal context
  • The sales owner decides findings, exact CRM corrections and action ownership

Example systems

Configure connections and permitted actions during setup.

  • HubSpot
  • Gmail
  • Google Drive

Checks to adapt

Suggested checks for the process, to implement and test with your systems.

  • Deal chronology

    Reconstruct the buying timeline from the opportunity record, buyer communications, and proposals.

  • Loss-reason evidence

    Compare CRM loss codes with buyer statements and flag unresolved contradictions.

  • Review and corrections

    Record owner findings, execute approved CRM updates with read-back verification, and document deferred changes and retained uncertainties.

  • Recurring loss patterns

    Compare reviewed deals with source links and counts before calling an issue a trend.

Process stages

Adapt closed-lost audit with your team

Sign up