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

Memberships

AI Automation Mastery

29.4k members • Free

Ai Automation Vault

15.2k members • Free

AI Automation Society

381.7k members • Free

Synthesizer: Free Skool Growth

42.3k members • Free

5 contributions to AI Automation Society
From Personal AIOS to Company AIOS
I just finished watching Nate’s AIOS course For those of you who’ve made the leap and implemented a Company AIOS 1) What did you have to redesign so it could scale across roles and teams instead of staying a personal system? 2) What are the 2–3 best practices that made it work at team scale? Looking for concrete setups / resources / examples.
What if?
If you could automate ONE thing in your business tomorrow — What would it be? (Mine changed everything when I finally set it up)
0 likes • 24h
@Drique Sd interesting, that’s one of the biggest pain points, can you share more details about your flow?
Law firms are drowning in manual follow-ups. I built a system that handles all of it before the attorney even opens their laptop.
Every morning at 8AM, this workflow runs silently in the background. Here's what it does: It pulls every active case from Google Sheets. If a client was already contacted today — it skips them. No double emails. Then it checks three things: Filing deadline in 7 days? The attorney gets a Slack alert. Filing deadline in 3 days? Critical Slack alert. Escalate now. No contact in 14+ days? An AI writes and sends a check-in email on behalf of the attorney. Client ghosting on documents for 7+ days? A separate AI-written reminder goes out — polite, firm, urgent. Every email is generated by Llama 3.3 via Groq. Warm tone. Professional. Sounds like the attorney actually wrote it. After each send, the sheet logs "Contacted" + the exact timestamp. The firm stops chasing. The system chases for them. Tools: n8n · Groq (LLaMA 3.3) · Gmail · Slack · Google Sheets
Law firms are drowning in manual follow-ups. I built a system that handles all of it before the attorney even opens their laptop.
1 like • 1d
Is it possible for this AI workflow to function without using n8n?
I built an automated blog writer for my restaurant management app!
I am building an AI native restaurant management OS and one of the AI automation use cases I thought to try was to automate the creation of weekly blog posts to build up my SEO - and man what a feeling this was! Here's how it works, every Monday, it kicks off a 6-stage agent sequence: 1. Researcher Agent — generates keyword candidates, pulls live Google SERP data (serper.dev), picks the best opportunity, and drafts an outline 2. Writer Agent — writes a 1,400-word post in our brand voice, with hard guardrails against competitor mentions and clichéd phrasing 3. SEO Optimizer Agent — generates meta title, description, schema markup, and internal link suggestions automatically 4. Illustrator Agent — plans and generates custom images using GPT Image, uploads them to storage. This is the area that I think needs most work because the images generated are very much AI looking. 5. Compiler Agent — splices the images into the article and renders the final HTML 6. Publisher Agent — goes live At 3 points in the pipeline (brief, draft, final), I get an email with an approve/reject link (served by Resend). One click either advances the post or kills the run. The whole thing runs on pg_cron in Postgres. One SQL line schedules the entire weekly content operation. One post per week, basically on autopilot. Now could this be done simpler? Probably, but I wanted to try out the agent hand-offs and human in the loop. Also this was built on Supabase Edge Functions not Claude routines. If you're curious to look at the output here is a link https://www.withbagel.com/blog
1 like • 2d
@Mahmoud Tello Sure, AEO (Answer Engine Optimization) is the SEO for AI platforms. Instead of optimizing to rank on Google, you optimize to become the answer AI tools recommend consistently. You’re basically optimizing to be the chosen, most reliable answer.
1 like • 2d
@Mahmoud Tello After suggesting the AEO, I went down the rabbit hole on your site and I got super interested in what you’re building. Especially the AI agent side and turning it into the “OS” / brain of the restaurant. That got my brain spinning because I’m looking at building something similar but for a different niche. Would you be open to sharing a bit about your stack/process/backend architecture? Mainly how you’re structuring the agent layer, tools/actions, memory/context, orchestration, etc. (No worries if not, I know that’s a big ask.) If you happen to have a demo, architecture notes, recommendations on what frameworks/tools you’d use again (or avoid), or even some filtered AIS videos, I’d love to see it. Feels like you’re really onto something here. Appreciate it!
🚀New Video: The Playbook for a $100M AI Agency
I sat down with Devin Kearns, co-founder & CEO of Custom AI Studio, to break down what it actually takes to build an AI agency with real enterprise value, not just another lifestyle business. We get into why most AI work being sold today won't survive 2027, why the mid-market is the prime opportunity (not SMBs or enterprises), the 11 ways AI experts are actually making money right now, how to position with frameworks instead of being just another vendor, and the five things Devin wishes he knew sooner. If you're building, running, or thinking about starting an AI agency, this is the strategic conversation I wish I'd had two years ago.
1 like • 2d
@Ila Bressington Constant adaptation is key. I wonder whether AI agents will eventually handle much of that adaptation automatically.
1 like • 2d
@Mathias Dc Any tips on keeping up with the pace? Feels like Nate is moving faster than AI.
1-5 of 5
Ana Paula Hur
3
41points to level up
@ana-paula-hur-3974
Longevity | AI

Online now
Joined May 17, 2025
Powered by