Notes on software a company can own.
What we learn mapping processes, writing contracts before code, and running software that stays governed after the first release.
-
MEMORY.md vs CLAUDE.md vs AGENTS.md: which file does what
MEMORY.md vs CLAUDE.md is a question of who writes the file. What each one loads, when Claude Code reads AGENTS.md, and how to use all 3 without duplicates.
-
AI agent memory architecture: what to keep, and where
AI agent memory architecture in practice: the 4 kinds of memory my Claude Code agents use, where I keep each one, and what breaks when they mix.
-
Multi-agent orchestration with Claude Code: my setup
Multi-agent orchestration without a framework: how I split marketing work across Claude Code agents that share one memory in Markdown files, and what broke.
-
Custom software vs SaaS: when renting stops fitting the company
Custom software fits one company's process; SaaS fits the average. 4 questions that show which side your company is on, and what a third option costs.
-
Who is accountable for AI-generated code in your company
A tool built with AI works until the person who prompted it leaves. Four things nobody wrote down, why a PDF policy is not evidence, and what to check this week.
Bring the process, not the pitch.
A 30-minute fit call on the one process your team keeps working around. If standard software is the better answer, we say so.