The first mistake isn't made inside Notion.
It's made before you ever open it.
Most freelancers open a blank page, start creating databases, and figure out the structure as they build. It's a natural approach. It's also the main reason systems collapse.
A Notion system should be designed before it's built. Three decisions are enough. They don't take long. But they determine how solid everything you build afterwards will be.
Decision 1: what exactly is the scope of this system?
Notion can hold anything. That's precisely why you need to decide what it won't hold.
A system with no boundaries turns into a catch-all. And nobody maintains a catch-all.
The question isn't "what could I put in Notion?" It's "what does this system need to cover, and nothing else?"
For a freelancer, the useful scope almost always comes down to two things: clients and projects. Everything else — finances and invoicing in particular — can live elsewhere without your business suffering for it.
Placeholder: diagram with two zones, a circle labelled "In the system" containing Clients and Projects, and items sitting outside it (Finances, Invoicing, Personal notes).
Write down what your system covers, in plain words. One sentence is enough: "This system manages my active clients and my current projects. Nothing else."
Decision 2: who are the core objects of your business?
In Notion, everything is built on databases. Before you create one, you need to identify the objects that actually structure your work.
An object is an entity you track over time — something that has a status, a history, information attached to it.
For most freelancers, there are two: clients and projects. Sometimes a third: tasks, if that level of detail is actually worth tracking.
The question to ask yourself: if you had to sum up your business in three words, what would they be? Those are probably your core objects.
Placeholder: simplified view showing two linked databases, Clients and Projects, with a handful of essential properties visible.
Each core object becomes one database in Notion. The common mistake is creating too many from the start. Start simple. You can add complexity later if the need genuinely shows up.
You know you need to build. You don't know where to start.
In 1 hour, we nail down your scope, your core objects and the right level of complexity. You leave with a plan before you open Notion.
Article 2 of 8 · See all articles in this guide →