Sales CRM reports: a daily and weekly rhythm for the team

Short answer

CRM reports for a sales team are built on three rhythms. The daily report is for the manager: whom to call today, which new leads are waiting, which steps are overdue. The weekly report is for the team meeting: leads, speed to first touch, stage movement, leads won and lost. The monthly report is for trends and causes. Every report needs an owner and one action that follows from it. If someone reads a report and does nothing, the report is not needed.

Why reports go unread

In many teams, reports sit in the CRM's "reports" section and nobody goes there. The team lead pulls together an Excel sheet at month end, and managers see reports as a control tool: "they're checking up on me". The report arrives late and influences no decision.

A report that works meets two conditions: it comes to where people already work, and it answers "what should I do now?". For a manager that is a work list; for a team lead it is a signal of where the team needs help.

Daily: the manager's work list

1. 1Steps due todayIn time order: whom, why, through which channel.
2. 2New, untouched leadsAssigned to the manager, but with no first touch yet.
3. 3Overdue stepsWork left over from yesterday — the most important part of the daily list.
4. 4Conversations with a replyThe customer has written and the manager has not answered yet.

The list should look like a work plan, not a report, and be on the manager's phone when the day starts. Its source is the next-step field — covered in the CRM next step.

Weekly: the team meeting

The weekly report is the team meeting's agenda. One row per manager, five columns:

• New leads, and how many were touched in time.
• Stage progress: how many leads moved to the next stage this week.
• Leads won and lost, and the main reason for the losses.
• Stuck leads: those past the normal time in their stage.
• Open leads without a next step.

Monthly: trends and causes

Once a month a wider view is needed: win rate by lead creation month, the breakdown of loss reasons, sales by channel and source, average sales cycle. This report is the basis of the meeting between sales and marketing, and it draws on the same metrics as the CEO's weekly screen. The short version for the CEO is described in CRM dashboard metrics for CEOs.

Reports must come to where people work

Managers spend the day in a messenger, not in the CRM's reports section. If the daily list and reminders arrive on the manager's phone and the weekly report lands in the team group an hour before the meeting, people read them. Timing matters too: the daily list when the working day starts, the weekly report on meeting day, early enough to check the numbers.

Format: one screen, a target and a comparison

A good report fits on one phone screen. Every number needs two things beside it: a target and a comparison with the previous period. "New leads touched in time: 78% (target 85%, last week 81%)" says far more than "78%". Use colour sparingly: highlight only the metrics below target, not everything. Long tables go to the end of the report, under "details". The manager's daily list should carry no percentages at all — only names, times and actions, because it is a work plan, not a control sheet.

From report to action

For each block of a report, write down in advance: if this number gets worse, who does what? Examples:

• Untouched leads rise → the shift lead checks the assignment rule and workload.
• Many leads without a step → a 15-minute list clean-up together with the manager.
• Leads pile up in one stage → change the script or offer for that stage.
• One reason dominates → read the reason itself: open 10 lost conversations.

Avoid the league table

Ranking managers top to bottom in one table is tempting, but it backfires: leads come from different channels with different quality, and the manager at the bottom often works the hardest segment. A league table also encourages "beautifying" data: leads get closed quickly, reasons get written neatly, and the real picture disappears. Show the numbers to help, not to compare, and never make them the only basis for evaluation.

An illustrative example

This is an illustrative example. A travel agency has five sales managers. The team lead used to prepare a 20-column Excel sheet every Friday and the meeting took an hour. In the new rhythm, each manager gets their own list at 9:30 in the morning, and the weekly report lands in the team group on Friday at 10:00.

The meeting shrinks to 30 minutes, and instead of reading numbers aloud, one stuck lead per manager is discussed. A month later, the number of overdue steps is visible on the morning list and starts to fall.

Common mistakes

• Producing every report once a month, and late.
• Showing managers the team lead's report instead of their own work list.
• "Waiting" for people to open reports inside the CRM — nobody goes there.
• Only reading numbers aloud in the meeting.
• Presenting activity (call counts) as an outcome.

Limitations

A report cannot be better than the data in the CRM: if managers record outcomes late, the daily list will be wrong. In a small team weekly numbers move by chance, so draw conclusions from four-week trends. Reports also do not show conversation quality — that takes reading conversations or quality analysis.

The reporting rhythm in Vexvon

In Vexvon, a daily or weekly sales report can be sent automatically to a Telegram group at a time the company chooses; the send time is checked every 30 minutes. Due lead reminders reach the manager as a private Telegram message, and the manager records the call outcome, stage, note and new reminder right there with the buttons under the notification — each action goes into the lead's log. More on Vexvon CRM.

Next step

List your current reports and note next to each: who reads it, where, and what they do after reading it. Stop any report without an answer. Call metrics are covered separately in sales call metrics. More articles are in the AI CRM section, and we can set up your reporting rhythm together during a demo.