how to build a project management system from scratch as a solopreneur

how to build a project management system from scratch as a solopreneur

for the first two years of running my own business, I did not have a project management system. I had sticky notes, random text files, a couple of spreadsheets, and a lot of stuff that only existed in my head. somehow I made it work, until I started dropping balls. missed deadlines, forgotten follow ups, duplicate work, and the constant nagging feeling that something important was slipping through the cracks.

building a project management system from scratch changed everything. and I want to emphasize “from scratch” because the biggest mistake I see solopreneurs make is copying someone else’s elaborate system without understanding why each piece exists. you end up maintaining a system instead of actually using it.

in this guide, I will walk you through building your own system step by step, the same way I built mine.

step 1: assess what you actually need

before you touch any tool, sit down and answer these questions honestly:

how many active projects do you run at once? if the answer is 2 to 3, you need something simple. if it is 10+, you need something with real structure.

do you work with clients? if yes, you need a client management layer. if you are building a product solo, you can skip this.

how many tasks do you generate per week? 10 tasks per week needs a different system than 50 tasks per week.

do you work with anyone else? contractors, virtual assistants, or collaborators change your tool requirements.

what is your budget? this matters because the right tool at the wrong price is still the wrong tool.

I made the mistake early on of building an elaborate system for a business that only had 3 projects and 15 tasks per week. the system took more time to maintain than the work itself. start simple and add complexity only when you feel genuine pain.

step 2: choose the right level of tool complexity

not every solopreneur needs Notion or Asana. here is how I think about tool selection:

complexity level best for recommended tools cost
minimal 1 to 3 projects, fewer than 15 tasks/week Apple Reminders, Google Tasks, paper free
light 3 to 5 projects, 15 to 30 tasks/week Todoist, TickTick, Things 3 free to $5/mo
moderate 5 to 10 projects, clients, 30 to 50 tasks/week Notion, Trello, Basecamp free to $12/mo
advanced 10+ projects, team, complex workflows Asana, ClickUp, Monday.com $10 to $25/mo

most solopreneurs fall in the light to moderate range. I will focus on the moderate level using Notion because it offers the best flexibility for building a custom system. but the principles apply regardless of tool.

for more on this, see our guide on best ai project management tools in 2026 (manage projec.

step 3: set up your Notion workspace (or equivalent)

I am going to walk through building this in Notion specifically because it is what I use and because it is flexible enough to grow with your business. if you prefer a different tool, adapt the concepts.

create these five pages in Notion:

  1. dashboard (your home base, links to everything)
  2. projects (database of all active and archived projects)
  3. tasks (master task database)
  4. clients (if applicable, database of client information)
  5. resources (SOPs, templates, reference materials)

that is it. five pages. resist the urge to create more. you can always add later, but removing clutter is much harder than adding structure.

the projects database

create a Notion database with these properties:

property type purpose
project name title what the project is called
status select (active, on hold, completed, archived) where it stands
priority select (high, medium, low) how important it is
deadline date when it needs to be done
client relation (to clients database) which client this is for
category select (your categories) type of work
notes text context and details

I keep my project statuses simple. a project is either active (I am working on it), on hold (waiting on something), completed (done), or archived (done and no longer relevant). I have seen people with 8 status options. that is too many.

the tasks database

this is where most of your daily interaction happens. here are the properties I use:

property type purpose
task name title what needs to be done
status select (to do, in progress, done) current state
project relation (to projects database) which project this belongs to
priority select (high, medium, low) how urgent and important
due date date when it needs to be done
estimated time number hours you think it will take
actual time number hours it actually took (fill after)

the estimated vs actual time tracking is optional but incredibly valuable. after a few weeks of tracking, you will learn how long things actually take you, and your planning will get dramatically better.

step 4: build your task management workflow

having a database is not enough. you need a workflow, a repeatable process for how tasks flow through your system. here is mine:

capture. when a task comes to mind or appears (from an email, a call, a random thought), I capture it immediately into the tasks database with minimal info. just the name and the project. I do this on my phone using Notion’s mobile app or Todoist as a quick capture tool.

process. once a day, usually in the morning, I go through unprocessed tasks and add priority, due date, and time estimate. this takes about 5 minutes.

plan. during my weekly planning session (sunday evening), I look at all tasks due this week and assign them to specific days using Notion’s calendar view.

execute. during the day, I work from my daily view which shows only today’s tasks sorted by priority.

review. on friday, I review what got done, what did not, and adjust next week’s plan accordingly.

this capture, process, plan, execute, review cycle is the backbone of any good system. the specific tool does not matter as much as having this consistent flow.

step 5: add project tracking views

one of Notion’s strengths is views. you can look at the same data in completely different ways. here are the four views I use for my projects database:

board view (kanban). columns for each status (active, on hold, completed). I use this for a quick overview of where everything stands. this is my default daily view.

table view. all projects with all properties visible. I use this when I need to see details or filter by client, category, or deadline.

calendar view. projects plotted by deadline. I check this during weekly planning to see what is coming up.

gallery view. each project as a card with a cover image and key details. honestly, I mostly use this to make my dashboard look nice. but it does help me spot active projects at a glance.

the key insight is that these are all showing the same underlying data. when I update a project’s status in the board view, it automatically reflects in the table and calendar views. one source of truth, multiple ways to see it.

step 6: add the client management layer

if you work with clients, you need a way to track them. this does not need to be a CRM. for solopreneurs, a simple Notion database works perfectly.

here is my client database structure:

property type purpose
client name title company or person name
contact name text primary contact
email email main contact email
status select (active, prospect, past) relationship status
projects relation (to projects database) linked projects
monthly value number revenue from this client
notes text important context
last contact date when you last spoke

the “last contact” field is one I check weekly. if I have not spoken to an active client in more than two weeks, something is wrong. either I am not communicating enough or the project is stale.

I also create a simple client page template that includes: a project summary section, a communication log, key documents and links, and invoicing notes. when I open a client’s page, everything I need is right there.

step 7: build the automation layer

once your basic system is working (and I mean actually working, not just set up), you can start adding automation to save time. here is what I automate:

recurring tasks. every monday I need to check analytics. every friday I need to send invoices. every first of the month I need to review subscriptions. instead of remembering these, I set them up as recurring tasks. in Notion, you can use the recurring template feature or a tool like Zapier.

email to task. when I get an email that requires action, I forward it to my Notion email address (available on the Plus plan) and it becomes a task automatically. this saves me from using my inbox as a to do list.

status automations. when I mark all tasks in a project as done, I want the project status to automatically change to completed. Notion’s built in automations handle this.

automation tool what it does
recurring tasks Notion recurring templates creates weekly/monthly tasks automatically
email to task Notion email integration or Zapier turns forwarded emails into tasks
project completion Notion automations updates project status when all tasks done
weekly report Notion + Zapier generates a weekly summary of completed tasks
calendar sync Google Calendar + Notion syncs deadlines to your calendar

I want to be clear though. do not automate anything until your manual system works for at least a month. automation on top of a broken system just creates faster chaos.

step 8: scale the system over time

your system at month 1 should not look the same as your system at month 12. here is how mine evolved:

month 1 to 3: bare bones. just the projects and tasks databases. no automation, minimal views. I was learning what I actually needed by doing the work manually.

month 3 to 6: added clients and views. as my client work grew, I added the client database and connected it to projects. I built the calendar and board views when I realized I needed different perspectives on the same data.

month 6 to 12: automation and templates. once I understood my repeating patterns, I automated recurring tasks and built templates for common project types. a new client onboarding template saves me about 2 hours per client.

month 12+: refinement. I stripped out things I never used (several custom properties, some views, a resource library that I never updated). the system got simpler over time, not more complex.

the best systems are living things. they evolve as your business evolves. set a reminder every quarter to review your system and ask: what am I not using? what do I wish I had? what is causing friction?

common mistakes to avoid

overbuilding on day one. I see solopreneurs spend a full weekend building an elaborate Notion setup with 15 databases, custom formulas, and synced blocks everywhere. then they never use it because it is too complex to maintain. start with the minimum and add only what you need.

copying someone else’s system. YouTube is full of “my ultimate Notion setup” videos. those systems were built for that specific person’s workflow. your workflow is different. use them for inspiration, not as templates to copy wholesale.

not using the system daily. the best system in the world is useless if you do not put tasks in it and check it every day. build the habit first, optimize later.

tracking too many things. every property you add to a database is something you need to update. if you are not going to consistently fill in a field, delete it. I removed a “energy level” property from my tasks after I realized I never once updated it.

ignoring the review process. the weekly review is not optional. it is where you catch what fell through the cracks, notice patterns, and improve the system. skip it and your system slowly degrades into an outdated mess.

my recommended starting template

if you want to get started today, here is the absolute minimum viable system:

  1. create a Notion account (free plan is fine to start)
  2. create one database called “tasks” with: name, status (to do/in progress/done), priority (high/medium/low), due date
  3. create a board view grouped by status
  4. create a calendar view for deadlines
  5. add your current tasks (start with what you know you need to do this week)
  6. every morning, check the board and pick your top 3 tasks
  7. every friday, review what got done

that is it. no projects database, no client tracking, no automation. just tasks. use this for two to four weeks. if you feel the need for project grouping, add it. if you need client tracking, add it. let the system grow from real needs, not imagined ones.

frequently asked questions

how long does it take to build this system?

the minimum viable version takes about 30 minutes. the full system with projects, clients, views, and basic automation takes about 2 to 3 hours spread over a few sessions. but the real building happens over months as you refine based on actual use.

should I use Notion or something simpler?

if you have fewer than 3 active projects and fewer than 15 tasks per week, Notion is overkill. use Todoist, Apple Reminders, or even a paper planner. Notion shines when you need the flexibility to connect tasks to projects, projects to clients, and build custom views of your data.

what if I already have tasks scattered across different tools?

do a migration over one weekend. collect tasks from all your current locations (email, notes, sticky notes, your head) and put them into your new system. then commit to using only the new system going forward. the transition period is uncomfortable but necessary.

how do I handle projects that have subtasks within subtasks?

keep it flat. I learned the hard way that deeply nested task hierarchies become impossible to maintain as a solopreneur. if a task is too big, break it into 3 to 5 smaller tasks at the same level. if a project has multiple phases, create a separate task for each phase. resist the nesting temptation.

can this system work for a small team, not just solo?

yes, with some additions. you will need to add an “assigned to” property on tasks and adjust your views to filter by person. Notion’s free plan supports up to 10 guests. for a team of 2 to 5, this system scales well. beyond that, consider dedicated tools like Asana or ClickUp that are built for team workflows.

related reading

more articles from the same topic I think you will find useful: