Use cases / Self-writing reports
Use case
The month-end report, assembled overnight.
Every business runs on its numbers — and in most of them, somebody spends days each month collecting them. Exporting, pasting, formatting, emailing. By the time the report is read, it's already history.
The last week of every month.
Someone exports sales from one system, costs from another, hours from a third. Pastes it all into the master spreadsheet, fixes the chart that always breaks, writes two lines of commentary, saves the PDF, emails it round. By the time anyone acts on it, the numbers are a fortnight stale — and the person who assembled it was hired to do something else entirely.
Month-end gets treated as a fixed cost — the week it takes is just what it takes. But the assembly is the part software does without tiring or mistyping; only the judgement on top needs a person. Most firms have the two welded together.
How it actually works.
- We agree the numbers that drive decisions. Not everything you could measure — the handful you'd actually act on: cash, sales, work in progress, whatever runs your week. It's usually a shorter list than the current report.
- We wire the sources. The figures flow in from the systems that already hold them — accounts, job system, bank — so nothing is exported or retyped. It's the same plumbing as stopping the re-keying, pointed at your numbers.
- The report is assembled overnight. In your format — the board pack, the Monday email, the partner summary — with anything odd flagged in plain English: a margin that moved, a client gone quiet, a figure that doesn't usually look like that.
- A live view replaces the scramble. The same numbers any hour of any day, not once a month. Month-end becomes reading and deciding, not collecting and formatting.
Where we've done it
Written overnight, read by breakfast.
Reporting is one of the first things we wire into any system we build, because the fog around the numbers is where owners feel the pain first. The clearest recent example: a UK firm's operating platform where the management reports are built overnight — work that replaced the firm's reporting subscription outright, one of five the platform retired.
What module one looks like.
We don't build a wall of dashboards. Module one is usually one report — the one that eats the most hours, or lands too late to act on.
One report, off your desk
We wire its sources, agree the format, and it's assembled from live figures each night — running alongside the old spreadsheet until you trust it. Live in about a month. Then the next report, or the live view.
What the assembly costs.
Hand-assembled reporting has two prices and neither shows up in the accounts: the days someone spends collecting and formatting, and the decisions made late because the numbers arrived late. Nobody can hand you those figures off the shelf — but the assembly is mostly re-keying by another name, and you can time it. Our calculator prices one loop of it across a year, at published ONS wages.
Work out what the assembly costs you →Most owners have never timed it — the report has been part of month-end for so long it reads as fixed. Timing it is how you find out.
Not sure this is the one to fix first? The 20-question self-audit ranks your processes — free, two minutes, no email →Where this goes next
- For wholesale & distribution → — where the overnight-reports module fits a distributor's week.
- For recruitment agencies → — the same module, shaped to a placement desk.
- The case study → — the platform where the reports are built overnight.
Start here
Bring us the report that eats your month-end.
A free process audit is thirty minutes. Walk us through how the numbers get from your systems to the page, and you'll leave with a written map of how it could be assembled for you overnight — whether or not we ever work together.
No pitch deck, no obligation. The map is yours either way.