Activity
Mon
Wed
Fri
Sun
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
What is this?
Less
More

Owned by Joe

HVAC Techs Unite

1 member • Free

A Place for people in the HVAC industry to network and chat about things you find in the field and discuss them and learn from each other.

Memberships

AI Automation Society

322.6k members • Free

OpenClaw Users

745 members • Free

Samin's Resource Hub

6.1k members • Free

Pro AI Automation

2.4k members • $2

The AI MBA

1.6k members • Free

AI Automation Agency Hub

308.2k members • Free

Unison Producer Growth Hub

44.9k members • Free

Mastering.com Members Club

34k members • Free

Producer Pathway

7.6k members • Free

1 contribution to OpenClaw Users
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: 1. How do you structure your client knowledge bases? One repo per client? Flat files? Notion? Something else? 2. Are you using Claude Projects, Claude Code, OpenClaw, or something entirely different to maintain context across clients? 3. For Make.com builders — where do you store your scenario documentation, module notes, and client-specific logic so it's actually findable later? 4. 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 like • 1d
you let your agents do it for you. I mean, why would you be doing it? You let your agents create a schedule. You should have a scheduling agent. You should have an organization agent. You have all this stuff. I've got mine like this: - Coordination Agent - Intake Agent - Analysis Agent - Builder Agent - Review Agent - Delivery Agent - Workflow Mapping Agent - Automation Architect Agent - AI Agent/Generator - Chief Automation Agent (that's also an integration builder agent) - Scheduling Agent Use Claude Code in Visual Studio to build a CRM that inputs all my customer input and puts it in there: all the handwritten notes, typed notes, voice messages, whatever. I put it all in their customer file, and then I hit analyze and it'll tell me what tools they need for their business and for their industry. I then review it. I like that little bit of human oversight, just a review, and I review it with my review agent, and then it goes over into the building stage. I then have my other agents build these tools and automation workflows for them. My company is built a little bit different. I've got my company built in two parts. My company is Axiom Forge Architects. I have a consulting arm of my business, which is Axiom Pilot, and then I have a builder arm of my business, which is Agent Forge. Together they make Axiom Forge Architects, but I have a couple of these agents work on the consulting portion side and some that work on the builder side, and then I have some that are kind of in between. They mix and mingle pretty well. prompt them correctly, and they know their role and they know what they're supposed to be doing and how they're supposed to operate together as a team. It all flows, but you have to set it up right. If you're not setting it up right in the backend with all their identity files or role files and all that stuff, then it's never going to work. You've got to set that stuff up properly first; that's like baseline. I literally rebuilt my whole... I had it all set up, and I realized it wasn't going to work like that. I just wiped it all and just redid it, and I started building their identity files and everything exactly like I needed them to be built. I realized that after I'd already done it the first time that it wasn't right
1-1 of 1
Joe Kline
1
3points to level up
@joe-kline-5102
Bred into music with a deep understanding and connection with the language like no other. i hear radio waves when its quiet. just sayin....

Online now
Joined Mar 30, 2026
Powered by