The 5 Notion Databases for Freelancers Who Work Alone
Five databases, not fifty pages
It is Thursday afternoon and you cannot answer three basic questions: who owes you money, what is due tomorrow, and which project is quietly losing money. Your Notion workspace has a note about all three and a structure for none of them. The fix is not another template with forty linked pages. It is five Notion databases for freelancers, each holding one kind of row and pointing at the row that owns it.
A Notion database is a table whose rows open as pages. That single fact is why it beats a folder of notes for anything you need to count, sort, or total. Five tables give you five answers. A folder of notes gives you five things to read.
The five Notion databases for freelancers who need them
| Database | One row is | The question it answers | Minimum properties |
|---|---|---|---|
| Clients | A person or company who pays you | Who is active, what do they pay, how much have they billed? | Name, Status, Rate, Email |
| Projects | One scoped piece of work | What is in flight, what is late, did it make money? | Name, Client, Status, Start, Due, Budget, Hours Logged |
| Tasks | One next action | What do I do today, and what slipped? | Name, Project, Status, Due, Priority |
| Finances | One money movement | What came in, what went out, what is still unpaid? | Name, Date, Type, Amount, Client, Paid On |
| Content | One piece of writing or media | What is going out, on which channel, for which project? | Name, Channel, Status, Publish On, Project |
The property column is the part people overfill. Nine properties on Clients looks thorough, and then half of them stay empty for months. Every property above exists because a view sorts or filters on it. If you cannot name the view that uses a property, do not add the property.
The Content database is the one you can postpone for a month. A service business can run on four databases while it is busy delivering. Content earns its place when publishing is a real workstream and not a good intention.
Build them in this order
- Clients first. Two other databases point at it, so it has to exist before them. Fill in the six or eight clients you have now, including the quiet ones, so old invoices have somewhere to land.
- Projects second. Add the Client relation and link every project to exactly one client row. The relation is the point of this step.
- Tasks third. Add the Project relation. One task belongs to one project. If a task serves two projects, it is really two tasks.
- Finances fourth. Add the Client relation on income rows only. Expenses do not belong to a client.
- Content last. Build it once the first four hold live data, not before, and add its
Projectrelation when the first piece is scheduled.
The order is not arbitrary. Relations live on the many side and point at rows that must already exist, so building in this sequence saves you from re-linking everything later. If the relation step is where you stall, connecting clients, projects, and tasks walks through the clicks in order.
Three formulas are enough
Three formulas turn these tables from records into a business. The first counts lateness on Tasks:
`` if( or(empty(prop("Due")), prop("Status") == "Done"), 0, max(0, dateBetween(prop("Due"), today(), "days")) ) ``
It returns zero when there is no due date or the task is done, and otherwise counts whole days from the due date to today, never below zero. Paste it into a Formula property called Days Overdue, set the number format to whole numbers, and sort the Overdue view by that column.
The second puts a real number under a fixed fee. On Projects, with Hours Logged kept up to date:
`` if(prop("Hours Logged") == 0, 0, round(prop("Budget") / prop("Hours Logged"))) ``
That is the effective hourly rate: what the project actually paid per hour rather than what you quoted. A project billed at $2,400 and 19 hours returns $126. The same project at 31 hours returns $77, which is the number that starts the difficult conversation.
The third is the optional one. It measures how long an invoice took to pay, which matters most on the client who pays in 40 days:
`` if( prop("Type") == "Income", if( empty(prop("Paid On")), dateBetween(prop("Date"), today(), "days"), dateBetween(prop("Date"), prop("Paid On"), "days") ), 0 ) ``
An unpaid invoice reports its age, climbing daily, while a paid one reports the gap between sending and payment. Days overdue earns the time in month one; payment speed becomes interesting in month three. When you want these numbers rolled up per client, the rollups for freelancers setup is the next step after the five tables exist.
What to leave out in month one
A surprising amount of a Notion setup is subtraction. If a database would hold fewer than ten rows a year, it is a page, not a database. If you cannot name the view you would open weekly, skip the database. Skip the habit tracker, the reading list, and the dashboard that exists to display other dashboards. Skip the status property on Content until you publish twice a month. If you are unsure whether a database earns its place, wait a week and notice whether you missed it.
Every property is a field you have to keep filled, and the version you maintain beats the version you designed. Two views carry most of the value, and neither needs customization: Tasks filtered to Status not Done and sorted by Days Overdue descending, plus Projects sorted by effective rate ascending where hours are logged. Build those two, open them every morning, and let the other views wait until a question repeats twice.
Do this today
- Create the five databases with the exact names above, and add nothing else from any template for now.
- Add the three relations and link every existing project, task, and invoice row before you enter anything new.
- Paste the
Days Overdueformula on Tasks, open the Overdue view, and sort it before you close the laptop.