Notion Office Hours: Notion for Freelancers 🖇

Freelancer Tim’s Notion setup centers on one idea: build a small set of core databases (projects, tasks, calendar, companies, contacts, content, and more), then assemble them into a single “dashboard” that drives daily decisions—what’s urgent, what’s overdue, what’s next, and what’s still in the pipeline. The payoff is less clicking and less context switching, because the system links work items together while keeping the day-to-day view focused on the few lists that matter.

Tim’s journey into Notion started after bouncing through spreadsheets and tools like Google Sheets, Trello, Asana, and Airtable without getting a streamlined workflow. Notion arrived via Product Hunt, and the “deep dive” that followed turned it into his “organizational assault made it”—first for an entrepreneurship club managing events and budgets, then for his consulting work (no-code automations and operations). About three months into running Optimization full-time, Notion became the backbone of client and project management.

The workspace is intentionally utilitarian. Tim uses full-screen mode and treats Notion like an internal internet: pages link up and down through levels rather than relying on the sidebar. His daily entry point is a dashboard called “This Week,” designed around linked views of the same underlying task database. Tasks are modeled with a priority field (normal vs. urgent) and a status formula that outputs multiple states such as complete, blocked, overdue, and on time. “Blocked” is tied to a “waiting on” property; removing the date or the blocking condition changes the computed state, letting one task property reflect the task’s real-world condition.

Calendar management is handled through a single calendar database that includes milestones, deliverables, meetings, and events, separated visually using emojis (chat bubble for meetings, box for deliverables, etc.). Templates speed up repetitive data entry—clicking a meeting template can auto-apply emojis and tags. For meeting structure, Tim experiments with “database inception”: a meeting can contain a database of discussion items, each of which can spawn tasks or calendar events tied to that agenda.

Beyond tasks and calendar, Tim tracks client relationships and business context with databases for companies (including technology stack), contacts, and a curated “tag” database of tools harvested from sources like CrunchBase and G2 Crowd. He also uses attachments via Dropbox links, and captures research with the Web Clipper into a content database that can be filtered by topics.

The dashboard ties everything together with three operational lanes: normal tasks, urgent tasks, and completed items—plus additional sections for active projects, meetings, and a “dump” area for unstructured ideas. Tim avoids deleting tasks because historical reference matters for client communication and future scoping/estimating. He also treats the system as a living organism: instead of over-architecting, he starts small, then iterates based on friction found through real use. When asked about recurring tasks, he doesn’t rely on true automation; instead, recurring work is handled by keeping items pinned via status and viewing them through board-style day groupings.

Finally, Tim acknowledges tradeoffs: there’s no direct Google Calendar integration, so he uses Fantastical for fast event creation while maintaining a Notion calendar for planning. He also shares that his public-facing Notion pages prioritize lead generation over perfect SEO, focusing on “good enough” performance until scale makes optimization necessary. The overall message is pragmatic: design a workflow that matches how a freelancer actually thinks, then let Notion’s linked databases and dashboards do the heavy lifting.