Most solopreneurs who try repurposing do it wrong. They write an article, copy a paragraph into a LinkedIn post, paste a different paragraph as a Substack Note, and then wonder why it all feels thin and repetitive.
The content is the same. Only the container changed.
Real repurposing doesn’t work that way. One piece of writing contains multiple layers – the argument, the example, the counterintuitive angle, the practical implication, the feeling behind it. Each of those layers can become a standalone piece. Different surface, different depth, different audience entry point.
That’s the distinction that changes everything: repurposing is extraction, not copying.
This is how I think about it, and how I run it.
The problem with “post it everywhere”
The standard repurposing advice sounds reasonable: write once, post everywhere. Take your article, chop it into social posts, schedule it across platforms, done.
The result is usually five weak pieces instead of one strong one.
The article becomes a LinkedIn post that’s too long and too dense. The Substack Note is just a block quote with a link. The email feels like a summary nobody asked for.
It doesn’t work because the content wasn’t adapted – it was compressed. Compressing the same argument into a shorter format doesn’t make it better for that format. It just makes it smaller.
The other problem: when you post the same thing five ways in the same week, returning readers notice. And they stop reading, because there’s no reason to check more than one place.
Good repurposing solves both of these problems. You’re not taking the same thing and shrinking it. You’re taking different elements of the same piece and letting each one breathe in its own format.
What a piece of writing actually contains
Before you can extract well, you need to see what’s there.
Most articles – if they’re any good – contain more than one publishable idea. They contain the main argument, but they also contain the specific example that makes it concrete, the counterintuitive claim buried in the middle, the personal story that grounds the whole thing, and the practical implication at the end.
Those aren’t just supporting elements. Each one is a standalone piece waiting to be pulled out.
Here’s how I think about it. When I finish an article, I look for five things:
The core claim – one sentence that captures the article’s central idea. This becomes a GROUND Note or a punchy LinkedIn post. Short. No explanation needed. Just the claim.
The concrete example – the specific, real thing I described to make the argument land. This can become a behind-the-scenes email or a SIGNAL Note pointing back to the article. The example is often more interesting standalone than as a footnote inside a longer piece.
The counterintuitive angle – the part where the article goes against the obvious take. This is usually where the article gets interesting. It makes a strong RELATE Note or a LinkedIn hook because it stops people mid-scroll.
The practical step – the most actionable part of the article. This works well as an email that stands alone. It gives something useful without requiring the reader to have read the full piece.
The question raised – almost every good article opens a question it doesn’t fully answer. That question becomes an OPEN Note. You’re not extracting an answer – you’re extracting the tension.
Five elements. Five different pieces. None of them a copy of the others.
The stack in practice
This is my actual repurposing stack for a single article, roughly in the order I produce the pieces:
Day 1 – Publish the article. The full thing goes out first. Everything else is built from it. The article is the source.
Day 2 – One Substack Note. I pick whichever of the five elements is strongest and write a standalone Note. I don’t reference the article in the Note. The Note works on its own.
Day 3 – One LinkedIn post. Usually the core claim or the counterintuitive angle. One idea, written for LinkedIn’s rhythm: short paragraphs, no padding, a real point. I put the article link in the comments, not the post body.
Day 4 – One email to the list. I take the practical step from the article and write it as a standalone email. Subject line that makes it feel fresh. No “as I mentioned in my article.” Just the thing itself, with its own framing.
Day 5 or 6 – A second Note. I pick a different element from the five. Usually the question raised, because by this point the article has had a few days to breathe and I have a better sense of what resonated.
That’s it. Five publishing moments from one piece of writing. Three platforms. Nothing repeated. Each piece uses a different layer of the original.
The article lives for weeks. The derived pieces have a half-life of hours. That asymmetry is the whole point.
What makes it not feel repetitive
There are two reasons a repurposing stack goes stale fast.
First: you use the same element twice. If your Substack Note and your LinkedIn post both lead with the core claim, they’re the same piece in different containers. Pick different elements for different platforms.
Second: you frame the pieces as “from my article.” The moment you write “I wrote about this in my latest piece,” you’ve told the reader they already know what’s coming if they read it. The derived piece loses its reason to exist.
The fix is simple: each piece should be able to stand without the article. If someone never reads the original, the Note should still make sense. The email should still be useful. The LinkedIn post should still stop the scroll.
This also means you can’t just copy-paste a paragraph and call it done. You have to reframe. A paragraph from an article is written to lead somewhere else. A standalone Note has to be complete in itself. Same raw material, different craft.
The limit
Repurposing is not infinite. One article gives you roughly one week of derived content, sometimes less. If you’re trying to stretch a single piece across three weeks, you’ll run out of interesting things to say and start repeating yourself at a lower quality.
The stack works because articles are dense. You wrote 1,200 words. You extracted the best five ideas from them. After that, what’s left isn’t worth publishing.
So the model isn’t: one article feeds everything forever. The model is: one article per week, one stack per article, one week of content per stack. Then a new article starts the cycle again.
If that cadence sounds like a lot, the answer isn’t more repurposing – it’s a sustainable writing rhythm. That’s a different article. (See: How I Run a Content Operation Alone)
Where to start
If you’ve never done this systematically, start with your last published article.
Open it. Read it looking for the five elements: core claim, concrete example, counterintuitive angle, practical step, question raised. Write them down as single sentences.
Then write one piece from one element. Just one. Post it.
See if it works as a standalone. See if it gets engagement from people who didn’t read the article. If it does, you’ve found the lever.
You don’t need a complicated system to start. You need to understand that the article is not the content. The article is the source.
If you want to go deeper on the content system behind this, download the Solo Content System – a free guide to running a one-person content operation with one input and three consistent outputs. You can download it here.
