Reporting projects usually start with a tool. Someone decides the business needs better visibility, and the first question asked is which dashboard product to buy. I think that is the wrong first question. The small business reports worth having are mostly ones your accounting package already produces, and most businesses aren’t reading them on any particular schedule. Here are five that come first, and the test for when something fancier is actually justified.
The five small business reports that come first
None of these need a new tool. All of them answer a question an owner should be able to answer on any given Monday.
- Cash position, plus the next 60 days. What is in the bank, what is committed to go out, and what is expected in. Not a forecast model — a short, honest list.
- Aged receivables. Who owes you money and how late they are. Xero calls this the Aged Receivables Summary report; MYOB documents the same thing under monthly ageing of invoices. This is the report most likely to pay for itself the week you start reading it.
- Revenue concentration by customer. Your top few customers as a share of total revenue. Not a performance number. A risk number.
- Gross margin by job, product or service. Revenue tells you how busy you were. Margin tells you which of that work was worth doing.
- Committed forward work. What is already booked or contracted for next month. Even a rough figure beats the alternative, which is finding out in three weeks.
That is the whole list. Four of the five come straight out of accounting software. The fifth usually lives in a spreadsheet or someone’s calendar, and that is fine for now.
Why businesses skip these and buy a dashboard
Partly because the five are dull. Each one is a single number or a short table. None of them feels like a project, and none of them makes anyone look like they have modernised the business.
A dashboard feels like progress. It has charts and a colour scheme, it can be shown in a meeting, and it produces a sense that the data problem has been dealt with. The trouble is that a dashboard sitting on top of numbers nobody has agreed on does not resolve the disagreement. It distributes it faster, to more people, with better typography.
I would rather see a business reading five plain reports every Monday than looking at a beautiful dashboard once a quarter. Frequency beats polish, and it is not close.
The part that actually takes the time
The hard bit of reporting is almost never the chart. It is agreeing what a number means.
Take revenue last month. Is that invoiced or received? Does it include GST? What happens to a job invoiced in July and delivered in August? Two capable people can pull that figure and produce different answers, and both can be right by their own definition. Until the business picks one, every report built on it is contested.
The same goes for margin. Does it include the owner’s own time? Most small businesses quietly exclude it, which makes some work look profitable when it isn’t. And for customers: does a client who bought once in March still count as active in August?
These questions are unglamorous and nobody sells a product to answer them. They are also the difference between reporting that gets trusted and reporting that gets argued with.
How to tell a report is working
Three tests, in my view:
- Something changes because of it. Somebody chases an invoice, drops a product line, or moves a job. If nothing ever changes, the report is decoration.
- It gets read on a schedule, not only when there is already a problem. A report you open during a cash crunch is a diagnostic, not a warning.
- There is one version of it. The moment two people maintain different copies, meetings become arguments about whose figure is right.
When something fancier is justified
There is a real test for this, and it is narrower than most vendors suggest. Build the custom layer when a question repeats every week and answering it means joining two systems that don’t talk to each other.
Margin by job where the hours live in a scheduling tool and the costs live in accounting. Revenue by channel where the sales sit in a POS or an online store and the ledger only sees a daily total. Those are genuine cases. Something has to do the joining, and doing it by hand every week stops being sensible.
If the question comes up once a quarter, export both sides and join them in a spreadsheet. That is not a failure of ambition. It is the correct answer, and it costs nothing. If you are not sure which situation you are in, working out what you already have and where it disagrees with itself is exactly what a data health check is for — and it is worth doing before, not after, you choose a tool.