--- title: Stop Pitching Win/Loss. Start Pitching The Answer. canonical: "https://winlossresearch.com/perspectives/executive-buy-in-win-loss-research/" pubDate: "2026-07-06T00:00:00.000Z" author: Daniel Oxenburgh description: A general case for win/loss research gets nodded through and never scheduled. A pitch built around a felt problem gets a budget the same quarter. --- # Stop Pitching Win/Loss. Start Pitching The Answer. "We should really be doing win/loss research." That sentence gets nodded along in almost every leadership meeting where it comes up, and then nothing happens for two quarters. The pitch has no forcing function attached to it, no specific question anyone in the room needs answered by a specific date, so it sits on a list next to a dozen other good ideas competing for the same budget - and it has nothing to do with executive skepticism about the value of win/loss. A general pitch describes a discipline. It doesn't describe a decision anyone is waiting to make, and leadership funds decisions faster than it funds disciplines. I've watched this play out the same way across enough client conversations that the pattern is worth naming plainly. A program pitched as "let's understand our win rate better" sits for a year, gets referenced occasionally in a planning deck, and never gets a start date. A program pitched around a win rate that just dropped ten points in Enterprise, or a sudden spike in losses on deals that included a trial, gets a budget and a timeline inside the same quarter it was raised. Same discipline, same methodology, same eventual value. Completely different fate. Programs get funded when they answer a problem someone can already feel. That's the whole mechanism, and it's simpler than most people building an internal case expect. Leadership doesn't need convincing that buyer research is valuable in the abstract. Nearly everyone in the room already agrees with that in principle, which is exactly why the general version of the pitch gets a nod and no budget. What most pitches are missing is urgency tied to something already happening, not urgency the pitch is trying to manufacture on its own. A metric moved somewhere nobody can fully explain, and the room already knows it, wants an answer, and would rather get one this quarter than sponsor a general audit of deal history with no deadline attached. This changes what the internal case for win/loss should actually sound like. Pitching "we should have a win/loss program" asks leadership to fund a capability. Pitching "win rate in Enterprise dropped ten points and we don't know why" asks leadership to fund an answer to a question they're already carrying into every pipeline review. Only one of those gets approved with a start date attached, and it's rarely the one that sounds more strategic on a slide. Here's the part most people building the internal case get backward. The broader value of a win/loss program, the finding nobody thought to ask for, the pattern that reframes a strategy nobody had questioned, still shows up once the program is running. That value was never the reason it got funded, and pitching it as the reason is exactly why so many good win/loss ideas sit unscheduled for a year waiting for a champion. Leadership approves the specific question first. The broader value arrives afterward, as a byproduct of running the program, not as the ask that got it started. This has a direct implication for how you frame the request, and it's simpler than most people expect once they've seen the pattern. Find the metric that's already moved. A win rate that dropped in a specific segment, a sudden run of losses on a deal type that used to close reliably, a competitor that started showing up in evaluations where they never used to. Attach the win/loss program to that specific, already-felt discomfort, not to the general case for buyer research as a practice. Name the date leadership needs the answer by, not just the topic they'd like more visibility into over time. If you've pitched this before and it stalled, go back and check what you actually asked for. "We should do win/loss" and "win rate dropped ten points in Enterprise and we need to know why before next quarter's planning" are not the same request, even when both are asking to fund the identical program underneath. One is a discipline waiting for a champion to keep pushing it. The other is an answer leadership is already looking for, with your program positioned as the fastest way to get it. Pair the felt problem with a concrete shape for the answer, not just the question. Name the interview count you're targeting, the deal set you'll pull from, and the date leadership can expect findings. A leader who's already uncomfortable about a metric wants to know the discomfort has a resolution date attached, not just that someone agrees the discomfort is real. The specificity that makes the problem urgent should carry through into the specificity of what you're proposing to do about it. The next time you're building the case internally, don't lead with why win/loss research matters as a category. Lead with the number that's already making someone in the room uncomfortable, and let the program be the way you answer it. ## Related - [How to Build a Win/Loss Research Program](/topics/how-to-build-win-loss-program/) - [How do you get executive buy-in for win/loss research?](/faq/how-do-you-get-executive-buy-in-for-win-loss-research/) - [What does a win/loss program include?](/faq/what-does-win-loss-program-include/) - [Win/loss program](/glossary/win-loss-program/)