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.

As someone who’s been using cold email to get AI automation clients for a while now. The one thing I realised pretty quickly is that people don’t really care about your service. Instead what they actually care about is their problem. I used to position my AI automation offer around what it did, how it worked, the features, etc. But even though everything sounded “good”, replies were still inconsistent because the messaging didn’t feel relevant to the person reading it. Once I started positioning the offer around problems the client already cared about, everything changed. The conversations felt more natural and people instantly understood the value. So I put together a quick breakdown of how I approach offer positioning now, so you don’t end up sending offers people don’t immediately connect with. Here is the breakdown, hope it helps!

One that needs the clicks and views to survive. And one that needs to solve problems to get paid. The difference? Well, if you want clicks, the easiest way is NEWS. News will always work. Which is why if you go to YouTube right now you'll see that we're getting flooded by Claude. Not only because it's new, but also because they're dropping new features every single day. So if you want clicks, create content about Claude Designer, or why not about the latest skill? That's the views game. And what about the other side of the coin? Solving problems and getting paid. Well, if you try to enter this space thinking that Claude will be the thing, you'll get punched in the face by life. Because it's not. The fact that businesses are still using Zapier today sounds crazy. I mean, when was the last time you even came across Zapier before I mentioned it? And this is what I mean: I get paid to solve business problems. I do not sell Claude Code solutions. If I were, I would need to set up a server and manage the code. Do I want to do that when there are easier ways to solve the problem? No. The only instance I'll set up a Claude Code solution is when I can't find an API that will work in my case. Besides that, I don't bother. What people will watch is quite different from what will make them money. It is what it is, but it's more fun to watch the latest Claude feature. Because watching the same video about how to do outreach gets boring fast. So you need new. But if you want to make money, old and boring is the safe path.

Not the trigger. Not the API calls. The part in between. I can follow a tutorial, copy a workflow, even build one with Claude's help. But, if someone said "okay, now build it from scratch," I'd freeze. Because nobody teaches the logic layer. How do I know which node comes next? How do I know when to use a Merge node vs. an IF node? That's what I need to learn. Not "here's a workflow you can copy." But: - How do you think through a workflow before you build it? - How do you know what nodes to choose? Google for example has over 20 Actions. Do I choose Create or Update and create? - How do you understand and map the logic? - How do you work forward step by step, knowing what data you have, and what the next action needs? - When do you split, merge, loop, or filter?) @Nate herk Ai Can you make a video explaining this, please?

I currently have AntiGravity and NotebookLM on a Desktop but also want to work from my laptop. I use an external drive (F: on my desktop, D: on my laptop) to take all my important files between the two machines. The Question: How are you guys managing your antigravity skills folder for this dual-setup? - Do you keep the SKILL.md files on the local C: drive of both machines? - Or do you point the Global Skills path to the External Drive so the "brain" travels with the hardware? I’m trying to avoid broken paths if the drive letter changes, but I also want my skills to stay in sync. What’s the "pro" workflow for staying mobile?