Every Friday afternoon, Evan sits down with a 61-page document.
He didn't write it. His assistant didn't write it. It's completely AI-generated, and it covers his entire upcoming week in more depth than any amount of frantic Sunday-night prep ever could.
I built it as part of a digital chief of staff system we deployed for him. And when I show it to other executives, the reaction is usually the same: “I had no idea this was possible.”
Here's what's actually in it.
What the Weekly Executive Briefing Contains
The briefing starts with a calendar overview for the coming week. Every meeting, every person, what the meeting is about, how it fits into the week's overall shape.
Then it goes deeper. For every person scheduled on the calendar, the AI has pulled background: who they are, their recent activity, the relationship history between them and Evan, and anything relevant from prior email threads. It flags key opportunities — deals in a certain stage, relationships that need attention, follow-ups that have gone cold. It flags risks — schedule conflicts, back-to-back meetings without buffer, anything that could derail the week.
There's a visual summary too. A quick graphic that shows at a glance how the week is loaded, where the heavy days are, where there's breathing room.
Evan reads the whole thing in about 30 minutes on Friday afternoon. Then he goes into the weekend knowing what's coming.
Why Friday Instead of the Night Before
Most executives do their meeting prep the night before, or sometimes the morning of. That's fine for one meeting. But when you have 15 or 20 meetings in a week, doing individual prep the night before each one means you're never really ahead. You're always in catch-up mode.
The shift to a Friday briefing is about batch processing. AI is very good at research and synthesis. It's not ideal at doing that under time pressure while you're already in back-to-back meetings and trying to mentally be somewhere else. You want the AI doing the research when you have time to set it up properly — not at 10pm when you're trying to remember what you know about someone you're seeing at 9am tomorrow.
One batch. Friday. Whole week done.
How to Define What Goes In It
Before building this for any client, I ask one question: “If your upcoming week went perfectly, what would it look like?”
That sounds simple, but most people have never actually articulated it. They can describe a bad week pretty fast. A good week takes more thought.
One client — a VC named Evan — said he wanted to walk into every meeting knowing the person's background without having to Google it the morning of. He wanted to see relationship flags (who had he been meaning to follow up with, who had referred whom). He wanted a clear view of schedule density so he could plan his energy, not just his time.
Those three things became the blueprint. Everything in the briefing traces back to that original answer.
The AI design principle here is what I call Agent Design Backwards: start with the end state, then build back to the inputs and triggers that produce it. If you start with the tool “what can AI do?”, you end up with a document no one reads. If you start with the outcome (“what does a perfectly prepared executive look like on Monday morning?”), you build something that actually gets used.
What This Is Replacing
It's worth being clear about what the briefing replaces, because it's easy to assume nothing like this existed before.
It's replacing 45 minutes of scattered googling before each meeting. It's replacing the email archaeology that happens when you're trying to remember where a relationship stands. It's replacing the low-level anxiety of knowing you're going into a week underprepared — or the higher-level anxiety of realizing that in real time, mid-meeting, when someone references something you should have known.
For executives who had human assistants doing some of this prep, it's replacing the parts that are research-heavy and time-consuming. The EA can shift to higher-judgment work. The briefing handles the information gathering.
Building Your Own Version
The setup is not as complicated as a 61-page document makes it sound.
At the core, you need a system that runs on a schedule (Friday evening works well), pulls from your calendar and email, and generates structured output in a format you'll actually sit down with.
Start smaller. One client built a version that just does contact research — pull the calendar for next week, pull LinkedIn and email context for every person listed, generate a one-paragraph brief per meeting. That's useful as a first step and builds the habit of reading a briefing before the week starts.
Add depth once you have the habit. Opportunity and risk analysis, schedule density views, relationship flags — those can come later. What matters first is getting into the ritual of reviewing your week before it starts, not the night before each meeting.
The first time Evan saw the briefing, he asked how long it would take to set up. I told him a few days to build, a few weeks to calibrate. He's been using it since December and hasn't gone back to Sunday-night prep.
61 pages sounds like a lot. But when you know what's coming, it's just clarity.
