Build a Notion Freelance Dashboard in One Afternoon
The dashboard that turns into a second job
Most Notion freelance dashboard builds fail the same way. The first version looks good: a cover image, four columns of linked databases, a gallery of client logos, a quote at the top. Three weeks later half of it is stale, because keeping it current means eleven clicks across five views, and nobody pays you to maintain a dashboard.
The real test of a Notion freelance dashboard is not how it looks on the day you build it. It is whether it still fills itself in on a Wednesday in February, when you have a deadline and no patience for housekeeping. That points toward fewer databases, fewer typed-in fields, and views that answer a question instead of displaying data.
Four databases behind one Notion freelance dashboard
A dashboard that works reads from four databases: Projects, Clients, Tasks, and Invoices. Every number on the page is a view of those four. If a figure cannot be traced back to one of them, it will be wrong within a month.
| Question | Source database | What the view shows |
|---|---|---|
| What am I working on? | Projects | Active projects, sorted by next deadline |
| Who is waiting on me? | Tasks | Status not Done, sorted by due date |
| What is late? | Invoices | Status Sent, days overdue above zero |
| Who have I gone quiet on? | Clients | Days since last touch, highest first |
| Can I cover next month? | Invoices plus a Cash row | Collected this month against monthly burn |
Five questions, five views. Anything that answers none of them is decoration, and decoration is what makes a page feel expensive to maintain.
The five questions in plain words
- What is due this week, and is the work actually moving?
- Which invoice is late, and by how many days?
- Which client has not heard from me in three weeks?
- Which project has burned more hours than the fee covers?
- How many months of expenses are covered if nothing new lands?
Question four is the one that changes behavior. Hours logged is the field people resist, and it is the only way to see that a fixed-fee project is quietly paying half your rate. Fill it in or the dashboard will lie to you politely.
Log hours where the work happens, on the task itself, in the same sitting. An estimate typed in on Friday evening is a guess wearing a number, and guesses are what make a fixed-fee project look profitable until the week you finish it.
Two properties to add now
A real Date property for invoice due dates, not "Net 30" typed into a text field. Text cannot be sorted or compared, and a due date you cannot sort by is a due date you will forget.
A Next Action date on every active project. It can sit empty for projects waiting on a client. Empty for more than a week on your own side of the work is the slack you keep meaning to find.
Formulas worth their maintenance
Three formulas cover almost everything the page needs. Paste them as Formula properties and sort or filter on the result.
Days overdue
`` dateBetween(prop("Due"), today(), "days") ``
Anything above zero is overdue, zero is due today, and negative is still in the future. Sort the invoice view descending and the worst problem sits at the top. The aging number itself is worth understanding, and the invoice aging guide covers what to do with it.
Days since last touch
`` dateBetween(prop("Last Touch"), today(), "days") ``
Run the same pattern against a client's Last Touch date and you get how long you have been quiet. A client at 45 days is not annoyed yet; they have started to forget you. That is cheaper to fix than a lost renewal, and it belongs next to revenue rather than buried in a notes page.
Runway
`` if(prop("Monthly Burn") == 0, 0, round(prop("Cash on Hand") / prop("Monthly Burn") * 10) / 10) ``
The multiply and divide around round() is deliberate. Notion's round() returns whole numbers, so 5.5 months of runway would display as 6, and rounding up on a survival number is a bad habit.
Notion has two formula engines in circulation at this point. These three behave the same in both, but date formatting tokens differ, so check your workspace version before rewriting anything if a formatted date returns an error.
What to leave off the page
Skip the habit tracker, the reading list, and the vision board. Skip the client gallery with photos, which is a page for your ego rather than for your week. Skip anything you have not opened in ten days.
Also skip the second dashboard. One dashboard per client, or per service line, is how a system doubles in size without adding a single decision. A client-facing page is a different build with a different audience and different rules, which is why the client portal setup is separate rather than a section of this page.
Look at it on a schedule, not by mood
A dashboard is a tool for a recurring question, so put it in a recurring slot. Twenty minutes, five questions, same order every week, and the numbers stay honest because something reads them. If you want that ritual written out, the Notion weekly review is the version to copy.
The build takes an afternoon. Looking at it every Friday is what keeps it from rotting, and that costs about as much as one coffee.
Do this today
- Create the four databases and the three formula properties before you add a cover image.
- Build the late-invoice view first, sort it by days overdue, and open it now.
- Put a recurring twenty-minute block on Friday afternoon and name it after the dashboard.