Content repurposing fails for a boring reason: teams automate the generation step and leave every other step manual. You end up with forty AI-written drafts nobody has time to check. The workflow below fixes the sequencing, not the writing.
Start from a source asset, not a content calendar
Repurposing only compounds when the source carries information that cannot be generated — a real job walkthrough, a customer call, a teardown, an original number you measured. Generic source material produces generic derivatives, and the AI cannot add substance that was never there.
The five-stage workflow
- 01Capture — one substantial asset per cycle: a long-form post, a recorded walkthrough, a customer conversation you had permission to record.
- 02Transcribe and mark — turn it to text, then tag the three or four passages that carry the actual insight. This is the highest-leverage human step and takes about ten minutes.
- 03Derive — generate platform-native variants from the marked passages only, never from the whole transcript. Constrained input is what keeps output specific.
- 04Edit for fact — check every claim, number, name, and price. This step is not optional and does not shrink over time.
- 05Schedule and space — distribute derivatives over weeks so one source does not saturate a feed in two days.
Audio and video sources
Recorded material is the highest-yield source because it is dense and cheap to capture — you were going to have the conversation anyway. Transcription is close to solved, so the constraint has moved to selection: a sixty-minute call might hold four genuinely useful minutes, and the entire value of the workflow is finding those four.
What to automate and what to leave alone
Automate the mechanical, deterministic steps. Leave anything with a judgment or a fact in it to a person. The rough rule: automate transitions between stages, not the decisions inside them.
- ›Safe to automate — file handling, transcription, formatting, scheduling, cross-posting, and moving an approved asset to the next stage.
- ›Keep human — passage selection, fact and claim checks, anything naming a price or a customer, and final approval to publish.
- ›Never automate — publishing without an approval gate. The cost of one wrong published claim about your own business exceeds the time the gate saves.
Making it scale without adding people
A repurposing system scales when the per-cycle human time stays flat as output grows. If each new derivative adds edit minutes, you have built a treadmill, not a system. Measure the minutes per cycle, not the posts per week — output volume is the vanity number here.