By eleven on Tuesday you have re-pasted the same three paragraphs of background into a chat for the third time this week, because the assistant that felt like a hire on Monday remembers nothing by Wednesday. The draft it handed back was confident and wrong in exactly one place, so you read the whole thing again to find which place. A report you automated back in spring broke overnight when the source quietly renamed a column, and you spent twenty minutes locating the rule and nudging it back into line. None of that was the work. You would not put a single line of it on a timesheet. It still ate the morning.
Here is the claim, and you are allowed to disagree with it. The AI tools you adopted this year did not give you time back. They handed you an unpaid operations job, and the only reason it feels free is that the bill is paid in minutes nobody counts.
Automating a task never deletes the task’s labour. It changes what the labour is. The machine takes the easy, repeatable middle and hands you back two things: the job of watching it, and the ugly edge cases it was never going to handle. You feed it context. You check its output because you have learned the hard way that you have to, and you patch the thing when the world shifts under it. The tool did the typing. You do the operating.
The tax that hides in small change
People who run systems for a living have a name for this and a budget for it. They call it toil, the manual upkeep that keeps a machine running and produces nothing that lasts, and they consider it corrosive enough that Google’s own reliability teams cap it at half a person’s time and staff whole teams to fight it. Half. With a cap on it, and colleagues to share it. You run your personal stack of assistants with neither. No cap, and a team of one to absorb everything. You pay all of it and call it productivity.
The reason this stays invisible is arithmetic, not weakness. Each individual act of upkeep is genuinely small. Ninety seconds to re-paste the background. Two minutes to re-run a bad answer and skim it for the lie you now assume is in there. Nothing in that is worth objecting to in the moment, so you never object, and because you never object it never lands anywhere you would notice. A cost you pay in loose change, one coin at a time, does not feel like a cost. It feels like the way the work goes now.
And it compounds in the worst way, quietly. Every context-feed and every output-check is a small switch away from the actual work and back, and those switches cost more the less routine the task is. Deciding whether an answer is right is never routine. So the interruptions that look cheapest are the ones landing on the work that could least afford them.
You cannot prompt your way out
The tempting objection is that this is a skill problem. Get better at prompting, write a cleaner setup, and the upkeep shrinks to almost nothing. Some of it will. But look at what you have just agreed to. Getting better at operating the machine is still operating the machine. A sharper prompt is a nicer tool for a job you should not be holding in the first place. The person who tunes their rig until the toil is bearable has not escaped the operator role. They have gotten good at it, which is the same trap wearing a badge of honour.
The way out is not a better prompt. It is a different relationship to the machine. The point was always to direct AI agents, to say what a good outcome looks like, name the handful of moments you want to be asked about, and then have something else carry the upkeep. Not you feeding context at eleven on a Tuesday. Not you reading every output to find the one wrong line. You already know how to work this way, because it is exactly what you do with a capable person you hand real work to. You brief them, you decide the things worth deciding, and the maintenance is theirs.
That is the bet behind be/brief. The operating was never the price of the autonomy. It was the price of hosting the autonomy yourself. Move the toil off your desk and Tuesday reads differently. The report that broke asks you one clear question and then sorts itself. The context is already known. And the morning you spent re-pasting paragraphs into a box is a morning you get back for the work you were there to do.
Brief is opening to a small group at a time. Direct a team instead of operating one more tool.
Request access