What is a memory file, and why every operator should keep one

A memory file is a plain text file that tells Claude the things it would otherwise ask you every single time — what you’re building, who your users are, how you write, what you’re trying to ship this quarter. You write it once. Claude reads it every time you work in that project. That’s the whole idea.

Most operators never write one, and it’s the reason their AI output feels generic. They open a fresh chat, describe their situation in two rushed sentences, get a two-sentence-quality answer back, and conclude that AI isn’t that useful for their specific business. The model isn’t the problem — it’s working from a thin slice of the truth.

Here’s the fix. Make a folder for your work. Start with three files, in plain markdown — the shared company brief:

• PRODUCT.md — what you’re building (or what you sell), who it’s for, what stage you’re at, what makes it different
• USERS.md — your actual users, what they complain about, the request you keep hearing
• GOALS.md — your top priorities this quarter and what “on track” looks like

Now every time you work inside that folder, Claude already knows all of it. You stop re-explaining your business and start getting answers that fit it.

Where it goes from there. Those three files are the brief a whole team agrees on before anyone starts. In the Founding Four, each AI cofounder then gets a memory file of its own on top of the brief — GROWTH.md, OPS.md, BRAND.md, one role’s mandate each. Same mechanism, different owner: the shared files describe the company, a role file describes one job inside it.

That’s also where VOICE.md lives — the file that makes drafts come back sounding like you instead of a press release. It’s the Brand role’s core file, and in the roadmap you write it in Week 2, when you hire that cofounder. Paste in two or three things you’ve written that you’re proud of. Then, every time Claude produces a line that doesn’t sound like you, add it to a short “not me” list at the bottom. The file gets sharper as you go.

You don’t need to perfect any of these. A first-draft, 70%-right set of files beats blank ones by a mile, and you’ll improve them every time you notice Claude getting something wrong. The tuning happens in the files — not in a longer prompt you retype every morning.

Writing the shared brief — PRODUCT.md, USERS.md, GOALS.md — is Week 1 of the 90-day roadmap. The role files follow, one a week. Everything after assumes the brief exists.