Your task board says one thing. The client email says another. The document with the actual scope is somewhere in Google Drive, and you know you wrote down the next step. Somewhere.
So you open another tab.
This is the part of running a business that gets described as “getting organized,” but I think that undersells it. You’re trying to make decisions while piecing together the information you need.
A useful Notion business setup gives that information a connected home. You can find the project, see the next action, and open the relevant notes without rebuilding the whole picture in your head.
And yes, you can make it look good. I love that part too. But let's get it working first…
Start with a workflow, not a blank dashboard
Before creating databases, choose a piece of work you actually do. For a service-based founder, that might be taking a new client from inquiry through delivery.
Write down the stages. Where does the inquiry arrive? Where do you record the scope? What happens after someone says yes? How do you know what needs doing next?
Then identify the information you need to track: people, projects, actions, and reference material.
That's your starting architecture. You don't need to build a section for every future version of your business before the current one has a usable task list.
Step 1: Give the workspace a clear structure
Start with a Home page and a few useful destinations:
Work: projects and tasks.
Relationships: contacts and follow-ups, if you need them.
Knowledge: instructions and reference material.
Archive: completed or inactive work you still need to retain.
Keep your master databases in stable locations. Your Home page can display filtered views of them, so you aren't moving records around to make the dashboard useful.
The labels aren't sacred. Use names that make sense to you. The test is whether you can tell where new information belongs without debating it every time.
Step 2: Build the databases your work needs
For many service businesses, Projects, Tasks, Contacts, and Knowledge make a useful starting set. Financial tracking is optional and should have a clear purpose.
Projects: what you're working toward
Give each project a name, status, and relevant dates. Add a relation to Contacts if the work belongs to a client, and a relation to Tasks for the actions supporting it.
Define what a completed project actually means. “Website updated” is more useful when you know which pages are included and what has to be tested before you close it.
An owner property becomes useful when someone else is involved. A solo founder doesn't need to populate their own name in every record purely for completeness.
Tasks: what needs action
Each task should describe something you can do. “Client onboarding” might be a process; “Send the onboarding questionnaire” is an action.
Start with Status and a Project relation. Add dates deliberately.
I like separating the date I intend to do something from the date it is actually due. They answer different questions. If everything gets the deadline as its work date, the dashboard won't help you see what needs attention beforehand.
Standalone tasks can exist too. Don't invent a project just to satisfy a relation.
Contacts: the relationship context
A single Contacts database can hold leads, clients, collaborators, and vendors, with a Type property distinguishing them. And I’m telling you—I do think this is the superior strategy. I’ve done it the other way, separating my clients from my Contacts but you know what happens? A contact becomes a client! And then you have a duplicate database and contact page.
Just make one.
Add follow-up dates and pipeline stages only where they help your actual process. A vendor doesn't need to move through the same sales pipeline as a lead.
Related projects make a contact record more useful. You can see what you've worked on together instead of reconstructing their history from email.
Knowledge: information you'll use again
Use a Knowledge database for repeatable instructions and reference material. Useful properties might include Type, related Project, and a review date for information that can become outdated.
You don't have to turn every thought into an official procedure. A practical instruction someone can follow is more valuable than a polished document nobody opens.
Finances: an optional visibility layer
Notion can help you track an invoice's project, amount, payment status, and next action. That does not make it your accounting ledger.
Keep authoritative financial records in appropriate accounting software. If you mirror information in Notion, define how it stays current. Otherwise, you've created two places to update instead of one useful view.
Step 3: Connect records where the relationship is useful
A relation connects one record to another. A task can relate to its project; a project can relate to its client.
A rollup summarizes a property from related records. For example, a project can show a task-completion measure when you've configured the relation and the relevant task property.
Matching property names across databases isn't what makes that work. The configuration is. Consistent labels simply make the system easier to understand.
And be careful with completion measures: checking off nine tiny tasks doesn't mean the tenth, business-critical task is almost finished. Use the numbers as a signal, not a substitute for reviewing the work.
Step 4: Create templates for work you actually repeat
A project template might include:
The agreed outcome and scope.
Milestones or delivery stages.
A place for relevant notes.
A linked Tasks view filtered to the project.
Test the template by creating a sample project and task. Confirm the task appears in the right place. A view sitting inside a project page isn't automatically filtered correctly just because it looks like it belongs there.
Start with one common project type. Add variations when repeated work shows you need them.
Now…just a note: I think this is an important step here: add variations ONLY when repeated work shows you need them. This is why I say that. I’ve built the overcomplicated system to start with, trying to anticipate my every need. And you know what happened? I built things I NEVER use. Ever.
So, let life and business inform the systems you need. Sure there’s a place for anticipation, but you can also anticipate yourself into an overcomplicated system you never use, too.
Step 5: Build a dashboard around questions
Your dashboard should help you decide what to do, not show off everything you've built.
Useful questions include: What am I doing today? Which projects need attention? Who am I following up with? What am I waiting for?
Answer those with a small number of linked database views. A linked view displays the source records; it doesn't create a second copy. Editing a record through that view changes the underlying record.
For example, your Tasks database can appear on Home as “Today,” inside a project as “Project Actions,” and in a weekly planning page as “This Week.” Those are different windows into the same work.
The views will reflect changes to the data. They will not magically know that a client moved a deadline if nobody updates the record.
Step 6: Check access before inviting people
Keep the initial permission setup as simple as the business allows. A solo founder working with one contractor doesn't necessarily need departmental teamspaces and elaborate groups. Hell, I run my business out of a “private” space. No team spaces over here at Coach Ellyn! Will that change in the future? Maybe. But I’ll deal with that change if and when it happens…
Decide what each person needs to see, edit, or administer. Remember that a filtered view is not a security boundary. Hiding a record from a view isn't the same as restricting access to it.
Notion supports page and database access controls, including database page-level (and row-level) rules. Available features depend on your plan, so check the current documentation and test with the intended collaborator's access before storing confidential information.
Step 7: Run one real project through it
Before migrating years of content, use the setup for real work.
Create the project. Add its next actions. Capture a note. Change a date. Finish a task. See whether your dashboard helps you notice the right things.
If a step feels awkward, investigate that step. Don't respond by adding three new dashboards.
The first useful milestone is being able to find the current context and next action without hunting. You can build from there.
When a template makes sense
If you know you need a connected starting structure but don't want to architect it from scratch, my Solopreneur Life & Business OS gives you a prebuilt foundation for your life and business workspace.
A template is a starting point you adapt. It isn't a promise that your existing tools, information, and custom workflows arrive migrated and configured for you.
If you aren't sure what needs fixing—or whether moving something into Notion is even the right decision—The Huddle is where we investigate that together before committing to a build.
Frequently Asked Questions
-
Enough to support the workflow you're building. Projects and Tasks may be sufficient to start; Contacts and Knowledge become useful when that context is otherwise scattered. Add financial visibility only when it solves a real need.
-
No. Pilot one workflow, then move active information in manageable stages. Keep historical material accessible while you decide what deserves a place in the new setup.
If most of your work requires you, that is something worth thinking about, and it might be harder for you to scale just by using AI. If you do a lot of repetitive tasks, AI is going to help a lot.
-
Absolutely. A clear task view and a usable project page can do more for your day than a dashboard packed with widgets.
And honestly? Sometimes Notion just needs to be the brain. If you work better by interacting with a ChatBot, I highly recommend setting up Notion AI, Claude + Notion, or similar so that your Notion just becomes the BRAIN and the AI bot becomes the muscle doing the thing!
Make the workspace useful before making it bigger
You should be able to open your workspace, find the current information, and know your next action.
Build that first. Everything else has to earn its place.
