Your Sales Team Isn't the Problem. Your Discovery Process Is.

I have sat in enough post-mortems to know the shape of what usually follows. Leadership assumes the team isn't working hard enough, or isn't closing well enough, and the intervention is a new methodology, a new tool, or a new head of sales. None of it addresses what's actually broken.

What's broken is the first thirty minutes of the first meeting.

What most discovery conversations actually uncover

The standard IT sales discovery framework teaches reps to qualify on three things: budget, timeline, and technical fit. These are logical. They are also the three questions a buyer can answer without any real commitment to move forward. A prospect with no budget, no mandate, and no urgency can still tell you they have budget, are evaluating in Q3, and that your solution looks like a good fit. They're not lying. They're being polite.

The result is a pipeline full of technically qualified, politically uncommitted opportunities. They don't progress, they don't die — they hibernate. They sit at 60 or 70 percent probability while the rep keeps calling them warm and the CRM keeps counting them as active. The quarter-end forecast looks reasonable until it doesn't.

The question that actually predicts deal velocity

In twelve years of working with IT sales teams, the qualification question that most reliably separates real opportunities from courtesy meetings is this: who in the client organisation is losing something if this decision doesn't get made?

Not "who wants it" — lots of people want things that never happen. Not "who has budget" — budget exists until it doesn't. But who is accountable for an outcome that depends on this decision being made? That person is the real sponsor. They have internal urgency, not just interest. Deals with a real internal sponsor move. Deals without one age.

This question is harder to ask than "what's your budget?" It requires a degree of directness that many reps have been trained out of. It sometimes ends a conversation that would have wasted three months. That is a feature, not a bug.

The cost of not asking it

In the collaborations I've been part of that successfully compressed deal cycles, the mechanism was consistent. Not a new methodology or a new tool. The team agreed on a clear definition of a real opportunity — not budget and title, but a named internal problem owner — and became disciplined about removing everything from the pipeline that didn't have one.

The pipeline got smaller. The win rate went up. The forecast became something the CRO could defend without caveats.

The discovery conversation doesn't need to be longer or more complex. It needs one better question near the front.