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

Memberships

Founders Accelerator (Free)™

19.5k members • Free

AI Automation Society

380.9k members • Free

6 contributions to AI Automation Society
🚀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.
2 likes • 22m
This is such a valuable breakdown - the focus on mid-market over SMBs/enterprise really resonates as the sweet spot for AI agencies right now. Devin's framing around frameworks vs. being just another vendor is gold. Definitely watching the full episode tonight!
The real problem with AI slop.
So I'm sure you guys have heard the term "AI slop", and everyone sorta defines it differently. Maybe you think it's those TikToks of AI-generated fruits going on dates. Maybe it's infographics with misspelled words. Maybe it's something else entirely. But I want to talk about it in the context of communication. Internal, external, content you put out into the world. I write my LinkedIn posts with AI. My agent knows my business, how I write, how I speak. That's just how I work now. And there's nothing wrong with that. I think everyone should be using AI to write if it makes them more efficient. But this isn't a binary yes or no. It's a spectrum. Sometimes AI can draft and send automatically. Most of the time, I want it to just draft. Then I review. If someone sends me an email with em dashes everywhere, I don't actually care at all that they used AI. The fact that I can clearly tell it's AI-generated isn't the problem. What I do start asking is: → Did they proofread this? → Is this completely accurate? And subconsciously, I might start losing trust. Not just in the email but in the person who sent it. Our job here has changed from writer to reviewer. This quote has really stuck with me: "You can outsource your thinking, but you can never outsource your understanding." When your name is attached to the content, you take credit if it lands, as you should. But that also means you need to take accountability if it's incorrect. Taste and reviewing are becoming more important than ever. AI is super intelligent and powerful, but I don't want to see a world where we trust AI so much, that we stop reviewing things, and then the human on the other end of the content starts losing trust in us. That's why even though I write with AI, and people know that, I still try my best to disguise it and make it sound as "Nate" as possible. Check out the LinkedIn post I just wrote about this HERE
1 like • 1h
This really hit. I think the biggest difference between AI slop and real AI leverage is whether the output is connected to an actual business process. A random AI-generated graphic is easy. But an AI system that improves sales follow-up, reporting, onboarding, customer support, documentation, or delivery — that’s where the value compounds. I’m starting to see that the future is less about “make content faster” and more about “build operating systems that reduce friction.”
Building my AIOS around Claude Code + Codex
I’ve been thinking a lot about where AI automation is heading. For me, the goal is not just to “use AI tools.” The real goal is to build an operating system around my work and businesses. My current direction: Claude Code = main builder; Codex = coding support / second opinion; MCP = connecting tools and workflows; Skills = reusable business processes; Subagents = specialist operators for finance, marketing, admin, sales, and reporting. I’m currently building this around a few real businesses and projects: Mora Capital — funding readiness, deal packaging, credit memos; Hafro — content, WhatsApp sales, customer support, operations; AptTick — learner-to-income workflows; 24 Comms — creator campaign OS; Personal OS — tasks, learning, execution, accountability. My biggest realisation so far: AI automation is not about replacing effort. It's about removing repetitive friction so you can focus on judgment, strategy, and execution. Curious to learn from others here: For those building AIOS-style systems, are you starting with personal workflows first or client/business workflows first?
Starting Out Paralysis - Mental Costs of wanting "Perfect"
Question Target: Beginners & Experts -- I'm very curious to hear about it from both perspectives -- Hey there fellow dreamers! I'm struggling with the following mindset: - Fear of Overwhelm from merging projects and learnings when starting slow - Want the perfect start, setting up an AIOS from the beginning - Codex + Claude Code should work together (installed & subscribed) - Keeping up with the latest AI development as a beginner is HARD - Establish Best Practices from the get-go - Not wanting to FIX project structure on my machine all the time - Wasting Tokens + Context (daily/weekly) So have you been dealing with this too? If so, how did you manage to deal with it? I'd love to hear about your experiences, get some guidance, maybe even actual help setting everything up. Take care everyone, Enjoy building ✨
0 likes • 3d
This is real. I think the mental cost comes from trying to build the full system before proving one useful workflow. What’s helping me is reducing it to one question: “What is the smallest AIOS workflow that would make this business easier to run this week?” That could be a lead tracker, a follow-up workflow, a document checklist, or a knowledge base. Start with one painful bottleneck. Then compound from there.
🚀New Video: The AI Offer You Can Sell Tomorrow Morning
Most people trying to start an AI business jump straight to pitching retainers or projects and end up frozen. The move is to sell one-on-one hours helping business owners set up their AI Operating System. This video walks through that offer, why it works in 2026, and a 7-step plan to land your first clients.
5 likes • 3d
This is a strong reminder that the offer needs to be simple before the system becomes complex. I’m thinking about AIOS from a business diagnosis angle: 1. Map how the business currently operates 2. Identify where leads, documents, sales and delivery break down 3. Rank the bottlenecks by commercial impact 4. Build only the workflows that improve revenue, delivery or decision-making The temptation is to sell “AI automation”, but I think clients actually buy cleaner operations, faster follow-up, better visibility and less founder dependency.
1-6 of 6
@tiego-morallane-8700
tiegz

Active 2m ago
Joined Mar 17, 2026
Powered by