Your first overnight agent gets one job. Not a second employee. Not “run my life.” One recurring chore that already happens every week, with a clear done, that you keep doing badly at 11pm. Invoice reminders. A Friday status. A first draft of the same newsletter. Then you stop adding work.
Work less, ship more — a six-part series. 1. Sunday setup · 2. Don’t open Slack first · 3. Leave the meeting when it ends · 4. Write once, ship five times · 5. Your first overnight agent · 6. The 4-hour Friday
This is part 5. It sits on the Sunday setup and the overnight brief. The brief is a note you read in the morning. The agent is a chore that finished while you were gone. If you skip to this post without the four buckets, you will build a babysitting hobby.
Pick the chore like a cheap employee
It qualifies if all four are true:
- You already do it on a rhythm (weekly is perfect)
- Done is obvious (sent, filed, sitting in the dump as a draft)
- A wrong answer is annoying, not fatal
- You can check it in under five minutes
Good: “Every Thursday night, draft the Friday client status from this week’s dump and calendar, leave it in the dump, do not send.”
Good: “Every Monday at 6am, list invoices older than 14 days from this sheet / this label, draft three reminder emails, do not send.”
Good: “Sunday 8pm, turn the dump into a 400-word newsletter draft. Leave it. I ship it.”
Bad: “Handle my email.” Bad: “Keep the blog going.” Bad: “Be my chief of staff.” Those are jobs. Jobs need a human in the loop all day. You are trying to work less.
The contract you pin
Whatever runs overnight (Grok Bot, Gemini Spark, a scheduled Claude, Claude Code on a timer, even a calendar reminder that opens the same chat) gets a written contract. Not vibes.
You have one job: [chore]. You run [when]. You write the result to [dump / draft folder / this thread]. You do not send, post, pay, delete, or message anyone. You do not start a second chore if you finish early. If you are missing a fact, you write [NEED] and stop. I will review in the Start block. Protect my stop time. This is not a request for more work.
The “do not send” line is the whole safety system. Drafts multiply your morning. Sends multiply your incidents. We already watched what happens when agents share a machine and get fuzzy goals. Do not give yours fuzzy goals.
Three ways to run it, same contract
Path A — no new product. A recurring calendar event: “Run the Thursday status.” When it fires, you (or a shortcut) paste the week’s dump + calendar into the same chat with the contract. If you are already in bed, that is Path B.
Path B — a teammate that can wake up. Grok Bot, Spark, a scheduled Claude, whatever you already have that can run without you. Point it at the dump and the calendar only. Not at all of Slack. One output, one place. We used a teammate for a day on this blog; the useful version was scoped. The useless version would have been “go be a blogger.”
Path C — Claude Code auto, for a repo chore. If the recurring work is “open the weekly notes file and draft the changelog,” auto mode can sit on it overnight. Same contract: write a file, do not push, do not email. Auto mode is a permission setting, not a manager. You still name the one job.
Pick the path you already pay for. Switching tools is a second chore.
The five-minute morning
Start block. Open the dump, not Slack. The agent either:
- left a draft worth sending after one pass, or
- left a [NEED], or
- went wide and wrote you a strategy memo
One and two are success. Three means the contract was too polite. Tighten it. Do not “improve” the agent by adding a second job so it feels useful. If the draft is good, ship it with write once, ship five times if it has to go to more than one place. Then stop.
If you spend more than five minutes fixing the draft, the chore was too big. Cut the output in half next week. A short status that exists beats a perfect one you rewrite by hand.
When to add a second chore
Not this week. Not when you are excited. After three clean runs of the first one, with no babysitting. Then you may add a second recurring draft, still no-send. Two chores that finish themselves is a staff. Six half-wired automations is a second job with worse benefits.
If you want a number: one overnight chore per month of using the Sunday setup, max. Most people should stay at one through the quarter.
Do this Thursday
Write the contract for the thing you already dread. Put the calendar invite on it. Run it once while you watch, then once while you sleep. In the morning, send or delete. That is the whole post.
The setup made the buckets. The brief protects the morning. The meeting leave-behind protects the afternoon. Write-once kills the rewrite tax. This one buys you a night. Next: the 4-hour Friday — what the agent owns over the weekend, what you refuse to touch, and how Monday starts from the brief instead of the wreckage.
Work less, ship more — a six-part series. 1. Sunday setup · 2. Don’t open Slack first · 3. Leave the meeting when it ends · 4. Write once, ship five times · 5. Your first overnight agent · 6. The 4-hour Friday
Share this article
Leave a Reply