The creators posting twelve times a week are not creating twelve times a week. Almost all of them run the same system: one substantial piece of content, systematically shredded into platform-native derivatives. It's called pillar-and-derivatives repurposing, and it's less a growth hack than an arithmetic trick — the thinking happens once, the distribution happens ten times. Here's the whole system.
Pillars: make one thing worth shredding
A pillar is any piece of content substantial enough to contain multiple ideas:
- A 5–15 minute video (YouTube, webinar, podcast episode)
- A long-form article or newsletter issue
- A talk, livestream, or interview
- Even a dense 10-slide carousel can pillar for smaller derivatives
The quality bar matters more here than anywhere else in your content operation: derivatives inherit the pillar's substance. A thin pillar shreds into ten thin posts; a strong one into ten strong ones. Spend your creative energy at this layer.
The 10 standard derivatives
From one video pillar (the richest kind), the standard extraction:
- 2–4 vertical clips — the strongest moments, subtitled, for Reels/TikTok/Shorts
- A carousel — the pillar's structure as slides (the video→carousel method)
- A second carousel — a different angle: the "mistakes" version of a "how-to" pillar
- 2–3 quote cards — the most screenshot-able lines in branded templates
- A text post / thread — the core argument, native to X or LinkedIn
- A stat or chart post — if the pillar contains one number that surprises
- A "one thing" post — the single most useful takeaway, alone
- A newsletter section — the pillar summarized with a link
- A community prompt — the pillar's most debatable claim as a question
- The pillar itself, cross-posted — full video to every long-form surface
Text pillars map the same way (pull quotes instead of clips). You won't use all ten every week — eight is a strong yield.
The weekly cadence
The system runs on a one-week loop:
- Day 1 — create the pillar. The week's only heavy creative session.
- Day 1, same sitting — extract while it's fresh. Mark clip timestamps, pull quotes, list the derivative angles. Twenty minutes now beats two hours cold.
- Day 2 — batch-produce derivatives. With templates for each format (quote card, carousel, stat post), this is assembly, not design.
- Days 2–7 — staggered publishing. Pillar first, then derivatives spaced across the week, per-platform timing. Never everything at once: the point is presence, seven appearances from one effort.
Then the loop repeats. One pillar a week ≈ 35–45 posts a month.
Automating the assembly line
Steps 2–4 of that cadence are mechanical, which makes them automatable. The pipeline version: the pillar's transcript goes in; a Custom Agent node reduces it to slide copy, quotes, and a text post in your voice; each lands in its branded template via an Apply Template node. There's no dedicated approval-gate node in FeedForce's canvas — the practical pattern is to run the workflow manually up through the template step, review the drafted slides in the editor, then publish once they look right, rather than wiring a timer trigger straight through to Post. That's a standard workflow on FeedForce's automation canvas (workflow #5 in our automation workflows roundup) — you produce the pillar and review the batch; the shredding, design, and scheduling stop being your job.
The mistakes that break it
- Deriving before the pillar is good. Ten derivatives of nothing are nothing.
- Same asset everywhere instead of native re-expression — that's reposting, and each platform's audience can tell.
- Publishing the batch simultaneously. You get one loud day and six silent ones.
- Skipping the system when busy. The week you're too busy to repurpose is precisely the week the system exists for.
Repurposing isn't about squeezing more from less — it's the honest recognition that distribution, not creation, is where most content dies, and that your best idea deserves more than one attempt at finding its audience.