My 5-Table Freelance OS: Clients, Projects, Invoices, Notes, and Nothing Else

I used to have seventeen Notion databases.

Client CRM. Project tracker. Task manager. Meeting notes. Content calendar. Idea inbox. Vendor list. Personal CRM. Goals. Habits. Reading list. And a few more I created at 11 p.m. because it felt productive.

Most of them were ghosts. They looked organized for about nine days and then quietly died.

When I finally got honest, I deleted almost everything and kept five tables. That stripped-down system still runs my entire freelance consulting practice.

This is the exact setup.

The rule that forced the cut

If a database did not help me get paid, keep a promise, or avoid dropping a ball, it got archived.

Everything else was productivity theater.

The five tables that survived

1. Clients

The single source of truth for every relationship that involves money or potential money.

Core properties:

• Status (Lead / Active / On Hold / Closed)

• Primary Contact

• Email

• Last Contact Date

• Next Follow-Up Date

• Health (Green / Yellow / Red)

• Lifetime Value

• Linked Projects

• Linked Invoices

• Linked Notes

I update Health every Monday. If a client sits on Yellow or Red, they move to the top of my list until the status changes.

2. Projects

Only active or recently completed work. No graveyard of old ideas.

Core properties:

• Client (relation)

• Status (Not Started / In Progress / Waiting / Done)

• Owner

• Due Date

• Priority

• Estimated Hours

• Actual Hours (simple number I fill in at the end)

• Open Tasks (rollup)

• Linked Invoices

• Linked Notes

When a project moves to Done, I leave it for thirty days and then archive it. The database stays clean.

3. Invoices

The money table. I used to track this in a spreadsheet and in my accounting tool. That was two places too many.

Core properties:

• Client (relation)

• Project (relation)

• Invoice Number

• Amount

• Status (Draft / Sent / Paid / Overdue)

• Issue Date

• Due Date

• Paid Date

• Payment Method

• Notes

I filter this view by “Unpaid” every Friday. Anything overdue turns red. No more surprise cash-flow gaps.

4. Notes

Meeting notes, key decisions, important emails, and random context that needs to survive longer than my memory.

Core properties:

• Client (relation)

• Project (relation)

• Date

• Type (Call / Meeting / Email / Decision / Other)

• Key Takeaways

• Follow-Up Needed (checkbox)

I force myself to fill in Key Takeaways before I leave the page. Future me never wants to re-read five pages of raw notes.

5. Tasks

The action layer. Kept deliberately light.

Core properties:

• Client (relation, optional)

• Project (relation)

• Status (To Do / Doing / Done)

• Due Date

• Priority

• Blocked (checkbox)

• Time Estimate

• Notes

I do not put every tiny personal to-do here. Only work that would create a problem if it slipped.

The views I actually open

Today

Filtered Tasks + Follow-Ups due today or overdue. Sorted by priority. This is my default home page.

Client Health

Clients sorted by Health, then Last Contact Date. Yellow and Red sit at the top.

Money Waiting

Invoices filtered to Sent or Overdue. I look at this every Friday before I close the laptop.

Waiting On Someone Else

Projects and Tasks where Status is “Waiting.” Stops me from chasing things that are not mine to move.

How the five tables talk to each other

• Every Project belongs to one Client

• Every Invoice belongs to one Client and usually one Project

• Every Note and Task can link to a Client, a Project, or both

• Rollups show me open tasks and unpaid invoices without extra clicking

That is the entire relationship map. No deep nesting. No rollup of a rollup of a rollup.

What I refuse to add

I get asked all the time why I don’t have:

• A separate Leads database

• A Content calendar

• A Personal goals tracker

• A Vendor or contractor database

• Time-tracking integrations

Answer: because each one would need weekly maintenance, and most weeks I will not give it. The five tables already cover getting paid, keeping promises, and not dropping balls. Everything else can live in a simple note or a temporary page.

The Monday reset that keeps it alive

Fifteen minutes. Timer on.

1. Update Client Health

2. Clear or reschedule overdue Tasks and Follow-Ups

3. Check the Money Waiting view

4. Archive anything that has been Done for more than thirty days

If I cannot finish the reset in fifteen minutes, the system has gotten too heavy and something needs to be cut.

Results after running this for eighteen months

• Zero lost client follow-ups

• Invoices go out faster because the data is already sitting in the Project

• I can answer “What’s the status?” in under thirty seconds

• New client onboarding takes minutes instead of half an hour of copying information around

• The system still works when I am tired, traveling, or dealing with a sick kid

How to build your own version

1. Create five full-page databases with the properties above

2. Add the relations

3. Build the four views

4. Create a simple “New Client” template button that pre-fills Status, Health, and a default follow-up task

5. Run the Monday reset for three weeks before you add anything else

That is the whole operating system.

Five tables.
Nothing else.

If it takes longer to maintain than the work it saves, it does not belong on the pegboard.