There's a category of work in every small business that has no owner and no name. Somebody does it, every month, because it needs doing. It isn't in anybody's job description. It never comes up in a meeting. And it takes an evening.
A wall calendar rebuilt from scratch. A price sheet retyped into a new document. A report assembled by copying numbers out of one system into another. A list of this month's jobs pasted into a spreadsheet so somebody else can read it.
Nobody was hired to do any of it. It accumulated.
Why Nobody Notices These Jobs
Three reasons, and all three are about when and how the work happens rather than how big it is.
It happens monthly, so it never feels urgent. A daily annoyance gets fixed because it annoys you daily. A monthly one is over before you have finished being irritated by it.
It's nobody's specialty, so nobody complains about it. The person who does it is usually doing it because they were the one holding the file, and to them it's just part of the job.
It looks small in isolation. Two hours isn't worth a meeting. Two hours a month, times however many of these you have, is a working week or more a year, and nobody adds it up because nobody sees them as the same category of thing.
How to Find Yours
Ask a different question than the one people usually ask. "What takes the longest" surfaces the big jobs that are somebody's real work.
Ask: what do we rebuild?
Rebuild is the word that finds them. Anything that gets made from scratch on a schedule, out of information that already exists somewhere else, is on the list. Anything typed twice is on the list. Anything where somebody opens last month's version and edits it into this month's version is definitely on the list.
Ask the people who do them. The owner usually doesn't know these exist, because they stopped being the person doing them years ago.
Then Do the Arithmetic, Out Loud
Write each one down with two numbers next to it: how long it takes, and how often it happens. Multiply out for a year.
One job looks small. Add them all up. Most businesses have several of these jobs, and the total surprises everyone in the room.
That total is the number that matters, more than the biggest job on the list.
What to Do With the List
Sort it by a simple test: does it happen the same way every time, from information that already exists?
The ones that pass are the candidates. Something rebuilt monthly from a file somebody already maintains can be generated from that file, and the person who used to rebuild it only has to check it.
The ones that fail usually fail because there's judgment in the middle. Those aren't lost causes, but they're a different job: the machine does the parts either side and hands a person the decision, which is still most of the saving.
What Makes the Saving Stick
The saving decays if the outputs come from different places. If the calendar on the wall and the listing on the website are generated from two separate files, somebody has to keep them agreeing, and that somebody is doing a new monthly job you just invented.
When every output comes from one source, a change to the source updates all of them, so nobody has to keep two files agreeing.
That's the property worth insisting on, and it's the difference between automating a task and getting the evening back.
We have a worked example of exactly this on the site, with a sample you can run in your browser: the calendar automation. It started as one job at one studio, which is how they all start.