Sales Coaching with CRM Data: What to Review Each Week

    Most pipeline reviews are just deal counting. Here is what to look at in your CRM each week if you want coaching conversations that actually change what reps do.

    By Sebastian StreiffertPublished Jul 3, 2026Updated Jul 3, 20266 min read

    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 did not. Here is how to use what is already in your CRM to have coaching conversations that actually change behavior.

    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?

    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.

    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. The data does not 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.

    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.

    Stage conversion trends. If proposals are converting at 40% for three months and then drop to 18%, something changed. 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.

    Four questions that 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.
    • Who else is involved on their side? Single-contact deals are fragile. Coaching reps to find additional stakeholders is more valuable than almost anything else.
    • What is the one specific thing that moves this forward? Not "follow up." Something specific.
    • What could make this deal fall apart? Asking reps to name the biggest risk forces them to think about what they are avoiding.

    The thirty-minute weekly rhythm

    Block thirty minutes before your first 1:1 of the week. 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. Work through the flagged deals. Note what you want to ask in the 1:1.

    In the 1:1, lead with the flagged deals. Not the ones the rep is excited about. The deals worth your time are the quiet ones.

    What the pattern across reps tells you

    When 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.

    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 transitioning from doing all the selling themselves to managing someone else doing it.

    Frequently asked questions

    How long should a weekly CRM review take?

    Thirty minutes if you are prepared. If it takes longer, you are probably reviewing data and having coaching conversations at the same time. Keep them separate.

    What if reps don't keep their CRM updated?

    Then you have a different problem. The most common cause is that the CRM requires manual entry for basic activity logging. If the system does not sync email and calendar automatically, adoption will always be partial.

    Is this kind of review useful for a team of one?

    Yes, and more useful than you might think. When you are the only person selling, a weekly CRM review is how you catch deals you are quietly avoiding.

    What is the difference between pipeline review and sales coaching?

    Pipeline review looks at deals. Coaching looks at behavior. You can run a pipeline review and leave knowing nothing about how to help anyone improve.

    How many deals should a manager review in depth each week?

    All active ones, but not all at the same depth. Filter for the ones that meet at least one signal threshold, review those in detail, and give everything else a quick scan.

    Was this article helpful?