The Workspace Was Collapsing Under Its Own Weight
My Notion workspace had grown organically for two years. Pages nested inside pages nested inside pages. Duplicate databases. Orphaned notes. Three different task lists that each tracked a subset of the same tasks. A page hierarchy so deep that finding anything required knowing the exact path – or giving up and using search.
The workspace worked when I ran two businesses. At seven businesses with 18 managed websites, it was actively slowing me down. Every search returned duplicates. Every new entry required deciding which of three databases to put it in. The structure that was supposed to organize my work was generating more overhead than the work itself.
So I burned it down and rebuilt it. One Cowork session. New architecture from the ground up. Six core databases, three operational layers, and a design philosophy that scales to 20 businesses without adding structural complexity.
The Three-Layer Architecture
Layer 1: Master Databases. Six databases that hold every record across every business: Master Actions (tasks), Content Calendar, Master Entities (clients and businesses), Knowledge Lab, Contact Profiles, and Agent Registry. These are the canonical data stores. Every record lives in exactly one place.
Layer 2: Autonomous Engine. The automation layer – triage agent configuration, air-gap sync agent rules, scheduled task definitions, and agent monitoring dashboards. This layer reads from and writes to the master databases but operates independently. It is where the AI agents interface with the workspace.
Layer 3: Command Centers. Focus rooms for each business entity – Tygart Media, Engage Simply, a restoration company, a restoration company, Restoration Golf League, BCESG, and Personal. Each focus room contains filtered views of the master databases showing only records tagged with that entity. Plus client portals accessed from this layer.
The key principle: data lives in Layer 1, automation lives in Layer 2, and humans interact through Layer 3. No layer duplicates another. Every view is a window into the same underlying data, filtered by context.
The Entity Tag System
Every record in every database has an Entity property – a relation to the Master Entities database. This single property is what makes the entire architecture work. When I create a task, I tag it with an entity. When content is published, it is tagged with an entity. When an agent logs activity, it is tagged with an entity.
The entity tag enables three capabilities: filtered views per business (Layer 3 focus rooms show only their entity’s records), air-gapped client portals (sync only records matching the client’s entity), and cross-business reporting (roll up all entities for portfolio-level metrics).
Before the reorg, switching between businesses meant navigating to different sections of the workspace. After the reorg, switching is a single click – each focus room is a filtered lens on the same unified data.
The Triage Agent
New records entering the system need to be classified. The Triage Agent is a Notion automation that watches for new entries in Master Actions and auto-assigns entity, priority, and status based on content analysis. A task mentioning “golf” or “restoration golf” gets tagged to Restoration Golf League. A task referencing “engage” gets tagged to Engage Simply.
The triage agent handles approximately 70% of record classification automatically. The remaining 30% are ambiguous entries that get flagged for manual entity assignment. This means most of my task creation workflow is: describe the task in one sentence, let the triage agent classify it, and move on.
What the Reorg Eliminated
Duplicate databases: from 14 to 6. Orphaned pages: 40+ archived or deleted. Average depth of page hierarchy: from 7 levels to 3. Time to find a specific record: from 2-3 minutes of searching to under 10 seconds via entity-filtered views. Weekly overhead maintaining the workspace: from approximately 3 hours to under 30 minutes.
The reorg also eliminated the psychological overhead of a messy system. When your workspace is disorganized, every interaction carries a tiny cognitive tax – “where does this go? Did I already capture this somewhere else? Is this the current version?” Multiply that by hundreds of daily interactions and the cumulative drain is significant. A clean architecture removes the tax entirely.
Frequently Asked Questions
How long did the full reorganization take?
One extended Cowork session, approximately 4 hours of active work. This included architecting the new structure, creating the six databases with proper schemas, migrating critical records from old databases, configuring the triage agent, setting up entity tags, and creating the Layer 3 focus rooms. The archive of old pages was done in a separate cleanup pass.
Can this architecture work for a single business?
Yes – and it is simpler. A single business needs the same six databases but without the entity tag complexity. The three-layer architecture still applies: data in master databases, automation in the engine layer, and human interaction through focused views. The architecture is the same regardless of scale.
What tool did you use for the migration?
Notion’s native relation properties and the Notion API via Cowork mode. The API allowed bulk operations – creating database entries, updating properties, moving pages – that would have taken days to do manually through the UI. The Cowork session treated the reorg as a technical migration, not a manual reorganization.
Architecture Is Strategy
Most people treat their workspace as a filing cabinet – a place to put things so they can find them later. That model breaks at scale. A workspace that manages seven businesses needs to be an operating system, not a filing cabinet. The three-layer architecture, entity tagging, and autonomous triage agent transform Notion from a note-taking app into a business operating system that scales horizontally without adding complexity. The architecture is the strategy. Everything else is just typing.
Leave a Reply