Agency OS

Agency OS is the operating system a studio opens every Monday. Every client, every engagement, every brief, every handover, every post-mortem lives on one backbone. The client portal, the internal workspace, and the post-mortem archive are the same Notion databases with different permission layers.

You stop running the agency out of Slack threads and Google Drive folders. You start running it out of one workspace the whole team reads the same way.

Agencies scale by repeating work. The same brief template, the same kickoff ritual, the same handover checklist, across 10, 20, 30 clients. The usual failure is each account lead inventing their own version. By the tenth engagement, there are ten different brief formats and the ops lead spends Friday reconciling them.

Agency OS enforces one shape. One brief template, one kickoff page, one weekly status report, one handover checklist. The database is the template. New engagements inherit the shape automatically.

Five databases. Clients holds the account record, the stakeholder map, the engagement history. Engagements holds each active project with scope, budget, and owner. Tasks holds the work, linked to the engagement. Meetings holds Fireflies transcripts with extracted tasks and decisions. Post-mortems holds the close-out notes, the repeatable learnings, the next-engagement tags.

Every engagement has a client portal view, limited to what the client should see. Same rows, different permissions.

Monday, every account lead opens their engagement view. Status report auto-wrote from last week's tasks. Tuesday to Thursday, meetings feed Fireflies transcripts into the Meetings database, Claude pulls tasks and decisions into the right pages. Friday, the partner opens the agency-wide view and sees margin, utilisation, and blockers across every client.

Post-engagement, the account lead writes a post-mortem in 20 minutes using the template. The learnings tag into the Playbook library for the next similar engagement.

The biggest failure is the client portal drifting from the internal workspace. Teams copy-paste updates into a separate client-facing doc, and by month two the two versions disagree. Fix: the portal is a filtered view of the same database. One source. One update.

The second failure is post-mortems nobody writes. Fix: the engagement cannot close to "archived" until the post-mortem page has content in three required fields. It takes 20 minutes and the next engagement inherits the learning.

The third failure is brief-template drift. Fix: the brief template is a Notion template button. New engagements click it. Old briefs stay as they were, new ones follow the shape.