If you’re running an agency and every new client means another round of copying pages, rebuilding databases, and hoping your editors figure out what’s due, this one’s for you. I built a workspace that turns client onboarding from a 2-hour headache into a 5-minute duplication.
The Situation
The founder of a social media agency came to me with a problem I see constantly: a Notion workspace that worked when the business was small, but completely broke down as it grew.
They already had a Notion workspace in place: a content calendar, some client pages, basic task tracking. But the business had evolved. They’d expanded their service offering, taken on more clients, and hired dedicated video editors for different accounts. The original workspace couldn’t handle any of it.
Content was scattered across separate pages with no unified view. Editors had no clear dashboard showing what needed cutting and when it was due. Onboarding a new client meant manually recreating the entire structure from scratch. And the founder, who was also scripting videos, managing client communication, and reviewing edits, had no single place to see what was happening across all accounts.
They sent me a Loom walking through the chaos: “I need a scalable place for my clients… every client should have a small space where he can see his to-dos, a roadmap… and for my editors, they should also see which videos have to be cut.”
The Approach
This wasn’t a simple template job. The core challenge was building a system where three different roles (the agency owner, each client, and each editor) all needed different views of the same data, with different permissions, across an unlimited number of client accounts.
I started by mapping the entire architecture in Whimsical before touching Notion. The structure needed to answer three questions simultaneously: What does the agency owner need to see across all clients? What does each individual client need to see about their own content? What does each editor need to see about their assigned videos?
The answer was a hub-and-spoke model. One central internal dashboard for the owner. Individual client portals that could be duplicated per onboarding. And editor views nested inside each client space, shared separately so editors only ever see their assigned work.
There was one more constraint that shaped the entire architecture: Notion’s database permission model. This is the pain point most agency owners hit and don’t know how to solve. If you put every client’s tasks into one shared database and just filter the views per client, those clients can remove the filter and see everyone else’s data. Filters aren’t real permissions. For an agency handling multiple clients (sometimes competing ones), that’s a dealbreaker.
The workaround is architectural, not technical. Each client gets their own dedicated databases inside their portal, so their data is physically separate from every other client’s. The owner’s internal HQ then uses Notion’s Tasks feature to roll up to 10 of those per-client task databases into one combined cross-client view, giving the owner a unified dashboard without ever exposing one client’s data to another. Notion used to allow unlimited databases in a combined Tasks view; they’ve since capped it at 10, which is why the system is designed around that number.
The second challenge was the content workflow itself. The agency had two distinct patterns for how content gets created: sometimes the client submits an idea that the agency scripts and produces, and sometimes the agency proposes ideas that the client approves or rejects. Both paths needed to coexist in the same pipeline without confusion.
I designed two automation buttons, Option A (client submits idea) and Option B (agency plans the video), each generating a different sequence of tasks with role assignments and relative deadlines baked in. Hit the button, pick the content type, and the entire workflow populates automatically.
The Build
The workspace has five major components:
Client Portal Template (×2 versions). A detailed version with roadmap, projects, content pipeline, brainstorm system, task manager, resources library, notes, and an embedded course section, plus a streamlined basic version for simpler engagements. Both are duplicated and customized per new client in minutes.
Content Pipeline with Smart Views. Two content types: Standard Video (with hook, script, B-roll suggestions, drive links, and a full status workflow from Idea through to Ready) and Meme/Text-on-screen (lighter structure for quick-turnaround content). Board view for status tracking, calendar view for scheduling. Each content item auto-generates tasks for every person involved.
Two-Way Brainstorm System. This was the most complex piece. The client sees two sections: “Ideas by Client” (their own ideas flowing through Idea → Script → Review → Record stages) and “Ideas by Internal Team” (agency-proposed ideas they can Select, send to Revision with required feedback, or Reject). The agency owner’s view mirrors this from the other side; they see client ideas to script, and can propose new ideas that flow to the client for approval. Revision loops require the client to explain what they want changed before it bounces back.
Role-Based Task Automation. Every content item generates a task chain: Review Idea → Write Script → Client Reviews Script → Client Records Video → Client Uploads Raw Files → Editor Edits Video → Client Approval. Each task is assigned to the right person (owner, client, or editor) with deadline offsets from the creation date. The owner chose to manually set recording dates (fixed shoot days per client) and editor deadlines (target: ready by Saturday for the following week).
Central Internal Dashboard. The owner’s HQ. Filtered task views across all client databases: My Tasks, Editor Tasks, Overdue, Today’s Tasks. A content pipeline overview per client. Client-level brainstorm views for scripting and idea management. One place to start the workday and know exactly what needs attention.
The Result
The founder went from a workspace that required hours of manual setup per client to one where onboarding takes minutes. Duplicate the template, rename it, share the right views with the client and their editor, done.
Editors log in and see exactly which videos need cutting, with deadlines and all the assets they need. Clients see their tasks, submit ideas, review scripts, and approve final content without ever leaving their portal. And the founder sees everything, across every client, every editor, every deadline, from one dashboard.
That’s the kind of problem I love solving: not just building something that works today, but building something designed to scale with the business.
The Takeaway
If you’re duplicating pages manually every time you onboard a new client, you don’t have a system — you have a workaround. The difference between a workspace and a workaround is whether it gets easier or harder as you grow. A well-architected Notion workspace should make your 20th client as easy to manage as your 2nd.
This build also solves the client data separation problem every multi-client agency runs into in Notion. Each client gets their own dedicated databases, and the owner sees everything through one combined Tasks view that rolls up to 10 of them at once.
Running an agency and want something similar? I build custom Notion workspaces for agencies managing multiple clients.