Your best post from January reached, at most, a small slice of the people who followed you in January. Since then your audience has grown, turned over, and mostly never met it. And yet almost every founder we work with treats a published post the way they'd treat a spent match: it burned once, it's done.
No ecommerce operator runs inventory this way. If a SKU sells through, you don't discontinue it out of politeness. You reorder it. A content re-run system applies the same logic to the one asset class founders refuse to restock: their own proven material.
We wrote recently about the edit-vs-repost decision — what to do in the first hours after a post ships with something wrong in it. We said then that reposting a good post months later to a turned-over audience is a legitimate move and a completely different question. This is that question, answered properly.
The Math Nobody Runs on Their Own Archive
Start with what a single post actually reaches. Richard van der Blom's 2026 Algorithm Insights report — 1.3M posts across 50,000 creators — puts typical post reach at 8–12% of followers, down from 15–20% a year earlier. Call it one in ten. On the day your best post of the year published, roughly nine in ten of your then-followers never saw it.
Now add turnover. If your account is growing at all, a meaningful share of your current audience arrived after that post ran. A founder who grew from 6,000 to 9,000 followers since January has 3,000 people — often the most recently engaged, most commercially relevant people, since they followed the current version of you — for whom that post simply does not exist.
Multiply the two and the conclusion is uncomfortable: the strongest thing you have ever written has been seen by a minority of the audience you have right now. The founders who feel like they're repeating themselves are almost always calibrating off the wrong reader — themselves, the one person who has seen everything.
What a Re-Run Is (and What It Isn't)
A re-run is not hitting the repost button on your own eight-month-old post. It's a rewrite of a proven idea, published as a new post. That distinction matters for three reasons.
First, a new post gets a fresh test pool. The platform grades it on its own merits, to a first-hour audience that is materially different from the one that graded the original.
Second, a rewrite forces the update. Your January post about a fee change, a tactic, a client pattern — some part of it has aged. The re-run is where you refresh the number, sharpen the example, or add the thing you've learned since. The idea is the inventory; the words are the packaging, and packaging is allowed to improve.
Third, a rewrite protects you from the one real risk. The people who do remember the original are disproportionately your most engaged readers. A verbatim repost tells them you ran out of things to say. A rewritten version — same spine, new door, updated receipts — reads as conviction. Nobody has ever unfollowed a founder for making the same true argument better.
Building the Re-Run Shelf
The system is a small file with strict fields. If you already run a monthly content retro, this bolts onto it in five minutes: as you review the month's posts, tag the ones that earned a second life.
Each entry needs:
- The core claim — one sentence, stripped of the original hook. This is what you're re-running. Not the post; the argument.
- Original date and performance — with a note on which metric earned it the shelf. A post that pulled saves and DMs is a re-run candidate. A post that pulled easy likes usually isn't; applause doesn't compound.
- What must be updated — the number that will be stale, the example that has a better successor, the platform mechanic that may have moved.
- Earliest re-run date — we use 90 days as the hard floor, and most of our re-runs happen at 6–9 months. Below 90 days you're not reaching a new audience, you're testing the patience of the old one.
- Format shift — optional but powerful. The text post becomes the carousel. The framework becomes the worked example. Same claim, different vehicle, and a different vehicle often reaches a different reader.
That's the whole apparatus. The founders who overbuild this into a database never use it. A shelf with 10–15 entries, reviewed monthly, is enough to supply a quarter of a posting calendar.
The Re-Run as a Diagnostic
Here's the part almost nobody exploits: a re-run is the only true A/B test your account ever gets to run on itself. Same author, same core claim, two moments in time.
When the re-run outperforms the original, you've learned your audience grew in the right direction — more of the people who need this argument are now in the room. When it underperforms during an otherwise healthy stretch, you've learned something too: either the topic has decayed, or your lane has drifted far enough that the platform no longer knows who to show it to. Both findings are worth more than another post's worth of reach.
We log the comparison on the shelf entry. Over a year it becomes a map of which of your arguments are durable assets and which were moments.
What Never Gets Re-Run
The shelf has a bouncer. Four things don't get past it:
News-pegged posts. Anything whose engine was timeliness. The mechanics of re-running kill the only thing that made it work.
Expired mechanics. A tactical post about how a platform behaved in 2024 doesn't get re-run; it gets converted — into the "here's what that mechanic taught us, and what replaced it" post, which is a different and often better piece of writing.
Posts that flopped. A flop you still believe in deserves a better version, and writing the better version is legitimate — but that's revision, not a re-run, and it doesn't get to skip the line by wearing the re-run label. The shelf is for proven material only. That's the entire point of the shelf.
Anything you no longer believe. Sounds obvious. Isn't. Founders re-run old winners they've quietly outgrown because the numbers were good, and the audience can smell a writer performing a conviction they used to have.
FAQ
Won't my followers notice I'm repeating myself? The ones who could notice are the small overlap who saw the original, months ago, and still remember it — your most loyal readers. For them, a sharpened version of an argument they liked is reinforcement, not repetition. The complaint you're imagining has, in our experience across every client account, never actually arrived.
How much of a calendar can be re-runs? We cap it at 20–30%. Below that you're leaving your archive idle; above it the account stops generating new proof, and new proof is what earns the next shelf.
Is this different from repurposing? Repurposing usually means spreading one piece across channels in the same week. A re-run is the same channel, months later, rewritten. Different tool, different job.
Most founders don't have a content volume problem. They have a distribution amnesia problem — a shelf of proven arguments earning nothing while they strain to invent unproven ones. If you want help building the system that fixes both sides of that, this is what we do all day.