Your daily executive brief, assembled before you wake up

A scheduled AI job that runs before you wake, reads your inbox and calendar, pulls the one metric you watch, and leaves a single-page brief waiting for you, so your day starts oriented instead of scrambling.

What you'll have when you're done

A one-page brief in your inbox or a doc every morning, assembled while you slept: what came in overnight that needs you, what today's calendar holds, the key number you track, and the two or three things that need a decision. You start the day with the whole picture on one page instead of reconstructing it across five apps. This is your first scheduled AI workflow, the jump from "I prompt it" to "it runs on its own."

You spend the first 30 minutes of every day reconstructing the picture

The morning scramble is universal: open email, scan calendar, check the dashboard, try to remember what was unresolved yesterday, and slowly rebuild a picture of where things stand before you can actually decide anything. That reconstruction happens every single day and it is pure overhead. The information is all there; it is just scattered, and assembling it is a job. I used to do this across five tabs with a coffee, and by the time I had the picture assembled, half my freshest hour was gone, spent gathering instead of deciding. The galling part was that the gathering produced nothing new. It was the same five sources, every morning, that a machine could have stitched together while I slept.

It is a job a machine can do at 5am. A scheduled Claude routine can read your connected inbox and calendar, pull a metric, and write the brief before you are awake. This is the same harness idea behind everything else on this site, a cron-scheduled job doing work on your behalf, applied to your own morning. The one discipline: treat the brief as a sharp draft, not gospel, because an automated summary can miss a thread or misread a number.

What you need first

• Claude Code with routines, the scheduled-task feature (launched as a research preview in April 2026). Cloud routines run on a schedule even with your laptop closed.
• Connectors for the sources: Gmail and Calendar, and optionally a metric source (a Stripe export, a Google Sheet).
• A business plan, since the brief reads sensitive inbox and calendar data.
• An output destination: an email to yourself, or a doc the routine writes to.

Step-by-step

Step 1Build the brief as a prompt first

Before scheduling anything, get the brief right as a one-off prompt:

Assemble my daily executive brief as one page:
1. Overnight email that needs me (sender, one-line, why it matters).
2. Today's calendar with the 1-2 meetings that need prep flagged.
3. [Metric]: today's number vs yesterday, one line on the move.
4. Open decisions: anything waiting on me to decide.
Keep it scannable. Flag anything urgent at the very top.

Run it manually a few mornings until the format and content are exactly what you want. Here is the shape you are aiming for, illustrative:

☀️ Tuesday, June 2

⏰ Urgent: Acme's renewal is up Friday and their champion has gone quiet, four days no reply. Worth a personal nudge today.

Overnight email (3 need you)

• Lead investor replied on terms, wants a call this week. [thread]
• Top candidate cleared the reference check, asking about timeline.
• A support escalation; the team lead cc'd you.

Today

• 10:00 Acme renewal (prep flagged, see urgent).
• 2:00 product review. 4:00 1:1. Open gap 11-2, good for deep work.

Revenue (MTD): $128K vs $119K same day last month, +8%, on two enterprise closes.

Open decisions: pricing change (6 days waiting); approve or punt the conference sponsorship.

One page, sixty seconds, and you are oriented. The urgent line at the top is the highest-value habit in the whole brief: it catches the quiet-champion-before-renewal pattern that you would otherwise notice on Friday, too late.

Step 2Turn it into a scheduled routine

Once the prompt is dialed, set it as a Claude routine on a daily trigger (say 5am). Use a cloud routine so it runs whether or not your machine is on. Note the practical limits: routines run no more frequently than hourly, and a short daily run costs roughly eight cents of routine time plus tokens, trivial for the value, but worth knowing it is not free.

A couple of scheduling specifics save a confusing first week. Set the trigger to your timezone and pick a time that gives the job a buffer before you actually look, 5am for a 7am reader, so a slow run or a retry still finishes in time. The cloud-versus-local distinction is the one people trip on: a local routine only fires when your laptop is awake, so the morning you most need the brief (you slept in, lid closed) is the morning it silently does not run. Cloud routines run server-side regardless, which is the whole point of "assembled before you wake up." If your brief mysteriously stops appearing, this is the first thing to check.

Step 3Scope the credentials tightly

A scheduled job that reads your inbox needs stored access, so scope it to exactly what the brief needs and no more. This is standard hygiene for any routine that runs unattended with your credentials: least access, and review what it can reach.

Step 4Read it as a draft, not gospel

The brief is a fast, usually-right summary, not an oracle. It can occasionally miss an email or misstate a number, so use it to orient, then trust your own eyes on anything that drives a real decision. The brief tells you where to look; it does not replace looking.

Step 5Tune it over a week

The first week's briefs will be slightly off, too long, missing a source you wanted, flagging the wrong things. Adjust the prompt as you go. The tuning is concrete and fast: if it buries the urgent item, add "the single most time-sensitive thing always goes first, in bold"; if it pads, add "no item gets more than one line, no preamble, no sign-off"; if it flags routine newsletters as needing you, give it examples of what to ignore. Keep a running note of each miss and fold the fix into the prompt the same morning. After a week of that, it converges on exactly the page you want waiting every morning, and from then on you are reading a brief, not building one.

How you'll know it's working

Your mornings start with a decision, not a reconstruction. The 30 minutes of "where do things stand?" collapses into a two-minute read of a page that is already assembled. And you stop missing the overnight thing that needed you, because the brief surfaced it at the top before you even opened email.

When it breaks

• The routine did not run. Check it is a cloud routine (a local one needs your machine awake) and that the schedule and credentials are valid. Routines reject sub-hourly schedules.
• The brief hallucinated or missed something. This is why Step 4 matters, it is a draft. If it is consistently wrong on a source, that connector may be misconfigured.
• It is too long. Tell it to be ruthless: top items only, one line each.
• Credentials feel over-scoped. Tighten them. An unattended job should have the minimum access that produces the brief.
• The metric line is wrong or stale. The metric source is the part most likely to break quietly, a Sheet that moved, a Stripe export that changed shape. Have the brief print the timestamp of the data it pulled, so a stale number announces itself instead of hiding.
• It surfaces the same "urgent" item for days. Something is genuinely stuck (a decision you keep deferring), or the brief cannot tell resolved from open. Tell it to note how long an item has been waiting, which turns nagging into useful pressure.

Make it yours. The brief should mirror what you actually decide on. A sales-led CEO wants pipeline movement and at-risk renewals up top; a product CEO wants usage metrics and the support-escalation count; a fundraising CEO wants investor-thread status and runway. Add or drop sections until the page is the exact set of things that, seen together, tell you how the business is doing this morning. And if you run other routines, have the brief fold in their output too, so the one page is genuinely the only thing you need to read to start the day oriented.

Where this fits in your harness

This is the capstone of the daily-operations cluster: it pulls together inbox triage, the calendar review, and your metrics into one morning page. It is also your first real scheduled routine, the conceptual bridge to running parts of your business on autopilot (the same pattern powers a competitor-monitoring routine). It anchors the five workflows every CEO should install first.