EDIT: WE HAD OVER 100 PEOPLE SIGN UP IN TEN MINUTES....GOING TO BE ROLLING OUT ACCESS ON SLOWER BASIS NOW SO I DONT RUIN MY BANK ACCOUNT WITH TOKEN SPEND FOR YALL (im covering ai costs for everyone) but keep applying we are keeping track and will be letting more people in and reaching out about getting you all access one by one especially VIP. Our Platform is here, the thing a lot of you have been asking for and I have been teasing Take your ICM folders and second brains, put them in the cloud, and work on them together in real time. You upload your folders and files. One strong model with a good harness reads the map and becomes the agent you need. No new agents to build, no zip files to pass around. Each workspace runs in its own container. It renders your markdown, edits your files, installs packages, runs Python and Playwright, and multiple people can work in the same space at once. No Mac Mini needed to keep your data separate either. We're opening it to VIP and alpha testers first, and I'm covering the AI cost while we test so cant do a full role out yet. Free AI use which is great for those users, not great for my bank account haha. ✍️ Sign up for access: https://docs.google.com/forms/d/e/1FAIpQLSdSnToxclxt8EgoB2GizrEvHP7gzOedVcRXdCkpi1SZwR8ZfA/viewform 🔗 Questions, or want to work heavier with this? Email [email protected]

If anyone's curious if the methods I'm teaching here will last long enough. Just know that y combinator is now asking for solutions we built years ago. https://www.ycombinator.com/rfs

I explain the details about it on today's high tea . I built a Claude skill that turns a process, an idea, or a messy folder into an ICM workspace. The folder structure does the orchestration. Numbered folders carry the order, the hierarchy scopes context, and plain markdown files hold state. One agent walks the right files at the right time and does the work a multi-agent setup would. Repo: github.com/RinDig/icm-architect 📦 What it does Two modes. 🔨 Build. You describe your work and it pulls out the structure already sitting in how you talk about it. The stages, the points where you stop and check, what stays the same every run versus what is new. Then it picks one of five proven forms and scaffolds the smallest workspace that carries the job. ♻️ Restructure. Point it at a folder, repo, or vault you already have. It reads every file, sorts each one by role, shows you a migration map, waits for your yes, then moves and checks the result. 🧩 The five forms Pipeline, umbrella, record library, knowledge bundle, context map. They mix and nest, so most real workspaces use more than one. ✅ The walk test Every result gets checked cold. An agent with no memory has to open the root, find its way, act, and report status from the files alone. If it can't, the structure gets fixed until it can. ⚙️ How to use it You can honestly just tell claude to download it from the link, but if you're using codex or something else it will just have to restructure the claude.md to agents.md Or if you want to do more Hands-On install Claude Code: drop the folder in ~/.claude/skills/icm-architect/, then say "ICM this" or "build me a workspace for X." Claude apps: zip the folder and upload it under Settings, then Capabilities. Fork it, break it, tell me what you built. 👇

Hey everyone 👋 Quick question — how much are you paying monthly for your CRM right now? 297?297?497? More? I got tired of paying a SaaS tax just to manage contacts, pipelines, and appointments for my agency clients. So I started building my own. It's called OpenLevel — and I just open-sourced it. I wanted to build this as a true foundation that you can tailor to your exact needs. Why? Because your CRM should adapt to you, not the other way around. It's the same way Jake teaches ICM to his needs: depending on what you are doing or building, your ICM can have adjustments, additions, or subtractions... as long as it serves you. OpenLevel gives you that flexible starting point so you can build exactly what your operations require, without being locked into someone else's opinionated structure. 🔧 What it does: — Contacts & CRM with custom fields — Pipeline & deal tracking — Calendar & appointment booking — Multi-tenant (manage multiple client locations) — Built-in AI assistant that actually understands your data 🏗 How it's built: — React frontend + Hono backend — One API powering both web app AND mobile app — Deterministic automations first (n8n, webhooks), AI where it counts — Follows the 60/30/10 methodology ⚠️ Fair warning: This is a V1 work-in-progress. The web app works but might have some rough edges. Mobile app is still cooking. But the foundation is rock solid. The whole point is: you own your stack. No more white-label fees. No more praying Zapier doesn't break at 2am. Fork it, customize it, make it yours. 🔗 GitHub: https://github.com/jahfeelautomation/openlevel Would love your feedback — what features would YOU want to see next?

Intros for The Connection Hub - The Vault 👤 Who I am: (name + where you're based) 🛠️ What I actually do: (the specific work — not "I'm in real estate" but "I run a 3-agent team doing residential resale in Austin") 🤖 What I'm building with AI right now: (your current project, workflow, or the thing you're stuck on) 🎯 What I'm looking for connection-wise: (pick one or two) 💡 Someone who's solved [X] 🤝 A collaborator / accountability partner 👀 Just here to learn from people in my field 🧰 Trading workflows & systems 📬 Best way to reach me: (DM here / comment / link)