How are you structuring your AI + automation agency brain across 30+ clients?

Running an agency with 30+ clients, each with their own automations, knowledge bases, and workflows (mostly Make.com + Claude). Curious how others are solving the organizational layer — not just the automation itself.

My current stack: ClickUp for team management, Google Docs for documentation, OpenClaw (Codex GPT primary / MiniMax backup) running locally, and Claude Code via Cowork which honestly has been moving fast. Background is cybersecurity (that's my major) with solid SQL and working knowledge across several languages — so I'm comfortable going deep technically, just want to make sure I'm not building a mess at scale.

I'm weighing a move toward a local monorepo structure — one folder per client holding prompts, scenario docs, context files, API notes — something I can actually version control and build from systematically.

A few things I'd love to hear from the community:

How do you structure your client knowledge bases? One repo per client? Flat files? Notion? Something else?
Are you using Claude Projects, Claude Code, OpenClaw, or something entirely different to maintain context across clients?
For Make.com builders — where do you store your scenario documentation, module notes, and client-specific logic so it's actually findable later?
Version control — are you Git-versioning your prompts and automation docs, or is that overkill for most agency ops?

Not looking for the perfect system — just what's actually working in production for people running real client loads. Drop your setup below 👇

1 comment