A question for those using ICM to provide software or consulting services: When you work with multiple customers, does one ICM system support all of them, with separate customer configurations, requirements, data, and outputs? Or do you create and maintain a separate ICM structure for each customer or software product? I’ve been thinking about this through the way I create my own products. I reuse many of the same standards, checks, scripts, and production methods, but different product types may still need different schemas and workflows. A devotional is not built exactly like a prayer card set, even though they share part of the same underlying system. I’m curious whether software providers (or consultants) approach this similarly. Do you maintain a common core and adapt it for each customer, keep every customer implementation completely separate, or use some combination of the two? I’m still learning how others structure this, so I would genuinely appreciate hearing what has worked for you—and where separation becomes important.

I've been playing around with Claude for a while, optimising workflows, supercharging a recent discovery sprint. But this week I actually shipped something. A simple idea capture tool for Mac. I used to use Things 3, and whilst the app structure never quite worked for me, I loved the quick capture feature. Keyboard shortcut, text input, thought saved. I've tried everything since: Apple Shortcuts to Reminders, Quick Notes, third-party apps. Nothing matched how I actually work. So I built my own. It's written in Swift, a language I've never touched before. I've been following development best practices as far as I remember them, pushing to a GitHub repo, branching for new features. Notes save as JSON that my ICM workspace can action, The whole thing was built with Claude. I haven't thought about anything else all weekend.
 Scope creep is real. It now has optional task types, a menu bar drop down with sync status, a live list of recent captures, inline editing, tagging. I drafted the initial design in Figma, then went back and forth between VS Code and Figma, designing where I needed to, tweaking code where I needed to. As a designer, syntax was always the wall between having an idea and building it. But working in a real codebase, you're closer to the actual product. It allows a level of finesse you can't achieve in Figma. Refining a micro interaction, adjusting an animation timing, polishing subtle UI details. I am very excited to make progress with my ICM workspace build out, lots of product ideas to be built!

You just watched the full 23-minute folder architecture walkthrough. Vote below, then drop your use case in the comments. What are you building this system around?

You just learned the book, movie, video game framework. Vote below, then tell us in the comments: name one thing in your work that you now realize is on the wrong layer.

Step-by-step interactive guide from idea to output. Design an ICM workflow alongside Maya, one decision at a time, and watch a messy process become something an AI can run again and again. Right now, Maya has to try to remember what needs to be done and where each piece of information is kept. She needs a better solution. https://claude.ai/public/artifacts/7c9618f4-8324-4048-902c-cbcf77c9c102 Let’s build one with her. 😀