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

Memberships

AI Mate Lite

1.6k members • Free

AI Money Lab

68.1k members • Free

AI At Work

89 members • Free

OpenClawBuilders/AI Automation

480 members • Free

Openclaw Labs

1.4k members • Free

AI Cyber Value Creators

8.6k members • Free

Openclaw Founders

796 members • Free

AI - OpenClaw - Code

337 members • Free

OpenClaw Users

764 members • Free

4 contributions to OpenClawBuilders/AI Automation
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 • 3d
@Augustas Kligys All good Boss, I honestly post the same stuff in like 6 of the groups that I am at. Super positive feedback Overall. I did manage to get it setup in a more structure way based on all the feedback I receive. I went ahead and connect my Claude code and my open claw machines, so I am super based now with the memory. Thanks!
The OpenClaw Builders Command Pack - 59 Commands, Zero Fluff
I Just dropped the updated Command Pack for the community. 59 copy-paste commands for OpenClaw; organized by department, reviewed for quality, and built specifically for how we actually use these agents (solo operators, freelancers, and builders). What's in it: - Section 1: Outreach & Pitching > Lead qualifying, cold outreach, objection handling, follow-ups - Section 2: Marketing > Content repurposing, SEO briefs, email sequences, landing pages - Section 3: Solo Operator Tools > Morning briefs, meeting notes, invoicing, expense tracking, tool audits - Section 4: Danger Mode > Advanced agent configs, SOUL.md editing, cron jobs, sub-agent delegation - Section 5: OpenClaw Builder Commands > Installation fixes, token cost tracking, memory debugging, VPS backups, security scanning, local LLM setup, and more Section 5 was built directly from questions and pain points posted in this community. If you've asked about installation failures, token burn, memory issues, browser service problems, or ClawHub security; there's a command for it now. Here's a sample of what included: - (Custom Skill Builder, Channel Setup Wizard, MEMORY.md Guide, Prompt Injection Defense Checker, ommunity Post Drafter - Every command scored and reviewed against Google's EEAT quality framework. - How to use it: 1. Download the PDF (attached below) 2. Find the command you need 3. Copy it into your OpenClaw chat (Telegram, Discord, TUI) 4. Replace the [brackets] with your info 5. Hit send That's it. What I need from you: If you use a command and it doesn't work the way you'd expect, tell me. If there's a question you keep running into that should be a command; drop it in the comments. This pack is a living doc and Section 5 will keep growing based on what you all actually need.
2 likes • 10d
Claude making this documents is a game changer! My proposals have the same theme. Xd Great content! thanks
API vs Claude Max?
I've burned an embarassing amount of money on LLM tokens on this thing over the past 6 weeks, learning as I go. Some streamers are talking about just connecting the openclaw gateway to anthropic via standard Oauth rather than api. I thought that only worked for Claude Code and actual anthropic apps. Is it possible to run openclaw (main and sub agents) just on the flat Claude Pro/Max plan to cap token costs?
1 like • 18d
Qwen i did run it locally with my 24vram gpu. But i honestly prefer the stability of Oauth and API. So i run those two and its been good. I pay $20 claude to troubleshoot stuff manually or now using cowork its super honestly. Kimi i did pay first month of openclaw like $100 on kimi k testing and learning.
0 likes • 16d
@Josh Ogg I do run qwen local 9b with my 24gbvram gpu. But i use that for frequent stuff. heartbeat and similar stuff. Glad its working!
Co-Work Invites
I received 3 invites for a week of cowork. Looking to give them away in the group. Looking for ideas on how to have them out. Best OpenClaw Skill build out , submit your skill and show us how it works Best Mission Control Setup Best OpenClaw Troubling shooting tip. Best use case writeup that we can build together on a series of Lives Or , randomly select from the posts, available for the first people who send in one of the following Just share your information here 👇
1 like • 23d
Nice Idea, I like it. Do we just share our stuff in here? 🤣
1 like • 19d
@Keith Motte Sorry for the delay — it’s been a hell of a week on my end. I wanted to throw my name in because I think what I’ve been building with OpenClaw is a really strong real-world use case. I’m using it less like a simple assistant and more like an operational system for my agency. Right now I’ve built out structure around: • a proposal system with separate proposal, scope of work, and service terms • a lead relay workflow for routing incoming leads into the right WhatsApp groups • a Mission Control style setup for organizing projects, clients, workflows, and priorities • documentation and operating structure so it’s actually usable and repeatable So if you’re giving one away based on practical OpenClaw usage, I’d love to be considered. Appreciate you offering these to the group.
1-4 of 4
Carlos Jimenez
2
15points to level up
@carlos-jimenez-4904
Founder at @R21Digital with Cyber Security Major. Father of 2 Girls. Ask anything!

Active 7h ago
Joined Mar 4, 2026
Mesa, USA
Powered by