Why I Run My Entire Business Out of One Notion Doc
The standard Notion advice is to build a system. Linked databases. Filtered views. A hub page with rollup properties that calculate your quarterly goals from your daily tasks from your project tracker from your CRM.
I did all of that. Spent weekends designing it. It was beautiful. I used it for maybe three weeks before I started routing around it.
Now I run everything out of one doc. Not one workspace. One document. And it works better.
Why the system always breaks
The problem with a sophisticated Notion setup isn’t that it’s wrong. It’s that it has to be maintained. Every time the work changes — new project, new client, new thing you’re building — the system needs updating. You have to decide where the new thing lives, whether it needs a database or just a page, how it connects to the rest.
That friction isn’t huge. But it’s daily, and it accumulates. Eventually you stop putting things in the system because updating the system takes more thought than the work itself. Then the system becomes aspirational infrastructure. A ghost town with really good architecture.
What one doc actually means
I’m not saying it’s literally one page. It’s more like one root document that I live inside, with sub-pages and a loose nesting logic that I understand because I made it for me — not for the version of me I aspire to be.
The key difference: it has no maintenance layer. I don’t need to update a database schema to add a new project. I make a page, put it under the right heading, and start working. The structure follows the work instead of the other way around.
That’s the thing most Notion setups get backwards. They design for abstraction first — create the containers, then fill them. One doc is the opposite. You start with content and let the structure emerge.
What’s actually in there
Everything. And I mean everything:
- Active projects, with status and next steps as inline text
- Client notes and context, nested under each client
- Writing drafts and ideas
- Weekly review — a single recurring page I update every Monday
- Reference material I actually need, not aspirational reading lists
No separate CRM. No separate task manager. If a task is on a page, it gets done or it gets deleted. There’s no separate database to keep in sync with reality.
The argument against this
I know what the objection is. This doesn’t scale.
It doesn’t need to. I’m one person building things I care about. The goal isn’t a system that scales to a team of fifty. The goal is that I know where everything is, I can add things without thinking, and I’m not spending Sunday afternoons reorganizing my tools instead of building.
If I hire people, I’ll restructure. But that’s a different problem for a different version of my business. Right now, the one-doc setup is the highest-leverage thing I can maintain without it becoming a second job.
The best productivity system is the one you actually use. For me, that turns out to be a document, not a system. Smaller than I expected. Better, too.