I automated my LinkedIn pipeline so the posts are basically a byproduct of work we were already doing. Here is how it works: - Everything gets captured raw → Meeting transcripts, voice notes, messy half-thoughts: they all get dropped into one inbox folder. Zero formatting, zero cleanup. Capture first, structure later. - An AI agent parses the inbox → It reads every drop and sorts what it finds into people (CRM update) , tasks, decisions, ideas, and content angles. Every single meeting gets asked " is there a LinkedIn idea in here?" ( I have flows for what is considered "content" , aligned with the brand) - I approve every item → The agent proposes, I decide. - Approved ideas land as drafts from a template, each one linked back to the meeting it came from. - The words come from a voice fingerprint → I fed my own transcripts into a profile of how I actually talk, so the drafts sound like me. - Once a month I sit down with the agent for a proper conversation → It brings what the industry published that month and what our own meetings taught us, and together we draft the company posts. - I edit, pick the visuals from a small set of templates, and schedule. The end goal: capture once, decide once, and let structure do the rest. If you want to build this yourself, start with the inbox. One folder where everything raw lands. Everything else grows from there.

1. Go check out 📚Navigating The Course to see how to get around and what's here. 2. Start with The Foundation. Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things join in on our Biweekly competitions and win some real cash. ⭐ Competitions Mega Thread 5. If you are wanting to dive into the masterminds, grab all the past templates, artifacts and resources. Upgrade and head into the The Vault for Premium and The Drawing Room (VIP) for VIP 6. Post your work. Ask questions. Help others when you can. What are you here to build?

—- To comply with the EU AI Act's Article 50(2) Code of Practice on Transparency of AI-Generated Content, Anthropic has announced that "New models will mark AI-generated content from day one". —— This feels like a much bigger shift than simply adding an “AI-generated” label. After a few years building systems that make AI output increasingly indistinguishable from human work. Seems we may be entering a phase where the systems themselves are expected to carry proof of where that work came from. For those of us here building with AI: will this change how you design your systems today? Where do you think the line should be — what should be marked as AI-generated, and what shouldn’t?

Been heads down on something the past month plus. Not a lesson, nor a Tea round but more like the layer under all of it. Kept seeing the same thing in comments and onboarding calls: People not knowing where to even start or if something’s already been covered somewhere in here. We're working on fixing that. Not ready to put it in your hands yet.

I’m curious how much autonomy everyone gives AI in their workflows. Do you mostly use AI as a tool where you approve each meaningful step, or do you let it make decisions and continue working without checking in with you? I’ve been thinking about where that line should be. For those of you building with AI regularly, how much freedom do you actually give it? What can it do without asking you first, and where do you still require a human decision?