Notion for marketing agencies: the honest review

TL;DR

Notion is the best knowledge layer an agency can buy and a poor system of record for clients and work. As the wiki — SOPs, briefs, meeting notes, onboarding docs, the compounding institutional memory — it has no real competitor at the price, and the AI search across your own corpus is genuinely useful. As the agency OS, it breaks in four places: databases are documents wearing tables (relations exist, integrity doesn't); the page-tree sharing model makes client confidentiality walls a discipline instead of a default; client communication never lives there, so the "client record" is a beautifully formatted partial truth; and work management lacks the agency-shaped machinery — department routing, recurring cadences, workload views — that turns tasks into an operating rhythm. The setup that holds up is the hybrid the stack post already recommends: Notion owns documents and knowledge, something agency-shaped owns clients, work, and communication, and the two link to each other liberally. The failure mode is the same as Airtable's, with a different personality: asking the best tool in one layer to be the whole stack.

---

If Airtable's true believer is the operations builder, Notion's is the documentation idealist — the person who genuinely fixed your agency's knowledge problem and now wants to run everything through the same beautiful tree of pages. Both believers are right about their layer and wrong about the OS. Here's the Notion version of that line.

Where Notion genuinely wins

The wiki, definitively. SOPs that people actually read, client onboarding docs, meeting notes that thread into briefs, the "how we do PPC audits" page — Notion is where agency knowledge stops living in people's heads. The SOP discipline still applies (owners and expiry dates, or the wiki rots like any other), but no tool makes the writing and finding of operational knowledge this frictionless.

Documents with structure. A campaign brief that embeds the timeline database, a QBR doc that pulls the quarter's deliverables table — the doc/database blend is Notion's real invention, and for document-shaped work it beats both Google Docs and every PM tool.

Cost and adoption. Cheap per seat, zero training burden, and the AI layer (search + Q&A across your own workspace) is one of the few "AI feature" line items that earns its keep daily.

Where it breaks as the agency OS

1. Databases are documents wearing tables. Notion relations connect pages; they don't enforce anything. No required fields that actually block, no types beyond the surface, no integrity when someone duplicates a template wrong. An Airtable base decays into convention drift; a Notion "CRM" starts there. The client list, the pipeline, the tracker — they're all pages, and pages tolerate every inconsistency a busy Tuesday produces.

2. Client walls are a discipline, not a default. Permissions inherit down the page tree, guests get invited per page, and one well-intentioned "share parent page" exposes a sibling client's folder. Configurable into safety? Yes. Audited quarterly by someone who owns it? That's the real requirement, and it's the same confidentiality argument from the Airtable review — agency-shaped systems make the client the permission boundary by construction; horizontal tools make it your ongoing job.

3. The communication hole, again. Client email doesn't thread into Notion; there's no inbox, no portal, no message history on the client page. The "client hub" pattern — a gorgeous page per client with links, notes, and embeds — documents the relationship while the relationship itself happens in personal inboxes. Partial records aren't neutral: they're confidently misleading, because they look complete.

4. Tasks without an operating rhythm. Notion task databases handle "a list of things with checkboxes" fine. What they don't ship: department-tagged routing (PPC vs SEO vs CRO views with different workflows), recurring cadences that create real work items, workload and capacity views, or the cross-client "what does the team owe everyone this week" query. Those aren't power features — they're the operating rhythm itself, and rebuilding them from database templates is the Airtable maintainer trap with worse relational tools.

The hybrid that actually holds up

Our stack post already calls this in Layer 4: Notion + a real system of record is where most agencies under 50 people land, and it's the right landing. The division of labor:

• Notion owns: SOPs, briefs, meeting notes, internal how-tos, the knowledge that compounds. Anything whose natural shape is a document.
• The agency system owns: client records, tasks and their rhythm, client communication, tracking documentation — anything whose natural shape is a record with rules, where types, permissions-by-client, and history are product opinions rather than your conventions.
• The seam: link liberally in both directions. The client record links to its brief; the brief links back. Seam friction is real but small — far smaller than either tool failing at the other's job.

The verdict, by agency shape

• Any size: buy Notion for the knowledge layer without hesitation. It's the best money-per-compounding-value line in the stack.
• Under ~8 clients, doc-heavy work (content/brand studios): running more of the operation in Notion is livable; you'll feel breaks 2–4 as friction. Assign a permissions owner anyway.
• 10+ clients or any paid-media practice: keep the OS jobs out. The moment tracking infrastructure, department workflows, and client threads matter, document-shaped tools are the wrong substrate — that's the buyer's-guide distinction between tools that ship opinions and tools that ship surfaces.

Disclosure, same as the Airtable review: Phloz is the category the "Notion as OS" pattern competes with, and the four break points above are exactly the product opinions we ship. But the honest summary cuts the other way too — nothing we build replaces a good wiki, and an agency running Phloz plus a well-kept Notion is better run than one trying to live entirely in either. Best tool per layer, links across the seam: boring advice, keeps working.