The Overnight Queue: How to Put AI Agents to Work While You Sleep

A founder in my coaching group gave Claude Code one command before bed: "Don't go to sleep. Keep going."

While he slept, it reorganized his files and laid the groundwork for training a new agent. He woke up to finished work. On our coaching call this week, he named the feeling underneath the whole experiment: "I need five of me."

I hear a version of that from almost every founder I coach. My answer is a system that works the night shift. I call it the Overnight Queue, and it has become one of the highest-leverage pieces of my entire AI infrastructure.

What is an Overnight Queue?

An Overnight Queue is a running list of tasks that qualify to be executed by AI agents while you sleep. Mine lives in a simple Notion database. Each entry is a piece of work that is fully scoped, needs zero decisions from me in real time, and produces something I can review with my coffee the next morning.

The idea came from an observation on a coaching call. Everyone in the room was using Claude Code daily. Everyone closed the laptop at night. Which means everyone owned tools capable of working 24 hours a day and ran them like a day job.

Running AI agents overnight closes that gap. You design the work before bed. The agents execute while you sleep. You review in the morning. The hours you used to lose become production time.

Why does your business stop compounding when you sleep?

Most founder-led businesses run on the founder's attention. When your attention turns off, the business turns off with it. Content production pauses. Research pauses. The systems sit and wait for you to come back.

AI changed the math on this, but only for founders who write things down. An agent can only run what has been clearly defined. If your processes live in your head, nothing can execute them at 2 AM. If they live in written infrastructure, your business gains hours it never had before.

This is why I tell every founder I work with that written infrastructure is the number one separator in the agentic AI era. It is the one thing that scales. Claude, AI agents, automations, all of them depend on knowledge you actually captured. Write it down once and it works for you every night after.

What tasks qualify for running AI agents overnight?

Only certain work belongs in the queue. Every task has to pass 4 filters:

1. Well-scoped. The task has defined inputs, defined boundaries, and a clear starting point. "Write blog posts from this specific transcript using my keyword database" is scoped. "Improve my marketing" is a wish.

2. Zero real-time decisions. If the agent needs to wake you up to ask a question, the task fails the filter. Everything it needs to make choices has to be written into the instructions before you go to bed.

3. Clear definition of done. The agent should know exactly what finished looks like. A number of outputs, a format, a destination. Vague endings produce vague work.

4. Reviewable output in the morning. The task produces an artifact you can evaluate over coffee. A draft, an organized folder, a research summary, a populated database.

Tasks that pass: drafting blog posts from call transcripts, file reorganization, research summaries, data cleanup, matching content against keyword research, prepping training documents for a new agent.

Tasks that fail: anything touching payments, anything that gets sent to a client without review, anything where the next step depends on a judgment call only you can make.

What can AI agents actually produce overnight?

The first night I ran my Overnight Queue, Claude Code wrote six blog posts.

The pipeline looked like this. It pulled a call transcript from my Notion. It ran my extraction skill to find the strongest teaching moments. It matched those moments against my database of keyword research. It wrote the drafts, then ran a polish pass so every post sounded like me. It dropped the finished pieces into my content library, staged for review.

I woke up, reviewed, and shipped. Work that used to consume an entire week of creation windows happened while I slept.

One thing matters here: overnight work is draft work. I review everything before it goes anywhere public. The leverage comes from waking up at the 80 percent mark, where my only job is the final 20 percent. I bring the vision and the judgment. The system brings the volume.

What separates a workshop from a production line?

Last week I saw that Spotify's chief architect shared how they ship 4,500 deployments a day with 2,900 developers using Claude. He called it their production line.

That framing rewired how I think about my own business. A workshop is where a craftsperson builds one thing at a time. Quality is high. Every build is custom. Output depends entirely on the operator showing up. A production line is a system that ships continuously, whether or not any one person is standing at the station.

Most founders, including me until recently, run workshops. The Overnight Queue was my first real move toward a production line. One connected system where work flows from transcript to draft to library without me touching every step.

You do not need 2,900 developers to live this principle. You need one well-scoped task running tonight.

How do you build your first Overnight Queue?

Start simple. Here is the exact path I give founders:

1. Create the container. A Notion database or even a single document titled Overnight Queue. The tool matters less than the habit.
2. Brain dump candidate tasks. Aim for 10 to 30. Think about admin work, content drafts, research, organization, and prep work you keep pushing to tomorrow.
3. Filter every task against the 4 criteria. Well-scoped, zero real-time decisions, clear definition of done, reviewable output. Cut or rewrite anything that fails.
4. Write each task like a brief for a capable new hire. Inputs, steps, what done looks like, and where the output goes.
5. Run one task tonight. One. Resist the urge to launch all 30 on night one.
6. Review in the morning and tighten the instructions. Every review makes the next run better. This is where the compounding lives.

Within a couple of weeks you will have a queue that earns its place in your business every single night.

What should you do tonight?

Pick one task. Make it small, scoped, and clearly defined. Hand it to your agent before you close the laptop. Review what you find in the morning.

A business that compounds while you sleep is a design decision. You make that decision in writing, one task at a time, before bed.

Your tools are ready to work the night shift. Give them the job.