Turn One Podcast Episode Into a Week of Content
A repeatable repurposing loop for one episode: pick the spine, draft five assets from the same evidence, and keep attribution intact.
Guide5 min read
One good episode can carry a week of writing. Most teams get a thread and a "new episode is out" post, then move on, because repurposing looks like five separate jobs.
It is one job with five outputs. The work is choosing the spine — the two or three claims you are willing to defend — and then cutting different shapes from the same evidence.
Who this is for
Two audiences, with one important difference.
You make the show. You own the audio and the transcript. You can republish quotes freely, and the episode is the source of truth.
You are listening to someone else's show. You can quote with attribution and a link; you cannot republish the whole transcript or lift a five-minute segment into your own video. The line is fair use plus courtesy, not a technical limit. When in doubt, quote less and link more.
The workflow is the same; only the rights change.
Pick the spine first
Before writing anything, read the summary and mark the three claims that would still be interesting in a year. Ignore the news of the week; it dates the post.
If you use Podwise, the takeaways and highlights are the shortlist. The chapters tell you where the evidence lives. For a 90-minute conversation, three claims is usually two too many — pick the sharpest one and keep the other two as backup.
The five assets
1. The thread. Six posts, one idea each. Lead with the claim, quote the guest once, end with a link to the episode. Do not open with "New episode!" — nobody shares a press release.
2. The newsletter section. 150 words: the claim, the best quote, and what it changed in your thinking. One idea per issue is fine; a newsletter is not a summary service.
3. The blog post. This is the only asset that needs new structure. Take the claim, add your own example, and note the strongest counterargument. A repurposed blog post that just transcribes the episode is a duplicate; one that argues with it is content.
4. The clip. 20–40 seconds where the guest says the thing plainly. Add one line of context in the caption and a timestamp link. If the episode is someone else's, quote the clip with credit and drive people to the original.
5. The internal memo. Half a page for your team: what the episode claims, what it means for us, one decision it affects. This is the asset with the highest hit rate of actually changing something.
A week that fits
| Day | Work | Time |
|---|---|---|
| Mon | Read, mark the spine, verify quotes | 30 min |
| Tue | Thread + newsletter | 45 min |
| Wed | Blog post draft | 60 min |
| Thu | Clip + captions | 20 min |
| Fri | Memo + schedule next week | 20 min |
Under three hours if the episode is already processed. The bottleneck is never the writing; it is re-listening because you did not capture the quotes the first time.
Verify before you publish
Repurposing magnifies mistakes. A misheard name in a private summary is harmless; the same name in a thread is a correction.
- Open every quote at its timestamp. If the transcript says "Sacks" and the audio says something else, the audio wins.
- Check the guest's title and company against the episode page, not your memory.
- If the claim is a prediction, date it in the copy: "in a 2024 episode" is honest, "experts say" is not.
- Link the original episode even when you own it. It is the receipt.
Where the tools help
The summary gives you the shortlist, the transcript gives you the quote, and the export gives you the file. export_episode_markdown with the highlights section is the fastest way to get a working doc; send_episode puts it in Notion or Readwise if that is where you draft.
Clips are the part people underestimate. Saving the moment while listening (or from the headphone controls in the phone apps) means the evidence is already cut when you sit down to write, instead of a note that says "good bit around 40 minutes."
If you want the whole loop as prompts for an AI app, the recipes page has the episode-to-thread version with the tool calls behind it.
The rule that keeps it from becoming spam
One episode, one argument. If the thread, the post, and the newsletter all restate the same summary in different fonts, you have published the same thing three times. Each asset should make a different point from the same evidence: the thread introduces it, the post tests it, the memo applies it.
That is the difference between repurposing and repeating.
