Advice written for teams doesn't fit a one-person business. You don't need permission tiers, folder owners, or a naming convention that survives committee review. What you need is a structure that takes no thought at 11pm, works when you're juggling six projects, and doesn't collapse the first time a project runs long.
The constraint that shapes everything: you are the only person maintaining this, and you will not maintain anything elaborate.
Start by splitting business from personal
Before folders, accounts. One cloud account for business, one for personal — or at minimum, one clearly separated top-level folder for each.
This is worth the small hassle for four reasons that all arrive eventually: you can hand a contractor or accountant access to business files without exposing personal ones; tax time doesn't involve sorting; if you ever incorporate or sell, the business files are already a discrete thing; and if a client relationship goes badly, your business records are separable from your life.
Do it at the start of a tax year if you can. Retrofitting later is a weekend.
The top level, solo version
00 Inbox
01 Admin
02 Finance
03 Clients
04 Projects
05 Marketing
06 ArchiveThe addition versus a company structure is 04 Projects — your own work that isn't for a client. Products you're building, the website, a course, speculative work. Freelancers who don't separate these end up with personal projects filed under a client's folder because that's where they started.
If you have no self-directed work at all, drop it. Six folders is better than seven.
The anatomy of a project folder
03 Clients/
Northwind Design/
2025-04 Brand refresh/
00 README.md
01 Brief/
02 Working/
03 Deliverables/
04 Invoices/Two levels: client, then project. Date-prefix the project folder in YYYY-MM so multiple projects for the same client sort chronologically.
For clients where you do one continuous thing, skip the project layer and use the five standard folders directly. For clients where you do discrete jobs, the project layer earns its place fast — the third time you work with someone, an undifferentiated folder becomes hard to read.
00 README.md is the highest-value file in a solo setup, because you have no colleague to remind you of anything:
Northwind Design — Brand refresh
Contact: Ana Reyes, ana@northwind.example
Started: 2025-04-01 Due: 2025-05-30
Fee: 4,200, 50% up front (paid 4/3), balance on delivery
Scope: logo, colour, type, one-page guide. NOT website.
Status: concepts sent 4/8, awaiting feedback
Notes: Ana prefers phone over email. Approvals go through Tom (CFO).Update the status line whenever anything changes. Ten seconds. When you come back to this project after two weeks on something else, this file is the entire context reload — and the scope line is what protects you when a "quick extra" arrives.
Working versus deliverables, even alone
The instinct when working alone is to skip the split, since you know what's what. Don't.
The value of the deliverables folder shows up at three specific moments: when a client asks for a file eight months later, when a client disputes what was delivered, and when you're building a portfolio and want the finals without sifting.
03 Deliverables contains exactly what the client received, named the way they'd recognize it, in the format they got. Nothing else. Even if it's three files.
Handle the desktop and downloads problem
For solo workers, the desktop and downloads folder are the real filing system, and everything else is aspirational. Two mechanisms:
A staging folder that isn't the desktop. 00 Inbox at the top of your drive. Anything with no obvious home goes there instead of the desktop. It's allowed to be messy. You empty it Friday.
A weekly desktop sweep. Five minutes, same time. Everything on the desktop goes to its project folder, to 00 Inbox, or to the bin. The desktop returns to empty.
The reason the desktop accumulates isn't laziness — it's that filing requires deciding, and deciding mid-task is expensive. The inbox folder removes the decision from the moment of the interruption and batches it into a time when deciding is the task.
Templates, so starting is free
Keep a _TEMPLATES folder at your drive root:
_TEMPLATES/
_TEMPLATE Client Project/ ← the empty folder structure + blank README
Proposal.docx
Contract.docx
Invoice.xlsx
Client questionnaire.pdfNew project: copy the folder, rename, fill the README. Under a minute, and it means every project starts organized rather than being organized later, which never happens.
The underscore keeps _TEMPLATES sorted first, where you'll see it.
The active list, outside the folders
Folders don't tell you what's urgent. Keep one file — 00 ACTIVE.md at the drive root, or a note pinned somewhere you look daily:
ACTIVE
Northwind brand refresh — concepts sent 4/8, chase 4/11
Ferris website copy — drafting, due 4/22
Own site rebuild — stalled, pick up after Ferris
WAITING ON
Ana — logo feedback (since 4/8)
Ferris — sitemap approval (since 4/2) ← chase this
INVOICES OUT
INV-0184 Northwind 2,400 — due 4/22
INV-0181 Ferris 1,100 — OVERDUE 21 days ← chaseThree sections, one screen, updated as you go. Solo work fails at the seams — the thing you're waiting on, the invoice nobody paid — far more often than it fails in the middle of the work. This file is where the seams live.
Close projects properly
When a project ends, five minutes:
- Final files in
03 Deliverables, named for the client - Final invoice sent, noted in the README
- Portfolio-worthy exports copied to
05 Marketing/Portfolio - README status changed to
CLOSED [date]with one line on how it went - Move the project folder to
06 Archive/Clients/2025/
Step three is the one freelancers skip and regret. Pulling portfolio images out of a project two years later means opening source files, hunting for the right export, and often discovering the fonts are gone. Doing it at close takes three minutes.
Step four's one-line note — went well, scope crept in week 3, quote 15% higher next time — is worth more than any general business advice you'll read this year, because it's about your actual work.
Back it up like the business it is
One-person businesses have one point of failure and it's usually a laptop. The minimum:
- Everything in a synced cloud drive, not just on the machine
- One separate backup that isn't that sync — an external drive or a second cloud service — because sync propagates deletion and corruption faithfully
- The small permanent pile (contracts, tax, registrations) copied somewhere off-site
Sync is not backup. If you delete a folder or a file corrupts, sync copies the problem everywhere within seconds. Most services have a recovery window, and most people discover its limits at the worst time.
Next in this series: How to Archive Finished Projects Safely