When deploying an ICM folder structure to an actual client, asking them to drop it into their claude seems reasonable for us techy people, but some of my clients are not technical enough to even do that. What other options are people using? I'm a traditional web app guy, so deploying a cloudflare worker with some backend code and a database etc is what I would traditionally try and do. That model is not as clear cut as a winner as it used to be! Is it time to look at agentic systems to be able to deploy ICM so my clients can actually use it in their day to day? Or do we simply train them up to use claude? Or is there something else that people are doing?

This will tell you a lot about the future and the way I think, give it a read if you have time. https://jakevanclief.substack.com/p/the-machine-is-smart

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. ---- 🇬🇧 We're back. Good morning from London. 👋 Thanks for the patience last week. Jake and I needed a few days to breathe before London Tech Week kicked off, and you all responded with nothing but support. We don't take that for granted. Now let's get back to building. ---- 📋 THE CHALLENGE Build a folder-based AI operator that handles ONE operational workflow end-to-end. You pick the workflow. This week's deliverable is one operator folder that someone could drop into a Claude project and use to handle a real business workflow without babysitting. ---- 🎯 PICK YOUR WORKFLOW The workflow is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 🎫 Customer support triage (which tier handles this ticket?) - ✅ Content review and approval - 📨 Lead intake and qualification - 💸 Refund request handler - 🤝 Partnership pitch evaluator - 🎙️ Podcast guest pitch sorter - 💼 Freelance project intake - 📄 Resume screen for one specific role - 📅 Meeting request triage (book, decline, delegate) The more specific, the better. "Customer support" is too broad. "Refund request triage for an ecommerce store doing under 200 orders per month" is right. 📎 If you want a fully written client brief as a reference, the attached PDF walks through one example. Don't build the example. Use it as a template for how to think about scoping your own operator. ---- 🗂️ THE METHODOLOGY If this is your first comp, welcome. Here's what you need to know: This week (and every week) you're learning interpretable context methodology. Folders as architecture. Each file does one job well. Your operator is a folder with five things: - 📄 identity.md (who the operator is and what workflow they own) - 📐 rules.md (the decision logic: criteria, edge cases, escalation rules) - 💬 examples.md (decisions in action, including at least one edge case) - 📚 reference/ (checklists, templates, rubrics) - 📖 README.md (how to use it)

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. ---- 🇺🇸 Quick note first. This post is going up Today because we took Memorial Day off yesterday. To keep things fair, you've got until Sunday May 31st at 12:00 PM EST to submit. Same week of build time, just shifted. ---- 📋 THE CHALLENGE Build a folder-based AI researcher for a specific topic or industry. You pick the domain. This week's deliverable is one researcher folder that someone could drop into a Claude project and use as their personal research partner for whatever domain you've built it for. ---- 🎯 PICK YOUR DOMAIN The domain is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 🏦 M&A activity in one industry (fintech, healthcare, defense) - ⚖️ Court cases in one area of law (employment, IP, immigration) - 🧬 Scientific research on one health condition or treatment - 🏘️ Real estate market dynamics in one city or asset class - 🥊 Competitive intelligence for one product category - 📜 Historical research on one period, place, or movement - 📚 Academic literature in one specific subfield - 📋 Regulatory developments in one sector - 📰 Journalism research on one beat (climate tech, AI policy, biotech funding) The more specific, the better. "Research assistant" is too broad. "M&A research analyst for early-stage fintech deals in the US and Europe" is right. ---- 🗂️ THE METHODOLOGY If this is your first comp, welcome. Here's what you need to know: This week (and every week) you're learning interpretable context methodology. Folders as architecture. Each file does one job well. Your researcher is a folder with five things: - 📄 identity.md (who the researcher is, what domain they cover) - 📐 rules.md (how they research) - 💬 examples.md (what good looks like) - 📚 reference/ (frameworks, source lists, key concepts) - 📖 README.md (how to use it)

💰 $325 CASH PRIZE 💰 That's a full year of Premium. Win this and your membership pays for itself. 📋 THE CHALLENGE You just got hired again. Different client this time. Meet Sarah, a freelance copywriter who's drowning in context-switching. 📎 Download the full client brief attached to this post. Short version: She works with three types of clients (SaaS founders, ecommerce brands, local service businesses) and starts from scratch every project. She doesn't need another tool. She needs a system. Your job is to build her a folder-based AI specialist she can drop into any Claude project. The folder IS the deliverable. 🗂️ THIS WEEK YOU LEARN ICM Up until now, comps have been "build a thing." This week you utilize the methodology taught throughout the community. 🧠 Folders as architecture. That's it. That's the whole concept this week. Your specialist is a folder with five things: - 📄 identity.md (who they are) - 📐 rules.md (how they respond) - 💬 examples.md (what good looks like) - 📚 reference/ (source material) - 📖 README.md (how to use it) Drop the folder into a Claude project. Claude becomes the specialist. Reusable. Shareable. Portable. 🎯 PICK YOUR SPECIALIST Don't pick copywriting. That's Sarah's example. Pick something YOU would actually use. A few sparks to get you thinking: - A salary negotiation coach - A meal planner that knows your dietary restrictions - A code reviewer for your stack - A real estate market analyst for your city - A technical recruiter screener - A grant writer for nonprofits in your space The more specific, the better. "Marketing expert" is not a specialist. "B2B email expert for enterprise SaaS targeting CFOs" is. 💼 WHY THIS ONE LANDS ON YOUR RESUME Real talk. Winning a comp in a Skool community doesn't get you a job by itself. But shipping a working folder-based AI specialist with a clean README and a public repo? That's a portfolio piece.