Automated sales reporting: what to check before building one

Automating the wrong number

Many sales reporting projects fail because of a false start. The company hires someone to automate the report that is already being built by hand, without first checking whether that report is actually the right one. The result is a fast, good looking dashboard that keeps generating the exact same argument in Monday's sales meeting.

Before automating anything, it is worth answering these five questions. They take an afternoon to work through and save months of maintaining a report nobody ends up using.

1. What counts as a closed sale in your company

This sounds like an obvious question and it almost never has a single answer inside the same company. For the sales team a sale closes when the customer signs the order. For finance it closes when the invoice goes out. For whoever handles cash flow, it closes when the payment actually arrives.

An automated report that mixes these three moments without making it explicit produces a number that every department reads differently, and meetings fill up with clarifying what the figure on screen actually means instead of deciding what to do about it.

2. Where the real number actually lives

In most companies the real sales figure is scattered across the CRM, the ERP and the spreadsheet each salesperson keeps with their own opportunities. All three usually say slightly different things for the same week.

Before automating, you need to decide which of those sources wins when they disagree, and what happens with the data that only exists in one salesperson's spreadsheet. Automating without settling this only gets the discrepancy onto the screen faster.

3. What level of detail each viewer actually needs

A sales director and an individual salesperson do not need to see the same thing. The director wants the whole team's trend against the quarter's target. The salesperson wants their own open opportunities and how far they are from this month's quota.

Building one single report for everyone usually ends up too dense for leadership and too general for the salesperson who needs to act on their own numbers today.

4. How often it actually needs to refresh

Not every sales cycle needs the same refresh rate. A sale that takes weeks to close gains nothing from data updated every hour, while a team working with daily orders loses real value if the report only refreshes once a week.

Deciding this frequency before automating avoids building something oversized or, on the other hand, something that always lags one step behind what the team needs to decide today.

5. What happens the day a quota, territory or salesperson changes

Sales teams restructure more often than most other departments. Territories get redrawn, quotas get adjusted mid year, a salesperson leaves or takes over an account.

An automated report that was not built to absorb these changes forces someone to rebuild parts of it every time one happens, and ends up creating more manual work than it was meant to remove.

What to do about it

None of these five questions requires buying any new tool. They get answered by talking to the sales team and checking where each number actually comes from today, before touching anything in the automation itself.

I automate exactly this kind of sales reporting. The first meeting is one hour and free of charge, and it is there to go through these five questions together before deciding what to automate first.