Lesson checklisttap to expand
18 min read+50 pts

The Content Engine, Not the Content Piece

Posting daily isn't a strategy. Building a system that produces ten pieces from one idea is.

# The Content Engine, Not the Content Piece Here's the trap a lot of smart people fall into: they treat content like a to-do list. Write a post. Check. Record a video. Check. Send the newsletter. Check. Then the week ends, the calendar resets, and you start over from nothing. Every Monday you're back at square one, staring at a blank doc, wondering what to say. The "post daily" advice makes this worse. It turns content into a treadmill — you have to keep running just to stay in place, and the second you stop, the audience evaporates. Or so the fear goes. The real game is different. It's not about how often you post. It's about building a system that turns one good idea into ten pieces of content without burning you out or making everything look like it was generated in bulk. That's what this course is about. ## Why the piece-by-piece approach fails When you think in terms of individual pieces, you make the same mistakes every time. You start from scratch. Every post is a cold start — new angle, new research, new draft. Even if you write fast, you're spending most of your time on setup, not substance. You miss the repurposing moment. You write a good long-form piece. It performs well. You move on. Three weeks later you could have posted the same insight as a carousel, a short video, a tweet thread, a newsletter section — but you've already mentally filed it away. You produce content that doesn't compound. Individual pieces are one-and-done. A system produces assets that work across formats and platforms, and that you can reuse, remix, and resurface over time. The fix isn't to work harder or faster. It's to think differently about what you're producing. ## The engine model Think of your content operation as a factory with three stages. **Stage 1: Source.** One long-form piece per week. An article, an essay, a detailed thread, a case study — something substantive enough that there's real thinking in it. This is your raw material. Everything else comes from this. **Stage 2: Refine.** AI helps you extract the angles, reformat the structure, and adapt the register. The same insight that belongs in a 1,200-word post sounds different in a 60-second video and different again in a 5-tweet thread. AI handles the conversion. You handle the judgment. **Stage 3: Distribute.** Scheduled, staged, and tracked. Not "post and pray" — a deliberate plan for which format goes where and when. This is the system I actually run. Not in theory. The newsletter you might have gotten that led you here — that came from this process. ## What Galen's actual week looks like Monday: I write the main piece. Usually 1,000–1,500 words. This is the only creative session that requires being fully "on." Tuesday: I run the repurposing pass. I paste the piece into Claude with a repurposing prompt I've refined over months. Out comes a thread draft, a newsletter intro, a few short-form angles, and a hook list. I read through and cut anything that feels flat. Wednesday–Thursday: I schedule the derivative pieces. Some go out the same week, some get queued for the following week, some get saved for a slow period. Friday is optional. If something's topical — a reaction to something that happened in the space — I'll write a fast piece and run it through the same system at a smaller scale. That's the whole thing. Four focused sessions, maybe six hours total, produces eight to twelve pieces of content across formats. Not because I'm unusually productive, but because the system does most of the work. ## What AI is good for and what it's not This matters before we go any further. AI is good at: - Converting long-form content into shorter formats while preserving the core idea - Drafting variations on a hook or opening line so you can pick the best one - Generating images, audio, and video that fit a brief you've defined - Catching the "AI tells" in your writing so you can fix them before publishing AI is not good at: - Knowing what's worth writing about (only you know your audience, your experience, and what's true) - Replacing the original thinking in the main piece (derivative content only works if the source is real) - Making final creative calls (the AI has no taste — it has patterns) The course is built around this division of labor. You bring the substance. AI handles the production. ## What this course covers **Lesson 2 — Writing with AI without sounding like AI.** The five tells that mark AI-generated text, and how to rewrite around them. Voice references and how to train AI on your own style. **Lesson 3 — Images that actually belong on your site.** Hero images, context images, editorial photography with AI. Three tools, three use cases, and the principle that separates images that work from images that scream "prompt dump." **Lesson 4 — Product photos without a photo shoot.** How to produce studio-quality product photography with AI tools — without booking a photographer, renting a space, or waiting two weeks for delivery. **Lesson 5 — Short-form video with AI.** The 9-second rule for AI video. Sora, Veo, and Runway — which to use when, and how to get something that doesn't look like a screensaver. **Lesson 6 — Voice and audio with ElevenLabs.** Voice cloning, narration, and audio production for people who aren't audio engineers. **Lesson 7 — One piece becomes ten.** The repurposing matrix. Exactly how to turn a single piece into a full week of content across every format that matters. **Lesson 8 — The weekly rhythm.** What to ship every week, what to ship every month, and when to step back and refactor the engine. ## What you'll need - ChatGPT or Claude — any paid tier works, free tiers are fine for most of the writing exercises - A topic or product you're already creating content around (doesn't have to be a business — a newsletter, a side project, a craft, anything with an audience) - Optional: Midjourney, Nano Banana, Ideogram, ElevenLabs — free tiers are sufficient for this course - About an hour per lesson, with actual doing time built in No team required. That's the point. Let's build the engine.

Mark the lesson complete when you're ready. No submission required.