Back in August 2025, I found Nate's YouTube channel. I was curious about AI automation but had no idea where to start. I joined AI Automation Society and started learning. Two weeks in, I saw Nate post about a hackathon event. Did not have a clue what that meant. The catch: it was only available in the paid community, AI Automation Society Plus. The very first week, a hackathon dropped: build a lead gen system in 2 weeks. 119 builders entered. I had no business competing. One month into my automation journey. Zero tech background. But I went all in. Every night after work. Debugging until 3am. Stuck on nodes for hours. Asking Claude, ChatGPT and pretty much any LLM I could talk to explain code like I was 5. I used multiple because I kept hitting my context window... anyway. My final build scraped Google Maps, enriched leads with Hunter + Apollo, scored them, and pushed qualified ones into cold email campaigns — all automated. 50 leads scraped, enriched, and loaded in under 60 seconds. I won first place. $1,000. This began a crazy journey! But what does any of this matter to you? I have a feeling I was once in the same place as many of you. Are you still watching tutorials... or are you actually building? What's stopping you from going all in? For me, it was fear. I didn't think I was ready. I thought I needed to learn more first. But here's what I realized — you don't learn by watching. You learn by doing. I call it massive imperfect action. The hackathon forced me to build. The paid community gave me the structure to finish and be rewarded for hard work. This is why I took the leap of faith and what AIS+ provided for me: → Structure — actual courses that walk you through building real systems → Accountability — hackathons and challenges that force you to ship → Access — Nate and other advanced builders who answer questions and give feedback → Momentum — being surrounded by people who are actually building, not just watching I'm not saying the free community isn't valuable. It is. I started here.

They have a scheduling system problem. Caregivers calling off.Clients complaining.Schedulers glued to the phone all day. That’s not a people issue.That’s a systems design issue. This short video shows why “schedule chaos” happens — and how a simple system change fixes it. https://youtu.be/5McjYJq1sGw

Hey guys! Feels good to finally be back again. I’m a design college student who’s been building my AI portfolio up on the side. I’ve been partnering with all kinds of companies to create solutions, all while documenting the whole thing. I’ve built sales automations improving deal flows for €1M+ uni startups, to recently ”graduating” to working with global agencies that focus on SMEs employee buyouts in NA/UK/EU markets. Everything I do is rooted in transparency, which is why I share most of the stuff and not gatekeep knowledge between people that may be ahead in the journey. Incase you’re interested in how I do what I do, or wanna ask me anything feel free to write me! What’s one thing that you’re currently struggling with? Maybe I can help. - Rohan

Helped someone recently who was struggling with automation fundamentals—specifically the jargon and basic programming concepts that we all take for granted. Put together 2 quick reference guides that might help others getting started: 📄 Automation Fundamentals (concepts, terminology, when to automate vs when not to) 📄 Programming Cheat Sheet (APIs, webhooks, JSON, authentication—the stuff you need to know) Attaching both here. Free. No strings. If you're just getting into automation and feeling overwhelmed by the technical stuff, these should help cut through the noise. And if you're still stuck after reading these, feel free to DM me. Happy to point you in the right direction.

Through the day, what is your best zone in time? How long you work and when you take a breaks?