I have been implementing CRM systems in sales companies for 8 years. One question comes up at almost every implementation kickoff: how do we improve sales reporting? The answer is always the same: stop collecting data manually, let the system do it for you.
Before we get to the solution, though, let us look at the problem. Specifically at what is happening in hundreds of sales companies every Friday afternoon.
The Friday ritual: the manager chases salespeople for results
It is Friday, 3:00 PM. The sales manager opens their laptop and sends an email to six salespeople: "Please update the spreadsheet by 5:00 PM." A familiar ritual, repeated every week for months.
By 3:30 PM the responses start arriving. The first salesperson sends back a file from two years ago, with columns nobody has used except them. The second forgot to fill in the forecast column, writing "in progress" instead of a number. The third sent the correct template, but the currency cells use a different format than everyone else. The fourth did not reply at all because they are in a meeting. The fifth and sixth sent files that need to be manually merged into the master spreadsheet.
The manager sits down to merge. This is a two-hour job full of copy-pasting, format fixes, and calling the salesperson who has not responded. By 5:30 PM the report is half-finished. It gets completed on Monday morning.
The report reaches leadership on Monday before 9:00 AM. It shows data from the previous week. On the basis of that data, leadership makes decisions about resource allocation, priority shifts, and targets for the coming week.
This is not an incident. This is the standard reporting process in companies that manage sales through Excel and email. And it costs more than most people realise.
How much time leadership actually loses on Excel reporting
Sales managers spend an average of 4.6 hours per week collecting and consolidating data from different sources instead of analysing it and making decisions.
Salesforce, State of Sales Report 2024
4.6 hours per week. Let us translate that into concrete figures.
A sales manager on a gross salary of £60,000 per year works approximately 168 hours per month. Their effective hourly rate is therefore around £35. At 4.6 hours per week on reporting that is roughly £160 per week, or over £640 per month, spent solely on chasing and merging spreadsheets.
That is only part of the cost. Add the time salespeople spend. Each of them devotes 30 to 60 minutes per week filling in spreadsheets, refreshing data, and answering the manager's questions like "is that opportunity still live?" With six salespeople that is an additional 3 to 6 hours of team time per week that could otherwise go into client conversations.
The hidden cost: time that is not working
The real cost is broader still. The manager who spends Friday afternoon merging spreadsheets is not analysing the data. They are not noticing that one salesperson has a pipeline full of opportunities with no close date for three months. They are not reacting to the fact that conversion from proposal to negotiation has been falling over recent weeks. They are not preparing for a difficult conversation with a client who just showed renewed interest.
Collecting data and analysing data are two entirely different tasks. The first is mechanical and requires none of the manager's expertise. The second is impossible without data that is current as of right now.
Companies that have deployed CRM systems with automated reporting report that the time managers spend on administration drops by 60 to 80%. That time moves into analytics and working with the team.
Stale data: decisions made on week-old numbers
Consider the following situation. On Wednesday a salesperson speaks with a client who had been expected to close this quarter. The client says they are freezing budgets until next year. An opportunity worth £80,000 disappears from the pipeline.
At that moment the manager knows nothing. Leadership knows nothing. The quarterly forecast still counts that opportunity as highly probable. The information will only surface in Monday's report, if the salesperson bothers to update the spreadsheet at all.
This is not an isolated incident. It is a structural information delay that affects every decision based on Excel reports:
- Allocation of sales resources for the following week is based on data from the previous week
- Decisions to provide extra support to a specific salesperson arrive too late
- Revenue forecasts are out of date by the time they reach leadership
- Opportunities requiring immediate management intervention are buried in the weekly reporting cycle
In B2B sales, where a single well-timed call or email can determine the outcome of a negotiation, a week-long information lag is a real business cost. It is not just about the hours spent on spreadsheets. It is about the decisions that were never made because nobody knew they needed to be.
The consistency problem
There is another dimension that appears in every company managing sales through spreadsheets: a lack of data consistency.
Every salesperson has their own interpretation of what the "proposal sent" stage means. One records it when they have sent a preliminary quote by email. Another waits until the client actively asked for a proposal. A third treats every meeting as "proposal in progress." The result is that the manager's pipeline is a combination of four different logics pasted into one spreadsheet. Stage-by-stage conversion rates cannot be calculated. Funnel analysis is impossible.
For more on how teams without a shared system lose synchronisation, see the article on three salespeople without CRM and the chaos that follows.
CRM reporting: a real-time pipeline view
CRM changes the logic of reporting from the ground up. Instead of "collect data, merge, send report," the principle is inverted: data is collected continuously as a by-product of salespeople's normal work in the system.
A salesperson updates the status of a sales opportunity in the CRM. At that exact moment the change appears in the manager's dashboard, in the revenue forecast, and in the team activity report. No Friday email. No merged spreadsheets. No week-old report.
What CRM reporting looks like in practice
The manager logs in in the morning. They can see the current pipeline: how many opportunities are at each stage, their combined value, which ones have a close date this month. They click on a specific salesperson and see how many activities they had last week: calls, emails, meetings. They can see which opportunities have had no activity for weeks and have probably gone cold.
That takes 5 minutes. Not 4.6 hours.
Leadership has access to a separate dashboard with aggregated company-wide data. They do not need to wait for the manager's report. They do not need to ask whether the data is current. They can log in at 7:00 AM on a Wednesday and check the quarterly revenue forecast, which already incorporates yesterday afternoon's events.
To understand what this kind of implementation looks like in practice, explore the article on how long a CRM implementation actually takes.
Six reports every sales manager should have
A good CRM should deliver ready-made reports without any manual configuration. Here are the six reports every sales manager should have access to.
1. Real-time pipeline
A view of all open opportunities grouped by stage. Shows: how many opportunities, what their combined value is, what the probability of closing is at each stage. Updates automatically every time a salesperson makes a change. This is the report that replaces the Friday email.
2. Salesperson activity
A report showing how many calls, emails, and meetings each salesperson completed in a given period. The manager can immediately see who is working actively and who has low activity that warrants a conversation. In Excel this report does not exist, because salespeople do not log how many calls they made in the spreadsheet.
3. Close forecast for the current and next month
A list of opportunities with close dates falling in the current or next month, along with their value and probability. The manager can see a realistic revenue forecast rather than just what salespeople entered in the "forecast" column of a spreadsheet.
4. Stage-to-stage conversion
The percentage of opportunities moving from one stage to the next. If conversion from proposal to negotiation is falling, the manager knows something is happening at that stage before the month ends. In Excel this analysis requires manual calculations and is done once every few months at best.
5. Sales cycle length
Average time from first contact to closing an opportunity. The report shows whether the cycle is shortening or lengthening, which salesperson has the shortest cycle, and which has the longest. This data helps identify best practices and problem patterns.
6. Lost deals: why clients say no
A report of negatively closed opportunities broken down by rejection reason: price, competition, no budget, no need, other. Without this report a company does not know why it is losing clients. With it, the company can systematically work to eliminate the specific causes of failures.
Excel vs CRM in sales reporting
| Criterion | Excel | CRM |
|---|---|---|
| Data freshness | Data from last week or older | Real-time data |
| Report preparation time | 2 to 4 hours per week | 0 minutes, report is always ready |
| Leadership access | After receiving manager's email | 24/7 directly in the system |
| Data granularity | Whatever the salesperson entered | Every activity, every status change |
| Forecasting | Subjective estimates from salespeople | Algorithmic, based on close history |
| Historical records | Depends on how many files were saved | Full history from day of implementation |
How to choose a CRM with good reporting
Not all CRMs have equally strong reporting. When selecting a system for a sales company with 3 to 15 people, check these points.
Dashboards without additional configuration. Reporting should work from day one, without needing a developer or CRM consultant to build reports from scratch. Check whether the system has built-in pipeline, activity, and forecast views available straight after implementation.
Custom views. Every company has slightly different needs. CRM should allow filtering, grouping, and sorting data by your own criteria, without any knowledge of SQL or programming.
PDF and Excel export. Even if CRM reporting replaces spreadsheets, having the ability to export data is useful. Some leadership teams still expect a PDF report for quarterly meetings. A good CRM should allow that with a single click.
Mobile access. Managers and salespeople need access to data from their phones. A real-time report loses its value if it can only be viewed at a desk.
Role-based permissions and views. A salesperson should not see their colleagues' results. A manager should see their entire team. Leadership should have a separate aggregated view. A CRM with good reporting should allow this to be configured precisely.
It is also worth remembering that reporting is only one of the problems CRM solves. Teams without a shared system also face synchronisation failures and loss of context, which I cover in the article on three salespeople without CRM and team chaos. Response time to client inquiries is also directly affected: companies using CRM with follow-up automation react faster, which directly impacts conversion rates.