The report nobody reads: kill it or automate it
The Friday ritual
Somewhere in your business, odds are, a person spends part of every week assembling a report that began life as somebody's good idea. It gets built, sent, and skimmed by two people out of the eight it goes to, or filed unread. The builder suspects this. The recipients confirm it by never mentioning it.
A hand-built report nobody reads is the worst possible configuration: full labor cost, zero decision value. Both directions out of it are improvements.
Run the silence test
Finding out which reports matter costs nothing: skip one cycle and see who notices. Send nothing on Friday. If three people ask where the numbers are by Tuesday, the report earns its keep. If silence, you have your answer, and it was free.
Run the test on every recurring report once a year. The results reshuffle more than most owners expect, because reports outlive the decisions they were built to feed.
Then sort into three piles
Each report lands in one of three buckets:
- Read and used: automate the assembly, the machine pulls and formats, a person adds the two sentences of judgment on top
- Read by one person for one number: kill the report, automate an alert that sends that number, or only sends when it crosses a line
- Read by nobody: kill it outright, and enjoy the recovered hours
Judgment is the human part
The pattern across every keeper: machines gather and format, humans interpret. The half-day someone spent hunting numbers becomes ten minutes writing what the numbers mean, which was the only part anyone ever valued. The Monday report that builds itself is the worked example.
The audit answers this for your business
Two weeks, $2,500 flat ($1,000 for the first three clients), and you get the map of your own automatable work with dollars on it.