User
Write something
🔒 Q&A w/ Nate is happening in 4 days
Pinned
🚀New Video: Opus 4.8 Just Dropped. Here's How To Actually Use It.
Opus 4.8 just dropped and the benchmarks are honestly nuts, but the numbers only tell part of the story. In this video I break down my key takeaways after reading through Anthropic's own documentation, and how I'm thinking about slotting Opus 4.8 into my actual workflows. If you want to actually get the most out of this model instead of just running it the same way you ran 4.7, start here. TOKEN DASHBOARD REPO
Pinned
If you've ever felt "AI Overwhelm", please read this.
Every single person following AI right now is overwhelmed. Including me. I make videos about this stuff for a living and I still feel the pressure. New model drops. New framework. New feature update. It feels like every single day. But after hearing a ton of you guys bring up "AI overwhelm" week after week, I realized this: → There's a HUGE difference between knowing the "what" and knowing the "how." Staying aware does not mean testing everything. Most new tools and features only need the "what." You see the title. You understand what it does. You move on. The "how" is reserved for the stuff that solves a problem you actually have right now. So when something new drops, I ask myself one question: Does this solve a specific pain point I'm currently dealing with? If yes, I test it in a real scenario. I test it against something that actually matters to me. If no, I save the link. I mentally file it away. And I keep walking. Because here's the thing. Your north star is probably very different from mine. Part of my job is to experiment, form opinions, and share what I think is useful. So naturally I test a lot of stuff. But if your north star is building a business or getting better at your craft, then every shiny new tool might just be a distraction. The number one mistake I see people make is they try to learn everything. They watch every video. They test every tool. They jump to the next thing before the last thing even had a chance to work. And if I've contributed to your overwhelm with my daily uploads, I apologize. hehe. But a lot of people think that this ties directly into how you measure your day. Productivity is not how many hours you worked. It's how many meaningful outputs you created that actually moved the needle towards your north star. Someone can work 12 hours one day and feel insanely productive, but they were just watching tutorials and playing around with new tools. Meanwhile someone else sits down for 5 hours, ships the one thing that actually matters, and makes more progress.
Pinned
🏆 Weekly Wins Recap | May 16 – May 22
From first client wins and live workflows to AI voice agents, portfolio momentum, and production-level fixes - this week inside AIS+ showed what happens when builders keep stacking reps consistently. 🚀 Standout Wins of the Week inside AIS+ 👉 @Michael Garcia closed his first major deal with a wholesale real estate automation engine handling property sourcing, Claude-based deal scoring, and investor pipeline management. 👉 @Luca Giovinazzo delivered his first full client project live — including 11 n8n workflows, CRM systems, Telegram bots, inventory tracking, booking systems, and KPI dashboards for an auto detailing business. 👉 @Paulo Calpatura built a fully automated AI voice receptionist using Vapi, n8n, Claude, Google Maps, Google Calendar, Google Sheets, and ElevenLabs. 👉 Bo Gonzales presented two AI builds internally, stood out in front of 79 employees, and ended up in a 30-minute AI strategy conversation with his CEO. 👉 @Shatadru Majumdar joined just 7 days ago and already completed multiple AIS+ modules while shipping a customer-support workflow using n8n + Claude. 🎥 Super Win Spotlight | @Griffin Maklansky Griffin joined AIS+ after getting laid off and within a month and a half, landed a new AI-focused role. What started it all? Watching Nate’s “Master 95% of Claude Code in 36 Minutes” video and realizing how quickly AI could turn ideas into real products. Since joining, Griffin has: - Built his own personal website to stand out while job hunting - Started learning AI automation seriously despite having no traditional dev background - Used Nate’s templates and systems to level up his Claude workflows - Connected with builders inside the community and started taking real conversations around opportunities - Went from laid off to employed again with a strong salary in under 45 days
🏆 Weekly Wins Recap | May 16 – May 22
Do you agree with Elon?
https://youtube.com/shorts/-WRFaunACsM?si=B8ZJahDDnMEDG8aB
0
0
Feeling overwhelmed by all the new AI tools — is n8n still the right choice?
Hey everyone, looking for some honest advice. I’ve been building AI automation systems for clients using n8n and genuinely love it — but lately I keep seeing videos about Claude Code, Hermes agents and a bunch of other tools and I’m starting to second guess myself. Am I behind the curve sticking with n8n? Or is it still the right tool for delivering client solutions? Would love to hear from people actually building and delivering for clients — not just experimenting. What are you using and why?
1
0
1-30 of 17,793
AI Automation Society
skool.com/ai-automation-society
Learn to get paid for AI solutions, regardless of your background.
Leaderboard (30-day)
Powered by