User
Write something
🔒 Q&A w/ Nate is happening in 4 days
Pinned
🚀New Video: I Tested Every Claude Code Feature, These 12 Are the Best
I've spent over 500 hours inside Claude's ecosystem, so I ranked every feature from D tier all the way up to S tier based on how much each one actually changes my day-to-day knowledge work and automation. Then I walk through my top 12 in order and explain exactly why each one earned its spot. Keep in mind I'm doing a lot of automation and knowledge work, not heavy software engineering, so you'll probably disagree with some of my placements. That's the point, you value these features differently based on how you use Claude Code.
Pinned
🏆 Weekly Wins Recap | May 23 – May 29
From $64K+ in closed deals to first paid projects, first workflows, and first technical builds - this week inside AIS+ showed what happens when builders stop consuming and start moving. Some wins were big money. Some were first steps. Both matter. 🚀 Standout Wins of the Week inside AIS+ 👉 @Jacob West closed two deals in one week — a $22.5K custom software build for a local gym and a $42K AI OS rollout for a mid-market energy business. 👉 @Luca Giovinazzo delivered his first full client project live — 11 n8n workflows, CRM, Telegram bot, inventory alerts, booking system, KPI tracking, user guide, and Loom walkthrough. 👉 @Fadwa Naboulssi landed her first client three weeks into the community — a candidate sourcing workflow on a $150-per-successful-hire commission. 👉 @George Maitland completed his first technical build using Claude Code + n8n MCP — a local content engine with Telegram as the command center. 👉 @James O Neill built a free portfolio site for a friend-of-a-friend’s side hustle… and she insisted on paying anyway. First real money landed. ⸻ 🎥 Super Win Spotlight | @Josh Holladay Josh joined AIS+ because he wanted more than scattered learning. He wanted momentum. Focused content. Better access. And a room full of people actually moving. Since joining, he has: - Closed real client work - Built stronger confidence around pricing and value - Used the portfolio course to get clear on where he was and what needed to happen next - Learned how to turn client conversations into real business opportunities - Found a place to celebrate wins with people who actually understand the journey
🏆 Weekly Wins Recap | May 23 – May 29
Pinned
What do you get if you upgrade to AIS+?
Some of you have never heard of the AIS+ community. Others have but the part that trips you up is the actual difference between the two. Either way, this post will give you clarity. This free group is a bundle of quick resources pulled from my YouTube videos, plus a massive open community that anyone can join. It's a great place to get your bearings and see what's possible. But it's open to everyone, it can be noisy and overwhelming, and there's no path through it. You can get help from other members, but I rarely answer questions here. AIS+ is the opposite: - A step by step roadmap with a clear order, so you're never guessing what to do next - A much smaller community of people who are seriously committed to building and selling AI agents - I answer questions every day and run a weekly Q&A call where you can get direct access to me For the course material: The roadmap takes you from zero to building and selling AI agents, and the whole thing is built on the latest tech like Claude Code and Codex. We update it constantly. The old n8n material has been archived. It's still there if you want it, but it's no longer the focus, because the way you build today has moved on and the courses moved with it. Here's the actual roadmap inside, in order, with when each piece opens up: 1. Start Here (opens the moment you join). Gets you oriented. How the community works, the path ahead, and how to get help when you need it. 2. Build Your Portfolio (opens the moment you join). Why a portfolio matters, beginner level tutorials, and what types of projects to focus on. You end up with real work you can show a client. 3. Claude Code (opens the moment you join). This is now its own dedicated course. Build faster, turn ideas into working automations, and go deep on the tool serious builders are using right now. This takes you from beginner to advanced, step-by-step. 4. Get Your First Clients (opens after 30 days). Getting your first clients is hard, because you don’t have any case studies yet. So, we analyzed all of the success stories from our members and found they get their initial clients with two different techniques: warm outreach and Upwork. So, we teach both techniques in detail with exactly what to say, exactly how to position yourself when you have no proof.
Lovable Apps Have a Security Problem Nobody's Talking About
To preface, I run a security auditing service that seeks to address the technical debt that comes from building with AI tools in order to give founders additional peace of mind prior to shipping. That said, last week I scanned a total of 8 lovable built apps, since I noticed that with the Lovable platform specifically that its vulnerabilities always seemed to be structured in the same exact way across different apps. Furthermore, many of these products had actual user bases and live billing mechanisms in place, and thus the data that these apps were handling were particularly important. That out of the way, these are 5 of the most common findings that I came across among almost all of the Lovable built applications that i have audited thus far: 1. 8/8 apps had at least one HIGH severity finding; though, typically within a short 10-15 minute window, I was able to source multiple (even within some of the better built products, same idea). Many of these findings were able to be sourced with fairly rudimentary tooling. For instance, almost all of the apps I scanned seemed to have secrets of all kinds baked right into the front end; accessible through DevTools alone. Things ranging from JWTs, API keys, etc etc. However, it gets worse: 2. 7/8 apps had a hardcoded supabase token sitting in the front in JS bundle sitting in plain sight. This being the code that your browser actually downloads first before loading your app, what this means is that anyone can open devtools on their local machine, and search for this directly within the sources tab with next to no effort. This key, plus an unprotected database means that anybody online can utilize this to grant themselves direct read/write access to your data without even being logged in. 3. 7/8 apps had no rate limiting mechanisms configured on login. What this means is that there is absolutely nothing stopping someone from attemptions thousands of password guesses on any account that they choose. Configuring an automation tool to cycle through common password lists to target specific users is simple, and what this means is that anyone can access any account they desire by running said scripts overnight. So thus, rendering user passwords completely useless as safeguarding mechanisms. Furthermore, on these same apps there was a complete absence of other such mitigation methods (ie: CAPTCHA trigger, account lockout/slowdown mechanisms), so this confirms that anybody can log in wherever they choose to on these sites completely under the radar.
Welcome! Introduce yourself + share a career goal you have 🎉
Let's get to know each other! Comment below sharing where you are in the world, a career goal you have, and something you like to do for fun. 😊
1-30 of 18,398
AI Automation Society
skool.com/ai-automation-society
Learn to get paid for AI solutions, regardless of your background.
Leaderboard (30-day)
Powered by