Where do you work out of? Do you build in Cowork and access through dispatch on the phone? I am constantly building out a personal work project, and I get ideas that need to be added or run into bugs that need to be fixed. Working during drive times would be nice. Claude, with the phone, only has dispatch to work through. If you are in Chat, it works for both desktop and mobile, but not great for the build. What do you guys do? Thank you in advance. This is truly amazing, and I look forward to implementing the ICM method. Currently, I only use Claude, which moved from ChatGPT. What I am building is an Operations CRM in the construction field that deals with a client from beginning to end. Intake, CRM, Emails, Maps, Operations, Materials, Ordering, Managing crews, paperwork, it's too much. I was relying on Claude to remember everything. Works great, but now I see that it can't find what I need. I need to work from the desktop and mobile.

Today was spent in flow. Moving through one chat but multiple folders and sub projects within the project. If anyone is lost let me know I was lost for the first few days and know I am grasping more everyday. But today was my first day with ICM and the workflow is amazing. I remember waiting for 30 seconds to sometimes minutes. Image writing three prompts in one chat instructions for a feature update, logic for a different feature and a revision and it working on all three things with a hang time of 46 seconds. Something Cowork (even in projects would struggle with). Thanks Jake and team and those who help with this morning.

Operations is the top funnel (Operations of my business) Broken down into three areas of work. There will be more, but I don't want it too fragmented. Claims-CRM is my workspace Daily Operating system and where my daily routines live Scopes and revisions are a construction workflow operations/ ├── CLAUDE.md ← the map / router ├── claims-crm/ ← APP workspace (your live repo) │ └── CONTEXT.md ├── daily/ ← daily operating system (evening pass) │ └── CONTEXT.md └── scopes/ ← scopes & revisions ├── CONTEXT.md └── resources/ ← drop your blank scope forms here

This is the system I'm proudest of, and it's deliberately worth nothing to anyone but me. I've been building it for about two and a half months. My goal? Free up time personally, and test and learn everything I was learning here so that I could be confident in building out things that are proper products at work (or, more accurately, architecting things for my team to build). So this system flies in the face of some of what we learn - it's not meant to have a product launch, it's meant to be so damn unique and customised that it holds no value to anyone other than me. Current outcomes (and I'm going to build again so this will improve): - ~63 hours per year freed up for me - ~ 104 hours per year freed up for my husband - ~$2400 per year saved in food costs (around $50 per week approximately) and reduced food wastage - A calmer family who are not stressed out about what needs to be done when for school - we've gone from a last minute scramble or forgotten gear about once every 2-3 weeks to one item that was a day late in the last two and a half months. (With the root cause of that miss fully addressed instantly in the system). - Three weekly runs in a row where I didn't have to change anything in the heaviest and most challenging workflow (the weekly planning workflow). I just reviewed and approved it to write. Every minute of build time has already been paid back with interest before counting the time freed up for my husband, and I'm only two and a half months in. In fact, the first thing I built paid back on the first run with me being an hour better off from that first run even when you factored in the build time. Here's how it's actually doing that: - Term-start — the first thing I built, and the one I love most. It takes a 7 day timetable screenshot and a CSV file exported from the school app and turns it into an ICS file I can upload into my calendar. Rather than manually creating it, it can apply the reasoning required over the root information and give me the output. It even has a second-pass logic built in for the edge case logic where days aren't in the CSV which usually happens for 1-3 days each term. It works flawlessly. It began as a series of saved prompts and was my first ICM pipeline once I found this community.

This has happened a lot to me. On Thursday or Friday my usage goes down. I was at weekly 97% yesterday and now at 65% (Pro plan paid annually) Does it happen to anyone else?