Workflow automation for two-person US content teams
If your content team is a founder and one part-time editor, here’s the automation stack that actually compounds — and the one that wastes a quarter.
Two-person content teams are the most over-tooled and under-shipped operations on the internet. A founder, a part-time editor, and somehow eleven SaaS subscriptions. The fix isn’t more tools — it’s automating the right four steps and ignoring everything else.
The four steps worth automating
- Idea capture to backlog. A single Slack channel or one shortcut that drops every idea into Notion or Linear with a timestamp and the source. No more "I had a great idea on a walk and lost it."
- Draft to review handoff. When the founder finishes a draft, the editor gets pinged with a link, a deadline, and the context. Manual handoffs are where two-person teams lose three days a week.
- Approved to scheduled.Once the editor signs off, the post goes into the publishing queue automatically — Buffer, Hypefury, or whatever your scheduler is — with the right metadata.
- Published to repurposed. Long form goes out, the system spins up shorts, threads, and email versions in draft form. The humans approve. Nothing publishes itself.
What the stack actually looks like
Notion or Linear as the backlog. Google Docs for drafting (yes, still). Slack for handoffs. Buffer or Hypefury for scheduling. Zapier or Make stitching it together. Optionally, Claude or ChatGPT for the repurposing step. That’s the whole stack. If you’re running more than this, you’re running a content ops department with two people, which is the same as not running one.
What to never automate
- The first draft. AI first drafts cost more in editing than they save in writing. We tested this for six months across different niches. Same answer every time.
- The publish button. A bad post live is more expensive than a good post delayed. Keep a human on the trigger.
- Engagement.Auto-replies and auto-comments are obvious to your audience and the algorithm. Don’t.
The Slack channel that runs the show
Build one channel called #content-ops. Every automation posts to it — new ideas, drafts ready for review, posts scheduled, posts live, weekly stats. The founder and the editor both live in this channel. No DMs, no email threads about content. One channel, one source of truth. This single change tends to ship more posts per month than any other intervention.
The weekly fifteen-minute review
Every Friday, fifteen minutes, both humans on a call. Look at the backlog, look at last week’s ship rate, and pick this week’s three priorities. Anything not in the top three doesn’t happen. If you’re a content team in NYC or SF, you’ve probably had this meeting balloon to an hour with five people. Cut it back.
The numbers that matter
Posts shipped per week. Time from idea to publish. Reply rate on published posts. Skip everything else — followers, impressions, all of it. A two-person team can’t move vanity numbers anyway, and tracking them slows down the work.
How we help at The Nerdish Mic
We set up content ops for two-person founder-led teams. The exact stack above, customised to your tools, shipped in a week. If your backlog is full and your published feed is empty, that’s a workflow problem, not a creativity problem. We can fix it.