How to repurpose one long-form video into 20 posts

Most people who ask how to repurpose long-form video already have the raw material. A webinar sits in a folder. Three podcast episodes are published and untouched. The talk from last quarter has 400 views and nothing downstream. The bottleneck is not a shortage of content and it is not a shortage of AI tools. It is the absence of a cutting procedure — a fixed sequence you can run on any recording without re-deciding what to do each time.

This guide sets out that sequence: one extraction pass, one asset split, one editorial protocol. It is deliberately mechanical. Mechanical is the point — a procedure you can hand to somebody else, or run on a Tuesday when you are tired, is worth more than a clever workflow you only execute when inspired.

1. Why the obvious approach produces twenty bad posts

The naive method is to paste a transcript into a chatbot and ask for twenty social posts. It works, in the sense that twenty blocks of text come out. They are unusable for three predictable reasons.

• Flattening. A single request forces the model to average across the whole transcript. The sharpest ninety seconds of the recording — the part where you disagreed with the received wisdom — gets the same weight as the housekeeping at the start.
• Format collapse. A LinkedIn post, an X thread, a newsletter section and a short-form video script have genuinely different shapes. Asked for all of them at once, a model produces one shape with different line breaks.
• Voice drift. Without explicit constraints, output regresses to the statistical middle: throat-clearing openings, symmetrical sentence lengths, hollow transitions. Readers who follow you notice immediately.

Each failure has a structural fix, and the fixes have to happen in order.

2. The extraction pass: find the assets before you write any

Run one pass over the transcript whose only job is inventory. No drafting. You are looking for discrete, separable units of value:

1. Claims. Statements you would defend in an argument. "Most repurposing fails because nobody wrote down the cutting order" is a claim. "Content is important" is not.
2. Numbers. Any figure with a unit attached — hours, dollars, percentages, counts. Numbers are the single strongest differentiator between a specific post and a generic one.
3. Stories. Something that happened, with a before and an after. One paragraph is enough.
4. Procedures. Anything you described as a sequence of steps.
5. Objections. Every point where you said "people usually think X, but…". These convert better than anything else because they start from the reader's existing position.

A 45-minute recording that was worth making will yield somewhere between twelve and twenty-five of these. If it yields four, the honest conclusion is that the recording does not support twenty assets, and the correct response is to stop rather than to pad. That judgement — knowing when the source is too thin — is what separates a repurposing procedure from a content mill.

3. The split: assign units to formats, then write

Now assign. Each extracted unit maps to the format it naturally fits, rather than being forced through all of them:

• Claims → LinkedIn posts and X posts. A claim plus one piece of evidence plus one implication. 120–200 words on LinkedIn; one to three sentences on X.
• Numbers → carousel slides and standalone posts. A number with context is a complete asset by itself.
• Stories → newsletter sections and short-form video scripts. Narrative needs either the room of a newsletter or the pace of video; it dies in a 200-word post.
• Procedures → threads and how-to posts. Sequences want an enumerated format.
• Objections → hooks. The strongest openings in the batch will come from here.

Twenty assets typically resolves to roughly six to eight LinkedIn posts, four to six X posts or threads, two to three newsletter sections, and four to six short-form video scripts — but the split should follow the material, not a quota. Writing to a quota is how the padding creeps back in.

4. Negative constraints: what to ban, explicitly

Voice drift is not fixed by asking for a better tone. Adjectives like "bold" and "concise" are subjective and models interpret them loosely. What works is an explicit ban list applied at the instruction level, before any drafting:

• Opening sentences that state the topic before making a point.
• Connectives that carry no argument: furthermore, moreover, delving deeper, it is worth noting that.
• Clichéd metaphors: navigating the turbulent waters, double-edged sword, unlocking potential.
• Hedges that weaken a claim you actually hold: while some might disagree, it could be argued that.
• Uniform sentence length. Require deliberate variation, including fragments.

Pair the ban list with two or three samples of your own writing — one long-form, one tactical, one casual — and extract from them an explicit description of cadence, vocabulary and formatting habits. Reusing that description across every batch is what makes the output sound like a person rather than a category.

5. The editorial protocol: the part everyone skips

Volume without an editing gate is how repurposing damages a brand rather than building one. The protocol that holds up is short and applied per batch of five, not per asset:

1. Delete the first sentence. Read what remains. If it starts faster and lands harder, keep it deleted. It usually does.
2. Specificity check. Replace every vague phrase with the actual figure or tool name from the source. "Improved efficiency" becomes "cut the sync from four hours to twelve minutes" or it comes out.
3. Strip the enthusiasm. Exclamation points, hyperbole and cheerleading all go.
4. Fix the ending. No summary paragraph, no "what do you think?". End on the most definitive sentence you have.

Budget roughly fifteen minutes per batch of five. Twenty assets therefore costs about an hour of genuine editing. That hour is not overhead — it is the difference between assets that read as yours and assets that read as output.

6. What this costs, honestly

Done entirely by hand, turning one long-form recording into twenty distribution-ready assets takes most people somewhere between eight and twenty hours, which is why it does not get done. With a fixed procedure and AI handling the drafting inside explicit constraints, four to nine hours per twenty-asset package is a realistic range once you have run it two or three times. The first run will be slower than the third; that is true of every procedure.

Those ranges are working figures, not guarantees. Your material, your standards and your platforms will move them.

Related reading

• Curing AI slop — chapter 4 in full, free, no email required
• Stop Typing, Start Asking — full contents and what is included
• A one-page prompt recipe format that works in any free chatbot
• All Avalon Store products