Skip to content
AISCREENCASTS
Back to library

Five Lessons From Building Your Daily Briefing

The daily briefing track wraps with the five lessons that matter and the reusable pattern behind them: build a tracker, let Claude fill it, put it on a clock, synthesize across trackers. Next stop: your sales pipeline.

Full transcript +
Here's the full package. Flags are at the bottom for review before publishing. Cleaned Transcript Let's step back and take a look at what you've built. Every morning, you can get up, go to Notion, and click on your daily briefing on your phone, your iPad, your desktop, whatever. Eventually you'll have months filled where every day has a briefing just like today. And it's going to tell you what's going on. It shows me what the weather's going to be like, what kind of day I have, the top three things that need my attention, the meetings I have coming up, everything else. And remember, these derive from the daily email and daily calendar triages that we're running. And we've only scratched the surface. We haven't connected this to CRMs. We haven't had it start pulling LinkedIn profiles for people we're meeting with. We haven't had it start doing prospecting. We are just scratching the surface of what this tool can do. And for what we pay for it, if this is what three tasks do, imagine what happens when it's doing 30. I have literally replaced my virtual assistant with a virtual AI assistant using this methodology. And I'm going to show you exactly how as we continue to build these videos. Now, I promised you no hype. So let me just tell you: your first week, it's not going to be perfect. You're going to get things you don't want or don't like, or they'll be formatted in ways you didn't ask for, in orders you weren't expecting. And that's okay. Because we get to go back into the scheduled task. We get to go back into our daily briefing. I can go into my last run and say something like, "Update my daily brief to include a table of all the relevant data I'll need to skim my day. Put this at the top of the report." And I can now start adding tabular data. I can start saying I want more verbose summaries, or more succinct summaries. I can tell it to go look at different reports as we add them. We're going to continue to grow this thing. A couple of things I want to go back over from this track. A couple of things that we learned. First, connections are introductions. Microsoft, Google: you make the handshake. You introduce them. And after that, we're not putting passwords in chat windows. We're not ever putting passwords in chat windows. The plumbing just disappears and they're just connected. Second, our calendar is commitments, not blocks. Now everything reads like commitments. It reads like to-dos. It reads like I'm talking to somebody who's managing my calendar for me. Third, I can update these. Like "add an At a Glance to the top of today's briefing: both meetings and open blocks." Claude asks, "Want me to update the scheduled daily briefing task so every future briefing starts with this?" If I like the way it went, I say yes, go ahead. So the third thing is that we can update these, and everything is flexible. These aren't databases or spreadsheets. These are just things that serve us. Fourth, we use gatherers and we use writers. Every task does one thing and does that one thing really well. That's what we did during this track. And fifth, lastly, we want all of this to aggregate into one place. Even though we'll have a lot of workers all doing different things, they're all going to bubble up to synthesizers, just like our daily brief. So let's say we want to update this task. Remember, I said yes. It's showing me what the update is going to look like. I give it permission to update, and from now on this daily task will continue to include that. And that's a big part of what we're going to be doing. You can update the way your email triage works. You can update the way your calendar triage works. And it will automatically make sure your daily briefing is updated, because it goes and pulls that synthesized data and continues to synthesize it further. So that's the pattern. Build a tracker. Let Claude fill it. Put it on a clock. Build a reader that synthesizes across trackers. And now that we've run that pattern twice, once for email, once for calendar, the third time isn't a lesson. From now on, it starts becoming a habit. Here's what I want you to sit with while we close. Nothing about that pattern says email, and nothing about it says calendar. So what's the most valuable list in your business? For most of you, it's the same answer: your pipeline. Leads, deals, the people, the prospects, the follow-ups, the conversations. The ones that quietly cost six figures and never show up on a P&L, because lost deals don't leave a line item. They just slip through. So we're going to make the same move. We're going to start tracking prospects and customers, and letting Claude, our assistant, work from our inbox to our meeting notes, from the web to our calendar, building us briefings and insights so we can stay proactive instead of reactive, and work on the things that are best for us to do as humans. Our calendar tells us where our time goes. Our pipeline is where our money comes from. And we're going to start working toward that in our next track. Here's what I want you to think about as we leave. You didn't become a Notion person. You didn't become an AI person. You've become someone with a staff that is working for you while you sleep. Now let's point our staff toward sales. See you there.

This episode closes out the daily briefing track. Jason steps back to review what's been built: a Notion daily briefing, generated automatically every morning, that pulls weather, priorities, and meetings from the email and calendar triage tasks running on a schedule.
He covers the five lessons from the track: connections are introductions (no passwords in chat windows, ever), calendars are commitments rather than blocks, briefings are living documents you refine with plain requests, every task should do one thing well (gatherers and writers), and everything should aggregate up to a synthesizer. He also demos the honest reality of week one: outputs won't be perfect, and the fix is a plain-English request to the scheduled task, which then updates every future run.
The episode ends with the pattern named explicitly (tracker, clock, synthesizer) and a preview of the next track: applying the same move to the most valuable list in your business, your sales pipeline.