↳ Example report · synthetic data
§ Example · 01

You are reviewing a closed-lost sales quarter.

One prompt, run across 366 calls from 212 closed-lost mid-market deals. This is the real shape of a Discera report — executive summary, metrics, every deal examined, and what to do next. The data is synthetic; five deals are expanded in full below.

§ The brief

What was asked.

The same brief was applied to every closed-lost deal in the window. The output below is what the model returned per call, aggregated into the executive summary and metrics at the top.

Analysis instructions

“You are reviewing a closed-lost sales call. From the transcript and HubSpot context, extract the single most decisive reason this deal was lost, whether the economic buyer was ever engaged, the objections raised and how the rep handled each (with who said what), one thing the rep could have done differently, and whether the loss was about price, fit, timing, or process.”

§ Executive summary

The pattern across 212 deals.

Losses didn’t cluster on price. They clustered on who was in the room and how late the hard part surfaced. The three findings below cover 4 in 5 lost deals.

  1. Finding 01high

    The economic buyer never entered the room

    58% of lost deals ran their entire cycle on a champion who couldn’t sign. The person who controlled budget was absent from every call after discovery — reps were selling to the user, not the buyer.

    Share of losses58%
  2. Finding 02high

    ROI stayed qualitative past the proposal

    44% of lost deals reached pricing with no quantified business case in front of the buyer. Reps led with features and met price with a discount — three times in five, a discount was the first response to a pricing objection.

    Share of losses44%
  3. Finding 03medium

    Security and procurement surfaced too late

    29% of lost deals hit InfoSec, SOC 2, or legal review after week 3 with no path pre-wired. Where the approval chain wasn’t mapped early, the deal stalled in review and slipped the quarter.

    Share of losses29%
§ Signal at a glance

Four numbers that moved.

Avg. lost-deal size$71.4K18% below the won cohort
No economic buyer on call58%11 pts vs. prior window
Median days before slip34 daysstalled in one stage
Discount as first price reply61%3 in 5 pricing objections
§ Per-deal findings

Every call, examined.

  1. 01

    Meridian Freight Co.

    Feb 4, 2026

    Industry
    Logistics
    Amount
    $84,000
    Stage
    Closed Lost
    Expand ↓
    Stated reason

    Price too high vs. budget

    Underlying reason

    The champion never confirmed budget authority. The ROI conversation was deferred to a week-4 procurement review that no economic buyer attended.

    What could have changed it

    Quantify the cost of inaction in week 2, not week 4, and secure the budget owner on a call before proposal. Most likely shift: procurement accepts a phased rollout.

    Objections raised
    • Prospect

      “The annual is more than double what we set aside for this quarter.”

      Reframed by offering a 12% discount — no value anchor.

    • Prospect

      “I can champion it, but Finance owns the number.”

      Rep noted it but never requested a call with Finance.

    Deal health
    • Economic buyer engagedNo
    • Business case quantified·Partial
    • Approval path mappedNo
  2. 02

    Cedar Grove Health

    Feb 9, 2026

    Industry
    Healthcare
    Amount
    $142,500
    Stage
    Closed Lost
    Expand ↓
    Stated reason

    Went with an alternative

    Underlying reason

    A lower-priced alternative closed faster on integration depth. The rep changed the subject rather than addressing the gap head-on.

    What could have changed it

    Position honestly on the integration gap with a concrete workaround timeline. A deal-killer was treated as background noise.

    Competitive signal

    Buyer was mid-evaluation with a lower-priced alternative. No competitor was named on the page — Discera flags the pattern, not the vendor.

    Objections raised
    • Prospect

      “The other option syncs both ways out of the box — yours needs a middle layer.”

      Pivoted to the roadmap. The buyer didn’t re-engage.

    • Our rep

      “Let’s not open the integration question, just talk value.”

      Rep steered away from the objection that ultimately decided it.

    Deal health
    • Economic buyer engagedYes
    • Business case quantifiedYes
    • Approval path mappedYes
  3. 03

    Atlas Precision

    Feb 14, 2026

    Industry
    Manufacturing
    Amount
    $32,000
    Stage
    Closed Lost
    Expand ↓
    Stated reason

    Not a priority this quarter

    Underlying reason

    Discovery surfaced a problem the buyer didn’t actually feel. The project sponsor moved roles internally between calls, and no one re-qualified the pain.

    What could have changed it

    Pressure-test the priority with a quantified pain question on call 1. Likely outcome: disqualified before week 3, freeing rep capacity for live deals.

    Objections raised
    • Prospect

      “We might revisit in Q3 once the new VP of Ops is in seat.”

      Accepted the deferral; no commitment to re-engage.

    Deal health
    • Economic buyer engaged·Partial
    • Business case quantifiedNo
    • Approval path mappedNo
  4. 04

    Brightwave Systems

    Feb 18, 2026

    Industry
    Industrial Software
    Amount
    $56,000
    Stage
    Closed Lost
    Expand ↓
    Stated reason

    Internal stakeholder pushback

    Underlying reason

    Security review surfaced only after the third call. There was no early IT-engagement plan, and the security pack arrived nine days after it was requested.

    What could have changed it

    Pre-empt the security review on call 2. In this segment, most lost deals die between weeks 4 and 6 in security limbo.

    Objections raised
    • Prospect

      “InfoSec needs a SOC 2 letter and sign-off before this moves an inch.”

      Promised a follow-up; the pack arrived 9 days later.

    • Our rep

      “I’ll chase the security doc after the demo, it’s probably fine.”

      The delay let a competing priority overtake the deal.

    Deal health
    • Economic buyer engagedYes
    • Business case quantified·Partial
    • Approval path mappedNo
  5. 05

    Rowan Financial

    Feb 22, 2026

    Industry
    Financial Services
    Amount
    $96,200
    Stage
    Closed Lost
    Expand ↓
    Stated reason

    Procurement timeline outpaced budget cycle

    Underlying reason

    The buyer was running a parallel evaluation the rep didn’t learn about until week 5 — far too late to shift from informer to displacer.

    What could have changed it

    Ask a competitive-evaluation question on every discovery call. A two-week-earlier signal changes the posture from informer to displacer.

    Competitive signal

    A parallel evaluation ran unseen for weeks. Discera surfaced the signal from the transcript — no vendor named.

    Objections raised
    • Prospect

      “We’re weighing three options and briefing the EVP next month.”

      Treated as a status update; no displacement strategy.

    Deal health
    • Economic buyer engagedYes
    • Business case quantifiedYes
    • Approval path mapped·Partial
§ Recommendations

What to do Monday.

Ranked by expected impact, each with an owner. This is the part a folder of transcripts can’t give you.

  1. P0Sales leadership

    Gate stage-3 progression on a named economic buyer attending a live call.

    Would have flagged 123 of 212 deals for intervention before a proposal ever went out.

  2. P1Enablement

    Ship a one-page ROI worksheet reps complete before any pricing is sent.

    Targets the 44% of losses where price was met with a discount instead of a value frame.

  3. P1Sales

    Introduce the security and procurement path on call 2, not week 3.

    Addresses the 29% of deals that stalled and died in review limbo.

  4. P2RevOps

    Add a competitive-evaluation question to every discovery script.

    Surfaces parallel evaluations two weeks earlier — enough time to change posture.

Data caveats
  • Scope: closed-lost deals with at least one Gong-recorded call inside the window.
  • Deal amounts reflect HubSpot values at close; 14 deals had no amount recorded and are excluded from size metrics.
  • Prospect vs. internal speaker attribution is inferred from Gong participant metadata.
§ Run your own

Read the same shape on your pipeline.

Connect Gong, pick the segment, run the same brief. Most first reports finish in under five minutes.

No credit card required for the 30-day trial · Most first reports back before the next stand-up

↳ discera · example report · synthetic datav1.1 · 2026.07