AI / 02 of 08
Daily Briefs
Every morning, wake up to three things that are pressing, which require your input and your main objective for the day.
How it runs
Trigger
Weekday trigger
Step 01
Check roles, skip any missing
Parallel — 5 jobs
- Calendar: today and tomorrow
- Email asks you never answered
- Chat mentions and DMs, 2 days
- Per-project prep for tomorrow
- Your asks that never came back
Verify gate
Open each thread, drop if done
Step 02
Sort: needs attention, resolved
Step 03
Classify day: heavy, normal, open
Step 04
Render one self-contained page
Step 05
Screenshot check before sending
Outcome
Brief delivered
What it is
One page each weekday morning: the shape of the day drawn from your calendar, the few things genuinely blocked on you, and what closed overnight without needing you.
You need this if your first hour goes to reconstructing the day across a calendar, an inbox and four Slack channels, spending your most expensive hour on retrieval.
Digests get ignored by week two because they surface everything.
This one opens each thread first and drops anything you already replied to, so the list stays short enough to be true.
The actual build
What it does for you
Every item has been checked against the thread it came from
so you never open the brief to find three things you already handled.
Tomorrow's prep surfaces today
meaning the doc to skim or the decision you'll be asked for, so you walk into meetings holding something.
The shape of the day arrives as one drawing before you read a word
so by 8am you know whether today is a maker day or a manager day.
Built and running
Built internally for the business. Runs as a recurring weekday routine.
How to build it
- Connect a calendar, an inbox and a chat tool, and let the page skip any role that isn't connected
- Pull one calendar fetch covering today and tomorrow, since tomorrow is what makes prep items possible
- Pull email threads where you were asked something and haven't replied, plus chat mentions from the last two days ending in an unanswered question
- Ignore group @-mentions and team aliases, because if anyone on the list could answer it you aren't the bottleneck
- Open each candidate's own thread before listing it and drop anything you already replied to or reacted to
- Sort what survives into two lists, one for what costs you something if ignored and one for what someone else closed, then drop the rest silently
- Classify the day from the calendar alone, render one self-contained HTML page, and screenshot it before delivery
Want this one built into your business?
Thirty minutes, no deck. We map what you run today and tell you what it would take.