Most client dashboards fail for the same reason: they’re designed for the screenshot, not for Tuesday afternoon when you’re late on a deliverable and can’t remember which folder the logo files live in. I’ve built and rebuilt my own client system four times in three years, and the version that finally stuck is the least impressive-looking one. It has three databases, two views, and zero progress bars. That’s it.
The first thing to get right is the project database. Not a page per client—a database where each client is a row and each project is a linked row. I use two separate databases: Clients and Projects. The Clients database holds contact info, billing details, and a rollup of active projects. The Projects database holds the actual work: status, deadline, rate, and a relation back to the client. This sounds obvious, but most people I’ve helped were doing it the other way around—a giant page per client with sub-pages for each project. That works until you have eight clients and need to see every deadline in one list. Databases win.
Next, the views. You need exactly two: a Kanban board grouped by status, and a calendar view filtered to the current month. The Kanban gives you the satisfying drag-and-drop dopamine hit when you move something to Done. The calendar keeps you honest about overlapping deadlines. I also add a filtered table view called This Week that shows only projects with a deadline in the next seven days. That single view is the most valuable thing in my workspace. If you build nothing else, build that.
Now the part everyone skips: client-facing pages. Inside each project row, I create a linked page with a simple structure—Overview, Deliverables, Files, Notes. The Deliverables section is a checklist, not a paragraph. The Files section is a linked database of assets with a status property (Draft, In Review, Approved). This means when a client asks ‘where are we on the logo?’ I can share a single URL and they see exactly what’s approved and what’s not. No more email threads with six attachments.
Invoices deserve their own small database. I resisted this for a long time because I thought it was overkill. It’s not. An Invoices database with Client (relation), Amount, Due Date, and Status (Draft, Sent, Paid, Overdue) takes ten minutes to build and eliminates the awkward ‘hey, just checking in on that invoice’ email. I add a rollup on the client page showing total outstanding. Seeing that number at a glance has changed how I follow up.
The thing that makes this system stick is the weekly review. Every Friday, I open the This Week view, move anything unfinished, and check the Overdue invoice filter. It takes eight minutes. I used to skip reviews because my dashboard was so complicated that opening it felt like a chore. Simplicity is what makes the review happen. A beautiful dashboard you avoid is worse than an ugly one you check daily.
A few design notes, since this audience cares. Use a soft neutral background for the page (I like a warm off-white), one accent color for status tags, and consistent icons for your databases. Avoid more than three colors. The goal is calm, not carnival. I also hide the database title on linked views and add a small header image—it makes the page feel intentional when you open it in a rush.
One mistake I see constantly: putting everything in one giant dashboard. Your client work, your personal tasks, your reading list, and your grocery list do not belong on the same page. Split them. The client dashboard should only show client things. When you’re in work mode, you want zero distractions from your personal life, and vice versa. I keep a separate home page with links to each dashboard—Clients, Content, Admin, Personal—and nothing else.
Finally, don’t over-automate on day one. Notion’s formulas and automations are tempting, but every automation you add is something that can break or confuse you later. Start with manual statuses. Add a formula for ‘Days Until Deadline’ once you’ve used the system for two weeks and know you’ll keep it. I’ve watched people spend a whole weekend building an elaborate automated pipeline and abandon it by Wednesday because they didn’t understand their own setup.
If you want a shortcut, our Client Command template includes this exact structure—Clients, Projects, Deliverables, and Invoices databases, pre-linked with the views described above. You can duplicate it and be running in under ten minutes. But if you’d rather build your own, follow the order here: databases first, views second, client pages third, invoices last. Build it small, use it for a week, then add. That’s the version that survives.