Sales · Process breakdown

How should we run a win loss analysis?

A practical, evidence-aware process for running win loss analysis that combines deterministic automation, bounded AI help and necessary human review.

5 stepsTypical mix: AI + humanIllustrative analysisUpdated

Win loss analysis is the systematic review of why deals are won or lost. This guide explains which parts can be deterministic automation, which are bounded AI assistance, what needs human review and what should stay human. It includes prerequisites, controls, failure modes and a small pilot you can run in a sales or product team.

What each step needs

01 Human review

Define goals, scope and core questions

Decide which decision you want to influence: pricing, messaging, product fit or competitor play. Specify target segments, time window and sample size for interviews and record-keeping before any automation.

Set goals, segments, timeframe and minimum interview count before starting.
02 Standard automation

Collect structured deal data and recordings

Use deterministic automation to pull CRM fields, opportunity stages, product SKUs and call recordings into a central store. Ensure timestamps, participant lists and consent flags are captured to allow reproducible analysis.

Ensure CRM and call systems export standard fields and consent metadata.
03 AI candidate

Use bounded AI to summarise and code themes

Apply controlled AI models to transcribe calls, extract candidate themes and draft summaries. Keep prompts and model versions recorded. Treat AI outputs as hypotheses, not final findings, requiring validation.

Run AI summarisation against a labelled sample to validate theme extraction accuracy.
04 Human review

Human review, synthesis and interpretation

Experienced human analysts validate AI themes, interview transcripts and context. Humans reconcile conflicting evidence, interpret buyer intent and map findings to strategic actions like product fixes or sales coaching.

Assign experienced analysts to validate AI outputs and reconcile data conflicts.
05 Keep human

Operationalise findings and close the loop

Translate validated insights into specific actions: update playbooks, adjust pricing tests, change demo scripts and schedule follow ups. Maintain versioned records so future analyses can measure effect.

Create tracked action items with owners, deadlines and measurable outcomes.

A sensible first experiment

Run a small pilot with 8 to 12 deals from one sales team. Automate CRM export and call transcription, then pass outputs through a bounded AI model to extract themes. Have two human reviewers independently validate AI themes and meet to reconcile differences. Record time per deal, disagreements and the actions proposed.

The trap to avoid

Over-relying on AI summaries without human validation risks amplifying transcription errors, misattributed quotes and biased theme selection. Also avoid using an unversioned model in production. Failure modes include incorrect attribution, missed competitor signals and privacy breaches if consent is not tracked.

Questions teams ask

Which parts are best left to humans?

Interpretation, interviewing, stakeholder synthesis and sensitive judgement calls should stay human. Humans spot context, read tone and resolve conflicting evidence. Keep humans accountable for final recommendations and for mapping insights to strategic changes.

What should we automate first?

Automate deterministic plumbing: CRM exports, metadata capture, audio transcription and secure storage. Those tasks reduce manual work and create a reliable dataset for AI and human analysts to work from.

How do we control AI outputs?

Use versioned prompts and models, validate on a labelled sample, record confidence levels, and require human sign-off on themes. Maintain an audit trail with timestamps, model metadata and reviewer notes.

How big should the sample be for reliable insights?

Start with a focused sample tied to a clear segment or hypothesis, such as 8 to 12 deals for a pilot. Expand sample size based on variance in responses and available review capacity, and validate themes as you scale.

Illustrative workflow guidance by Arcgent. Each business needs its own assessment. No integration or savings claim has been verified for your systems.

Now, what about your process?

Get an assessment based on your own steps, systems, and constraints.

Audit my process See an example report ↗