Hi all, how do you show clients where their project stands without endless "where are we at?" emails? I got tired of that loop, so I built a few small pieces to fix it: 1. An internal tracker where every deliverable is marked as either mine or the client's, so it's obvious who is holding things up. 2. A short recap after every client call, where anything promised on the call becomes a deliverable. 3. A simple portal where each client opens their own private link and sees only their own work. No accounts and no logins, the link is the key. Would something like this be useful in the way you work, or do you handle client updates differently?

Hi all, does anyone else find editing eats more time than the actual content or strategy side? Cutting silences and filler words out of raw footage was my biggest time sink, even after the script and filming were already done. Had Claude Code help me build a small local tool that automates that part instead of adding another subscription to the stack. 1. Record raw footage as normal. 2. Run it through faster-whisper locally for a transcript (free, no API key, runs on your own machine, no cloud tool in the loop). 3. Use the transcript timestamps to auto-cut dead air and filler words instead of scrubbing manually. 4. Burn in captions from the same transcript instead of typing them out separately. Curious how everyone else here handles the editing step, still doing it by hand or already on an automated pipeline?

I spent weeks writing technical posts that completely tanked on mobile. I was spending 2 hours drafting in obsidian, testing the snippets, and checking the architecture On my desktop monitor, the drafts looked clean Then I opened one of the live posts on my iphone, it was unreadable. A 4-sentence paragraph had stretched into 14 lines of unbroken text. Readers on linkedin saw zero whitespace and scrolled away in 2 seconds The code was solid, but nobody reads a solid wall of text on a 6-inch glass screen. I only fixed the retention when I stopped guessing line breaks and started using a layout grid. Today, I run a 3-tool workflow that separates the writing from the mobile formatting: - Raw capture in obsidian: I dump my terminal outputs, error logs, and architecture notes into local markdown without worrying about line breaks - Fluff removal in claude: I run the draft through claude with a strict prompt to cut passive voice, strip filler words, and keep sentences under 15 words - Layout extraction: I grab the structural skeleton from posts in blotato and that held high engagement on linkedin. It strips away the author's words and leaves the whitespace grid: a 1-line tension opener, a 2-line problem frame, 3 short mechanism bullets, and a diagnostic closer I drop my cleaned notes straight into that empty grid and schedule the post The structure makes the post scannable in 45 seconds on an iphone, while the substance stays 100% technical. My drafting time dropped from 2 hours of manual reformatting down to 15 minutes of review. When you post technical work online, do you write freestyle into a blank box, or do you draft inside a fixed layout grid?

Hey everyone, Gab here. I do freelance AI automation and web builds for clients, mostly Claude Code based. Working through Maker School on the systems side and a lot of what's shared here lines up with that. Curious what's been the most useful automation you've connected into your content workflow so far.