Tygart Media

Tag: Notion Databases

  • Notion for Multi-Client Content Operations: The Pipeline That Manages Dozens of WordPress Sites

    Running a content pipeline across twenty-plus WordPress sites from a single Notion workspace is not the obvious use case Notion was designed for. It’s a use case we built — deliberately, iteratively, over the course of operating a content agency where the volume of work made ad hoc management impossible.

    The result is a system where every piece of content, across every client site, moves through a defined sequence from brief to published inside one Notion database. Nothing publishes without a record. Nothing falls through the cracks between clients. The status of the entire operation is visible in a single filtered view.

    Here’s how that pipeline works.

    What is a Notion content pipeline for multi-site operations? A multi-site content pipeline in Notion is a single Content Pipeline database where every piece of content across every client site is tracked through a defined status sequence — Brief, Draft, Optimized, Review, Scheduled, Published — with each record tagged to its client, target site, and publication date. One database, filtered views per client, full operational visibility across all sites simultaneously.

    Why One Database for All Sites

    The instinct is to give each client their own content tracker. Separate pages, separate databases, separate calendars. This feels organized. In practice it means your Monday morning question — “what’s publishing this week?” — requires opening twenty separate databases and manually compiling the answer.

    One database with entity-level partitioning answers that question in a single filtered view sorted by publication date. Every client’s content in motion, every publication date, every status, visible simultaneously. Add a filter for one client and you have their isolated view. Remove the filter and you have the full operational picture.

    The cognitive shift required: stop thinking about the database as belonging to a client and start thinking about the client tag as a property of the record. The database belongs to the operation. The records belong to clients.

    The Status Sequence

    Every content record moves through the same six stages regardless of client or content type: Brief → Draft → Optimized → Review → Scheduled → Published. Each stage transition has a defined meaning and, for key transitions, a quality check.

    Brief: The content concept exists. Target keyword identified, angle defined, target site confirmed. Not yet written.

    Draft: Written. Not yet optimized. Word count and rough structure in place.

    Optimized: SEO pass complete. Title, meta description, slug, heading structure, internal links reviewed and adjusted. AEO and GEO passes applied if applicable. Schema injected.

    Review: Content quality gate passed. Ready for final check before scheduling. This is the stage where anything that shouldn’t publish gets caught.

    Scheduled: Publication date set. Post exists in WordPress as a draft or scheduled post. Date confirmed in the database record.

    Published: Live. URL confirmed. Post ID logged in the database record for future reference.

    The Quality Gate as a Pipeline Stage

    The transition from Optimized to Review is gated by a content quality check — a scan for unsourced statistical claims, fabricated specifics, and cross-client content contamination. The contamination check matters specifically for multi-site operations: content written for one client’s niche should never reference another client’s brand, geography, or specific context.

    Running this check as a formal pipeline stage rather than an informal pre-publish habit is what makes it reliable at scale. When publishing volume is high, informal checks get skipped. A formal stage in the status sequence means the check is either done or the content doesn’t advance. There’s no middle ground where it was probably fine.

    What Notion Tracks Per Record

    Each content pipeline record carries: the content title, the client entity tag, the target site URL, the target keyword, the content type, word count, the assigned writer if applicable, the publication date, the WordPress post ID once published, and the current status. Relation fields link the record to the client’s CRM entry and to the associated task in the Master Actions database.

    The WordPress post ID field is the detail most content trackers skip. With the post ID logged, finding the exact WordPress record for any piece of content is a direct lookup rather than a search. For a pipeline publishing hundreds of articles across dozens of sites, that lookup speed matters every week.

    The Weekly Content Review

    Every Monday, one database view answers the primary operational question for the week: a filter showing all records with a publication date in the next seven days, sorted by date, across all clients. This view drives the week’s content priorities — whatever needs to move from its current stage to Published by the end of the week gets the first attention.

    A second view shows all records stuck in the same status for more than five days. Stale records indicate a bottleneck — something that was supposed to move and didn’t. Finding and clearing those bottlenecks is the second priority of the weekly review.

    Both views take under a minute to read. The decisions they drive take longer. But the information is current, complete, and doesn’t require any compilation — it’s all in the database, updated as work happens.

    How Claude Plugs Into the Pipeline

    The content pipeline database is one of the primary interfaces between Notion and Claude in our operation. Claude reads the pipeline to understand what’s in progress, writes new records when content is created, updates status as work advances, and logs the WordPress post ID when publication is confirmed.

    This write-back capability — Claude updating the Notion database directly via MCP rather than requiring a manual logging step — is what keeps the pipeline current without adding overhead. The database is accurate because updating it is part of the work, not a separate step after the work is done.

    Want this pipeline built for your content operation?

    We build multi-site content pipelines in Notion — the database architecture, the quality gate process, and the Claude integration that keeps it current automatically.

    Tygart Media runs this pipeline live across a large portfolio of client sites. We know what the architecture requires at real operating scale.

    See what we build →

    Frequently Asked Questions

    How do you prevent content written for one client from appearing on another client’s site?

    Two mechanisms. First, every content record is tagged with the client entity at creation — the tag makes it explicit which client owns the content before a word is written. Second, a content quality gate scans every piece for cross-client contamination before it advances to the Review stage. Content referencing geography, brands, or context specific to another client gets flagged and held before it reaches WordPress.

    What happens when content is published — how does the pipeline stay accurate?

    When content publishes, the record status updates to Published and the WordPress post ID gets logged in the database record. In our operation, Claude handles this update directly via Notion MCP as part of the publishing workflow. For operations without that automation, a daily or weekly manual update pass keeps the pipeline accurate. The key is building the update into the publishing workflow rather than treating it as optional.

    Can Notion’s content pipeline replace a dedicated editorial calendar tool?

    For most content agencies, yes. Notion’s calendar view applied to the content pipeline database provides the same visual publication scheduling that dedicated editorial calendar tools offer, plus the full database functionality — filtering by client, sorting by status, tracking by keyword — that standalone calendar tools lack. The combination is more capable than purpose-built tools for agencies already running Notion as their operational backbone.

  • Notion for Content Agencies: Managing 20+ Client Sites Without Losing Your Mind

    Managing twenty-plus client sites from one Notion workspace requires solving a specific problem: how do you keep clients separated while keeping your operation unified? Separate workspaces per client sounds clean until you’re switching between eight workspaces to get a picture of the week. One shared workspace sounds efficient until a client can see another client’s work.

    The answer is a single workspace with entity-level partitioning — one set of databases, one operating rhythm, one knowledge layer, with every record tagged to the entity it belongs to. Here’s how that works in practice for a content agency.

    What is entity-level partitioning in Notion? Entity-level partitioning is an architectural approach where all records across all clients live in shared databases, tagged with an entity or client property. Filtered views surface only the records relevant to a specific client or business line. The databases are unified; the views are isolated. It enables cross-client visibility for the operator while maintaining strict separation for any client-facing access.

    Why One Workspace Beats Many

    The operational case for a single workspace is straightforward: weekly planning requires seeing everything at once. If Monday morning means answering “what’s publishing this week across all clients?”, the answer should come from one view, not from opening eight workspaces and aggregating manually.

    A single workspace with entity tagging gives you that cross-client view. Filter by entity for client-specific work; remove the filter for the full operational picture. The same database serves both purposes.

    The Content Pipeline at Scale

    For a content agency, the Content Pipeline database is the operational core. Every article, audit, and deliverable across every client moves through the same status sequence — Brief, Draft, Optimized, Review, Scheduled, Published — in one database.

    Each record carries the client entity tag, the target site URL, the target keyword, word count, publication date, and a linked task in the Master Actions database for whoever is responsible for the next step. A filtered view scoped to one client shows that client’s complete pipeline. An unfiltered view shows the full operation across all clients simultaneously.

    The practical benefit: a Monday morning review of everything publishing in the next seven days across all clients is one database view, sorted by publication date. No aggregation, no manual compilation, no missing anything because it was in a different workspace.

    The Client-Specific Knowledge Layer

    Each client has unique constraints that govern the work: brand voice guidelines, keyword lists, approved topic areas, platform-specific rules, past decisions about what to avoid. This information needs to live somewhere accessible mid-session without requiring a search.

    In our system, each client’s reference documentation lives in the Knowledge Lab database, tagged with the client entity. A filtered view of the Knowledge Lab scoped to one client shows all the reference material for that client — brand guide, keyword strategy, approved personas, content rules — in one place.

    The critical piece: every client reference page carries the metadata block that makes it machine-readable mid-session. When working on a client’s content, Claude can fetch the client’s brand reference and style guide and read the key constraints from the metadata summary without reading the full document every time.

    Communication and Decision Logging

    At scale, the thing that creates the most operational problems is context loss between sessions: a decision made in a client call two weeks ago that wasn’t documented, a feedback note that lived in an email and never made it into the system, a constraint mentioned once and then forgotten.

    The communication log in each client’s portal and the session log in the Knowledge Lab together solve this. Any significant decision — a strategic pivot, a content constraint, a scope change — gets a one-paragraph log entry with a date. The next session starts by reading the most recent log entries, not by trying to remember what was decided.

    This is unglamorous work. It takes three minutes to write a decision log entry. Those three minutes prevent hours of re-work when the undocumented decision surfaces as a problem two months later.

    The Weekly Cross-Client Review

    The operational rhythm for a multi-client content agency requires one weekly moment of seeing the full picture: every client’s content queue, every stalled deliverable, every relationship that needs attention. This is the weekly review, and Notion’s filtered views make it tractable at scale.

    The weekly review covers four database views: all content scheduled for the coming week sorted by publication date; all tasks marked In Progress for more than two days across all clients; any Revenue Pipeline deals with no activity in the past seven days; any client CRM contacts who should have heard from you. Reading all four views and deciding what needs action takes twenty to thirty minutes. Everything else in the week flows from those decisions.

    Want this built for your content agency?

    We build multi-client Notion architectures for content agencies — the entity partitioning, content pipeline, knowledge layer, and operating rhythm that make managing twenty-plus clients tractable.

    Tygart Media manages a large portfolio of client sites from a single Notion workspace. We know what the architecture requires at that scale.

    See what we build →

    Frequently Asked Questions

    Should each client have their own Notion workspace?

    For most content agencies, no. Separate workspaces per client prevent the cross-client visibility that makes weekly planning tractable. A single workspace with entity-level partitioning gives you unified operations for the agency and isolated views for any client-facing access. Separate workspaces make sense only when clients need active collaborative access to the same workspace — a rare requirement for most content agency relationships.

    How do you prevent one client’s content from appearing in another client’s view?

    Every database record carries an entity or client tag. Every client-facing view is filtered to show only records with that client’s tag. As long as records are correctly tagged at creation — which becomes habitual quickly — the filtering is reliable. A brief weekly audit checking for untagged records catches any that slip through.

    What happens when a content agency grows beyond Notion’s capacity?

    Notion handles large workspaces well with proper architecture — the performance issues most people encounter come from databases with thousands of unarchived records, not from the number of clients. Regular archiving of completed records keeps databases performant. At genuinely large scale (hundreds of active clients), dedicated agency management software may be warranted, but most content agencies operating at twenty to fifty clients run well within Notion’s capabilities.

  • How to Build a Notion Knowledge Base That Claude Can Actually Use

    A knowledge base Claude can actually use is not the same as a well-organized Notion workspace. A well-organized Notion workspace is readable by humans who know where to look. A knowledge base Claude can use is structured so Claude can find the right information, understand it in context, and act on it — without you manually directing every step.

    The gap between those two things is real, and most Notion setups fall on the wrong side of it. This is how to close it.

    What does it mean for a knowledge base to be Claude-ready? A Claude-ready knowledge base is structured so that Claude can fetch relevant pages, understand their content and context quickly, and act on them without manual context transfer from the user. It combines consistent metadata on every key page, a master index Claude fetches first, and a page structure that frontloads the most important information.

    The Core Problem: Claude Doesn’t Browse

    When you look for something in Notion, you navigate — you know roughly where things live, you scan headings, you follow links. Claude doesn’t navigate the same way. In a session, Claude fetches specific pages by ID or searches for them by keyword. It reads what’s there. It doesn’t browse a folder structure or follow a trail of internal links unless explicitly directed to.

    This means a knowledge base that works well for human navigation can be nearly unusable for Claude. Pages buried three levels deep under unlabeled parent pages, content that requires reading five hundred words before the relevant part, databases with no descriptions — all of these create friction that degrades Claude’s performance in a live session.

    The fix is structural: make the most important information findable without navigation, readable without extensive context, and consistently formatted so Claude knows where to look within any given page.

    The Metadata Block

    The single most important structural change is adding a metadata block to the top of every key knowledge page. Before any human-readable content, before the first heading, a brief structured summary tells Claude what the page is for and how to use it.

    The metadata block should include: what type of document this is (SOP, reference, decision log, project brief), what its current status is (active, evergreen, draft, deprecated), a two-to-three sentence plain-language summary of what the page contains, the business entities or projects it applies to, any other pages it depends on, and a single resume instruction — the most important thing to know before acting on this page’s content.

    With this block in place, Claude can read the metadata of twenty pages in the time it would otherwise take to read one page fully. The index-then-fetch pattern becomes viable: Claude reads the index, identifies which pages are relevant, fetches only those, reads the metadata blocks, and proceeds with accurate context.

    The Master Index

    The master index is a single Notion page that lists every key knowledge page in the workspace: its title, page ID, type, status, and one-line summary. Claude fetches this page at the start of any session that involves the knowledge base.

    The index doesn’t need to be comprehensive — it needs to cover the pages Claude will actually need. SOPs for recurring procedures, architecture decisions for the major systems, client reference documents for active engagements, and project briefs for work in progress. Everything else can be found via search if it’s needed.

    The index page should be updated whenever a significant new page is added to the knowledge base. It’s a lightweight maintenance task — add a row to a table, fill in four fields — that pays off every time a session starts with accurate orientation rather than a search.

    Page Structure That Frontloads Context

    Beyond the metadata block, the structure of individual pages matters for Claude’s performance. Pages that bury key information deep in the content — behind extensive background, after long introductions — require Claude to read more to extract less.

    The right structure for knowledge pages: metadata block first, then a one-paragraph summary of the page’s purpose and scope, then the operative content (the steps, the rules, the decisions), then background and rationale for anyone who needs it. The most important information is always near the top. Readers who need background scroll down; Claude gets what it needs from the first section.

    Keeping the Knowledge Base Current

    A knowledge base Claude can use today but not in three months is not actually useful — it creates false confidence that the system has current information when it doesn’t. The maintenance discipline is as important as the initial structure.

    Two mechanisms keep the knowledge base current without significant overhead. First, a Last Verified date on every page, with a periodic check for pages that haven’t been reviewed in more than ninety days. Second, a practice of updating the relevant knowledge page immediately when a procedure changes or a decision is revised — not after the fact, not in a quarterly review, but as part of the workflow that produced the change.

    The second mechanism is the harder one to establish. It requires treating knowledge documentation as part of the work, not as overhead separate from it. Once that practice is established, the knowledge base stays current almost automatically.

    Want this built for your operation?

    We build Claude-ready Notion knowledge bases — the metadata standard, the master index, and the page structure that makes your workspace a genuine AI operational asset.

    Tygart Media runs this architecture live. We know what makes a knowledge base useful for AI versus what just looks organized.

    See what we build →

    Frequently Asked Questions

    Can Claude search a Notion workspace?

    With the Notion MCP integration, Claude can search Notion by keyword and fetch specific pages by ID. It doesn’t browse folder structures the way a human would. This means the knowledge base needs to be structured for retrieval — with a master index and consistent metadata — rather than for navigation.

    What’s the difference between a Notion knowledge base and a wiki?

    A wiki is typically organized by topic for human browsing. A Claude-ready knowledge base is organized by function and structured for machine retrieval — with metadata blocks, a master index, and page structures that frontload key information. A wiki works well for human reference; a knowledge base structured for AI retrieval works for both humans and AI systems.

    How many pages should a knowledge base have?

    Enough to cover the procedures, decisions, and context that matter for the operation — typically thirty to one hundred pages for a small agency. More pages are not better. A knowledge base with two hundred pages of varying quality and currency is less useful than one with fifty consistently structured, current pages. Curation matters more than comprehensiveness.

  • Notion Project Management for Small Agencies: The 6-Database Architecture

    The project management tools built for agencies assume you have a team. They’re priced per seat, designed for handoffs between people, and optimized for visibility across a group. If you’re running a small agency — two to five people, or solo with contractors — most of that architecture is overhead you don’t need and complexity that actively slows you down.

    Notion solves this differently. Instead of fitting your operation into a tool designed for someone else’s workflow, you build the system your operation actually requires. For a small agency managing multiple clients and business lines simultaneously, that system is a six-database architecture that keeps everything connected without the bloat of enterprise project management software.

    This is what that architecture looks like and why each piece exists.

    What is the 6-database Notion architecture? The 6-database architecture is a Notion workspace structure designed for small agencies and solo operators managing multiple clients or business lines. Six interconnected databases — tasks, content, revenue, CRM, knowledge, and a daily dashboard — cover every operational layer of the business, linked by shared properties so information flows between them without duplication.

    Why Six Databases and Not More

    The instinct when building a Notion system from scratch is to create a database for everything. A database for meetings. A database for ideas. A database for invoices. A database for each client. This is how Notion workspaces become unusable — too many places things could live, no clear answer for where they actually belong.

    Six databases is the right number for a small agency because it maps cleanly to the six operational questions you need to answer at any moment: What do I need to do? What content is in the pipeline? Where does revenue stand? Who are my contacts? What do I know? What matters today?

    Every piece of information in the operation belongs in one of those six categories. If something doesn’t fit, it either belongs in a sub-page of an existing database record or it doesn’t need to be documented at all.

    Database 1: Master Actions

    Every task across every client and business line lives in one database. Not separate task lists per client, not separate boards per project — one database, partitioned by entity tag.

    The key properties: Priority (P1 through P4), Status (Inbox, Next Up, In Progress, Blocked, Done), Entity (which business line or client), Due Date, and a relation field linking to whichever other database the task belongs to — a content piece, a deal, a contact.

    The priority logic is worth being explicit about. P1 means revenue or reputation suffers today if this doesn’t get done. P2 means this creates leverage — a system, an asset, something that compounds. P3 means operational work that needs to happen but doesn’t compound. P4 means it should be delegated or killed. If your P1 list has more than five items, something is mislabeled.

    The daily operating rule: never more than five tasks in Next Up at once. The system forces prioritization rather than enabling the comfortable illusion that everything is equally important.

    Database 2: Content Pipeline

    Every piece of content — articles, reports, audits, deliverables — moves through a defined status sequence before it reaches the client or goes live. Brief, Draft, Optimized, Review, Scheduled, Published.

    The Content Pipeline database tracks where every piece is in that sequence, which client it belongs to, the target keyword or topic, the target platform, word count, and publication date. The relation field links back to the Master Actions database so the task of writing a specific piece and the piece itself are connected.

    The hard rule: nothing publishes without a Content Pipeline record. This creates an audit trail that answers “what did we deliver in March?” in seconds rather than requiring a search through email threads or shared drives.

    Database 3: Revenue Pipeline

    Active deals, proposals, and retainer renewals tracked through defined stages: Lead, Qualified, Proposal Sent, Active, Renewal, Closed.

    Each record carries the deal value, the stage, the last activity date, and a relation to the Master CRM for the associated contacts. The weekly review checks whether any deal has sat in the same stage for more than seven days without activity — that stagnation is a signal that requires a decision, not more waiting.

    The Revenue Pipeline doesn’t replace an accounting system. It tracks the relationship status and deal momentum, not invoices or payments. Those live in dedicated accounting software. The pipeline answers “where are we in the conversation?” not “what was billed?”

    Database 4: Master CRM

    Every contact across every business line — clients, prospects, partners, vendors, network relationships — in one database, tagged by entity and relationship type.

    The CRM properties: Entity, Relationship Type (client, prospect, partner, vendor, network), Last Contact Date, and a relation field linking to any Revenue Pipeline deals associated with that contact.

    The weekly review includes a check for any contact who should have heard from you and didn’t. “Should have heard from you” is defined by relationship type — active clients warrant more frequent contact than cold prospects. The CRM makes that check systematic rather than dependent on memory.

    Database 5: Knowledge Lab

    SOPs, architecture decisions, reference documents, and session logs. This is the institutional knowledge layer — everything that would take significant time to reconstruct if the person who knows it left or forgot.

    Every Knowledge Lab record carries a Type (SOP, architecture decision, reference, session log), an Entity tag, a Status (evergreen, active, draft, deprecated), and a Last Verified date. The Last Verified date drives the maintenance cycle — any record older than 90 days gets flagged for a quick review.

    The Knowledge Lab is also the layer that makes the operation AI-readable. Every page carries a machine-readable metadata block at the top that allows Claude to orient itself to the content quickly during a live session. This is what transforms the Knowledge Lab from a static document library into an active operational asset.

    Database 6: Daily Dashboard (HQ)

    Not a database in the traditional sense — a command page that aggregates filtered views from the other five databases into a single daily interface. The goal is one page that answers “what needs attention right now?” without clicking through five separate databases.

    The HQ page contains: a filtered view of P1 and P2 tasks due today or overdue, the content queue for the next 48 hours, an inbox view of unprocessed items (tasks without a priority or status assigned), and a quick-access list of the most frequently used database views.

    The HQ page is where every working day starts. Everything else in the system is accessed from here or from the five source databases. It’s the navigation layer, not a database of its own.

    How the Databases Connect

    The architecture only works as a system if the databases talk to each other. The connection mechanism in Notion is relation properties — fields that link a record in one database to a record in another.

    The key relations: every Content Pipeline record links to a Master Actions task. Every Revenue Pipeline deal links to a Master CRM contact. Every Master Actions task can link to a Content Pipeline record, a Revenue Pipeline deal, or a Knowledge Lab SOP. These relations mean you can navigate from a task to the content piece it produces, from a deal to the contact it involves, from a procedure to the tasks that execute it — without leaving Notion or losing the thread.

    Rollup properties extend this further: a Content Pipeline view can show the priority of the associated task without opening the task record. A Revenue Pipeline view can show the last contact date from the CRM without opening the contact. The data stays connected visually, not just structurally.

    What This Architecture Replaces

    For a small agency, the 6-database architecture typically replaces: a project management tool (the tasks and content pipeline handle this), a CRM (the Master CRM handles this), a shared drive for SOPs (the Knowledge Lab handles this), and a deal tracker (the Revenue Pipeline handles this). It does not replace accounting software, calendar tools, or communication platforms — those remain separate because they do things Notion doesn’t.

    The consolidation matters not just for cost but for operational clarity. When every operational question has one answer and one place to look, the cognitive overhead of running the business drops significantly. The system becomes something you trust rather than something you maintain out of obligation.

    Want this built for your agency?

    We build the 6-database Notion architecture for small agencies — configured for your specific operation, with the relations, views, and daily operating rhythm set up and documented.

    Tygart Media runs this system live. We know what the build process looks like and what breaks without the right architecture from the start.

    See what we build →

    Frequently Asked Questions

    How is the 6-database Notion architecture different from using ClickUp or Asana?

    ClickUp and Asana are built around tasks and projects as the primary organizational unit. The 6-database architecture treats the business itself as the organizational unit — tasks, content, revenue, relationships, and knowledge are all connected layers of one system rather than separate tools or modules. The tradeoff is that Notion requires more upfront architecture work, but produces a system that fits your specific operation rather than a generic project management workflow.

    Can one person realistically maintain six databases?

    Yes — that’s what the architecture is designed for. The daily maintenance is five to fifteen minutes of triage and status updates. The weekly review is thirty minutes. Most of the database updating happens naturally as work progresses: publishing a piece updates the Content Pipeline, closing a deal updates the Revenue Pipeline. The system is designed for a solo operator or a very small team, not a department.

    What Notion plan do you need for the 6-database architecture?

    The Plus plan at around ten dollars per month per member is sufficient for everything described here — unlimited pages, unlimited blocks, and the relation and rollup properties that make the database connections work. The free plan limits relations and rollups in ways that would break the architecture. The Business plan adds features useful for larger teams but isn’t necessary for a small agency setup.

    How long does it take to build the 6-database architecture from scratch?

    Plan for twenty to forty hours to build, configure, and populate the initial system — creating the databases, setting up the properties and relations, building the filtered views, writing the first SOPs, and establishing the daily operating rhythm. Most operators who build it solo spend two to three months in iteration before it stabilizes. Starting from a pre-built architecture configured for your specific operation compresses that significantly.

    What’s the biggest mistake people make when building a Notion agency system?

    Creating too many databases. The instinct is to give everything its own database — one per client, one per project type, one for every category of information. This creates the same problem as a disorganized file system: too many places things could live, no clear answer for where they actually belong. Start with six. Add a seventh only when there’s a category of information that genuinely doesn’t fit in any of the six and that you need to query or filter regularly.

  • How I Run 27 Client Sites from One Notion Command Center

    I run 27 client WordPress sites from a single Notion workspace. No project management software, no agency platform, no dedicated CRM. Just Notion — architected deliberately across six interconnected databases — handling task triage, content pipelines, client relationships, revenue tracking, and the knowledge infrastructure that feeds an AI-native content operation.

    This is not a productivity tutorial. This is a description of a real system, built over two years, that runs across seven distinct business entities simultaneously. If you’re an agency owner, solo operator, or content business trying to figure out how to use Notion for something more serious than a to-do list, this is what the other end of that road looks like.

    What is a Notion Command Center? A Notion Command Center is a multi-database workspace architecture that functions as a single operating system for a business or portfolio of businesses. Rather than using Notion as a note-taking app, a Command Center connects tasks, clients, content, and knowledge into a unified system with defined workflows, priority rules, and daily operating rhythms.

    Why Notion Instead of Dedicated Agency Software

    The honest answer: I tried the alternatives. ClickUp has more native project management features. Asana handles task dependencies better out of the box. Monday.com is more polished for client-facing views.

    None of them let me build exactly the system my operation requires. And at the scale I’m running — 27 client sites, seven business entities, a live AI publishing pipeline — the ability to customize the architecture matters more than any individual feature.

    Notion also has a meaningful advantage that most people underestimate: it integrates with Claude natively. My entire operation runs on Claude as the AI layer, and a Notion workspace structured correctly becomes something Claude can read, reason about, and act on. That combination — Notion as the OS, Claude as the intelligence — is what makes this a genuinely AI-native operation rather than just an AI-assisted one.

    The 6-Database Architecture

    The Command Center runs on six core databases. Everything else in the workspace is either a view of these databases, a child page underneath them, or a standalone reference document. The six databases are:

    1. Master Actions

    Every task across all seven entities lives here. Priority levels run P1 (revenue or reputation at risk today) through P4 (delegate or kill). Each task carries an Entity tag, a Status, a Due Date, and a linked record in whichever other database it belongs to — a client, a content piece, a deal.

    The daily operating rule: never more than five tasks marked “Next Up” across the entire workspace at once. If your Next Up list has eight items, something is mislabeled. P1 means the thing doesn’t get done and real consequences follow today.

    2. Content Pipeline

    Every article across all 27 client sites flows through this database before it hits WordPress. Status stages run from Brief → Draft → Optimized → Scheduled → Published. The database links to the client entity, carries the target keyword, the target site URL, word count, and a publication date.

    Nothing publishes without a Notion record. This is a hard rule established after the alternative — articles written in sessions and pushed directly — created audit gaps that took hours to resolve. Notion first, WordPress second.

    3. Revenue Pipeline

    Client deals, proposals, and retainer renewals. Stage-based (Lead → Qualified → Proposal Sent → Active → Renewal). Links to the Master CRM for contact records. The weekly review checks whether any deal has sat in the same stage for more than seven days without activity — that’s a warning sign that gets flagged.

    4. Master CRM

    Every contact across all seven entities. Clients, prospects, golf league members, partners, vendors. Tagged by entity, relationship type, and last contact date. The weekly review catches anyone who should have heard from me and didn’t.

    5. Knowledge Lab

    SOPs, architecture decisions, session logs, and reference documents. This is where the institutional knowledge lives — the things that would take hours to reconstruct if I had to start from scratch. The Knowledge Lab uses a metadata standard (I call it claude_delta) that makes every page machine-readable, so Claude can fetch and reason about the content in a live session without losing context.

    6. William’s HQ

    The daily dashboard. A filtered view of P1 and P2 tasks due today or overdue, the content queue for the next 48 hours, and the inbox triage. This is the page that opens first every morning. Everything else in the system is accessed from here.

    The Seven Entity Structure

    The system manages seven distinct business entities, each with its own Focus Room — a sub-page containing that entity’s active projects, open tasks filtered by entity tag, and key reference documents. The entities are:

    • The parent agency — managing all client sites and retainer relationships
    • Personal brand — direct services, thought leadership, and new business
    • Client A — content operation for a contractor in a regional market
    • Client B — content operation for a service business in a metro market
    • Industry network — B2B community and event operation
    • Content property — topical authority site in a specific vertical
    • Personal — finances, health commitments, personal projects

    The entity structure means a task logged under “a regional client content operation” never bleeds into the the parent agency content queue. The databases are shared, but the entity tag acts as a partition. This matters operationally when you’re switching contexts fifteen times a day — the system tells you where you are and what belongs there.

    The Daily Operating Rhythm

    The Command Center only works if you use it on a rhythm. Mine runs on three loops:

    Morning Triage (10–15 minutes)

    Open William’s HQ. Zero the inbox — every untagged item gets a priority, a status, and an entity. Read the P1 and P2 list. Mentally commit to the top three. Check the content queue for anything publishing in the next 48 hours that isn’t scheduled. That’s a P1 fix before anything else happens.

    End-of-Day Close (5 minutes)

    Mark done tasks complete. Push anything untouched but intended — update the due date or reprioritize down. Check the content queue for tomorrow’s publications. If anything new was created during the day — a contact, a content piece, a deal — verify it’s logged in the right database with the right entity tag.

    Weekly Review (30 minutes, Sunday evening)

    Revenue: any deal stuck in the same stage as last week? Content: next week’s queue fully populated? Tasks: archive all Done tasks older than 14 days. Relationships: anyone who should have heard from me and didn’t? System health: any automation that failed silently?

    The weekly review is the repair mechanism. It catches the things the daily rhythm misses and resets the system before the next week compounds the drift.

    How Claude Plugs Into This

    The Knowledge Lab’s claude_delta metadata standard is what makes the Notion–Claude integration functional rather than theoretical. Every page in the Knowledge Lab carries a JSON metadata block at the top that tells Claude the page type, status, summary, key entities, and a resume instruction for picking up work in progress.

    In practice, this means I can start a session by telling Claude to read a specific Knowledge Lab page, and Claude has enough structured context to continue from exactly where the last session ended — without me re-explaining the project, the client, the constraints, or the decisions already made. The Notion workspace functions as persistent memory across Claude sessions.

    This is the part of the architecture that most people haven’t built yet. Notion as a note-taking app is one thing. Notion as a structured knowledge layer that an AI can navigate and act on is a meaningfully different proposition — and it’s the direction serious operators are moving.

    What This Architecture Costs to Build

    Honest answer: the architecture itself took about three months of active iteration to stabilize. The first version had too many databases, unclear relationships between them, and no real operating rhythm to enforce the discipline. The current version is the result of tearing down and rebuilding twice.

    The tooling cost is low. Notion’s Plus plan at $10/month per member handles everything described here. The BigQuery knowledge ledger that backs the AI memory layer runs on Google Cloud at effectively zero cost at this scale. Claude API usage for content operations runs roughly $50–150/month depending on session volume.

    What actually costs something is the setup time and the learning curve of building databases that relate to each other correctly. Most Notion setups fail not because the tool is limited but because the architecture wasn’t designed before the databases were created.

    Whether This Is Right for Your Agency

    The Command Center architecture works well for solo operators and small agencies managing multiple clients or business lines simultaneously. It works especially well when you’re running an AI-native content operation and need Notion to function as more than task management.

    It’s not the right choice if you need strong native time-tracking, Gantt charts, or client-facing portals that look polished without customization. Those cases have better-suited tools.

    But if you’re running a content agency, a multi-client SEO operation, or any business where the work is primarily knowledge work — briefs, articles, strategies, SOPs, client communications — and you want one system that sees all of it, the 6-database Command Center architecture is worth the build time.

    Want this built for your operation?

    We set up Notion Command Centers for agencies and operators — the full architecture, configured and documented, not a template to figure out yourself.

    Tygart Media has built and runs this system live across 27 client sites. We know what the setup process actually looks like.

    See what we build →

    Frequently Asked Questions

    How many databases does a Notion Command Center need?

    A functional Command Center for an agency or multi-client operation typically needs six core databases: a task database, a content pipeline, a revenue pipeline, a CRM, a knowledge base, and a daily dashboard. More than eight databases usually indicates an architecture problem — complexity that should be handled with views and filters, not additional databases.

    Can Notion handle 27 client sites without getting slow?

    Yes, with proper architecture. The key is using filtered views rather than separate databases for each client, and keeping database page counts manageable by archiving completed records regularly. Notion’s performance degrades when a single database exceeds a few thousand active records — archive aggressively and it stays fast.

    How does Notion integrate with Claude AI?

    Notion and Claude integrate through structured page formatting and the Notion API. By standardizing metadata at the top of key pages — page type, status, summary, key entities — Claude can fetch and interpret Notion content in a live session. More advanced setups use the Notion API to read and write records programmatically during Claude sessions, effectively making Notion the persistent memory layer for AI operations.

    What’s the difference between a Notion Command Center and a regular Notion workspace?

    A regular Notion workspace is typically organized around document types — pages, notes, tasks — without enforced relationships between them. A Command Center is organized around business operations — entities, pipelines, and workflows — with databases that relate to each other and a defined operating rhythm that governs how the system gets used each day.

    How long does it take to set up a Notion Command Center?

    Building the architecture from scratch takes 20–40 hours of focused setup time, including database design, relationship configuration, view creation, and SOP documentation. Most operators who attempt it solo take 2–3 months of iteration before the system stabilizes. Working from an existing architecture and having it configured for your specific operation compresses that significantly.

    Is Notion good for content agencies specifically?

    Notion is well-suited for content agencies because the core work — briefs, drafts, SOPs, client communication, publishing schedules — is document-centric. The Content Pipeline database, linked to a CRM and task system, gives visibility into every piece of content across every client at once, which is difficult to replicate in project management tools not built for document-heavy workflows.