.svg)
I don't run pipeline reviews anymore.
It’s not that I'm more disciplined. It’s just that I know which deals need attention before I open my inbox or CRM.
Every morning, Chief shows me what's stalling, what needs follow-up, and what's at risk. If I were going to sit down for a pipeline review, I’d already know what to talk about. That would give ⅔ of the meeting and prep time back.
Now, I'll state the obvious: I'm running a small, founder-led motion. My situation is probably different from yours. However, I felt this same pain as the CEO of a growth-stage software company. It’s even worse when you have AEs, managers, a forecast to defend, and a board that wants answers.
But here’s the thing: having that visibility every day taught me something about what pipeline reviews actually are. It's not what most revenue teams think.
The Pipeline Review Is a Workaround
Think about what happens in a typical pipeline review. A manager sits down with their reps. The reps recap deal status. The manager asks what's moving, what's stuck, what the close date looks like. They assign action items. The meeting ends.
If your goal is gathering information, that’s great. If you want to close more deals, this kind of pipeline review doesn’t get you there.
Information gathering shouldn't require a recurring meeting to accomplish. Every revenue team needs a system that surfaces the right information before anyone sits down. The pipeline review meeting exists largely as a primitive version of that system. If you’re disciplined, it fills the gap. If.
Even then, your pipeline review call comes with a price tag. Most teams have never calculated it.
For a revenue org with 8 AEs, 2 managers, weekly 60-minute reviews, and 30 minutes of prep per attendee, that number comes out to roughly $67,000 per year. Just to figure out what's already in the CRM.
Reps already spend only 28–30% of their week on actual selling. The other 70% goes to manual admin work and internal meetings. Pipeline reviews are a recurring line item in that 70%. Every hour spent updating a manager on deal status is an hour not spent moving a deal forward.
What 70% of Your Pipeline Review Is Actually About
Here's the honest breakdown of what happens in most pipeline reviews:
Some of it is genuinely valuable. Coaching a rep through a stalled negotiation. Deciding whether to accelerate or kill a deal. Talking through a prospect's internal politics. That's the work that requires a human conversation.
But most of it (roughly 70%) is answering questions that should already have answers. What's the last activity on this deal? Has the rep followed up since the last meeting? Is this close date realistic? Which deals haven't moved in two weeks?
Those aren't judgment calls. They're data points. And data points shouldn't need a meeting to surface.
If 70% of your pipeline review content was knowable before anyone sat down, that $67,000 isn't giving you any ROI. All it does is tell you what's in your CRM (and give you a warm, fuzzy feeling that you did something about it).
What to Change
You don’t need to kill the pipeline review. Just shrink it.
The version of the meeting worth keeping looks like this: everyone already knows deal statuses going in, and the conversation centers on what to do about it. Coaching. Escalation. Strategy. Judgment calls that actually require a manager in the room.
For that version to exist, the information has to arrive before the meeting does. Deal risk surfaces automatically. Stalled deals get flagged the day they stall, not the Thursday after. Follow-up gaps show up in a rep's inbox, not their manager's weekly review.
It's a different kind of infrastructure than most revenue teams have built. But that’s what it takes to turn a pipeline review from a status update into an actual decision-making session.
The Audit to Run
Before your next pipeline review, try this.
Write down every question you're planning to ask. Every deal you're planning to check on. Every rep update you're expecting.
Then ask: do these answers already exist somewhere in your CRM or activity data right now?
Every “yes” is an information gap you’re filling with the pipeline review.
The goal is to eliminate those gaps outside of the meeting. When you get there, the pipeline review actually does what it’s supposed to do.
We’re building Chief to facilitate better pipeline reviews by surfacing the right information at the right time. Try Chief free today, connect your calendar, and see the impact it has on your meetings.
