Notion Workspace for 12-Person Agency: 4+ Hours Saved Weekly
Built 7 interconnected Notion databases replacing 12 individual spreadsheets, eliminating a weekly 90-minute status meeting and giving the founder real-time capacity visibility.
Watch the walkthrough
3-6 minute screen-share showing Problem → Solution → Result
The Problem
No Single Source of Truth
Client information, project status, and task ownership lived in different tools and different people's heads. Account managers tracked clients in personal spreadsheets. The founder relied on Monday standups. By Tuesday, information was stale. No way to answer "who is working on what" without asking around.
Team Capacity Was Invisible
No system showed who was overloaded versus who had bandwidth. Work allocation happened by gut feeling. Some team members sat under 60+ hours of active tasks while others had capacity to spare. The founder only discovered imbalances after deadlines slipped and clients complained.
Content Pipeline Running Blind
40+ content pieces per month across multiple clients had no calendar, no status tracking, no way to see scheduled versus draft. Missed publish dates were becoming a client retention problem. Every piece was tracked by whoever happened to own it, somewhere.
The Solution
Architecture diagram — click to zoom
Layer 1: Relational Database Architecture
Designed 7 interconnected databases: Client CRM, Projects, Tasks, Content Calendar, Client Onboarding Tracker, Team Capacity, and an Executive Dashboard. Relational links tie every record to a client relationship. Tasks roll up to Projects. Projects roll up to Clients. Content pieces link to both Projects and Tasks. One click on a client record reveals every linked project, open task, and upcoming content piece.
Layer 2: Workflows and Automation Within Databases
Rollup calculations show active task counts, estimated hours, and project health at every level. Status workflows on the Content Calendar move pieces through Draft → Review → Approved → Scheduled → Published. Capacity status on each team member record auto-calculates to Available, At Capacity, or Overloaded using rollups from the Tasks database.
Layer 3: Views and Dashboards
Each team member has personal Kanban and table views filtered to their ownership. Project leads see everything tied to their accounts. The founder has a master Executive Dashboard pulling filtered views from every database into a single page: client health, tasks due this week, content going live, team capacity summary. Replaced 4 separate tools and a weekly 90-minute status meeting.
Layer 4: Governance and Access
Defined ownership rules: every task has an owner, deadline, and visible status. Onboarding checklist standardized so no new client kickoff misses a step. Access permissions scoped so team members see what they own plus shared client-level views. Capacity status visible across the team so work allocation is a shared-context decision, not a gut call.
The Impact
Quantitative Results
- Founder reclaimed 4+ hours per week previously spent gathering status updates
- Weekly 90-minute status meeting eliminated
- 12 individual spreadsheets replaced by 1 connected workspace
- 40+ monthly content pieces now tracked through a single pipeline
Strategic Value
- Work allocation now runs on data, not gut feeling. Red/yellow/green capacity indicators replaced guesswork
- Architecture supports doubling client count without adding administrative overhead
- Team accountability built into the system: every task has an owner, deadline, and visible status. Nothing falls through the cracks
Have a similar problem?
Tell me what is going on and I will tell you what I would do about it. No obligation.
Get in touch