I publish 8-12 pieces of content per week across LinkedIn, the TS blog, the IO platform, and Intelligent Operations's channels. Without a system, that would be a full-time job. With the right system, it takes about 6 hours per week.
The Notion Architecture
Everything starts in Notion. I run four core databases: Ideas (the raw capture), Pipeline (the production queue), Published (the archive), and Repurpose (the recycling system). Each database has specific properties that Claude can read and write to via the MCP server.
The Ideas database is the most important. Every thought, observation, or conversation that could become content goes here. I capture 15-20 ideas per week. About 4-5 of those make it to the Pipeline.
The Claude Layer
Once an idea moves to Pipeline, Claude takes over the heavy lifting. I have three prompts that run in sequence: Expand (turns a bullet-point idea into a structured outline), Draft (generates a first draft from the outline), and Refine (applies my brand voice and tightens the prose).
The key insight is that Claude doesn't write the content — I do. Claude generates the raw material, and I shape it. Every published piece has been through at least two rounds of human editing. The AI accelerates the process; it doesn't replace the judgment.
The Repurpose Engine
This is where the real leverage lives. Every long-form article gets fed back into Claude with a repurposing prompt that generates: a LinkedIn post, a tweet thread, an email newsletter intro, and a carousel script. One article becomes five pieces of content, each calibrated for its platform. The time savings compound exponentially.