User
Write something
Pinned
START HERE
Glad you made it in. Before you go anywhere else, work through the steps below. They will get you set up and ready to start. ✅ Introduce yourself in the comments. Tell us what you do and why you are here. ✅ Watch the Getting Started overview 📚Navigating The Course - Getting Started · Clief Notes ✅ Start with the Foundation course 0.1: Where All Of This Leads - The Foundation · Clief Notes ✅ Fill out your profile so people know who you are ✅ Join the next competition ⭐ Competitions Mega Thread - Getting Started · Clief Notes ⭐ On Competitions (and why I love them) We host a competition every two weeks. These are some of the most powerful places to learn and build here. Also Cash prices (often over $200) for the winners. Learning how to do something is one part of it. The real learning starts when you put it to work. That is what the competitions and the build sessions are for. On top of this they act as a portfolio a place to not just show us but show others (clients, bosses, your best friend) what you have been building and that you really CAN build. In order to win a competition you must be a paying member (It takes me hours to review submissions sometimes days. But if you win ONCE you can pay for a whole year of membership so I think that's only fair!) Watch the videos, then go make something.
START HERE
Pinned
40,000 People....I have only this to say
We just broke 40k Members, in less then 4 months... To say I am honored and blown away is an understatement. I feel like yesterday @Matthew Creamer quit his job to sleep on my floor and bust out 15 hour days to build out content, structure and anything else I thought you all would need to make this community worth it. But at the end of the day there is only one thing for me to say. THANKYOU None of this, and I mean NONE of this would be remotely worth it if it wasn't for you all. To list and tag everyone that have contributed so much valuable not just to this community but to me would be nearly impossible. Thank you to every single one of you. Thank you for commenting and helping out on posts Thank you for sharing the wins you have gotten both at home and professionally. Thank you for believing in me and what I am building septically those of you who have been around since the beginning (you know who you are). I cannot tell you how happy my heart is to get in front of you all and teach, talk, ask questions and even learn a lot myself. It is a dream come true to become someone that people can learn from; to share my thoughts and have those very thoughts change the way people live their lives and do their work. It's only the beginning too, I can't wait to see what the rest of the year has in store, and I promise to keep building, working and recording for you all. From the very very very bottom of my heart.....Thankyou! Thankyou to every single one of you reading this and for being part of such an amazing community.
40,000 People....I have only this to say
Pinned
🎆 THE LAST SALE EVER — HELP US GET TO VEGAS 🎆
🎯 WE READ ALL OF YOUR RESPONSES. HERE'S WHAT'S NEXT (AND A BIG ASK) A couple weeks ago we asked you what you wanted Clief Notes to become. You showed up. You wrote real, thoughtful answers, some of you wrote essays. We read every single one. Twice. So before anything else: thank you. This post is us answering you. 💬 YOU TOLD US. HERE'S WHAT WE'RE BUILDING. You said you want a clearer path from learning ICM to actually getting paid for it. → It's coming. A real learning-to-earning track, plus a talent platform we're building to connect you with people who want to hire what you can do. Heads up: the talent platform will be Premium and VIP only, one more reason to lock in below. You said competitions without feedback don't help you grow. → Fixed. Going forward, every single entrant gets tailored feedback on their build, not just the winner. We're moving to two competitions a month so we can do it right. And both monthly winners get a 30-minute call with me. You said the best builds get buried in the feed. → We're building a tagged library so you can actually find "ICM setups for solo operators" or "small team, non-coder" instead of scrolling for an hour. You said you couldn't map all the pieces, Skool, Discord, the Lyceum, ICM, what each tier unlocks. → A single orientation page is on the way. One place that breaks all of it down so nobody's lost. You said you want to connect with each other. → We hear you. Meetups, pairing, and a recorded "After Tea" hangout are on the table. South Florida alone has over 1,000 of you. Let's use that. You said we've felt spread thin. → The most honest one. You're right. We're bringing on real help to run the day-to-day so the community gets consistency, and so Matt and I can keep building the things above instead of dropping balls. You called it, and we're fixing it. 📍 QUICK NOTE ON ICM: a few of you asked for "ICM with Copilot" or "ICM with n8n, Sheets, GoHighLevel." Good news, ICM already works with any model and feeds straight into the tools you're using. It's the structure underneath all of them, not a separate thing you have to relearn per tool. If that's not landing for you, that's on us to make clearer, and we will.
How does everyone get Claude/AI to consistently follow ICM / Jake methodology on every build?
I've been working on this and have something that somewhat works, but I keep running into pieces that get messy and don't hold up well in practice. My current approach: the image I've attached lives in my AGENTS.md at the root of the project, so any time I build, the AI has the structure to reference. What I'm really after is the best way to implement the ICM system so that anything I build, Claude/AI already knows the way to build and stays inside that structure. Is anyone else doing this? Would love to hear how you've set it up.
How does everyone get Claude/AI to consistently follow ICM / Jake methodology on every build?
Stretching Claude Further: ICM to Orchestrate 2,350 Local Workers
We've been experimenting with treating ICM not as the whole system, but as one layer inside a larger orchestration architecture. For us, ICM solved something much bigger than prompting. It solved context. How do you keep models focused? How do you stop them from reading entire repositories? How do you bound work? How do you reduce drift? How do you move toward convergence? ICM gives us work packets, context contracts, routing, validation, and controlled handoffs. Once we started implementing it, we found ourselves asking: What happens if we build around that? Internally we've been experimenting with a governance layer we call AQ-CMF (just our internal name for it), but I think the more interesting thing to share is the orchestration itself. Right now it's basically a small "Swarm Orchestration Starter Pack." The idea is simple: Use the smallest model capable of doing the work. Reserve larger models for judgment and reasoning. Current setup: RTX 3060 12GB • 2,200 binary filtering workers • Qwen 0.6B • yes/no decisions • triage • filtering • classification RTX 5060 Ti 16GB • 150 structured extraction workers • Qwen 4B • schema completion • information extraction • template generation Cloud reasoning layer (introduced to me by @Ari Evergreen 's post https://www.skool.com/cliefnotes/i-run-100-agent-workflows-on-a-budget-model-heres-the-catch) • up to 200 Kimi 70B workers • interpretation • reasoning • code generation • higher-complexity analysis Claude Code • orchestration • synthesis • validation • architecture decisions • final judgment The smaller models don't really "think." They observe. They classify. They extract. They filter. Claude assembles. Claude validates. Claude decides. One thing we've noticed is that this also changes the economics considerably. Instead of paying frontier-model prices for every operation, we let local models perform the cheap labor.
2
0
Stretching Claude Further: ICM to Orchestrate 2,350 Local Workers
1-30 of 2,153
Clief Notes
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
Powered by