The system around the files.
Folder structure, session rules, write discipline, monthly rhythm. Your context is what fills it. The system is what keeps it working.
Every chat
starts from zero.
You've used Claude. You've used ChatGPT. Every chat, you re-explain who you are, how your team works, what matters this week. The AI is capable. It just doesn't know you yet.
Writing the files isn't enough. They calcify in weeks. Same AI, same subscription. The system around the files is what keeps them working.
Same AI · Same subscription · System keeps it workingHow this started.
I sit with founders and teams and build what's hard to build alone. Strategy, prototypes, AI systems. Recent work with 10team, VAISTO, and Moovmoor.
For a few years I did that work and walked away. The thinking lived in my head and a handful of decks. Then I started writing it down. Folders. Markdown files. Context structured so any AI could pick up where the founder left off.
Now I run that system with other founders.
"It felt like the model went from intern to co-founder."
↗ First install · 2025The four phases.
Each engagement runs through the same sequence. Extract pulls context out. Install lands it where you work. Tune fixes drift. Compound is the part that pays for itself.
Projects vs. Cowork. Claude or ChatGPT Projects are bounded by task. Cowork compounds across time.
What's in the box.
The system is the product. Folder structure, session rules, write discipline, monthly rhythm. Six brain files hold your content. Project instructions boot the whole thing. The system is what makes it compound.
What the retainer
actually does.
Each month is one working session, plus the work that follows. We extract what's changed since last time. New decisions, new team structure, new priorities. We update the context files. We tune what's drifting.
The retainer is also where the system grows. Setup installs your personal layer. Your company and team layers get built when the work demands them, not on a schedule.
The effect becomes visible after a few months. Each session starts with more context than the last. The system does not reset.
This isn't a check-in. It's how your work keeps building.
Specifications.
Solo founder or early-stage team
Growing team or active product cycle
Larger org or multi-team deployment
Thirty minutes.
No deck.
If it fits, we go.