When I started the AI Automation Society, I had no idea it would grow into this. Under two years later and we just crossed 400k. The largest AI automation community in the world. Yes, the space is exploding. But this community grew because you guys keep showing up, asking questions, dropping answers, sharing builds, and helping the person one step behind you. Huge thank you to the team that keeps this thing running, and to every single one of you who's posted, commented, or just been here. I feel lucky to get to do this. So excited to share with you guys what we've been quietly cooking up over here at AIS...👀 - Nate

Day 4 is done, and I built something I'm actually proud of! But honestly, this challenge nearly broke me before I truly got started. This was because I spent the last four days trying to get everything set up on an external drive and kept hitting walls. None of the required dependencies would fire no matter what I tried. Turns out the whole thing needed to live on my local drive. Once that clicked, everything opened up. From there, I worked with Claude Code to build out what I'm calling the "First Responder", an AI-powered lead response system built specifically for real estate agents. Aside from Trigger Dev, VS Code and Claude Code, the tech stack that I used to complete this project was: - Twilio (SMS text) - Gmail / Nodemailer (email) - Google Sheets (lead logging) Here's what it does: The moment a lead comes in, within 60 seconds, it sends a personalized AI-written email and text (Twilio) to the lead, notifies the agent, logs everything to a Google Sheet, and kicks off a follow-up sequence. I use the Twilio 7-day free trial, so I couldn't confirm the text messages being sent to my phone; however I will upgrade after the trial ends and confirm that the texts are coming through. I built this in roughly two hours. Compare that to the previous days I lost just on setting up the project up. But here's what really got me. I wasn't just clicking through steps and saying I completed the challenge. I was watching commits get written, pushed to GitHub, GitHub Actions trigger a Trigger.dev deploy, runs succeed and fail in real time. I actually understand how this works now and it's a great feeling!😁 The dental leads finder and the Nate B. Jones video monitor that Nate demonstrated were great exercises, but they made me want to go further and build something that could actually be a working and profitable product. "First Responder" is it. Honest assessment: After verified testing and getting consistent results, I believe that this will be an MVP I could walk into a real estate office with and feel confident in landing an actual client.

Today I decided to create a tool taht would help me with getting things done having ADHD. The skill helps me divided the big task into little tasks, and put them in my calendar. But I went a bit further, I wanted like a coach interaction with message, so I created a bot on telegram that sends me a message when i have to do a task and also sends me a checkbox every day to check if I've done my tasks. Everytime I tell Claude to help me with a task and run the ADHD skill he helps me with it. Not optimal yet but really enjoyable build this kind of stuff, goal is to build a proper personnal assistant later on!

Today I completed the third challenge of learning and working with skills. I had a blast with this one, and the concepts were definitely reinforced. I referred to the list in the module to build the following: Name - linkedin-post Description - Generates 10 LinkedIn posts on any given topic, written in the user's established voice and style. Each post is scored across five criteria, and a ranked summary table follows all posts. Trigger - "Write me a LinkedIn post on/about [Topic] / [Context] The one change I made was updating the formatting and the instructions to conform with the LinkedIn best practices for posting written content. Even though it was the first on the list in the module and it seemed pretty simple, the ideas just kept flowing on how I could expand things further. I am going to build upon this further by adding a LinkedIn image generator skill to generate a single image and a carousel images for the posts produced so that the post can get more engagement with visual content.

Today I completed the second workflow under the challenge. As with day one, it wasn't that difficult. The biggest obstacle I had to overcome was working out the kinks of setting up the Firecrawl MCP server and deconflicting where and what files the server was pointed to. I'm running Claude Code through VS Code which was causing a conflict between the folder I created for projects on my computer and the folder that was created by Claude Desktop. I ultimately worked things out and was able to get through the tutorial. I really like the use cases and now that I got things up and running I can do away with Scrapebox.