Content Operations
State of Flow
Learn how teams build channels that grow sustainably — with systems, not stress.
Decide what an ad test needs to prove
Our hook rates looked promising after a short run, but they couldn't tell us who became a customer. Write down the response each ad version is testing.
They signed up without a call
In our previous business, winning a customer meant direct sales and working through a deal. I still value calls, but I liked seeing someone decide alone.
Keep a small publishing routine during a busy season
Pick a few buyer questions you can answer in one short recording session, give the editor the takeaway, and agree when the founder reviews the first edit.
Give organic content and paid ads different jobs
An organic post can explain how your service works while an ad asks for the booking. Write each a separate brief and judge the result against that job.
AI took my debugging in circles
Each explanation contradicted the last, across several models, and I found the problem myself in the end. Now I check each suggestion against the failure.
I found my people talking systems
I couldn't match their content numbers, but I'd built and run a substantial business. When you're with people ahead of you, contribute from what you know.
Security doesn't wait for your roadmap
Updating a package is routine, which is what bothered me. We rotated secrets, updated our tooling and I had to rethink who holds sensitive access.
Reviews aren't just for employees
If someone on the team isn't succeeding, I look at my part in that first. I also pick one area to improve per review and come back to it in ninety days.
One failed attempt isn't the verdict
Our second go at outreach had a clearer message, testimonials and a better idea of who we were contacting. On LinkedIn it booked us several meetings.
Authors