Your Pipeline Shows Where Deals Stall. Your Calls Show Why.
Deal stage data tells sales leaders where deals slow down, but the reason usually sits in the conversation, and fixing it takes specific coaching, not another dashboard.
The forecast call is nearly over when someone points at the screen. Proposal-to-close conversion has slipped again. The room goes quiet, then fills with theories of pricing, timing, and a competitor on the offensive. By the end of the meeting, a new report that slices the numbers by region, deal size, and rep is on the to-do list.
It's a familiar reflex, and it rarely pays off. A sharper report will describe the symptom with more precision and say nothing about the cause. Your pipeline has told you where it hurts. It hasn't told you why.
Stage data works like a smoke alarm. It's indispensable, and it wil tell you which room is burning, but it can't tell you what lit the fire. That answer lives in conversations, what the rep asked, what the buyer revealed, what got promised, and what got politely dodged. Without those, leaders fill the gap with conjecture. Maybe it's pricing. Maybe a competitor. Maybe the leads are weak. Sometimes the guess is right. More often it's a comfortable story that spares us the harder work of listening.
Listen where the deal leaks.
Start narrow. Pick the one stage that leaks most and listen to a handful of calls from just before and just after the stall. You don't need dozens. A few conversations, whether recorded, transcribed, or heard live, will usually reveal a pattern, and three tend to surface again and again.
Shallow discovery. Picture a rep who asks what the buyer needs, hears a tidy answer, and moves straight to the demo. Nothing about why now, what happens if the buyer does nothing, or who else will weigh in. The deal reaches a proposal looking healthy, with a friendly buyer and no urgency, and then it sits. Listen for questions that draw one-word answers, for how quickly the call pivots to the product, and for how little the buyer is talking.
Vague next steps. Many calls end the same way: "I will send over some information and let's circle back next week." It sounds fine. But there's no date, no named person and no reason for the next conversation. Listen to the final two minutes of your calls. When the ending is soft, the deal tends to go quiet right after it.
Sidestepped objections. A buyer says, "We are fairly happy with what we have," or "The timing's tricky right now." The rep replies, "Totally understand," and moves on. Reps do this to keep the mood pleasant. But the concern doesn't dissolve. It goes underground and resurfaces later as silence. Listen for the moment a buyer hesitates and notice what the rep does with it.
These patterns often track where the pipeline leaks. Trouble early on tends to point to discovery, a mid-funnel stall to unclear next steps, and a late collapse to objections that were never truly addressed. Treat that as a hypothesis to test, not a rule.
Turn one observation into one coaching task.
Take a look at where good intentions go astray. A manager listens to a call, notices six things, and shares all six. The rep leaves with a long list, retains none of it, and changes nothing.
Choose one. Identify the single habit that, if it shifted, would most change the outcome at that stage, and turn it into a task the rep can practice before the next call. The test is whether it's specific enough to see and hear. "Ask better questions" fails. "In your next three discovery calls, ask what happens if they do nothing, then stay quiet until they've finished answering" passes.
The same goes for the other two patterns. For vague endings, the task might be like this: before every call closes, agree on a date, a person, and a purpose for the next conversation. For dodged objections, it might happen when a buyer raises a concern, ask one question about it before you respond. Each task is small, and the rep can tell whether they did it.
Then add a short rehearsal. Five minutes of role play beats 20 minutes of advice, because the words get spoken aloud once before they matter. After the next call, review a short clip together and ask the rep what he noticed. People trust what they discover far more than what they're told.
Be patient with the numbers. A coaching change shows up in conversations first and in the stage data weeks later. Check the dashboard too early and you'll conclude nothing happened and abandon the habit just as it takes root. Use the pipeline report to confirm the change, not to drive it.
None of this requires a new platform. Recording and transcript tools can make listening easier, but they don't do the listening for you. What matters is a leader who sits down, hears what a buyer actually said, and has a calm, specific conversation with a rep about one thing to try next.
Dashboards will keep growing more detailed, and that's fine. Just remember what they're for. They tell you where to look. The conversation tells you what to change. And the quiet discipline of coaching one habit at a time is how a red number on a slide becomes a deal that moves.
Luke Alexander is founder and CEO of Kendo AI.