--- title: One Team Got a Briefing. The Rest Kept Guessing canonical: "https://winlossresearch.com/perspectives/win-loss-findings-cross-functional/" pubDate: "2026-07-02T00:00:00.000Z" author: Daniel Oxenburgh description: "Win/loss programs built for sales enablement leave marketing, product, and CS working from theories, not the same buyer evidence sales gets." --- # One Team Got a Briefing. The Rest Kept Guessing Your sales team got a briefing. Everyone else kept guessing. Most win/loss programs get positioned as sales enablement from the moment they're scoped. The interviews happen, the findings get analyzed, and the output lands as competitive intel, objection handling, and rep coaching notes. Sales gets a briefing. The battlecard gets updated. The next enablement session references the research by name. Those outputs have real value. They also represent a fraction of what a full set of independent buyer interviews actually contains, and routing findings exclusively through the sales org is how most of that remaining value gets left behind, not through a deliberate decision to withhold it, but through the default path a sales-scoped program takes. Picture a mid-market SaaS company running its first formal win/loss cycle. The mandate comes from the VP of Sales, the interview guide gets built around competitive positioning and objection patterns, and the readout gets delivered to the sales org as a battlecard refresh. It's a good battlecard. Reps use it. Win rate against the named competitor improves modestly the following quarter. Nobody outside sales ever sees the same interviews. Buried in that same interview set, unrouted anywhere, is a recurring theme: buyers describing confusion about implementation timeline during the evaluation, a detail with zero relevance to objection handling and direct relevance to product and customer success. It never reaches either function, because the program was scoped and delivered as a sales tool from the start. Six months later, the same onboarding confusion shows up again, in the next cohort of closed deals, as though it were new information. It isn't. It was already sitting in a transcript nobody outside sales ever read. What lives inside a full set of independent interviews goes well beyond competitive positioning. Marketing needs to hear how buyers felt about your company and product before the evaluation started, what shifted their perception during it, and what they were left thinking once the decision was made. That's where your messaging either builds momentum or loses it, and it's a different signal than anything a battlecard captures. Product needs to hear about the evaluation step where confidence in the roadmap broke down, or the moment an integration story stopped holding up under scrutiny. CS needs to hear what post-sale expectations were set during the evaluation that nobody corrected before the deal closed, because those unaddressed expectations are the ones most likely to show up again at renewal. Each of those functions needs to interrogate the same research base, not a summary of it, because the signal looks different depending on who's asking. A finding that reads as a competitive loss to your sales team can read as a positioning gap to product marketing and a churn risk to CS, all from the same handful of interviews. Compressing that into one battlecard-shaped output means every function except sales works from theory instead of evidence, on exactly the questions independent buyer interviews were built to answer. This is where the competitive intelligence angle usually gets underweighted rather than ignored. A battlecard built from a sales-scoped program tends to capture what buyers said in the room during the deal cycle, the objections raised, the feature comparisons requested. It rarely captures what the buyer decided after your team left the call, or the internal conversation among stakeholders your reps never sat in on. That distinction is the same one that separates a rep debrief from a genuine win/loss interview, and it applies just as much to the CI function consuming the findings as it does to sales. A battlecard optimized purely for what reps heard is optimized for half the picture, even before the question of who else in the organization should see the research ever comes up. Someone has to own making distribution happen, because it doesn't happen on its own. That's usually the CMO, since the mandate and the cross-functional sight lines to route findings deliberately across sales, marketing, product, and CS typically sit there. Without an active owner, the default outcome is findings that reach whichever function commissioned the research and stop. That ownership gap is usually a scoping problem, not a resourcing one, decided the moment a program gets framed as sales enablement rather than a shared GTM asset. Two companies can run the same volume of interviews, staffed by the same research quality, and produce entirely different value depending on whether the initial scoping conversation included marketing, product, and CS as stakeholders or treated them as an afterthought once the battlecard was already shipped. The interviews don't know the difference. The distribution plan does. The same discipline that makes a finding useful for a battlecard is what makes it useful everywhere else. A buyer's account of why a competitor won is not just competitive intelligence. It's a data point about what your messaging failed to communicate, what your roadmap failed to deliver against, and what your onboarding process failed to set up correctly, all captured in the same conversation your sales team is currently treating as theirs alone. Your buyers told an independent researcher what they actually thought about your organization. Make sure your organization gets to hear it, not just the part of it holding the sales enablement budget. ## Related - [Win/Loss Research for GTM Strategy](/topics/win-loss-gtm-strategy/) - [Win/Loss Research for Competitive Intelligence](/topics/win-loss-competitive-intelligence/) - [How do you distribute win/loss findings across functions?](/faq/how-do-you-distribute-win-loss-findings-across-functions/) - [How do win/loss interviews improve battlecards?](/faq/how-do-win-loss-interviews-improve-battlecards/) - [Cross-functional distribution](/glossary/cross-functional-distribution/)