Agencies live and die by capacity. Claude Code changes the math: one senior engineer can shepherd 3–5 active SaaS builds at once without dropping quality. Here is how to structure the studio.
Updated: April 24, 2026
Keep a private repo with your standard CLAUDE.md, hooks, slash commands and MCP servers. Every new client project starts by symlinking this folder into `.claude/`. Updates propagate to all active projects on the next `git pull`.
One engineer, multiple projects. Use tmux or a session manager so each client has a long-running Claude Code session. Context per client is preserved; no re-learning cost between switches.
Most agencies keep their fixed-price retainers but charge API credits as pass-through. The math works: we bill 3× the API cost as engineer time and still come out ahead on margin versus pre-Claude-Code delivery.
Each client gets their own API workspace with isolated keys. Nothing crosses projects. For the most sensitive clients we run on Bedrock inside their AWS account.