Content Operations
State of Flow
Learn how teams build channels that grow sustainably — with systems, not stress.
Pick a job. Do it well.
We build Clipflow for teams making content at scale. When a paying customer asks for something outside that, I need more reason than being able to code it.
Build a business you want to keep building
We hit 444 projects in a week and my first instinct was to want that per day. I'm trying to notice the progress and build a business I can keep at.
Catch it before they do
Remembering a frustrated customer from our previous business, I'm building a client overview in Clipflow that shows their comments and projects together.
Stop repeating. Start looking properly
A list of delivered videos hides how many rounds each one took. I want revision and comment counts in view so the conversation starts from real feedback.
Deliver what you sold them
When you're trying to win work, it's tempting to make the offer sound better than it is. If I can't confidently deliver something, I shouldn't promise it.
Two businesses. One head.
Side projects rarely stay small. When a new idea turns up in a frustrating week, I suggest putting it on a list and looking again once the week has passed.
Read it before you run it
Moving fast with AI means more output to review. I want someone reading every suggested URL, command or change for what it will do, even on small requests.
Plan with AI. Check its work.
I go back and forth on the plan, let the AI write the boilerplate, then review each file. The architecture and how the app behaves stay my responsibility.
Only customers correct what counts
We built analytics because we wanted to know what content to make more of. How other teams would use it was something only paying customers could show us.
Authors