When offering AI consulting/advice/workshops to clients, what do you proposals and quotes look like, and what details are you providing? Pitching to a client today, I will probably end up giving a 1 day workshop then provide ongoing support/builds. I'm happy with the pitch deck but not sure what to put in the proposal once it lands. I can just do a basic quote in Xero but I feel like it should have more to it (yes I am also chatting about it with Fable).

We talk about folders all day, but the folders are FOR something. I want to know what... 🎖️Bonus points: comment with the single most painful manual process in your industry. The best comp entries come from exactly those answers.

I'm assuming I'm not the only who's done this and please tell me if it's a bad idea, but I'm assuming we've all turned ICM structure into a Claude skill? If I've got a new project I run /init-max that I've built, and Claude generates folders and MD files based off questions it asks me. It's not allowed to assume answers unless I blatantly say I'm not sure. To build it I've just pointed Claude at module 3 in the foundations classroom and said "make this a skill". Has anyone done the same or is this a terrible idea?

I’m running into a massive bottleneck with corporate clients right now. Because they’re handling market-sensitive data, their IT compliance teams have them completely locked down into Microsoft. No external APIs, no Claude—nothing. Ideal world would be building solutions in CC. I’m convinced the only real solution here is building custom tools and agents natively inside their system (Azure OpenAI, Power Platform, Copilot Studio, etc.) rather than trying to pitch external pipelines they'll just reject anyway. Has anyone actually built robust, advanced agent workflows strictly inside an MS-only corporate environment? Curious to know how you handled the architectural constraints, and if it's worth the headache of building inside their sandbox. Let me know what you've found works.

Microsoft is integrating OpenClaw, an open-source personal AI assistant framework, into its ecosystem through Project Lobster and the new enterprise-grade agent Microsoft Scout. Originally developed by Peter Steinberger, OpenClaw allows for autonomous, always-on agents that operate across messaging channels and Microsoft 365 apps, automating tasks like email triage, calendar management, and file operations. To address significant security concerns raised by Microsoft Defender—which warned that standard OpenClaw runs untrusted code with persistent credentials—Microsoft is hardening the technology via Scout. This version wraps OpenClaw in enterprise security controls, utilizing isolated Entra IDs for governance and sandboxed execution to prevent unauthorized actions like prompt injection attacks. While the core open-source tool remains local-first, Microsoft’s internal "Ocean 11" team is actively building reference patterns to make OpenClaw-based agents safe for large-scale corporate deployment. I incorporated ICM into my OpenClaw, and it helped tremendously. There might be opportunity here...