Content repurposing that doesn’t read like an echo.
Content repurposing is the cheapest content you will ever make, and almost everyone does it badly — the same paragraph pasted into four platforms, each of which rewards something different. We build the repurposing workflow that takes one real source and rebuilds it for each destination, so a single hour of your thinking becomes weeks of publishing that doesn’t read like an echo.
Copy-paste is not content repurposing.
The distinction matters because one of them compounds and the other quietly costs you credibility.
Take a 40-minute recorded conversation. There is genuinely enough in it for a long-form article, four or five LinkedIn posts, a handful of short vertical videos, an email, and the raw material for a search page. That is not optimism — it’s just what a dense 40 minutes contains once you stop treating it as one artefact.
What people actually do is take the transcript, ask a model to "make this into a LinkedIn post", and paste the result. Then they do the same for Instagram. The output is recognisably the same block of text with different line breaks, and the audience that follows you in two places notices immediately. Worse, none of the five pieces is any good, because each platform rewards a different shape: LinkedIn rewards a specific claim argued in public, YouTube rewards a promise kept over minutes, TikTok rewards the first second, search rewards completeness.
Real repurposing extracts the *ideas* from the source, not the sentences — and then builds each piece natively for where it lands. Same argument, five genuinely different artefacts. That’s a workflow, and a workflow is something we can automate.
The repurposing workflow, step by step.
This is the pipeline we build. It runs on n8n with Claude Code doing the reasoning at each stage, and every stage is documented so your team can change it.
Capture one dense source
A recorded conversation, a client call you’re allowed to use, a long-form video, or a written argument. We design the capture ritual so the source is naturally dense — the questions asked are the ones that make you say the interesting thing rather than the polite thing.
Deliverable: a capture ritual, the prompt set, and the recording setupExtract the ideas, not the text
The pipeline pulls out the distinct claims, the stories, the objections handled, and the numbers you’re cleared to use — as a structured list of ideas with the supporting material attached to each. This intermediate step is what separates repurposing from reformatting, and it’s the one everyone skips.
Deliverable: an idea inventory per source, stored and searchableRoute each idea to the platforms that suit it
Not every idea belongs everywhere. A nuanced argument dies in fifteen seconds of vertical video; a strong visual demonstration is wasted as a paragraph. The routing rules are yours, written down, and applied consistently instead of by whoever is doing it that week.
Deliverable: routing rules mapping idea types to platformsBuild each piece natively
Each destination gets its own drafting step with its own standards — structure, length, opening, and what "good" looks like there. The voice reference is shared; nothing else is. This is where one source stops being one post.
Deliverable: a per-platform drafting workflow with its own rubricSequence it across time
Five pieces from one source published on one day is a spike; spread across three weeks with the long-form anchoring it, it’s a campaign. The system schedules the sequence, keeps the anchor piece linked from the short ones, and stops the same idea landing twice in a week.
Deliverable: a scheduling sequence and a de-duplication ruleFeed the results back
Which ideas earned attention, on which platform, in which shape. Over a few cycles this stops being guesswork and starts telling you what to record next — which is the point at which repurposing becomes a strategy rather than an efficiency.
Deliverable: a per-idea performance view feeding the next captureThe routes we build most often.
Each of these is a real pipeline with its own rules, not a generic "cross-post" toggle.
YouTube → LinkedIn
A long-form video carries more argument than any post can. The pipeline pulls the distinct claims out and builds each as a standalone LinkedIn post that stands up without the video — while still pointing back to it.
YouTube → Short-form
Vertical clips for TikTok, Reels and Shorts — chosen on whether a segment actually stands alone, not on whether it happened to be 30 seconds long. Cuts, captions and the opening line rebuilt for a cold viewer.
Podcast → everything
Long conversations are the densest source there is. Transcript in, idea inventory out, then the full routing across written and video formats.
Blog → social
The reverse direction, and useful when your search content is already strong. Each section that makes a self-contained point becomes a post; the post links back and the page keeps the authority.
Source → search page
The one people forget. The same recording that produced a week of social is usually most of a genuinely good article — the compounding asset the social posts never become.
Everything → the knowledge base
Every source captured makes the next cycle cheaper, because the ideas, stories and numbers are now written down. This is why the system gets faster with use.
The honest cost.
Repurposing multiplies whatever you put in, which is a problem if what you put in is thin. A weak source produces five weak pieces faster than you could have produced one — the pipeline has no opinion about whether the thinking was any good. The capture ritual is designed to protect against this, and it still depends on you having something to say.
It also raises the stakes on the review gate. Five outputs per source means five chances for something wrong, off-brand, or not-yet-public to reach an audience. We build the gate to match, and someone on your side has to actually operate it.
And a repurposing system is not a substitute for a reason to publish. It makes publishing cheap. What to publish about, and why anyone should care, is still strategy — and if that isn’t settled, the honest advice is to fix that first and automate second.
Where to go next.
Repurposing is one stage of a larger machine. Here is the rest of it.
Content automation
The whole machine — knowledge base, voice, pipeline, review and measurement. Repurposing is one stage of it.
What we buildYouTube content system
The most common source in a repurposing pipeline, because a long-form recording feeds everything downstream.
What we buildSEO content system
Where the compounding lives. Social decays in days; a search page keeps working.
The full mapThe full service map
Content OS, Business OS, and the extensions — the whole picture in one place.
Read the thinking behind it
Content multiplication: one idea, many forms
The arithmetic behind repurposing: what one genuinely dense source is worth once you stop treating it as one artefact.
GuideHow to create content that compounds over time
Why most content depreciates the week it ships, and what makes the small share of it keep working for years.
Questions people ask before they book.
What is content repurposing?
Content repurposing is taking one substantial source — a recorded conversation, a long-form video, a detailed article — and rebuilding its ideas as separate pieces for different platforms. The important word is rebuilding. Reposting the same text in four places is cross-posting, and audiences that follow you in more than one place can tell. Repurposing extracts the underlying ideas and constructs each piece natively for where it will be read.
How many pieces can you realistically get from one source?
It depends entirely on how dense the source is, and we won’t give you a number that sounds impressive on a web page. What we can say is the shape: a genuinely substantial 40-minute conversation usually contains several distinct arguments, and each argument can support a written piece, a short video, and a section of a longer article. Thin sources produce thin output no matter what the pipeline does.
Won’t the platforms penalise us for duplicate content?
Duplicate-content penalties are largely a search concern rather than a social one, and they apply to identical pages competing with each other — not to an idea being discussed in different words on different networks. The real risk is human, not algorithmic: an audience that sees the same paragraph three times stops paying attention. Building each piece natively solves both concerns at once, which is why it’s the whole method.
Can this run without us recording anything?
It can run from written sources, and for some businesses that’s the right shape. But recorded conversation is usually the cheapest dense source a busy founder can produce — talking for forty minutes costs less than writing for four hours, and it tends to be more candid, which makes for better content. If recording genuinely won’t happen, we design the capture around what will.
What tools does the repurposing workflow run on?
Orchestration in n8n, reasoning and drafting in Claude Code, and whatever scheduler and storage you already use. Where Zapier or Make.com fits your existing stack better, we build it there instead. Everything runs in your accounts, so the workflow, the transcripts and the idea inventory belong to you.
Do you also write the content, or just build the system?
We build the system, and the system produces the content — that’s the distinction we care about. During the build we produce real output alongside your team so the standards are calibrated on actual work rather than described in the abstract. After handover, your team runs it. We’re architects rather than a content supplier, and the difference shows up the day you stop paying us: the system keeps running.
Let’s map what your content system could look like.
One conversation, an hour, no pitch deck. We look at what you already publish, where it stalls, and whether a system would actually help. If it wouldn’t, we’ll say so.
Start a Conversation