An automated report is a message your system sends you every week by itself: four to six numbers from tools you already use, with no retyping into Excel. Start with the one table you currently build by hand, define the data sources and the send time. Once the report arrives on its own, you actually read it.
Most owners know Monday morning. You open the CRM, then your email, then the accounting software, then last year's Excel file, and copy numbers into columns. Half an hour later you have an overview that is already slightly out of date. Next week you do the same again. The problem isn't Excel. The problem is the retyping.
What an automated report is, and what it isn't
It is an ordinary script or workflow that, at an agreed time, reads data from your sources, calculates a few totals and sends the result where you will see it. Usually that's email, but it can also be a Slack message or a Google Sheet that refreshes itself.
AI is useful at one point: if you want two sentences of explanation next to the numbers, for example "enquiries are down a fifth on last week, most of the drop is from the website form". The calculations should be done by ordinary code, not a model. A total has to come out the same every time.
Which numbers belong in a weekly report?
Fewer than you think. Nobody reads a report with thirty indicators. For most small businesses this list is enough:
| Area | Number | Where it comes from |
|---|---|---|
| Enquiries | New enquiries by channel | Form, email, Instagram |
| Responsiveness | Average time to first reply | Timestamps in CRM or email |
| Quotes | Sent, accepted, still open | CRM or quote template |
| Money | Invoices issued, unpaid invoices by due date | Accounting software |
| Capacity | Booked and free slots next week | Calendar or booking system |
| Exceptions | Enquiries with no reply for more than a day | CRM |
The last row is the most useful. The totals tell you how the week went. The exceptions list tells you what to do today.
Time to first reply is not a random pick. A 2011 Harvard Business Review study (Oldroyd, McElheran, Elkington) of 2,241 US companies found that the average first reply to an online enquiry took 42 hours, and that 23% of companies never replied. If you don't measure this number, you don't know yours. More in the post Speed to lead: what the research says.
How to set up your first automated report
- Pick one report. The one you build by hand every week today. Don't design a new one.
- Write down where each number comes from. If you don't know which field holds the data, automation won't find it either.
- Check input quality. If your team enters a quote status as "sent" once, "Sent" the next time and nothing the third time, the report will be wrong too. Standardise the fields first.
- Set the time and the recipient. Monday at 7:30 to the owner's email beats "somewhere in the system".
- For the first three weeks, compare with a manual calculation. If the numbers match, drop the manual version.
- Add the exceptions. Only once the basic version works, add the list of things waiting for you.
What a report can't do
An automated report is only as good as the data it gets. If enquiries vanish into private messages or onto paper, the report won't see them. So the first step is often different: collect enquiries in one place, for instance with a system for fast replies to enquiries that writes every message into your CRM.
A report also doesn't decide for you. It tells you there are eight open quotes. It doesn't tell you which customer to call first.
What about personal data?
If an outside tool builds the report and processes customers' personal data, Article 28 of the GDPR requires that the processing is governed by a contract or other legal act. In practice that means a data processing agreement with the provider. Also check where the data is processed and whether the provider uses sub-processors. This isn't legal advice, so ask a lawyer if in doubt. Often the easiest fix is a report that contains totals and no customer names.
How to start today
- Open the last weekly report you built by hand.
- Mark every number you retype from another program.
- For each one, write down the source and the field.
- Strike out anything you haven't used in a decision this past month.
- What remains is your specification. Time how long it takes this week and multiply by 46 working weeks. That is how many hours a year go on retyping alone.
For a wider view of which tasks to automate first, the post What to automate first has a simple scoring table.
Frequently asked questions
Which reports should I automate first?
The ones you already build every week from the same sources: new enquiries, quotes sent and accepted, open receivables, booked slots. A simple rule: if you have done the same copy-and-paste three times in a row, a system can take it over.
Do I need to replace the tools I already use?
No. The report usually pulls data from tools you already have: your CRM, the website form, your accounting software or Google Sheets. It assembles the numbers and sends them to your email or Slack. It does not replace your tools.
What about data protection if an outside tool builds the reports?
If the tool processes customers' personal data, Article 28 of the GDPR requires a contract with the processor. Sign a data processing agreement and check where the data is processed. A management report often needs no names at all, only totals.
Sources
Luka Tomič · Founder of Alra
Luka builds AI systems for Slovenian businesses that want to get more done with the same team. He writes about what he sees with clients: where time gets lost and how to get it back.