Your Sales Pipeline Review Shouldn't Be a Reporting Meeting
A coach who only reads the box score can tell you what happened. The coach who watches the film can tell you why it happened and what to change before the next game.
Let's be honest; a lot of sales pipeline reviews are box score readings. The numbers are already in the CRM, everyone knows it, and we still spend the hour reading them aloud. A sales pipeline review should be the film session, where we figure out what's really happening inside an opportunity and what to do about it.
There's a relationship between a sales leader and the sellers on the team that I think we sometimes make more complicated than it needs to be.
The seller is doing the work: gathering information, talking with prospects, and trying to understand what's happening inside an opportunity. The leader is trying to understand that work well enough to coach, allocate resources, forecast the business, and remove what's getting in the way.
The Mistake: Treating the Sales Pipeline Review Like a Status Report
Here's the mistake, stated plainly. The seller walks in and recites stage, amount, and close date, all of which already live in the CRM. The leader fires off questions to fill in whatever the CRM doesn't say.
That's not a working meeting. That's a reading of the box score.
I don't think it's laziness most of the time. It's a habit, and the cost is real: the hour is gone before anyone gets to the part that matters.
Why Reporting Meetings Fail
Reporting meetings fail because they make both people redo work that's already been done. The seller already put the information in the CRM. The leader should have reviewed it before the meeting. When neither happens, the leader has little choice but to ask what's going on, because nobody else can see what the seller knows.
That's why I think CRM discipline gets misunderstood. The purpose isn't a beautiful CRM, and it isn't even reporting. The information you capture is the foundation for better decisions. It lets a leader understand where deals really are, forecast with more confidence, put resources where they're needed, and recognize where a seller needs help.
When that information isn't there, the meeting turns into interrogation. Sellers feel grilled, leaders feel in the dark, and the coaching never starts.
What a Seller Brings to a Sales Pipeline Review
I wrote previously about building a Seller Hypothesis, where a salesperson develops an opinion about the signals they receive before and during the sales process. You look at what you know about the company, the people involved, what they're trying to accomplish, and the problems they may be trying to solve. Then you use your conversations with the prospect to test it.
The important part is that you're thinking. That same thinking should carry into the meeting with your leader. A seller should be able to walk in and cover four things:
What I know
What I believe, based on what I know
What I still need to learn
Where I need help
The last two are where the meeting gets valuable. Maybe you need an internal technical resource to help scope the opportunity. Maybe you're not getting access to the right people inside the customer's organization. Maybe discovery left gaps that make an accurate scope difficult. Or maybe the customer says they want to move forward, but their actions don't support that conclusion.
What a Leader Brings: Coaching, Not Interrogating
The leader's job starts before the meeting, by reviewing what's in the CRM. That frees the meeting to be about the hypothesis. A leader can challenge it, ask what evidence supports it, and recognize a step that's been skipped or a question that hasn't been answered. They can also bring in another resource or remove an internal roadblock that's slowing the deal down.
That's coaching.
The seller has a responsibility to do the work, capture what they're learning, and think critically about the opportunity. The leader has a responsibility to review that information, help the seller think better, and remove barriers. Neither person should make the other one do work that has already been done.
One more thing, and it's easy to underestimate. I'd take a steady weekly rhythm over an occasional deep dive every time. When sellers know the review is a working conversation and it happens consistently, they prepare differently. Consistency builds that trust faster than intensity does.
A Simple Cycle for a Better Sales Pipeline Review
If I were drawing this out, I'd put the customer in the center of the picture, with everything working outward from there. We gather information about their goals, challenges, decision process, and what has to happen for them to move forward.
We document what we learn because others in our organization may need it to help us. We build a scope because we need to connect what we can deliver to something the customer is trying to accomplish.
The CRM, the sales process, the Seller Hypothesis, the pipeline review, and the coaching all support that same work. Here's how the cycle runs:
The seller thinks more intentionally about the customer and gathers better information.
That information gets captured so it doesn't live only in the seller's head.
The leader uses it to coach instead of interrogate.
Better coaching helps the seller find gaps, challenge assumptions, and get resources where they're needed.
The seller goes back to the customer better prepared, and the cycle starts again.
How do you know it's working? Watch the clock. Think about your last sales pipeline review. How much of it went to gathering information your sellers should have already captured? How much went to telling you things you could have read beforehand?
The more of that hour you win back for challenging assumptions, helping sellers think through opportunities, and removing roadblocks, the healthier your review.
The Takeaway
None of this is especially easy work. It's thoughtful work, and in a complex sales environment, there's a lot of detail to manage. If you're selling something complex, you're not just saying, "Here's my widget. Would you like to buy my widget?" You're trying to understand how what you sell fits into someone's business and whether it can help them accomplish something that matters to them.
That takes judgment from the seller, discipline around the process, and good coaching from the leader.
So look at your next sales pipeline review through that lens and make it a working meeting rather than a reporting meeting.
If you have a seller who's still learning how to prepare for these conversations, forward this post to them along with my series on building a Seller Hypothesis. Ask them to come in ready to talk about what they know, what they believe, and where they need help.
Want help making that shift on your team? Let’s talk. And for sellers who want another place to work through their deals and test their assumptions, that's part of why we created B2B Sales Lab.
