It’s Friday afternoon, 4.20pm. A founder I’ve worked with for two years has just spent two hours on a deck for an internal stakeholder. She sends it. The recipient does not open it. Not that day, not over the weekend, not on Monday. She finds out the following Wednesday, in passing, at the bottom of an unrelated email. She tells me about it on a call later that week and we both laugh, and then we don’t, because she works a 55-hour week and two of those hours just went to the bin.
That moment is the post. A typical owner-managed week contains three to five hours of work like this. The work feels productive because it is hard. It earns the firm nothing.
What is zero-earn work?
Zero-earn work is anything you do in a working week that produces no revenue, no relationship capital, and no learning. It is not the same as overhead. Overhead has a measurable function. Zero-earn work survives because effort feels like progress, and because the founder is the one performing the effort. Harvard Business Review named the pattern directly in 2023.
McKinsey’s activity-vs-impact research has been tracking the gap at scale for several years now. The lean tradition has had a name for it for fifty: Toyota calls it muda, the form of waste that adds cost without adding value. The seven (sometimes eight) muda categories at Toyota map cleanly onto knowledge work, and zero-earn founder work is mostly overproduction and over-processing. The polish on the deck nobody opened is over-processing. The fortnightly internal report nobody reads is overproduction.
Why does this matter for an owner-managed firm?
It matters because the founder’s hour is the most expensive hour the firm owns, and zero-earn work concentrates in the founder’s diary disproportionately. The team will not flag it, because they cannot see what you agree to in the inbox. The board will not flag it either, because the board does not see the Friday afternoon block. Bain’s time-poverty research is the public number behind the pattern.
Bain put 30 to 50 per cent of the typical executive week into activity that does not create value, and the share is higher in firms where the founder is still the operating brain. Three to five hours a week sounds modest. Run the maths over a year. That is 150 to 250 hours of founder time, or roughly six to ten weeks, going to work that produces no revenue, no relationship, no learning. For an owner of a £1m to £10m services firm, that is a cluster of strategic moves not made, a hire not run, a customer conversation not had. The opportunity cost is what hurts, not the hours.
Where will you actually meet zero-earn work?
It shows up in four reliable categories. Ego deliverables: work done to demonstrate you are still the most senior brain in the room, where the deliverable itself never moves anything. Hedge-against-anxiety prep: the third version of a slide deck for a meeting that did not need a deck at all. Performative reporting and sunk-cost loops fill out the rest.
Performative reporting is the fortnightly internal update that goes to a distribution list of people who skim it once a quarter. Sunk-cost loops are the projects that have already cost you a quarter, where the next month is funded by your unwillingness to admit the first quarter was a write-off. Each category has a tell. Ego deliverables get sent late at night and rarely get opened. Hedge prep accumulates in document version histories with names like “v6 final FINAL”. Performative reporting has a recipient list rather than a recipient. Sunk-cost loops survive past their original deadline by exactly the amount of time you have already invested in them. Cal Newport’s “How Work Learned to Measure Itself” in The New Yorker traces the cultural mechanism that makes all four feel like good work even when the firm gets nothing back.
When should you ask AI for help, and when should you not?
Ask AI when you have a written record of the week and want a second opinion that is not socially calibrated to spare your feelings. Paste a week’s calendar plus your sent folder summary into a model, and run the three-question audit: who paid for this (literally, or in trust), what did you learn, what did it move. The model gives a flat answer because it has no stake in your identity.
A human team will soften the blow because they like you and have to work with you tomorrow. The first question of the weekly audit is the same question a manager would ask if your time were billed back to a client. Do not ask AI to cut for you. The decision to remove a piece of work is a leadership decision, not an analysis decision. The model can spot the candidate. The founder has to take it out of the diary. And do not run the audit for one week and act on it. One bad week is a bad week. Three weeks is a pattern, and a pattern is what a defensible cut needs.
What separates zero-earn work from long-cycle work?
Long-cycle work pays back over years, and the audit will misread it as zero-earn if you let it. A standing investor update that gets skimmed today buys you a faster fundraise in eighteen months. A Monday team huddle that produces no decisions today builds the operating rhythm that lets you step away in two years. The discipline that separates the two is a written prediction.
Before you decide a piece of recurring work is zero-earn, write down what you expect it to produce, by when. If the date passes and the prediction has not landed, it is zero-earn and you can cut it cleanly. If something has shifted, it was long-cycle and worth keeping. The written prediction is the bit that stops the brain rewriting history to protect the effort already spent. The Founder Freedom Programme reading of the second AI conversation puts long-cycle work inside the Do quadrant deliberately, because it is the work the founder is still the right person to perform. James Clear’s identity-based habits framing names the mechanism: the founder’s identity is wrapped in the effort, and the audit asks more of you emotionally than logistically. The slowness of the cut is what earns the win.
A practical add-on. Keep a one-page log of every cut you make, with the date, what you expected to feel different, and the prediction date. Three months later the log is a calibration tool. The cuts that held without anyone noticing teach you what the audit reads accurately. The cuts that quietly came back teach you where your judgement still beats the model. Both readings make the next quarter’s audit sharper, and the discipline of writing the prediction down is what keeps the cuts honest in a way no AI prompt can replace.
