What it reads
- EmailRead-only
- CalendarRead-only
- Slack or TeamsChosen channels, read-only
- CRMRead-only
- Ad accountsReporting only
Open-source playbook · 13 of 20 · For leaders
The first hour of every day goes to working out what changed overnight.
The systemA one-page brief before 9 am: what moved, what’s stuck and what needs your decision today.
// The problem
Every morning starts the same way: open each tool, scroll back to last night, and piece together what changed. By the time you know what needs you, the first hour is gone.
By hand
30–60 minutesOur morning brief
51 seconds// How it works
The dial is the night, from when you log off at 7 pm to 7 am. Each ring is a tool it reads; each dot is something that happened. At 7:00 the hand stops and the brief is written.
7:00 amBrief ready
7:00 am, on your phone
7:00
Morning briefto me · 7:00 am
Needs your decision today
What’s stuck
What moved
Read-only. It never replies, accepts, posts or changes anything.
Sample brief, fictional company.
// Why it’s safe to run daily
The brief is the only thing it ever sends, and it only sends it to you. Every decision on the page stays yours.
Plain-English rules, set once and changed whenever you like. For example:
Day 1
Link email, calendar, chat, CRM and ad accounts with read-only access. Pick the channels it may read.
Day 2
Decide what counts as a decision, what counts as stuck, and what never makes the page. Set the format.
Day 3
Set the time, run it for a few mornings, and cut anything you skipped. Then it runs every day.
// For your tech lead
One of the quickest systems on this list to build. It only reads, so the access is simple and nothing it does reaches anyone else. Most of the work is deciding what deserves a line.
| Job | Use | Or |
|---|---|---|
| Email and calendar | Gmail and Google Calendar | Outlook through Microsoft Graph |
| Chat | Slack, with a read-only app | Teams through Microsoft Graph |
| Deals and ad spend | HubSpot and Meta Ads reporting | Salesforce, Google Ads, LinkedIn Ads |
| Running it at 7:00 am | n8n, on a schedule | Make, Zapier, or a scheduled script |
| Writing the brief | Claude | ChatGPT, Gemini |
| Getting it to you | An email to yourself | a Slack or Teams message to you |
Start simple1 hour
A saved prompt in Claude with its Gmail, Calendar and Slack connectors switched on. You run it when you sit down.
Production2–3 days
n8n runs at 7:00 am, reads the five sources since last night, has Claude sort everything into decide, stuck and moved, and emails you one page.
Custom1–2 weeks
Remembers yesterday’s brief so stuck items show how long they’ve been stuck, adds a brief for each leader, and drops what you keep ignoring.
One person who is comfortable with n8n builds it in two to three days. After that, the leader who reads it owns it: a five-minute tweak each week to what deserves a line, and what doesn’t.
Needs
01Company Brain// Want help building it?
In 30 minutes with our founder, we’ll look at your tools and your week, and work out what your first AI systems should be and how long they’ll take.
Book a Strategy CallPick a time that works
No times are open right now. Please check back soon.
You're booked
While you wait, watch the 13-minute demo