Monday morning, before the meeting
Someone, often the sales manager or an operations person, exports deals from the CRM into a spreadsheet. They filter out the closed ones, fix a few stages that are obviously wrong, add last week's figures from last week's spreadsheet so they can show movement, build a summary table and a chart, and paste it into an email or a slide. It takes a good chunk of the morning.
Then in the meeting, someone asks why a deal dropped out, and the answer is not in the report, because the report shows this week's pipeline but not what changed since last week.
Why CRM reports do not replace it
CRM dashboards show the pipeline as it is right now. The questions asked in a pipeline meeting are mostly about change: which deals moved forward, which slipped a close date, which were lost, what is new. Answering those needs a record of what the pipeline looked like last week, and most CRMs either do not keep that in a reportable form or make it awkward to get at.
There is also a trust problem. The person building the report manually corrects obvious data issues as they go, such as a deal left in the wrong stage or a close date in the past. An automated CRM report shows the raw data, errors and all, so people go back to the hand-built version.
What the manual report costs
- A senior person's Monday morning, every week, spent on copying and pasting.
- Silent inconsistencies, because manual fixes are not the same each week.
- No history, so trends over a quarter are hard to see.
- Data problems in the CRM that never get fixed at source, because the report quietly works around them.
- Meetings that spend time establishing the numbers rather than discussing deals.
How we automate the pipeline report
- Connect to your CRM through its API, such as HubSpot, Salesforce, Pipedrive or Zoho, and read deals, stages, amounts, owners and dates.
- Snapshot the pipeline on a schedule into a small database, so any week can be compared with any other.
- Compute the changes: new deals, deals advanced, deals slipped, close dates moved, values changed, deals won and lost, each with the owner and the size of the change.
- Run data checks: close dates in the past, deals with no activity for a period you set, missing amounts, stages that do not match activity. These are sent to the deal owner to fix at source before the report is sent.
- Build the report: a summary, the movement since last week, and the flagged deals, delivered by email, in Microsoft Teams or Slack, or as a live dashboard in Power BI, Looker Studio or a simple web page.
- Add commentary space: the sales manager adds a few lines of context before it goes out, if they want to.
| Question in the meeting | Where the answer now comes from |
|---|---|
| What is new this week? | Deals created since last snapshot |
| What slipped? | Close dates moved later, stages moved back |
| What did we lose, and why? | Lost deals with the recorded reason |
| Is the pipeline growing? | Weekly totals by stage over time |
What Mondays look like afterwards
The report is there before anyone arrives. It is built the same way every week, so comparisons mean something. Data problems are fixed by the people who own the deals rather than patched in a spreadsheet, so the CRM itself gets better over time. The meeting can start from the movement and spend its time on the deals that need a decision.
The person who used to build the report gets their Monday back, and the weekly snapshots quietly become a history you never had. After a couple of quarters you can see how long deals typically sit in each stage, how often close dates move, and which stages deals most often die in. Those are the questions that improve a sales process, and they cannot be answered from a CRM that only knows the present.
Is this your Monday?
- Someone exports the CRM into a spreadsheet each week to build the report.
- The report shows the current pipeline but not what changed.
- Data is corrected in the spreadsheet rather than in the CRM.
- You cannot easily compare this quarter's pipeline with last quarter's.