How I Organize Multi-Project Code Repos, Docs, and Customer Notes Solo

The biggest operational danger of being a solo bootstrapper is not running out of cash or encountering impossible technical bugs.

It is cognitive fragmentation.

When you run a solo business, you don’t just write code. You switch constantly between five distinct mental modes:

• Shipping feature code and fixing bugs.
• Writing long-form marketing content and newsletters.
• Reviewing client feedback and drafting proposals.
• Managing DNS records, server configurations, and environment secrets.
• Logging expenses, receipts, and corporate filings.

If your digital workspace consists of twenty open Chrome tabs, files scattered across your Desktop, and notes split between Apple Notes, Google Docs, and Notion, every context switch costs fifteen minutes of mental reorientation.

After years of trial, error, and messy hard drives, I converged on a simple, local-first directory structure that keeps all my projects, documentation, and customer notes organized on a single machine.

Here is the exact taxonomy I use every day.

The Root Directory: Flat, Predictable, Local

Everything lives inside a single top-level directory in my user home folder:

~/Workspace/
├── _inbox/
├── _archive/
├── apps/
├── content/
├── client/
└── operations/

Notice the underscores on _inbox and _archive. In alphabetical file listings, this guarantees that temporary incoming files float to the very top, while retired projects sink to the bottom.

Let’s look inside each core directory.

1. ~/Workspace/_inbox/

This is the digital staging ground. Any downloaded contract, screenshot, unprocessed receipt, or raw audio recording lands here first.

I treat this directory like physical mail on an entryway table: it must be emptied and filed to its permanent home during my Friday afternoon review. Nothing stays in _inbox permanently.

2. ~/Workspace/apps/ (Software & Code)

Every web application, micro-SaaS, or internal tool has its own dedicated directory under apps/:

~/Workspace/apps/saas-project/
├── .git/
├── src/
├── docs/
│   ├── ARCHITECTURE.md
│   ├── ROADMAP.md
│   └── DEPLOYMENT.md
├── scripts/
└── .env.example

Crucial rule: Keep project-specific architectural decisions and deployment instructions inside a docs/ folder directly inside the Git repository.

When deployment instructions live inside the codebase, they remain synchronized with code changes across branches, rather than getting lost in an external third-party wiki.

3. ~/Workspace/content/ (Publishing & Editorial)

Editorial work requires a different mental model than software engineering. Mixing draft blog posts with code repositories creates unnecessary clutter.

Under content/, each publication has its own space:

~/Workspace/content/startuptrio/
├── articles/
├── newsletter/
├── assets/
│   └── diagrams/
└── STYLE-GUIDE.md

All content is drafted in plain Markdown. Plain text never requires an internet connection, never locks you into a proprietary document format, and can be searched across the entire hard drive in milliseconds using grep or Raycast.

4. ~/Workspace/client/ (Consulting & Advisory)

If you take on consulting or freelance advisory work, each client receives a standardized folder structure:

~/Workspace/client/acme-corp/
├── contracts/       <-- Signed MSAs, SOWs, and NDAs
├── invoices/        <-- Sent PDF invoices and payment receipts
├── notes/           <-- Timestamped meeting notes (YYYY-MM-DD-topic.md)
└── deliverables/    <-- Final exported PDF reports and Figma assets

By keeping contracts and invoices inside the client folder, tax season becomes trivial. You don’t have to search your email inbox to find out how much Acme Corp paid you in Q2; you just open their invoices/ folder.

5. ~/Workspace/operations/ (Legal, Taxes & Banking)

This directory holds the permanent records of the business entity:

~/Workspace/operations/
├── legal/           <-- Articles of Organization, Operating Agreement, EIN letter
├── banking/         <-- Annual bank statements, tax returns (by year: 2024/, 2025/)
└── subscriptions/   <-- Inventory of active software tools and renewal dates

When my accountant asks for my 2025 corporate tax documentation or state franchise tax proof, I can zip the relevant subfolder in under thirty seconds.

Fast Navigation with Raycast and Terminal Aliases

A clean folder structure is only useful if you can access files instantly without clicking through nested Finder windows.

1. Raycast / Spotlight Quick-Keys: Set up file search shortcuts. Typing apps saas opens the code repo in your editor immediately.
2. Terminal Zsh Aliases: Add quick jump aliases to your ~/.zshrc:

   alias cda="cd ~/Workspace/apps"
   alias cdc="cd ~/Workspace/content"
   alias cdo="cd ~/Workspace/operations"

The Mental Freedom of a Clean Desk

Your computer’s file system is the digital equivalent of your physical office desk.

When your files are organized into a clean, predictable hierarchy, cognitive friction disappears. You sit down in the morning, jump directly to the exact file or repository you need, and start building.

Take two hours this Friday. Consolidate your scattered tabs, empty your Desktop, and build a local directory taxonomy that supports your long-term creative focus.

Related Operational Guides

For deeper frameworks and complementary operational workflows, see:

• Minimalist founder tool choices that reduce complexity
• Resisting the temptation to endlessly migrate productivity tools
• Establishing office and digital boundaries to prevent burnout