I created a scope of work, quotes, and invoicing system that suggests project pricing for me! Pricing things out for quotes used to take me a long time and now I just have to review for accuracy! I work with a lot of nonprofits, so it also calibrates for this if flagged 🌬️🔥

Made it to Level 2!! I'm working on some ideas and folder structures that I'd like to share. Are we allowed to share github repo's here? Not sure of the rules, couldn't see any posting guidelines.

Every few months, a new AI orchestration framework drops. More dashboards. More abstractions. More complexity. You wire up a simple workflow… and spend hours debugging it. Here’s the truth: most AI workflows don’t need “smart” orchestration. They need structure. A simpler approach already exists: Jake's folder architecture. Inspired by Doug McIlroy and Unix pipelines: Do one thing well Use plain text Make steps work together The idea: Folder = Pipeline Each step is a folder: instructions.md → what to do output.md → result Flow: AI runs → human reviews → move to next step That’s it. No frameworks. No hidden state. Example: /01-research → /02-draft → /03-review → /04-publish Why it works: Clear input/output at every step Human becomes the control layer Easy to debug, edit, and stop Works with any AI tool Upgrade it with one small addition: Add status.md RESULT: SUCCESS | WARN | FAIL Now every step is measurable, not guesswork. Rules that make it powerful: • One folder, one task • Plain text only • Always include a stop instruction • Review before moving forward • Version your pipeline like code When to use it: When accuracy matters more than speed When human review adds value When you want clarity, not abstraction The Unix pipeline is 50+ years old and still runs the internet. Your AI workflow doesn’t need more tools. It needs better structure. Thanks to @Jake Van Clief for this workflow.

In Part 1, I was riding high. I had Chrome, Edge, and Firefox all running simultaneously, tripling my speed on a massive D365 rebilling project. I felt like I’d cracked the code to being "efficiently lazy." Link: Mini-Series Part 1: The "Manual Hell" Rebill Project · Clief Notes But the victory was short-lived. I was driving the car at 100mph, but I didn't realize how much fuel I was burning. The Crash: 3 Hours to Zero The next morning, I fired up all cylinders. It was beautiful—until it wasn't. In under 3 hours, I burned through my entire token allotment. I was dead in the water with a 1.5-hour wait until my limits reset. With the clock ticking and sales reps still needing updates, I had to go back to doing it manually. And that’s when the "Aha!" moment happened. The "Tab" Breakthrough While I was clicking and typing manually to pass the time, I realized something: I wasn't really using the mouse. I was mostly hitting Tab and Shift-Tab to navigate the D365 fields. I asked Claude: "Can Playwright just 'Tab' through the browser instead of searching for elements and taking screenshots for every move?" Claude’s answer: YES. My jaw dropped. From "Visual Driving" to "Macro Speed" The old workflow relied on Claude "seeing" the screen via screenshots to make sure it was in the right spot. It was accurate, but heavy. I had Claude rewrite the interior workflow to a deterministic loop: 1. The Setup: I open the URL, set the filters, and select the first row. 2. The Loop: * Tab to Invoice → Enter. 3. Repeat. I added small buffers (100ms between tabs, 4s for page loads) to ensure D365 could keep up. See the video for how the flow runs in real life! The Result: 90% Savings & 10x Efficiency I asked Claude to evaluate the two methods. The numbers were staggering: Old "Visual" Flow: - Tool Calls: ~500 calls per 50 orders - Token Usage: 100% (High Burn) - Logic: Screenshot-dependent (Slow)

EDUBA @Kay K has had the challenging task to redesigning my Company website to fit the folder and Unix theme. It may seem odd at first but as you scroll down through the site you will see the influence of traditional and fundamental structures, the simplicity of it is what I love. Figured I would share this here and share his hard work as I love the idea of making a website folder based, because as you know, I love my folders. EDUBA