Guide
Sales coaching with CRM data: what to review each week
Most pipeline reviews are just deal counting. A manager asks how many deals are in the pipeline, a rep gives a number, and everyone leaves feeling like something happened. It didn't. Here is how to use what is already in your CRM to have coaching conversations that actually change what reps do.
Pipeline review and coaching are not the same thing
A pipeline review answers: what do we have and what is likely to close? Useful for forecasting. Not useful for improving how anyone sells. Coaching answers a different question: what did the rep do, was it right for the situation, and what would be more effective?
Tiago sat in on a pipeline review at a software services firm in Porto where three managers discussed the same deal for forty minutes. They debated close probability. They mapped out scenarios. They never asked the rep what they thought the actual problem was. The rep was in the room the entire time, nodding along, and left without anything specific to do differently.
CRM data bridges the two conversations. It shows what actually happened on each deal: what was done, when, with whom. That is the starting point for coaching. Without it, you are coaching based on what the rep says happened. Which is a different thing entirely.
Four signals worth checking weekly
You don't need a wall of metrics. You need four things that tell you where deals are healthy and where they are not.
Last activity date
Any deal with no logged activity in the past ten to fourteen days needs an explanation. Not a reprimand. An explanation. Sometimes the deal is moving and the rep just did not log the last email. Sometimes the rep is avoiding it because they do not know how to move it forward. The data doesn't tell you which. The conversation does.
Days stuck in the same stage
Every stage in your pipeline should have a rough expected duration. If a deal has been at "Proposal sent" for three weeks and your average close cycle is four weeks total, something went wrong. A stuck deal is not just a data point. It is a signal that the rep may not know what the next move is.
Contact coverage
Single-threaded deals fail more often than multi-contact deals. If a deal has only one company contact and that person goes quiet, the deal stalls. Your CRM should show you which deals have one contact on the buyer side. Those are fragile. That is worth a coaching conversation about who else is involved and how to reach them.
Stage conversion trends
This one is more monthly than weekly, but if you check it regularly you catch changes faster. If proposals are converting at 40% for three months and then drop to 18%, something changed: the quality of what is going into proposal, the proposal format itself, the follow-up process, or the competitive situation. The data doesn't explain it. But it tells you which stage to look at first.
From data to an actual conversation
Looking at the CRM before a 1:1 is preparation, not coaching. The coaching happens in the conversation. The data tells you where to start.
The pattern that works: pull up a deal that a signal flagged, then ask questions instead of giving answers. Most managers do it backwards. They see a stalled deal and immediately tell the rep what to do. The rep nods. Nothing changes. When you ask the rep to explain the situation first, you usually find the real problem, which is often different from what the data suggested.
Four questions that tend to generate useful coaching from CRM signals:
- What did you do on this deal last week? Start with what happened, not with what should happen next. The CRM shows what was logged. The rep's answer tells you whether the log is accurate and whether the activity matched the situation.
- Who else is involved on their side? Single-contact deals are fragile. If the rep only knows one person at the buying company, coaching them to find additional stakeholders is more valuable than almost anything else you can do for that deal right now.
- What is the one specific thing that moves this forward? Not "follow up." Something specific: a call booked for a set time, a proposal revision around a concern the contact raised, an introduction to a second stakeholder. If the rep cannot name it, that is the coaching moment.
- What could make this deal fall apart? This question is underused. Asking reps to name the biggest risk on each deal is a useful habit. It forces them to think about what they do not know and what they might be quietly avoiding.
The thirty-minute weekly rhythm
Block thirty minutes before your first 1:1 of the week. Not during. Before.
Open your CRM and filter active deals for: last activity older than ten days, time in current stage over two weeks, or only one contact logged on the company side. That filter usually gives you a short list. Work through it. For each flagged deal, note what you think the situation is and what question you want to ask in the 1:1.
In the 1:1, lead with the flagged deals. Not with the ones the rep is excited about. Those will get attention on their own. The deals worth your time are the quiet ones: the deal mentioned three weeks ago that has not come up since, the proposal sent without a follow-up, the company that stopped responding after a meeting.
Keep the data review and the coaching conversation separate. One is preparation. The other is the actual work.
What the pattern across reps tells you
When you run this review across a few people, patterns emerge that individual coaching misses. If every rep has deals stalling at the proposal stage, the problem is probably not any individual rep. It is the proposal itself, the pricing, or what happens after the proposal goes out. That is a process problem, not a behavior problem. Individual coaching will not fix it.
Aggregate views across the team are where CRM data goes from useful to strategic. You can see whether a change you made two months ago (a new qualification criterion, a different proposal format, a new pricing structure) actually shifted conversion at a specific stage. Individual reps cannot see this. You can, because you have the full picture across all of them.
How Lumenbase supports this
- Activity timeline on every deal and company. Every email, meeting, and logged note shows up on the deal record and the company timeline. You do not need to ask what happened. You can look. That makes the coaching conversation start from facts rather than from what the rep remembers.
- Feed surface for quiet accounts. The Feed shows which contacts and accounts have gone quiet based on communication recency. For a manager, this is a fast way to find deals that need attention without opening every record individually.
- Deal stage history. You can see when a deal moved between stages. If something has been sitting at the same stage for three weeks, that is visible without the rep reporting it. That gives coaching a factual anchor instead of relying on what the rep volunteers.
- Email and calendar sync. Activity is captured automatically when email and calendar are connected. Reps are not manually logging every call. That means the data you use for coaching reflects what actually happened rather than what got entered during a slow Friday afternoon.
Who this is for
Sales managers at software agencies, consulting firms, and professional services businesses who are responsible for one to six reps. Also useful for founders who are transitioning from doing all the selling themselves to managing someone else doing it. If you have weekly 1:1s with reps and find those conversations cover the same deals without much changing, this approach is worth a try.