Daily briefing — inbox, calendar, Slack, actions

Three tabs before the first meeting

The first half hour of a founder’s day tends to go the same way. Open Gmail to see what came in overnight. Open the calendar to see who you’re meeting and when. Open Slack to catch the threads that moved while you were away. Then hold all three in your head at once and decide what actually matters before the first call.

None of it is hard on its own. It’s the stitching — three tools, three contexts, and the work of turning them into one clear picture of the day. That picture is what you actually want. Assembling it by hand is the part that quietly eats the start of every morning.

What the one-pager shows

The workspace produces a single morning page. At the top, the meetings on today’s calendar, each with the likely topic drawn from the most recent email thread with the people in the room. Below that, the inbound emails still waiting on a reply from you, with the ones that have been waiting longest surfaced first. At the bottom, the action items left open from yesterday — the things you said you’d do and haven’t closed out.

It reads from the channels you already live in. Your Gmail inbox, your Google Calendar, and the Slack channels you’re part of — the same inbox, calendar, and conversations you’d be checking anyway, not a separate system you have to feed.

From three channels to one morning page

1. Every morning, before you start. At the time you set, the workspace assembles the briefing on its own — you don’t have to ask for it. It’s waiting by the time you sit down.
2. It scans your inbox. The assistant reads the Gmail threads that landed since yesterday, narrows them to the ones that look like they need you, and pulls out the ones still owed a reply.
3. It reads the day’s calendar. It lists today’s meetings and, for each, finds the latest email thread with the attendees so the briefing can name the likely topic instead of just the time.
4. It pulls the Slack highlights. It reads the high-signal messages from the last day in the channels you’re part of — the decisions, the questions aimed at you, the threads that moved without you.
5. You review, then it posts. The briefing lands as a draft for you to read first. Once you approve it, the assistant posts the day’s plan to Slack so the people who need it see the same picture you do.

Time, filters, and the channel it posts to

• Briefing time — set when the page gets assembled. Earlier for a pre-coffee read, later if you’d rather it catch the first messages of the morning.
• Inbox filter — the email scan uses Gmail’s own search, so you can narrow it to a sender, starred threads, or a recent time window to control what makes the briefing.
• Calendar to read — point the briefing at your primary calendar, or a separate work calendar if that’s where the meetings live.
• Channels it reads — choose which of your Slack channels feed the highlights, so the briefing stays on the rooms that matter and skips the noise.
• Where the plan posts — pick the Slack channel, or a message to yourself, that the approved plan goes to once you sign off.

Change the time, the filter, or the channel

The briefing keeps the same shape every morning — meetings, replies owed, open actions — and that steadiness is the point: a dependable read on the day, without you rebuilding it by hand. What you change is the description behind it. Move the briefing earlier. Tighten the inbox filter to the senders you actually act on. Add or drop the Slack channels it reads. Send the approved plan to a different channel.

You described a morning routine, not a script that checks three services and formats a message. The workspace turns that description into the page you read each morning — and when your channels or your cadence change, you change the description, and the morning page follows.