A night-shift job starts itself, does the work unsupervised, and leaves a finished draft where you will find it. Your involvement moves from the front of the job to the end of it. The part people drop when they build this is the approval step, because it feels like it defeats the purpose. It does the opposite. I am willing to let jobs run unsupervised precisely because nothing escapes without me reading it first. Remove that and you can only safely schedule trivial work, which was never the work eating your week. What is in the guide Part One: ChatGPT and Claude both run scheduled tasks now, and there is a prompt block on page four you can paste straight in. It includes the one line that makes the difference between a job that finishes and a job that sits there waiting: explicit permission to make assumptions instead of asking you a question at 4am. Part Two: The four parts every job needs, two kinds of trigger and when to use each, and four failure modes that each cost me a week. One of those is worth the download on its own: my first version decided a new article was due by checking when I last published, which meant drafts waiting for my approval never counted as done, so it wrote me a fresh one every session while three unread ones piled up. Mark when the work is finished, not when it goes live. Last page is a worksheet. Fill it in before you build and the build takes an afternoon. Try one and tell me what happened Pick the job you do at the same time every week and resent doing. Not the most important one. The one you keep putting off because it is tedious and you already know exactly how it goes. Then drop a comment with what you put on the night shift and what came back. The failures are more useful to the rest of us than the wins, so post those too.

The setup guide for building your own AI executive assistant has been rebuilt, and the new version is attached to this post. The old one had two problems. It was written to follow along with a call, so the sections had video timestamps in them and it read strangely on its own. And the most important part, the big setup prompt, lived on my site as a link. If you came across the guide later, or forwarded it to someone, that link was easy to miss and the guide stopped working without it. Both are fixed. It is now one self-contained document. The full setup prompt is Appendix A at the back, so you copy it straight out of the PDF and paste it into Claude Code. Nothing to go hunting for. I also stripped it down so it is not branded to me or to this group. No logos, no references to our calls, and the examples are generic business examples instead of listing appointments and showings. That was deliberate. Several of you run teams, and a few of you have people who would use this. You can now hand this PDF to an assistant, a partner, or another agent, and it will not look like you passed along somebody else's marketing. What is inside: - Parts 1 to 3: install Claude Code, create your project, run the interview that teaches it your business - Part 4: your first skill (a daily brief) and your first sub-agent (call prep) - Part 5: how to keep it useful over months instead of abandoning it in week two - Part 6: connecting Gmail, Calendar, and Drive so it can actually send the email, not just draft it Set aside 30 minutes for Parts 1 through 3. That is enough to have something working. Part 6 is the technical one. It involves a few Google settings pages you have probably never opened. Every step is written out and every error I have watched people hit is in the troubleshooting section at the end of it. Take it slowly and it is fine. One suggestion. Do not skim the interview in Part 3. That is the part that decides whether this thing is useful to you or generic. The more real detail you give it about your business, your team, and what you are actually working on, the better everything downstream gets.