This is my first major win applying what @Jake Van Clief ef teaches. Since subscribing to Claude Code on March 19th, I’ve been able to show so much progress that my company has now upgraded me to the Max 5x subscription. Looking forward to pushing the boundaries of what’s possible and continuing to improve our processes! As a Finance Manager responsible for month-end closing, I wanted to see what Claude Code could actually achieve—and it delivered! Even without Azure or backend access to our ERP system (D365 F&O), I didn't let that stop me from being "efficiently lazy." Claude Code showed me how to use the Playwright MCP to control Chrome and handle the heavy lifting for me. The script now automatically downloads the monthly trial balance, populates an Excel template, identifies discrepancies via color-coding, and even takes screenshots to document numbers from various reports. I’m already tackling my next big automation project—a task that is notoriously tedious when done manually. Stay tuned for that post, as well as more month-end automation updates in the near future! I had Claude code describe the workflow: Common Reconciliation — Monthly Close Automation with Claude Code + Playwright MCP Every month-end I run a single slash command (/mec-common) and pass it a month number. Claude then drives the entire reconciliation process end-to-end, touching both a live D365 ERP system and a multi-sheet Excel workbook — no manual steps. The workflow in three phases: Phase 1 — Trial Balance Claude navigates to the D365 Trial Balance page, clears any stale filters, sets the correct date range, triggers a recalculation, and downloads the export. The Excel file is placed in the right folder, and the data is pasted (values only) into the reconciliation workbook's Trial bal D365 sheet. A full workbook recalculation is then forced before anything is read. Phase 2 — Revaluation Check Claude loops through ~50 reconciliation sheets. On each sheet it finds the last row where column C says "Revaluation" (there are two — the second one holds the actual diff) and reads the value in column G. If the diff is outside ±1, the sheet tab is colored red. One sheet (150070) is always flagged red and requires manual review regardless.

Before joining this community, I thought I needed better prompts. Turns out I was asking AI to work with nothing, no context, no structure... just random chats. Everything changed when I did one simple thing. I defined; what I’m building, what “good” looks like and what to avoid. That’s it. The outputs improved not because the AI got smarter, but because it stopped guessing. Most people here are still trying to “talk better” to AI, but remember better wording doesn’t fix missing structure. Are you still refining prompts… or actually building systems around them?

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

Following up on my previous post about automating month-end, I want to pull back the curtain on the project that really started it all. It involves a massive company reconstruction, a "manual hell" task, and a midnight breakthrough that tripled my productivity. The Problem: A Reconstruction Hangover On January 1, 2026, our company underwent a major reconstruction. Customers were assigned new sales reps, but the final list of who owned which account wasn't finalized until April. In the meantime, we kept invoicing as usual. The invoices were correct, but the Sales Rep field on the historical records was now wrong. To fix it, we had to go back and update thousands of already invoiced sales orders. The Manual Workflow (or: How to lose your mind): 1. Search for the Sales Order. 2. Click Invoice. 3. Click Rebill. 4. Change the Sales Rep. 5. Click OK. 6. Hit Esc to exit. 7. Repeat... hundreds (or thousands) of times. Enter Claude Code & Playwright I had just started using Claude Code on March 19th after watching @Jake Van Clief ’s videos. Two weeks later, this assignment landed on my desk in the middle of my usual accounting duties. Since I didn’t have backend API access to D365 F&O, I turned to the Playwright MCP. If I couldn't talk to the database directly, I’d have Claude "drive" the browser just like a human would. The Automation Logic: - Open Chrome to the D365 Sales Order URL. - Open the filters tab. - Add filter information (Customer account, dates for Q1 2026, and identifying which sales orders had the wrong rep). - Execute the "Rebill" click-path automatically. The "Aha!" Moment at 00:30 AM It worked, but it was real slow. D365 isn't exactly a speed demon. My boss was happy ("as long as we don't have to do it, I don't care how slow it is"), but I knew we could do better. Earlier that day, I was running it in one browser and it was taking forever. While the kids were finally asleep that night, I had an idea: Can I run this on more than one tab?

Second Monday. Second winner. Let's keep it going. @Alex Nartey topped the 7-day leaderboard with +191 points and earned himself free lifetime Premium access. 71 total contributions to this community. Not lurking. Not watching from the sideline. Showing up in the comments on Jake's posts, Matt's posts, other members' posts. Adding to the conversation. Engaging with the work. That's what the leaderboard actually measures. Participation that helps other people learn. Alex wasn't farming points. He was in the threads doing the thing that makes this community worth being in. 🎉 @Alex Nartey congratulations. You earned it. The leaderboard resets now. New week. New race. Whoever is on top next Monday morning gets the same deal. Free lifetime Premium. Already a paying VIP member? We'll upgrade you to free lifetime VIP. See you next Monday!!