---
title: What should a win/loss research deliverable include?
canonical: "https://winlossresearch.com/faq/what-should-a-win-loss-research-deliverable-include/"
description: "A win/loss deliverable should include a synthesized executive report, supporting interview evidence, and a live readout, not a stack of raw summaries."
---

# What should a win/loss research deliverable include?

A win/loss research deliverable should include a synthesized executive report identifying patterns across interviews, an interview repository with transcripts or notes for reference, and a live executive readout translating findings into recommended actions. The report should focus on patterns and recommendations, not a stack of individual deal summaries left for the reader to connect.

Each of these three components does a different job, and a deliverable missing any one of them leaves a gap in how findings actually reach a decision.

## The Executive Research Report

The core deliverable is a structured report that identifies the key patterns across the interview set: the recurring reasons deals were won or lost, buyer perception trends, cross-functional implications, and recommended GTM actions. The report's job is to focus on revenue-impact insights rather than functioning as a raw data summary. A reader should come away from the report understanding what changed and what to do about it, not just what individual buyers said.

This is the point where deliverable quality diverges most between vendors. Some providers deliver a write-up per interview with no synthesis connecting them, leaving the client's team to notice the pattern themselves. A report that does the synthesis work, naming a specific pattern across a dozen or more interviews and tying it to a specific recommendation, is what separates research from documentation.

## The Interview Repository

Clients should have access to the underlying source material: transcripts, interview notes, recordings where permitted, and tagged summaries organized by theme. This repository exists to support the report's conclusions, not to substitute for them. A team that wants to verify a specific finding, or explore a theme in more depth than the executive report covers, should be able to go back to the source material directly.

## The Executive Readout

A live presentation, typically around 90 minutes, covering key findings, implications for GTM teams, and recommended actions belongs in every deliverable. This session should include leadership and the cross-functional stakeholders the findings touch, not just the team that commissioned the research. The readout is where findings get discussed, questioned, and turned into specific next steps, which a written report alone rarely accomplishes.

Following the readout, a strategy discussion helps translate findings into concrete next-quarter priorities: GTM decisions, product roadmap implications, messaging adjustments, and competitive positioning changes.

## What Distinguishes a Strong Deliverable From a Weak One

The clearest signal of deliverable quality is whether the report leads with synthesized findings or with raw material. A weak deliverable reads like a series of individual case files: informative on their own, but requiring the reader to do the pattern-matching work the research was commissioned to do in the first place. A strong deliverable states the pattern directly, supports it with representative evidence from multiple interviews, and pairs it with a specific recommendation. The difference comes down to whether the synthesis work has actually been done before the report reaches the reader, not how polished the writing is.

## How the Readout Should Function

A readout that only recaps the written report adds little beyond what a reader could get from the document alone. A readout that works uses the live session to translate each major finding into a specific, function-stated action before the meeting ends, so that finance, product marketing, and competitive intelligence each leave with something concrete rather than a shared document they interpret independently afterward.

## Related

- [How to Build a Win/Loss Research Program](/topics/how-to-build-win-loss-program/)
- [How do you evaluate a win/loss research vendor?](/faq/how-do-you-evaluate-a-win-loss-research-vendor/)
- [How much does win/loss research cost?](/faq/how-much-does-win-loss-research-cost/)
- [Win/loss report](/glossary/win-loss-report/)
- [Win/loss readout](/glossary/win-loss-readout/)