Built a guided way to turn work you know by heart into something you and your AI can actually use. generates a HUGE packet for you. Workflow Audit Package - The Vault · Clief Notes This is inspired by something I do in my Corporate workshops and also wanting to build something sustainable to help out the Premium and VIP members. Start with a copy-and-paste interview prompt: your AI asks one question at a time about what comes in, what you do, where things get messy, what goes out, and the decisions you want to keep. It works for business owners, consultants, subject matter experts, creators, or anyone with a recurring task they want to understand and improve. You can answer in rough words or by voice; no technical background is needed. Once you have checked the interview, give it to the included builder skill with the blank HTML template. Your AI audits the answers and creates a detailed, editable workflow package with a map of your work, evidence for where improvement could matter, open questions, practical prompts, and a recommended folder structure based on ICM: ordinary folders and readable files that give the AI the right context at each step. Open the package in your browser, correct anything it got wrong, download your copy, and use the first-test plan on a completed example you can check. Everything you need to start is in the kit; the start guide explains both copy-and-paste and file-upload options. Workflow Audit Package - The Vault · Clief Notes

In 2021 and 2022 I was selling conversational ai (about $12,500 90 day pilots) to business with high value clients (think lawyers, HVAC, RE, mortgage brokers, etc) The thing that you have to take into account is the customer's awareness ladder (Eugene Schwartz) and you have to figure out a way to get them to most aware. I saw the other day @Leonard Dauksza mentioned being out in Seattle, networking with large tech type companies and they didn't even know what ICM was... They're unaware. His messaging needs to start by moving them up the framework. If large tech companies are, what do you think SMB's are? I explain the difference in what @Jake Van Clief is doing, who he is selling too, and reframe it so you can sell it to small businesses. it's 2 different ponds that we're playing in. Unless you're an MSP already with clientelle, or an agency that has client's trust you earned, you need to come over to this pond...it's nice a warm here. In anything you're doing, just understanding the customer's journey will help you in your own marketing systems. I teach you how to get the business owner asking you about ICM the same way I do and did in 2021 2022 when "conversational ai for sales" was only being ran by 1 company. You learn to gain trust and make some extra scratch on the way (woosender.com still a company today). Let me know any questions or comments below...

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ ($4,750 Seat) Pick your cohort. Technical, Business, or Creator. Your call. 📋 THE CHALLENGE This is a weird one, and you may feel lost at first. But it's up to you to make a map for those who come after and if there is no map, you must get lost to make one. Build a folder-based cartographer that can walk a body of work and leave a map a later reader can wander and show what that map is. The later reader is often an AI. Sometimes it is a new person. Same map. Same job. Not why it failed. Not how to fix it. Not a tour of how the week goes. What the nouns are. How they move. What else moves if you touch one. What is live, what is leftover, and what is a ghost with a name and no wiring. This week's deliverable is one cartographer folder someone can drop into a Claude project, point at a real body of work, and get back a map a cold reader can enter without reading the whole thing. 🎯 PICK YOUR TERRITORY Pick a body of work you have actually been inside. Something a new person or a cold model would get lost in. Something someone will change, not something you will only describe. A few sparks: 💻 A repo you own. Even a small one. The map is for the next developer, or the next session, that has never seen it. 📂 A client delivery folder a VA or a contractor has to inherit next month. 🧩 A Make, GHL, or n8n pack someone else will edit without you on the call. 📒 An Obsidian or Notion vault a collaborator has to add to without breaking the spine. 🧾 The live records behind how a job gets quoted, approved, and invoiced in your shop. The files. The objects. Not the story of a bad month. 🎓 A course or L&D library someone will update after you. 🏭 The asset and work-order objects in a plant system you actually touch. The more specific, the better. Maps how our business works is too broad. Maps the five objects a new hire has to understand before they touch the invoicing folder is right. 🧠 WHAT YOU ARE ACTUALLY LEARNING ICM has six forms. You have been living in the first ones. Pipeline. Coach. Editor. Diagnostician.

Finished Playbooks 1.1. I decided to use the "Script → Spec → Build → Render" workflow to try and explain the workflow itself. The biggest thing for me was realizing the code really doesn’t come first. Once I had the script and visual spec figured out, the build became way easier to direct and refine. The hardest part for me was trying to make too much happen at once visually, especially in the refine section. Once I started separating each idea and letting the visuals happen in sequence, it got a lot cleaner. I ended up taking the Remotion render into CapCut and finishing it with the voiceover, music, sound design, pacing, and subtitles. This was my first real run through the whole workflow, and I definitely understand it differently now that I’ve actually built something with it. Which part of this workflow has been, or looks like it’ll be, the hardest for you?

The full animation workflow: Script → Spec → Build → Render. Where'd you land after watching?