💰 $325 CASH PRIZE 💰 That's a full year of Premium. Win this and your membership pays for itself. 📋 THE CHALLENGE You just got hired again. Different client this time. Meet Sarah, a freelance copywriter who's drowning in context-switching. 📎 Download the full client brief attached to this post. Short version: She works with three types of clients (SaaS founders, ecommerce brands, local service businesses) and starts from scratch every project. She doesn't need another tool. She needs a system. Your job is to build her a folder-based AI specialist she can drop into any Claude project. The folder IS the deliverable. 🗂️ THIS WEEK YOU LEARN ICM Up until now, comps have been "build a thing." This week you utilize the methodology taught throughout the community. 🧠 Folders as architecture. That's it. That's the whole concept this week. Your specialist is a folder with five things: - 📄 identity.md (who they are) - 📐 rules.md (how they respond) - 💬 examples.md (what good looks like) - 📚 reference/ (source material) - 📖 README.md (how to use it) Drop the folder into a Claude project. Claude becomes the specialist. Reusable. Shareable. Portable. 🎯 PICK YOUR SPECIALIST Don't pick copywriting. That's Sarah's example. Pick something YOU would actually use. A few sparks to get you thinking: - A salary negotiation coach - A meal planner that knows your dietary restrictions - A code reviewer for your stack - A real estate market analyst for your city - A technical recruiter screener - A grant writer for nonprofits in your space The more specific, the better. "Marketing expert" is not a specialist. "B2B email expert for enterprise SaaS targeting CFOs" is. 💼 WHY THIS ONE LANDS ON YOUR RESUME Real talk. Winning a comp in a Skool community doesn't get you a job by itself. But shipping a working folder-based AI specialist with a clean README and a public repo? That's a portfolio piece.

I am doing things I never thought I was capable of doing thanks to Jake ( and everyone else here). I'm a 60 year old grandma designing an app that has the potential to help a lot of people in times of grief. I'm vibe-coding - two words I didn't even understand a few months ago. I saw a pain point, identified what was needed and then started designing it. Me. Nana.

If you haven't seen this yet: https://www.youtube.com/watch?v=GMIWm5y90xA

Today was a massive win. I had my meeting with the Head of AI for our global group, and it went beyond anything I had imagined. The Pitch: 132 Orders and a "Broken" System I had the chance to present a real-world challenge: Manually processing 132 sales orders in April. The workflow is a nightmare: Open each order, find the amount, cross-check it with an Excel sheet, invoice it, and repeat. To make it worse, there is a known bug in our D365 environment where the amount column simply shows "0" in the grid, meaning I can’t just export a list. It requires manual clicks. In a busy finance department, this takes days because of constant interruptions. I presented my workflow and explained how this concept isn't just for one task—it’s a framework for almost every repetitive monthly task we have. I knew from my previous Rebill Project that if I can automate the "friction," I can win back my time. The Result: Skipping the Queue When I told the Head of AI that this could turn a 3-4 day job into about 1 hour, his eyes lit up. Even though Claude Code is still stuck in corporate governance (it's currently with our CEO to decide on a global rollout), he didn't want me to wait. He immediately assigned me a Microsoft Copilot Studio license. These are highly restricted—usually, there’s a long waiting list, and if you don't use it for 30 days, you lose it. He bypassed the entire queue to get me started right away. Moving the Needle with IT To get "Copilot Cowork" talking to D365, I had to submit a technical IT ticket to enable the Model Context Protocol (MCP). I made sure to CC both the Head of AI and my own manager. The Head of AI jumped straight into the ticket with this comment: "I talked to Allan today. He has an idea to speed up a process in finance and save days of work... The use of the MCP server for this would help him very much. Open for a call if needed or any other help for the team."

1. Watch the intro video and introduce yourself in the intro post here 2. Start with The Foundation (free course). Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things, move to Implementation Playbooks (Level 2). When you're ready to build your own tools, Building Your Stack (Level 3). 5. Post your work. Ask questions. Help others when you can. What are you here to build?