I Kept stopping. I’ve been going back and forth trying to learn Jake's ICM. I would start. Feel overwhelmed. Stop. Then come back and repeat the same cycle. I would hear words like harnesses and MCP servers, API, automations etc. It wasn't that I couldn't learn it — it was that the list kept growing faster than I could get through it, and everyone seemed further ahead every week. Honestly, it became too much So I stopped. Then I came back to the community one day and started looking through Jake's Weekly comps. briefs, repos, winners etc. He said something along the lines of: "Pick a real workflow that belongs to you. Don’t build for a fake client this time" That made everything click. 💡 I already had a real workflow. I’m a solo architectural visualisation artist. Every new job requires quotes, invoices, project folders and client emails. So I built Workstation around that. THE OLD WAY ❌ A client email would arrive. I would: 1. Open Canva on another screen. 2. Manually enter every detail into a quote. 3. Triple-check everything then Export the PDF. 4. Write the response email. Repeat the process for two separate invoices. It took hours for the entire set. Sometimes I would find a mistake and check everything again. When a client asked for an imagery proposal, I felt a bit anxious if I'm being honest, because I knew this mess was waiting for me. Yes, I was creating invoices manually in Canva. I know. Insane. But that was my system. THE NEW WAY ✅ Now I paste in the client’s email. Workstation handles the rest: Client email Extract the job details ↓ Calculate the price ↓ Create the project folder ↓ Build the quote ↓ Build both invoices ↓ Render the PDFs ↓ Prepare the client email ↓ I check and send What previously took hours now takes minutes. HOW IT WORKS The system uses simple folders and Markdown files: 📁 00_intake: Reads and organises the brief 📁 01_quote: Builds the quote 📁 02_invoices: Builds the invoices and PDFs 📁 03_email: Prepares the emails on my dashboard

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]

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. 👇

This is a devlog from David! A lot of people are saying they want the ability to scale and deploy their ICM and their workflows. We looked at all the possible problems security issues and we have been spending a lot of time building something for all of you! It's almost ready for release, but here's a little developers log to kind of check out some things that David has been doing to build it up. It's far from perfect, but for those technical folks out there you may enjoy it!

(and a small change to how we run these) Hello everyone!! 👋 First, the honest bit. This one is landing later than Monday, and on purpose. Two things got us here. One, a lot more of you are submitting now. If I am going to really sit with every entry and give it a proper look, a weekend is not enough. This round I went through all of them, watched the videos, opened the repos, the full pass. That takes time and I would rather do it right than rush it. Two, I could feel a few of you running hot. Weekly is a sprint, and burnout was starting to creep in for some. So we are moving to bi-weekly. More room to build, more room to breathe, and the time for me to actually review the work the way it deserves. 🎥 Quick word on the videos. They were a step up this round. Some of the animated walkthroughs and live demos were a genuine pleasure to watch, and yes, I weigh them. A clean demo that shows the thing actually working makes a real difference. However I don't want that to ALWAYS be a requirement. Also you will notice the Heavy hitters that you usually see up here are not currently, some posted late and I decided to let the new entries and first timers also have a chance as well! But certainly, check the original post as every submission has something for you to learn from : 💰 Competition 7 ➖➖➖ 🛠️ A FEW THAT STOOD OUT (in no order, and if you didn't make it, it doesn't mean yours wasn't great) The Pipeline Operator — @Jayden Forshee Runs a whole sales pipeline. Paste a lead and it grades it, writes the outreach, and moves the card itself. The live board where you watch cards move on their own, sat right next to a normal chatbot, was one of the clearest ways anyone has shown what an operator actually is. https://github.com/griffainai/studio-pipeline-operator Board: https://pipeline-operator.vercel.app/board