First paid-path audit tomorrow — talk me through it? Tomorrow I run my first automation audit for a medical/behavioral health billing company. Free audit, paid build after — that's the deal. Setup so far: Pre-call email sent (tools list, screenshots, one real failure example) Client is recording Looms of the broken automations, narrating the "why" while clicking Zoom cloud recording on → transcript drops into 00_capture → workflow-map after One thing that's got my attention: they've worked with AI companies before, and those companies shut down. So I'm walking into a client who's been burned. Questions for anyone who's done a first client audit: What do you wish you'd asked on call #1? How do you handle a client who's skeptical because the last AI vendor disappeared? Anything you'd add to the 60/30/10 gut-check when auditing billing work specifically? Will report back after the call.

It’s live. Starting today, everyone in Clief Notes has access to the new Clief Notes AI. The easiest way to use it? Don’t overthink it. Ask it the question you would normally ask me. “Where should I start?” “What should I focus on next?” “Where did you talk about [topic]?” It’ll use what’s already inside Clief Notes to help answer you and point you toward the right lesson or resource when there’s something worth going deeper on. The goal isn’t to give you another AI tool to play with. It’s to make everything already inside this community easier to actually use. If you want Access to it Comment "READY" and we'll send you access to it!

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]

@Ry Mac did a GREAT job simplifying things down. Recommend taking a look. Has his own group too! https://skool.com/buildmarketclose/about

How are you guys using ICM folders to do development? ICM architecture works great with repeated tasks but programming a project requires a long list of different features (backend, frontend, art assets, etc). My main ICM uses now are a /feature-intake that writes implementation specs to a roadmap.md, /needs-review, and a decision-log.md (the index for a bigger historical decision-log-detailed.md). What I'd ideally want longterm is an ICM folder working as a development studio; I give a high level request in a document (e.g., I want to create a mobile app that [does xyz]", then it reviews->brainstorms, finds courses of action->specs it out->develops->reviews->final corrections. Just curious how everyone else is building projects with ICM.