If your team's status meeting could be replaced by a well-written email, it should be replaced by a well-written email.
Most founder-led companies between five and forty people have a standing leadership meeting on the calendar. Tuesdays at 10. Sometimes Mondays. Sometimes Fridays. Always 60 minutes. Usually 75. Always starts seven minutes late.
Most of those meetings exist because the founder felt out of the loop at some point and the meeting was the proposed fix. The meeting became a habit. The habit became the calendar.
The Friday summary inside AOS is meant to make most of those meetings cancellable.
What lands in the inbox
Roughly eight minutes of reading. What shipped this week, grouped by department, with the mission it came from and the reviewer who signed off. What is blocked, with the specific reason and the date the block started. Anything blocked more than seven days gets a red flag at the top.
The two or three decisions waiting on you, each with a recommendation and the alternative. You can usually reply yes or no in the email itself.
The metrics that moved this week with last week as context. Customer count. ARR. Mission completion rate. Approval queue depth. Customer-facing error rate. No vanity numbers. If it does not change what you would do this week, it is not in the summary.
One sentence on what the system remembered this week that it did not remember last week. That line is the difference between this and a Notion dashboard you keep meaning to open.
What I cut from the draft
Forecasts. The forecast was either obvious (you already knew) or aspirational (the system was wishing). Neither helped.
Personnel observations. AOS is not your HR system, even when part of your team is agentic. Performance conversations happen in the right channel, not in a Friday email.
Status of work with no blocker and no decision. The agents shipped it. The reviewer approved it. You do not need a brag list every Friday.
How it gets written without asking you anything
Every mission already has structured outputs. Artifacts, reviewer, status, gates touched. Every gate decision has its own log of asked-replied-rationale. Every blocker has a timestamp and an owner. The summary is a query against work that already happened, not a creative exercise.
Thursday night the CEO agent drafts it. Friday morning the Office of the CAO reviews for tone and completeness. 4pm local time the summary lands.
You do not write it. You do not edit it. Read in eight minutes. Click into two or three things for context. Reply yes or no on the decisions waiting. Done.
What changes about the calendar
The Tuesday standing meeting is usually the first to go. Most founders I have shipped to cancelled it inside three weeks. The team agreed almost immediately once they saw the summary doing the job.
What did not get canceled: the customer conversations, the strategy sessions, the rare cross-department working session where a real decision needs five people in a room. Those still happen. They happen because someone proposed them in the summary, not because they were on a recurring invite.
Most founders end up with one or two standing meetings a week. Both with people. Both because they want to.