What your
Friday inbox
will look like.
Give us three priorities you would feed your AOS this week. We will show you what the Friday founder summary would look like in your inbox. One email. What shipped, what is blocked, what needs you.
Four sections. Ninety seconds.
The founder summary is the same shape every week, so reading it becomes a habit, not a chore. It replaces the Monday status meeting, the Slack catch-up, and the Sunday-night dread of not knowing where things stand.
What shipped
Every mission that completed this week, with the one-line outcome and a link to the evidence trail. No status meeting required to know where things landed.
What is blocked
The handful of missions waiting on something: a decision, a vendor, an input only you have. Each one says exactly what it is waiting for.
What needs you
The two or three approval points that hit your desk this week. Money, public claims, customer data, anything risky. You decide; the rest already moved.
What is on deck
The missions queued for next week, so you can redirect before the work starts instead of after it ships.
You do not write the summary. AOS does. Every mission your instance runs leaves an evidence trail, and the operating memory keeps the decisions and rationale behind each one. On Friday afternoon the Chief of Staff role reads the week of trails, pulls the items that actually need a founder, and assembles them into one email.
That means the summary is never a guess or a vibe. It is a read of what the system did, which decisions are still open, and which approval points are waiting on you. The same evidence is one click away if you want to go deeper on any line.