1. Go check out 📚Navigating The Course to see how to get around and what's here. 2. Start with The Foundation. 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 join in on our Biweekly competitions and win some real cash. ⭐ Competitions Mega Thread 5. If you are wanting to dive into the masterminds, grab all the past templates, artifacts and resources. Upgrade and head into the The Vault for Premium and The Drawing Room (VIP) for VIP 6. Post your work. Ask questions. Help others when you can. What are you here to build?

I have a client in Australia who's looking for someone who understands ICM and can help him work on his software. Obviously he would prefer someone a bit more technical, but he's happy to have some people who are trying to learn as well. It's a pretty large software, but he's created a pretty good automated system and obviously he's using my methods so it's very well organized. Anyone out here looking for a project to take on the practice or learn more? Or is there anyone in the morning to get a little bit more work done at a higher level? He's looking for multiple skill levels.

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ ($4,750 Seat) Pick your cohort. Technical, Business, or Creator. Your call. 📋 THE CHALLENGE This is a weird one, and you may feel lost at first. But it's up to you to make a map for those who come after and if there is no map, you must get lost to make one. Build a folder-based cartographer that can walk a body of work and leave a map a later reader can wander and show what that map is. The later reader is often an AI. Sometimes it is a new person. Same map. Same job. Not why it failed. Not how to fix it. Not a tour of how the week goes. What the nouns are. How they move. What else moves if you touch one. What is live, what is leftover, and what is a ghost with a name and no wiring. This week's deliverable is one cartographer folder someone can drop into a Claude project, point at a real body of work, and get back a map a cold reader can enter without reading the whole thing. 🎯 PICK YOUR TERRITORY Pick a body of work you have actually been inside. Something a new person or a cold model would get lost in. Something someone will change, not something you will only describe. A few sparks: 💻 A repo you own. Even a small one. The map is for the next developer, or the next session, that has never seen it. 📂 A client delivery folder a VA or a contractor has to inherit next month. 🧩 A Make, GHL, or n8n pack someone else will edit without you on the call. 📒 An Obsidian or Notion vault a collaborator has to add to without breaking the spine. 🧾 The live records behind how a job gets quoted, approved, and invoiced in your shop. The files. The objects. Not the story of a bad month. 🎓 A course or L&D library someone will update after you. 🏭 The asset and work-order objects in a plant system you actually touch. The more specific, the better. Maps how our business works is too broad. Maps the five objects a new hire has to understand before they touch the invoicing folder is right. 🧠 WHAT YOU ARE ACTUALLY LEARNING ICM has six forms. You have been living in the first ones. Pipeline. Coach. Editor. Diagnostician.