Lots of people asked how I used Fable to edit its own launch video so I made a video about that!
TLDR it wrote a lot of code & tool calls to use transcription services, ffmpeg, do colorgrading, use the figma mcp, make remotion UI and render it.
I didn't touch a video editor.
Built my content pipeline the same way. Once workflows live in .md files, the bottleneck shifts from "how to build the system" to "what to automate next.
One person rebuilt an entire company’s brain in 7 days inside Claude Code.
Not a doc. Not Obsidian. A living galaxy of nodes.
Every employee. Every AI agent. Every SOP. Every tool. All wired together on one screen.
Click a department. The human agent team opens up. The SOPs attached to it open up. What each person is allowed to touch opens up.
That last part is the whole game.
Permissions baked into the brain. An employee opens the chat, the AI already knows what they can access. Agents, data, SOPs surface inside the conversation like you tagged them by hand.
Obsidian can’t do this. Notion can’t do this.
No dev team. No funding round. No 6-month roadmap. 7 days, 1 person, 1 terminal.
This is the part nobody has priced in.
The tools to build $200K enterprise software now sit on your laptop for free.
The only thing missing is the guy who opens the terminal.
Dynamic Workflows are the new skills.
i am replacing the most complex skills that i created in the last few months for doing chief-of-staff work - like dashboard management, asana management, ppt creation - with workflows.
A legit gamechanger.
@nityeshaga The non-technical use case is where it clicks for most people. Once you stop thinking of it as a coding tool and start treating it as a thinking partner that remembers context, the workflow changes completely.
@johnrushx The easy 99% used to be a moat — people charged for it because it was tedious. Now that moat is gone overnight. What's left is taste, timing, and knowing which problem is actually worth solving.