Win/Loss Analysis: Why Your Roadmap Keeps Missing the Point

Where the insight goes to die

The friction isn't that sales isn't having the right conversations. They are. Your reps hear, every week, what's missing, what a competitor does better, what the buyer tried before reaching out to you.

The problem is what happens to that information. It lands in a CRM field called "loss reason" with four dropdown options that don't capture anything real. Or it gets discussed in a sales postmortem that no PM attends. Or it lives in an AE's head until they leave the company.

I've seen this pattern in almost every B2B SaaS team I've worked with. The sales org and the product org each operate with half the picture. Sales knows why buyers leave. Product knows what's been built. Nobody is connecting the two systematically.

The gap isn't effort. It's the absence of a process.

Why this data is categorically different from user feedback

Win/loss data captures something your user research and NPS scores cannot: why a buyer who evaluated your product chose to pay someone else instead.

Existing users tell you what they wish worked better. Lost buyers tell you what they needed and did not find. Those are different questions with different answers. A feature request from a loyal customer might be a nice-to-have. A pattern across 15 lost deals where buyers consistently cited the same missing capability is a competitive liability.

Melissa Perri puts it clearly in *Escaping the Build Trap*: "The biggest risk is building something nobody wants. Sales data from losses gets you closer to the real market signal than almost anything else." When a buyer has already gone through evaluation, compared you against alternatives, and made a decision, their reasoning is as close to revealed preference as product teams ever get.

Most PM teams treat this as sales intelligence. It is product intelligence. The distinction matters.

The three questions that actually matter

A win/loss interview is not a customer interview in disguise. You're not trying to understand the job-to-be-done or map an opportunity solution tree. You're trying to understand a decision that already happened.

That means three questions matter above everything else:

Why did you lose? Not the surface reason. What would the buyer have needed to see to say yes? "Pricing" is almost never the real answer. It's the easiest answer. Push past it.

What did the buyer try first? This tells you where you sit in their consideration set and who you're actually competing against. Sometimes it's not your obvious competitor. Sometimes it's a spreadsheet.

What would have changed their decision? This is where roadmap signal lives. A buyer who says "if you had X we would have signed" is giving you a prioritisation input that no amount of internal strategy discussion can match.

Teresa Torres writes in *Continuous Discovery Habits*: "Opportunity interviews are most valuable when they reveal the gap between what customers are trying to do and what currently exists to help them." Win/loss interviews reveal a specific version of that gap: the one that is costing you deals right now.

The minimal viable loop

You don't need a dedicated win/loss tool to make this work. You need a process that moves insight from a sales conversation to a PM's attention within 48 hours.

Here's what that looks like in practice. After a deal closes or is lost, the AE fills out four fields in a shared Notion doc or Slack form: why did the prospect decide, who else were they evaluating, what feature or capability came up most, and one direct quote from the buyer. That's it. No essay.

The PM reviews it within two days and tags it as competitive intel, roadmap input, or positioning feedback. Once a month, you review patterns across five or ten entries. That's your win/loss process.

The output is not a slide deck. It's a roadmap input, a pricing conversation, or a decision to kill a feature nobody outside your team actually cares about. If the analysis doesn't end in a product or positioning decision, it was a waste of everyone's time.

The defensibility argument

There's another reason to build this habit beyond better product decisions. The PM who can trace a shipped feature back to five lost deals has the most defensible prioritisation argument in any roadmap review.

When a stakeholder pushes back and asks why you prioritised this over that, "because we lost deals over it" is a different class of answer than "because usage data suggested demand" or "because a key customer asked for it." Revenue that didn't arrive is a concrete cost. It's hard to argue with.

My experience is that this also changes the conversation with sales. When reps see that the things they reported actually shaped what got built, they report more carefully. The signal improves because the loop is closed. Most sales teams I've worked with are generous with insight when they believe product is actually listening.

The uncomfortable part

Most PMs I've worked with are making feature, pricing, and packaging decisions on instinct and internal conviction. That's not a criticism. It's what happens when there's no systematic way to hear from buyers who left.

Win/loss data is the empirical foundation of competitive positioning. If you're not collecting it, someone else is, and they're using it to sharpen exactly the gaps that keep showing up in your CRM as "lost on pricing."

The buyers are telling you what to build. They're just telling it to your AEs.

Set up the Notion doc this week. Ask your sales lead to fill in the next three lost deals. Read what comes back and see if it matches your roadmap. It probably won't, and that's the point.