Notion at Avo

Notion is where Avo keeps architecture decisions, deploy procedures, and client-facing documentation that does not belong in a code repository. Each client project gets a Notion workspace with three sections: system architecture (diagrams, data models, service boundaries), operational runbooks (how to deploy, how to roll back, environment variable reference), and handoff documentation (what the client needs to know to operate the system after delivery).

The architecture documents are written to be readable by a technical founder or a new engineer joining the client team, not just by Avo. Diagrams show request flows, data storage boundaries, and external service dependencies. If Avo exits the engagement, the docs are sufficient to onboard a replacement engineer.

Runbooks follow a specific format: prerequisites, step-by-step procedure, expected output, and what to do if the step fails. Ambiguous steps are not acceptable. Every runbook is tested against a staging environment before the project closes.

Internal use of Notion covers the Avo Engine build plan (200-plus tasks across 11 build clusters), the legal launch path research, and the cold email infrastructure research. Decision logs document why specific architecture choices were made so the rationale is recoverable months later.