The filing cabinet: a folder structure AI can find its way around

When I started working with Claude Code, my computer looked like most founders' computers. Brand notes in one place, a proposal on the desktop, a client's logo inside my website folder, the same document saved three times with slightly different names. I could find things because I remembered roughly where I'd left them. The AI couldn't, and it doesn't remember anything between chats.

So it guessed. It would write a post without reading the voice notes, because it never found them. It would ask me where the price list was. Once it put a client document in my website's code folder, and I had to move it out again.

The fix was a filing system with one rule I could explain in a sentence. This guide is that system, adapted so it works for your business.

Why folders matter more with AI

A person who joins your business learns where things live over a few weeks. An AI starts every session from zero. It can search your files quickly, but only if the files are somewhere sensible and named in a way that makes sense.

A clear folder structure is the cheapest improvement you can make to your AI's work. It costs an afternoon and nothing else.

Step 1: Make one top folder

Create a single folder that holds all your business work. Call it whatever you like: "Business", "Main Folder", your company name. Everything the AI needs to see goes inside it.

In that top folder, write a short file called README.md. A .md file is a plain text file (the letters stand for Markdown, a simple way of writing headings and lists). This one is a map: a line for each folder saying what lives there. When something new arrives and you're not sure where it goes, the map answers.

I call mine the top of the filing cabinet. The AI reads it before asking me where anything is.

Step 2: Sort everything into four drawers

Nearly everything in a small business fits one of four kinds. Each kind gets its own home, and nothing lives in two.

• Client and brand files. Voice notes, logos, proposals, invoices, drafts, finished work. One folder per client or brand.
• Records. Anything you'd filter, sort or add up: tasks, leads, deals, hours worked. These belong in a spreadsheet or a simple database, not in loose documents.
• Knowledge. What you've learned and decided, written as notes. How you price, why you stopped offering a service, what a client told you about their customers.
• Code. If you have a website or small tools, their files live in their own folders and contain nothing else.

The drawer I see founders mix up most is the last one. Brand documents end up inside the website folder because that's where they were working that day.

Step 3: Use one test when you're not sure

Here is the rule that settles almost every argument with yourself:

> Would this file still matter if the website was deleted?

If yes, it's a business document and it goes in the client or brand folder. If no, it's part of the website and it stays in the code folder.

A brand guide still matters without the website, so it lives with the brand. A page template doesn't, so it lives with the code. I had to correct the same mistake twice before I wrote this rule down. Once it was written down, the AI followed it too.

Step 4: Give every client folder the same shape

This step made the biggest difference for me. Every client folder on my machine has the identical set of subfolders inside. For a content business that might be:

• brand (voice, logo, colours, rules)
• drafts (work in progress)
• review (waiting for approval)
• published (what went out)
• results (numbers and reports)

Pick the stages your own work moves through and use those names. The point is that the shape repeats. Once the AI knows one client folder, it knows all of them. It can find the voice notes for a client it has never worked on, because they're in the same place as every other client's.

Don't build new client folders by hand. Make a blank template folder with the empty subfolders and a short starter document, then copy it each time you take on a client. Building them by hand is how small differences creep in, and small differences are what make the AI guess.

Step 5: Open the top folder, and put instructions there

Claude Code reads an instruction file called CLAUDE.md from the folder you open (the next guide covers what goes in it). I learned the hard way that if you open a big parent folder and the instructions only exist further down, inside the project folders, they may not be read at the start. One setup I helped with had all the right rules written down, and the AI ignored them because nobody had opened the folder they were in.

The fix is simple. Put a short CLAUDE.md in your top folder that explains the four drawers and the one test. Each client folder can have its own CLAUDE.md with rules for that client.

Step 6: Once tools depend on a folder, stop moving it

When you start building automations, some of them will point at exact folder locations. Move one of those folders while tidying up and the automation won't always throw an error. One of mine kept running against a folder path that no longer had anything in it, and for weeks it quietly reported that there was nothing to do.

Keep a short list in your README of folders that must not move. Tidy everything else as much as you like.

What to do next

Spend an afternoon on this before you do anything clever with AI. Make the top folder, write the map, sort your files into the four drawers, and stamp your client folders from one template.

Then carry on through this track:

• Write the one instruction file your AI reads first, so it knows the rules of the cabinet.
• Give your AI a memory that lasts between chats, so the knowledge drawer actually gets filled.

If you'd rather have someone look at how your files are organised now, ask me for the free audit. I'll tell you where the AI is likely to get lost and what to move first.