Content OS

Content OS is the workspace that turns one idea into four published posts. You write the brief once. Claude drafts a LinkedIn post, a Twitter thread, a newsletter section, and a YouTube hook off the same source. Every draft lives on its own page, linked to the parent idea, so nothing gets lost between Slack, Google Docs, and the scheduler.

It replaces the usual stack of Notion for notes, Google Docs for drafts, a shared Trello for status, and a separate tool for scheduling. One page holds the brief, the drafts, the review, the approval, and the scheduled time. Monday morning, you open the editorial calendar and see every post in flight for the week.

Content teams break for one reason. The brief, the draft, and the published post live in three different tools, and the handovers between them are Slack messages. By week three, nobody knows what was approved and what is still waiting on a reviewer.

Content OS collapses the three tools into one Notion page per idea. A rollup pulls every draft into a weekly view. The schedule column decides what goes out this week. The approval column decides who is still waiting. The founder reads one view on Monday and sees the whole week.

Four databases. The Ideas database holds every angle worth writing about, tagged by topic and channel. The Briefs database holds the approved brief, the target audience, and the key takeaway. The Drafts database holds the per-channel versions, each linked back to the parent brief. The Calendar database holds the schedule, the owner, and the published URL once it ships.

Every database links to the next through a relation property. A view on the calendar shows the brief, the draft, and the approval status in a single row.

Monday, you open the editorial calendar and see the posts scheduled for the week. Tuesday, you brief three new ideas, Claude drafts the variants, you review them in Notion. Wednesday, approved drafts go to Buffer or Publer and schedule themselves. Thursday, you check the performance view for last week. Friday, winning angles feed back into the Ideas database as new briefs.

The whole week runs on the same four pages. No new tool, no new tab, no new Slack thread.

The most common failure is skipping the brief and writing straight into the draft. The second post feels off voice, the third post is a different angle entirely, and by week four the calendar is full of drafts nobody approved. Fix: the brief field is required before a draft row can be created.

The second failure is letting the calendar become a wishlist. Every idea gets scheduled, nothing ships. Fix: the calendar only shows rows with an approved brief. Ideas without briefs stay in the Ideas database, where they belong.