
Adam Foster
Fractional RevOps
ESSAY
How to Run a Sales Pipeline Meeting That Fixes Your CRM
How to Run a Sales Pipeline Meeting That Fixes Your CRM
How to Run a Sales Pipeline Meeting That Fixes Your CRM
5 min
When a sales leader asks me to sort out their CRM, I ask to sit in on their pipeline meeting first. It tells me more than the system ever will.
When a sales leader asks me to sort out their CRM, I ask to sit in on their pipeline meeting first. It tells me more than the system ever will.
“If the weekly meeting accepts a vague update, that's the standard of data you'll get in the system.”
When someone asks me to sort out their CRM, the first thing I ask for isn’t a login. It’s an invite to the next pipeline meeting.
An hour in that meeting tells me most of what I need to know. Which questions does the sales leader ask? Which ones do the reps dodge? Is the conversation about what the buyer is doing, or about how busy everyone has been? Does anyone look at the screen, or is the real forecast in someone’s head?
The pipeline meeting sets the standard for your CRM data
A CRM reflects the conversations you have about deals. If the weekly meeting accepts “it’s going well, they’re keen” as an update, then that’s the standard of data you’ll get in the system. No field or validation rule will fix it, because the team has already learned what’s good enough.
The reverse is also true. If the sales leader asks the same questions about every deal, and expects to see the answers in the CRM before the meeting, the data improves within a few weeks. Reps will do the admin if it saves them a harder conversation on Monday.
This is why so many CRM projects disappoint. The system gets rebuilt, the fields get tidied, and six months later the data is just as patchy, because the meeting that decides what “good” looks like never changed.
What a good pipeline meeting looks like
The best pipeline meetings I’ve sat in share a few habits:
They’re short. Forty-five minutes for a team of up to eight reps is plenty. If it runs longer, the meeting is doing work that should happen elsewhere.
They don’t review every deal. They focus on what has changed, what is stuck and what is closing this month or quarter.
They run off the CRM. One report on the screen, the same report every week. Nobody brings their own spreadsheet.
They end with actions. Each deal discussed leaves with a named owner and a dated next step.
Who should attend, and how often
Weekly is right for most B2B sales teams. Fortnightly lets too much drift between meetings, and daily turns into status reporting. Pick a fixed slot early in the week so there’s time to act on what comes out of it.
The sales leader runs it, and every rep with an open pipeline attends. It’s worth inviting marketing once a month, so they hear first-hand which leads are turning into real deals and which aren’t. That one conversation often does more for sales and marketing alignment than any shared dashboard.
Keep the forecast call and the pipeline meeting separate if you can. The forecast call is about what will close and when. The pipeline meeting is about moving deals forward. When they’re combined, the forecast takes over and the coaching gets squeezed out.
Prepare before the meeting, not during it
The single biggest improvement most teams can make is to set a clear expectation: the CRM is updated by the end of the previous working day. Every deal has a current stage, a close date the rep believes in and a dated next step. The sales leader looks at the report beforehand and picks the deals worth discussing. The meeting then becomes a conversation about the deals that need help, rather than a data entry session.
Deal review questions that do most of the work
I’ve seen plenty of deal review frameworks, and most are too long to use every week. These cover most of what matters:
What did the buyer do since last week? Not what we did. What they did.
What has to happen next, and when? A dated next step, agreed with the buyer.
What could stop this closing? If the answer is “nothing”, the rep hasn’t looked hard enough.
Once those questions are routine, the CRM build is straightforward. Each one becomes a field or a view, and the meeting runs off a single report instead of going round the table.
Run the meeting from one CRM report
The report that runs the meeting should answer the sales leader’s questions before they’re asked. In most cases that means showing:
Deals that changed stage since last week, in either direction.
Deals where the close date has been pushed back.
Deals with no next step, or a next step that’s overdue.
Deals with no activity in the last two weeks.
Everything forecast to close this month, with its amount and stage.
When the report is built like this, the meeting naturally focuses on exceptions. Healthy deals don’t need airtime. The ones that have slipped or stalled get the attention, which is where a sales leader’s time actually changes outcomes.
Common pipeline meeting mistakes
A few patterns come up again and again:
Going round the table. Each rep talks through their whole pipeline. It’s slow, it rewards whoever talks most confidently, and it tells the leader very little.
Updating the CRM in the meeting. If the sales leader is typing while reps talk, the team has learned that the meeting is where data gets entered. It should be entered before.
Arguing about probability. If the meeting debates whether a deal is 40% or 60%, the stages aren’t defined clearly enough. Fix the stages and the debate goes away.
No follow-through. Actions agreed one week and never mentioned again teach the team that the meeting doesn’t matter.
Build the system around the meeting
This is the order I work in. Agree how the meeting should run. Decide what the sales leader needs in front of them to run it. Then build the CRM so that information is there, up to date, without anyone chasing.
Done the other way round, you get a beautifully configured system that nobody opens on a Monday morning.
If your pipeline meeting regularly overruns, or ends without anyone being clearer on the forecast, start there. The CRM work will follow, and it’ll be a lot smaller than you expected.

Adam Foster
Fractional RevOps
ESSAY
How to Run a Sales Pipeline Meeting That Fixes Your CRM
How to Run a Sales Pipeline Meeting That Fixes Your CRM
How to Run a Sales Pipeline Meeting That Fixes Your CRM
5 min
When a sales leader asks me to sort out their CRM, I ask to sit in on their pipeline meeting first. It tells me more than the system ever will.
When a sales leader asks me to sort out their CRM, I ask to sit in on their pipeline meeting first. It tells me more than the system ever will.
“If the weekly meeting accepts a vague update, that's the standard of data you'll get in the system.”
When someone asks me to sort out their CRM, the first thing I ask for isn’t a login. It’s an invite to the next pipeline meeting.
An hour in that meeting tells me most of what I need to know. Which questions does the sales leader ask? Which ones do the reps dodge? Is the conversation about what the buyer is doing, or about how busy everyone has been? Does anyone look at the screen, or is the real forecast in someone’s head?
The pipeline meeting sets the standard for your CRM data
A CRM reflects the conversations you have about deals. If the weekly meeting accepts “it’s going well, they’re keen” as an update, then that’s the standard of data you’ll get in the system. No field or validation rule will fix it, because the team has already learned what’s good enough.
The reverse is also true. If the sales leader asks the same questions about every deal, and expects to see the answers in the CRM before the meeting, the data improves within a few weeks. Reps will do the admin if it saves them a harder conversation on Monday.
This is why so many CRM projects disappoint. The system gets rebuilt, the fields get tidied, and six months later the data is just as patchy, because the meeting that decides what “good” looks like never changed.
What a good pipeline meeting looks like
The best pipeline meetings I’ve sat in share a few habits:
They’re short. Forty-five minutes for a team of up to eight reps is plenty. If it runs longer, the meeting is doing work that should happen elsewhere.
They don’t review every deal. They focus on what has changed, what is stuck and what is closing this month or quarter.
They run off the CRM. One report on the screen, the same report every week. Nobody brings their own spreadsheet.
They end with actions. Each deal discussed leaves with a named owner and a dated next step.
Who should attend, and how often
Weekly is right for most B2B sales teams. Fortnightly lets too much drift between meetings, and daily turns into status reporting. Pick a fixed slot early in the week so there’s time to act on what comes out of it.
The sales leader runs it, and every rep with an open pipeline attends. It’s worth inviting marketing once a month, so they hear first-hand which leads are turning into real deals and which aren’t. That one conversation often does more for sales and marketing alignment than any shared dashboard.
Keep the forecast call and the pipeline meeting separate if you can. The forecast call is about what will close and when. The pipeline meeting is about moving deals forward. When they’re combined, the forecast takes over and the coaching gets squeezed out.
Prepare before the meeting, not during it
The single biggest improvement most teams can make is to set a clear expectation: the CRM is updated by the end of the previous working day. Every deal has a current stage, a close date the rep believes in and a dated next step. The sales leader looks at the report beforehand and picks the deals worth discussing. The meeting then becomes a conversation about the deals that need help, rather than a data entry session.
Deal review questions that do most of the work
I’ve seen plenty of deal review frameworks, and most are too long to use every week. These cover most of what matters:
What did the buyer do since last week? Not what we did. What they did.
What has to happen next, and when? A dated next step, agreed with the buyer.
What could stop this closing? If the answer is “nothing”, the rep hasn’t looked hard enough.
Once those questions are routine, the CRM build is straightforward. Each one becomes a field or a view, and the meeting runs off a single report instead of going round the table.
Run the meeting from one CRM report
The report that runs the meeting should answer the sales leader’s questions before they’re asked. In most cases that means showing:
Deals that changed stage since last week, in either direction.
Deals where the close date has been pushed back.
Deals with no next step, or a next step that’s overdue.
Deals with no activity in the last two weeks.
Everything forecast to close this month, with its amount and stage.
When the report is built like this, the meeting naturally focuses on exceptions. Healthy deals don’t need airtime. The ones that have slipped or stalled get the attention, which is where a sales leader’s time actually changes outcomes.
Common pipeline meeting mistakes
A few patterns come up again and again:
Going round the table. Each rep talks through their whole pipeline. It’s slow, it rewards whoever talks most confidently, and it tells the leader very little.
Updating the CRM in the meeting. If the sales leader is typing while reps talk, the team has learned that the meeting is where data gets entered. It should be entered before.
Arguing about probability. If the meeting debates whether a deal is 40% or 60%, the stages aren’t defined clearly enough. Fix the stages and the debate goes away.
No follow-through. Actions agreed one week and never mentioned again teach the team that the meeting doesn’t matter.
Build the system around the meeting
This is the order I work in. Agree how the meeting should run. Decide what the sales leader needs in front of them to run it. Then build the CRM so that information is there, up to date, without anyone chasing.
Done the other way round, you get a beautifully configured system that nobody opens on a Monday morning.
If your pipeline meeting regularly overruns, or ends without anyone being clearer on the forecast, start there. The CRM work will follow, and it’ll be a lot smaller than you expected.

Adam Foster
Fractional RevOps
ESSAY
How to Run a Sales Pipeline Meeting That Fixes Your CRM
How to Run a Sales Pipeline Meeting That Fixes Your CRM
How to Run a Sales Pipeline Meeting That Fixes Your CRM
5 min
When a sales leader asks me to sort out their CRM, I ask to sit in on their pipeline meeting first. It tells me more than the system ever will.
When a sales leader asks me to sort out their CRM, I ask to sit in on their pipeline meeting first. It tells me more than the system ever will.
“If the weekly meeting accepts a vague update, that's the standard of data you'll get in the system.”
When someone asks me to sort out their CRM, the first thing I ask for isn’t a login. It’s an invite to the next pipeline meeting.
An hour in that meeting tells me most of what I need to know. Which questions does the sales leader ask? Which ones do the reps dodge? Is the conversation about what the buyer is doing, or about how busy everyone has been? Does anyone look at the screen, or is the real forecast in someone’s head?
The pipeline meeting sets the standard for your CRM data
A CRM reflects the conversations you have about deals. If the weekly meeting accepts “it’s going well, they’re keen” as an update, then that’s the standard of data you’ll get in the system. No field or validation rule will fix it, because the team has already learned what’s good enough.
The reverse is also true. If the sales leader asks the same questions about every deal, and expects to see the answers in the CRM before the meeting, the data improves within a few weeks. Reps will do the admin if it saves them a harder conversation on Monday.
This is why so many CRM projects disappoint. The system gets rebuilt, the fields get tidied, and six months later the data is just as patchy, because the meeting that decides what “good” looks like never changed.
What a good pipeline meeting looks like
The best pipeline meetings I’ve sat in share a few habits:
They’re short. Forty-five minutes for a team of up to eight reps is plenty. If it runs longer, the meeting is doing work that should happen elsewhere.
They don’t review every deal. They focus on what has changed, what is stuck and what is closing this month or quarter.
They run off the CRM. One report on the screen, the same report every week. Nobody brings their own spreadsheet.
They end with actions. Each deal discussed leaves with a named owner and a dated next step.
Who should attend, and how often
Weekly is right for most B2B sales teams. Fortnightly lets too much drift between meetings, and daily turns into status reporting. Pick a fixed slot early in the week so there’s time to act on what comes out of it.
The sales leader runs it, and every rep with an open pipeline attends. It’s worth inviting marketing once a month, so they hear first-hand which leads are turning into real deals and which aren’t. That one conversation often does more for sales and marketing alignment than any shared dashboard.
Keep the forecast call and the pipeline meeting separate if you can. The forecast call is about what will close and when. The pipeline meeting is about moving deals forward. When they’re combined, the forecast takes over and the coaching gets squeezed out.
Prepare before the meeting, not during it
The single biggest improvement most teams can make is to set a clear expectation: the CRM is updated by the end of the previous working day. Every deal has a current stage, a close date the rep believes in and a dated next step. The sales leader looks at the report beforehand and picks the deals worth discussing. The meeting then becomes a conversation about the deals that need help, rather than a data entry session.
Deal review questions that do most of the work
I’ve seen plenty of deal review frameworks, and most are too long to use every week. These cover most of what matters:
What did the buyer do since last week? Not what we did. What they did.
What has to happen next, and when? A dated next step, agreed with the buyer.
What could stop this closing? If the answer is “nothing”, the rep hasn’t looked hard enough.
Once those questions are routine, the CRM build is straightforward. Each one becomes a field or a view, and the meeting runs off a single report instead of going round the table.
Run the meeting from one CRM report
The report that runs the meeting should answer the sales leader’s questions before they’re asked. In most cases that means showing:
Deals that changed stage since last week, in either direction.
Deals where the close date has been pushed back.
Deals with no next step, or a next step that’s overdue.
Deals with no activity in the last two weeks.
Everything forecast to close this month, with its amount and stage.
When the report is built like this, the meeting naturally focuses on exceptions. Healthy deals don’t need airtime. The ones that have slipped or stalled get the attention, which is where a sales leader’s time actually changes outcomes.
Common pipeline meeting mistakes
A few patterns come up again and again:
Going round the table. Each rep talks through their whole pipeline. It’s slow, it rewards whoever talks most confidently, and it tells the leader very little.
Updating the CRM in the meeting. If the sales leader is typing while reps talk, the team has learned that the meeting is where data gets entered. It should be entered before.
Arguing about probability. If the meeting debates whether a deal is 40% or 60%, the stages aren’t defined clearly enough. Fix the stages and the debate goes away.
No follow-through. Actions agreed one week and never mentioned again teach the team that the meeting doesn’t matter.
Build the system around the meeting
This is the order I work in. Agree how the meeting should run. Decide what the sales leader needs in front of them to run it. Then build the CRM so that information is there, up to date, without anyone chasing.
Done the other way round, you get a beautifully configured system that nobody opens on a Monday morning.
If your pipeline meeting regularly overruns, or ends without anyone being clearer on the forecast, start there. The CRM work will follow, and it’ll be a lot smaller than you expected.