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

Memberships

AI Automation Agency Hub

328.6k members • Free

AI Automation Vault

21k members • Free

Chase AI Community

71.9k members • Free

AI Automation Society

423.5k members • Free

8 contributions to AI Automation Society
💎
May 20 • 
Announcements📢
💻New AIS Course: Build Your AI OS
Just dropped a new course in the classroom and I'm pretty pumped about this one. It's the full step-by-step on building your own AI OS. Same exact setup I use every day to run the YouTube channel, the community, and my team. 8 lessons, all my templates and prompts, plus a free GitHub repo so you can skip the boring setup and just start building. To unlock it in the classroom, you just need to hit level 3 in the community. Honestly pretty easy: - Drop an intro post if you haven't yet - Engage with a few other members in the threads - Help somebody out who's stuck on something That's pretty much it. Get to level 3 and the whole thing opens up. See you in there. - Nate
💻New AIS Course: Build Your AI OS
1 like • May 24
This looks great the youtube video is exactly how I have been pitching to clients so good to have that affirmed
1 like • May 25
@Yousef Alsayed it's working really well. In all honesty most of the clients I have so far are people I've had relationships with in the past so I run them more as exploration sessions. I found that's been more responsive than trying to actually sell them something.
How do you safely deploy client AI systems without taking login credentials?
I’ve been helping a few friends with small businesses design lightweight AI/automation “operating systems” for their workflows, but I’m trying to get clearer on the right way to handle deployment and access. For example, if a system needs to connect to Gmail, Google Drive, files, calendars, CRMs, MCP servers, or other business tools, what is the best-practice way to set this up without asking for or handling their actual login credentials? Is the usual approach to use OAuth, service accounts, scoped permissions, shared workspaces, client-owned API keys, or some kind of formal access/consent agreement? And from a legal/compliance perspective, are people typically using a basic service agreement, data processing agreement, or access authorisation form for this kind of work? I’m still learning the deployment and permissions side of building these systems, so I’d really appreciate any practical advice on how others are doing this properly and safely for small-business clients.
whatsapp coexistence - help needed with building a customer support agent
I am building a customer support agent on whatsapp for a client who wants to keep the number on whatsapp business app and also have the same number handle customer follow-ups via the API, I have been on a rabbit hole trying to figure out how to set up coexistence and whether I need to use a BSP, any tips, advice, help from anyone who has experience with this would be HUGELY appreciated
1 like • May 24
I was lazy and got my client to switch to telegram
I DID IT!
I took my first step toward creating my first company OS through CoWork. Gosh am I loving it!! Now I am starting to explore and learn Claude Design. What are your best tips and ideas for Claude Design? What worked and what saved you time?
I DID IT!
1 like • May 24
having a brand book and getting cluade to interview you to create the prompt
Hard Truth!
Most people will spend years learning AI. A small group will spend that same time building with it. One group has a skill. The other has an income. Which group are you in?
0 likes • May 24
defintely building
1-8 of 8
David Howard
3
43points to level up
@david-howard-7826
I'm David I work in education and I am interested in all things AI.

Active 8d ago
Joined Apr 25, 2026
Powered by