The AI Employee That Updates My AI Brain Every Night

Everyone's building AI brains at the moment. Folders of documents, a hundred pages that explain the business, the clients, the offers, the voice. I've built one, I've written up how to build one, and it's the best thing I've done for my business this year.

Nobody talks about what happens the day after.

Because a business changes every single day. A client call moves a project on. A task gets closed. A decision gets made in a chat at 4pm and never written down anywhere. And every one of those changes makes the brain a little more wrong, until three weeks later Claude is confidently telling you about a client situation that stopped being true a fortnight ago.

I wasn't going to update a hundred documents by hand every night. So I built an employee whose only job is to do it while I'm asleep.

What it does

Every night at 10:30 it wakes up and reads the day:

• Every Claude chat I had that day. What was done, what was decided, what got stuck, what got produced.
• ClickUp. Every task closed today and every task updated today, across every client list.
• Every file I created or changed that day in my working folders.

Then it writes it down, in the right place:

• Each client's daily log gets a new entry for today: what was done, decisions, blockers, outputs with links, tasks closed. It adds to the log; it never overwrites one.
• Each client's status page gets rewritten so it's true as of tonight. Where we are, what's next, what we're waiting on, the last three things done.
• My index gets the one-line status and "last updated" for every client it touched.

And if it finds something it can't place with confidence - a chat that might be about two clients, a file with no obvious home - it doesn't guess. It writes one line into a "for review" file and leaves it for me. Wrong information in the wrong client's file is worse than no information, so the rule is that it never guesses.

It never writes to ClickUp. It never invents anything. It reads and it files.

Why this is the employee everything else depends on

The reason I call this one my secret weapon is that every other thing I've built reads from what it writes.

My morning brief reads the client status pages to tell me where every client is. My call brief reads the last meeting and the open actions before every call. The writers read the client folder before they draft anything. If those files are stale, all of it is confidently wrong.

So the nightly updater isn't a nice-to-have. It's the thing that makes the brain a brain rather than a snapshot of the week you built it.

The routine

This is a routine - a skill on a timer. If you haven't set one up before, here's how routines work. This one is the chore type: one fixed job, every night, and it writes.

Open Claude, and paste this:

Set this up as a routine that runs every night at 10:30.

You are my Knowledge Base Updater. Your job is to read what happened
today and write it into the right client's files in my AI brain. You
never invent anything and you never write to ClickUp.

My AI brain is at [FOLDER PATH]. Each client has a folder at
[PATH]/clients/[client name]/ with a daily-logs folder and a STATUS.md
file. My index of clients is at [PATH TO INDEX].

Read, every run:
1. Every chat I had with you today: what was done, decisions, blockers,
   outputs created (with file paths or links). Summarise, never paste.
2. ClickUp: every task closed today and every task updated today, on
   every client list.
3. Every file created or changed today under [WORKING FOLDER].
4. Each touched client's current STATUS.md.

Mapping rule: something belongs to a client only if my index confirms
it - the chat is clearly about them, the task is on their list, or the
file is already in their folder. If you're not sure, it's UNMAPPED. Do
not guess.

Write, for every client you can map:
1. daily-logs/[today's date].md - create or ADD TO, never overwrite:
   what was done, decisions, blockers, outputs with links, tasks closed
   (name and link), tasks created (name and link).
2. STATUS.md - rewrite in place, one page: Where we are · What's next ·
   Waiting on · Open risks · Last 3 things done (dated).
3. The index - update only that client's one-line status and "last
   updated". Touch nothing else in it.

Anything unmapped: one line each in [PATH]/for-review/UNMAPPED-[date].md.

Rules: never write to ClickUp. Never invent. Never write passwords or
keys anywhere. If a read fails, note it in that client's log and carry
on - never abandon the run. Finish with a six-line report: clients
updated, files written, unmapped count, failures.

Claude sets it up and tells you when it'll first run. The next morning, open one client's status page and read it. If it's true, you've got an employee. If it's guessed something, tighten the mapping rule and run it again.

Three things that took me a while to get right

Add to the log, never overwrite it. The first version rewrote the day's log each time it ran, and if I'd written a note earlier that day, it was gone. Logs are only ever added to. Status pages are the thing that gets rewritten.

The mapping rule is the whole employee. Without it, the updater will file a chat about "the website" under whichever client had a website most recently. With it, that chat goes to review and I spend ten seconds a week sorting the pile. Ten seconds a week is a very good price for never having wrong information in a client file.

It runs late, on purpose. 10:30 at night means the day is actually over. Everything I did is in. The morning brief runs at six and reads what this wrote, so I open the laptop to a picture of yesterday that I didn't have to make.

Start with one client

If you've got an AI brain and you've never updated it, it's stale now. Don't try to fix the whole thing. Set this routine up, point it at one client folder, and let it run for a week. Read that client's status page each morning.

Once you trust it for one, point it at all of them. And then build the things that read from it - the morning brief, the call brief - because now they'll be reading the truth.

If you haven't built the brain yet, that's step one: The Co-Founder Setup. The client folder structure in there is exactly what this employee writes into.

And if what you want is the whole system - the pricing, the positioning, and the tech and AI that lets you run a business on three days a week - that's what I teach.

Watch the free training →