Win/Loss Findings

Win/loss findings are the conclusions a research program produces after buyer interviews are conducted, coded, and analyzed for pattern. A finding is a claim that holds across enough independent buyer conversations to be treated as a signal, backed by the interview volume needed to distinguish pattern from anecdote, rather than a single quote or one interview’s opinion.

That distinction matters more than most teams treat it. A CRM export of closed-lost reasons is not a set of findings, because it reflects what reps recorded, not what buyers experienced. A research report only becomes a set of findings once the raw material has been through analysis that separates recurring signal from one-off noise.

What Turns Raw Interview Data Into a Finding

A finding earns its status through repetition and specificity. If pricing surfaces as a factor in 14 of 20 loss interviews, in a specific deal size range, against a named competitor, that is a finding. If pricing comes up once, in one interview, without context on where else it appeared or didn’t, that is a data point, not a finding. Reducing findings to this level of specificity is what makes them defensible in a boardroom rather than dismissible as opinion.

Findings also carry a shelf life. Some hold their shape for years, such as how a buying committee structures its decision process. Others decay in months, such as how buyers perceive a specific competitor after that competitor ships a major update. Treating every finding as equally durable is a common failure mode, one covered in more depth under win/loss findings shelf life.

Findings Only Create Value When They Reach the Right Audience

A finding sitting in a report nobody reads outside the research team has produced nothing. GTM strategy runs on findings that reach the function that can act on them: messaging findings to product marketing, competitive findings to sales enablement, product feedback findings to the roadmap owner. This routing problem is distinct from the analysis problem, and it is covered under cross-functional distribution.

A Concrete Example

A SaaS company runs a research cycle expecting to confirm a pricing problem. The findings instead surface a pattern across a third of loss interviews: buyers cited a specific onboarding concern that never appeared in CRM notes, because reps had no reason to ask about it and buyers had no reason to volunteer it during an active sales process. That finding redirects a roadmap conversation that pricing data alone would never have triggered. The distinction between a finding and an anecdote is exactly what made the redirect defensible internally.

See Also