The exact 5-bucket fan-out methodology that turns 4 weekly sources into 100-140 platform-native posts a month. Per-source output allocation, credit-cost math, the labor-collapse economics across manual / AI-assisted / autopilot tiers, and the channel-mix presets for creator, B2B SEO, founder, and paid-ad goals.
One weekly source (podcast, YouTube long-form, or webinar) fans out into 25-35 platform-native pieces across five buckets — Video, Image, Text, Blog, Newsletter. Four weekly sources a month produce 100-140 posts. The mechanism is a single Persona Brief plus bucket allocation, not 100 separate writing sessions. On Kompozy Creator ($49/mo, 2,500 credits) the credit cost of a full month runs roughly $20-35 of the plan; the labor it replaces is 32-48 manual hours.
The single-source-to-a-month-of-content number sounds like a marketing claim until you do the arithmetic on a real episode. A 60-minute podcast carries 8,000-12,000 transcript words and 6-10 load-bearing ideas. Each idea is not one post — it is a video clip, an image card, two or three text posts, a paragraph of a blog, and a line of a newsletter. The multiplication is structural: one idea, expressed natively across five surfaces, is already five-to-eight pieces. Run that across 6-10 ideas and a single source has produced a week of content on its own.
The reason most operators never see this is that they treat each post as a separate act of creation. They write a tweet, then later write a LinkedIn post, then later script a Reel — three creation sessions for three pieces, all from the same underlying idea they already articulated once on the podcast. That is the labor trap. The fan-out methodology breaks it by treating the source as the only creation event and every downstream post as a transform, not a new write.
This is the operator-grade breakdown of that math — the per-source output allocation by bucket, how the allocation shifts when the goal is reach versus search versus founder authority versus paid-ad creative, the real credit costs at each Kompozy tier, the labor-collapse economics across manual, AI-assisted, and autopilot tiers, and the four conditions under which the math stops working. Full positioning disclosure: Kompozy is built around exactly this five-bucket fan-out (see the [content-repurposing methodology](/repurpose)), so the figures below are checkable against real credit costs, not hand-waved. For anyone running fewer than two sources a month, we will say plainly where the setup cost outweighs the leverage.
The fan-out works because a single recorded source contains far more distinct, reusable substance than a single post can hold. A 20-minute YouTube long-form has 40-60 candidate moments — energy spikes, complete claims, quotable lines, visual beats. A 60-minute podcast carries 6-10 framework-grade ideas, each with its own supporting argument and example. The substance is already created and already validated by the act of recording it; what remains is reformatting, and reformatting is mechanical in a way that creation is not.
Kompozy organizes that reformatting into five fixed buckets — Video, Image, Text, Blog, Newsletter — and every output type the engine produces maps under one of them. A clipped short and an avatar short both live in Video; a quote graphic and a carousel both live in Image; standalone posts and threads live in Text. The bucket model is what makes the math predictable: instead of asking "how many posts can I get," you ask "how many outputs does each bucket take from this source," and the buckets sum to a known per-source total. That is the difference between a vague "repurpose more" instruction and a countable production plan.
The single highest-leverage move in the whole methodology is the one most operators skip: locking voice once, at the source level, with a Persona Brief. Without it, every one of the 25-35 downstream outputs averages toward the LLM default register and the multiplication produces 35 pieces of generic slop instead of 35 pieces that sound like you. The Persona Brief is the reason fan-out scales — it is written once and applied automatically to every bucket, so the marginal voice-tuning cost per post is zero. The deeper Persona-Brief discipline is covered in the [podcast-to-social methodology](/repurpose/podcast-to-social); for the math here, treat it as the fixed cost that all 35 outputs amortize against.
The compounding effect is what changes the business case. One source a week is 25-35 pieces; four sources a month is 100-140. But the Persona Brief, the scheduler config, and the platform connections are written once and reused every week — so the per-source effort falls as source count rises. The first source carries the full setup tax; the fourth source is nearly free. This is why the methodology rewards consistency over intensity: a creator who records one disciplined source a week for a year out-produces one who batches ten sources in a sprint and then goes quiet.
At Kompozy's default bucket allocation, one weekly source produces the following spread. These are mid-range working numbers for a substantive 20-minute video or 45-60 minute podcast — thin or low-information sources land at the bottom of each range, dense ones at the top.
That sums to 25-35 outputs per source. The Text bucket carries the most volume because text is the cheapest to produce and the platforms (X, LinkedIn, Threads) reward the highest posting frequency; Video carries the most production weight but the fewest pieces because each one needs a render. The Blog and Newsletter buckets each produce exactly one durable, owned-channel asset per source — low volume, high half-life, which is what makes them the SEO and retention anchors of the spread.
| Source type | Length | Video | Image | Text | Blog | Newsletter | Total / source |
|---|---|---|---|---|---|---|---|
| Podcast episode | 45-60 min | 5-8 | 4-8 | 14-24 | 1 | 1 | 25-35 |
| YouTube long-form | 15-25 min | 6-10 | 3-6 | 10-18 | 1 | 1 | 21-36 |
| Webinar / workshop | 45-90 min | 4-7 | 6-10 | 12-20 | 1-2 | 1 | 24-40 |
| Customer / sales call | 20-40 min | 1-3 | 3-5 | 4-8 | 1 | 0-1 | 9-18 |
| Founder Loom / voice memo | 5-15 min | 1-3 | 2-4 | 6-12 | 0-1 | 1 | 10-21 |
The table shows why source selection matters more than source volume. A 40-minute webinar out-produces three 10-minute videos because density, not duration, drives the count — the webinar has more distinct ideas per minute and more framework-shaped material that carousels and blogs feed on. Operators chasing the 100-posts-a-month number should optimize for one or two dense sources a week, not a pile of thin ones.
The default allocation is a starting point, not a law. The right mix depends on what the content is for — reach, search, authority, or ad creative — and the buckets reweight accordingly. The Persona Brief stays identical across all four presets; only the bucket dials move. Below are the four presets that cover most operators, with the per-source and per-month totals each produces.
When the goal is audience growth, weight the buckets toward the high-frequency, high-distribution surfaces: heavy Video (6-8 shorts per source) and heavy Text (15-20 posts), with Blog and Newsletter kept to one each as the owned-channel anchor. This produces about 35 outputs per source, 140 a month across four sources. The reach preset accepts that most pieces are ephemeral — a short peaks in 48 hours — and bets on volume plus the algorithm finding the breakout. It is the right mix for a creator under 100k followers who needs surface area more than depth.
When the goal is compounding search traffic, invert the weighting toward the high-half-life buckets: 1-2 Blog posts per source (a main piece plus a variant targeting an adjacent long-tail keyword), every blog paired with a Newsletter, and Video trimmed to 3 shorts that serve as distribution for the blog rather than the main event. This produces about 22 outputs per source, 88 a month — fewer pieces, but each carries far more lifetime value because a ranking blog earns traffic for 18-36 months while a short is spent in a week. The blog-as-anchor pattern is detailed in the [twitter-thread-to-blog playbook](/repurpose/twitter-thread-to-blog), which applies in reverse here.
Founder-led marketing lives on LinkedIn and X, so weight there: 4-5 LinkedIn long-form posts per source, 2-3 X threads, and 3 shorts including one avatar reframe for the days the founder cannot record. This produces about 28 outputs per source, 112 a month. The founder preset trades raw volume for register — every text post is shaped to read as the founder's own argument, not a brand announcement, which is the entire point of founder-led content and the reason the Persona Brief's voice DNA matters most under this preset.
When the source is feeding a paid-acquisition engine, the buckets reshape around testable ad units: 8-10 Video shorts per source including POV-hook-plus-demo cuts, 6-8 Image cards for static-ad testing, and Text, Blog, and Newsletter trimmed to near-zero. This produces about 22 outputs per source, 88 a month, every piece ad-ready. The paid preset is the only one where Video and Image dominate the entire spread, because the destination is an ad account that consumes creative variants faster than any organic feed.
| Goal preset | Heaviest buckets | Per source | Per month (×4) | Optimizing for |
|---|---|---|---|---|
| Maximum reach | Video + Text | 35 | 140 | Surface area, breakout odds |
| SEO / search | Blog + Newsletter | 22 | 88 | Lifetime value per piece |
| Founder authority | LinkedIn + X threads | 28 | 112 | Register and trust |
| Paid-ad creative | Video + Image | 22 | 88 | Testable ad-unit volume |
Notice that the two highest-volume presets (reach at 140, founder at 112) and the two value-per-piece presets (SEO and paid, both 88) bracket the same source input. The methodology does not produce more substance under the reach preset — it slices the same substance into more, thinner pieces. Choosing a preset is really choosing how finely to cut a fixed amount of source material, which is why matching the preset to the goal matters more than chasing the highest output number.
The labor case is the headline, but the credit case is what makes the unit economics checkable. Kompozy charges credits per output, and the per-output cost varies sharply by bucket — text is near-free, video is the expensive line. Here are the verified 2026 per-output credit costs that drive every calculation below.
| Output type | Bucket | Credits | Approx $ on Creator | Approx $ on Pro |
|---|---|---|---|---|
| Text post | Text | 3 | $0.06 | $0.05 |
| Image / quote card | Image | 8 | $0.16 | $0.13 |
| Carousel (per slide) | Image | 8 / slide | $0.16 / slide | $0.13 / slide |
| Blog post | Blog | 12 | $0.24 | $0.20 |
| Clipped short | Video | 14 | $0.27 | $0.23 |
| AI (faceless) short | Video | 214 | $4.20 | $3.55 |
| Avatar short | Video | 106 | $2.08 | $1.76 |
Run those costs against the default per-source spread and the monthly arithmetic falls out. A reach-preset source (say 7 clipped shorts, 1 avatar short, 6 image cards, 18 text posts, 1 blog, 1 newsletter) is roughly 7×14 + 106 + 6×8 + 18×3 + 12 + 3 = 98 + 106 + 48 + 54 + 12 + 3 = 321 credits. Four such sources a month is about 1,284 credits — comfortably inside Creator's 2,500-credit allowance, leaving headroom for regeneration and experimentation. In dollar terms that is roughly $25 of the $49 plan consumed by a full month of fan-out, or about $0.18-0.25 per finished post.
The avatar short is the line that moves the budget. A single avatar short at 106 credits costs more than 35 text posts combined, and an AI faceless short at 214 credits costs more than an entire source's text-and-image spread. This is why the bucket allocation is an economic decision, not just a strategic one: a creator who leans on clipped shorts (14 credits) instead of avatar shorts (106 credits) for the same Video bucket stretches the same plan three-to-four times further. The methodology rewards using the cheapest output type that achieves the goal — clip when you have footage, generate only when you must.
The tier choice follows directly from monthly source volume. Creator ($49/mo, 2,500 credits) covers roughly 4-7 reach-preset sources a month or a larger number of text-and-image-heavy sources. Pro ($299/mo, 18,000 credits) is the pick once monthly output crosses roughly 120 finished pieces or once avatar/AI shorts become a regular line, because the per-credit price drops and the allowance stops being the constraint. The Founding tier ($39/mo, bring-your-own-key) routes generation through your own model API keys, which removes the credit ceiling entirely for operators who already pay for an LLM and video provider — see [pricing](/pricing) for the current tier breakdown.
Credits are the visible cost; labor is the cost that actually decides whether the methodology is worth running. The three tiers below — fully manual, AI-assisted with review, and fully autonomous after the autopilot ramp — describe the same 100-140-post month produced three different ways, and the gap between them is almost entirely labor.
Producing 25-35 native pieces from one source by hand takes 8-12 hours: transcribing, pulling clips, reframing and captioning each short, designing each carousel in Canva or Figma, writing each text post natively per platform, drafting the blog, writing the newsletter, and scheduling everything. Across four sources that is 32-48 hours a month of skilled labor. Add $200-400 of tool subscriptions (editor, design, scheduler) and, at a blended $50/hour labor cost, the all-in monthly cost lands at $1,800-2,800. Cost per post: roughly $20-30. This is the cost most teams are silently paying when they "do content in-house."
With Kompozy generating the full fan-out and a human reviewing before publish, per-source time falls to 1.5-2 hours — almost all of it review and the occasional caption fix, not creation. Four sources a month is 6-8 hours of operator time plus the $49 Creator plan, which replaces the stack of 5-7 separate tools. At the same blended labor rate the all-in monthly cost is roughly $349-449, or $3-5 per post. The jump from Tier 1 to Tier 2 is where the entire ROI of the methodology lives: an 80-85% labor collapse with no loss of output volume, provided the Persona Brief is dialed.
Once autopilot is trusted — meaning the Persona Brief has stabilized and the quality gates are catching off-brand outputs before they ship — the human role shrinks to a 30-minute weekly spot-check, about 2 hours a month. The plan cost is unchanged at $49. All-in monthly cost is roughly $149, or $1.00-1.50 per post. The step from Tier 2 to Tier 3 is a control trade-off more than a cost one: the dollar savings are modest next to the manual-to-assisted jump, and the real question is whether you are comfortable with outputs shipping without per-post approval. The autopilot mechanics and the four gates that make it safe are covered in the [autonomous cluster](/autonomous/autopilot-explained).
| Tier | Operator hours / mo | Tool cost / mo | All-in / mo | Cost per post |
|---|---|---|---|---|
| Fully manual | 32-48 | $200-400 | $1,800-2,800 | $20-30 |
| AI-assisted + review | 6-8 | $49 | $349-449 | $3-5 |
| Fully autonomous | ~2 | $49 | ~$149 | $1.00-1.50 |
The cost-per-acquisition view makes the tiers concrete for a B2B operator targeting a $50 customer acquisition cost. At 100 posts a month, roughly 0.5% converting to a trial and 10% of trials converting to paid, each post is worth about 0.05 customers. At the manual $25-per-post cost that is a $500 CAC — worse than paid acquisition, which is why hand-cranked content rarely pencils out. At the AI-assisted $3-5 cost it is a $60-100 CAC, competitive with paid. At the autonomous $1-1.50 cost it is a $20-30 CAC, cheaper than paid in most categories. The autonomy threshold is the point at which owned content becomes the lowest-cost acquisition channel a company has.
The abstract math is unconvincing without the operating rhythm, so here is a concrete month for a creator on the AI-assisted tier with one source recorded each Monday. The point of the sequence is that net-new creation happens once a week and everything else is review and scheduling against the fan-out the engine has already produced.
Week one, Monday: record the source — a 20-minute long-form or a 45-minute podcast. This is the only net-new creation event of the week. Tuesday: the source ingests, Kompozy fans it into the full bucket spread overnight, and the operator spends 90 minutes reviewing — approving the strong outputs, fixing captions the ASR mis-heard (brand names and jargon are the usual offenders), and discarding the two or three pieces that did not land. Wednesday through Sunday: the approved 25-35 pieces release on a staggered, platform-native cadence — the scheduler spaces them so the operator is not blasting everything in 24 hours and cannibalizing reach.
Weeks two through four repeat with a new source each Monday, and here is where the leverage compounds: the Persona Brief, platform connections, and scheduler rules are already configured, so the per-week setup cost is zero from week two onward. By month's end, four Monday recording sessions and roughly 6-8 hours of cumulative review have produced 100-140 platform-native pieces across every surface the audience uses. The creator never sat down to "write a tweet" or "make a carousel" as a separate task — every piece traces back to one of four recordings. That is the labor trap broken in practice, not in theory.
Not every source produces the same fan-out yield, and choosing the wrong one is the most common reason a single-source month underperforms. The highest-yield sources share three traits: they are long (more raw material to cut from), they are idea-dense (each minute contains a distinct claim, story, or framework rather than filler), and they are spoken or argued rather than read aloud. A 45-minute podcast where the host makes ten sharp points fans into far more usable output than a 45-minute screen-share walkthrough where the value is locked in the visuals and the audio is mostly "click here, now click there."
Ranked by realistic yield: a long-form interview or solo podcast sits at the top, because the conversational format naturally surfaces hooks and the length gives the clipper room to find them. A webinar or recorded talk is close behind, with the bonus of a built-in slide deck that converts straight to carousel frames. A written long-form (a flagship blog post or a detailed customer email) fans well into text and newsletter buckets but yields fewer video pieces without a talking-head recording to draw from. The weakest sources are short social posts and visually-dependent tutorials — the first lacks raw material, the second hides its value in pixels the text pipeline cannot read. The practical rule: if you can only record one thing a week, make it a long, idea-dense, spoken source, and let the rest of the month derive from it.
The methodology is not universal, and the honest failure conditions matter as much as the success case. Four conditions break the economics, and each one is detectable before you commit a month to it.
The pattern across all four conditions is the same: the methodology is a multiplier, and a multiplier applied to a weak input produces a weak result at scale. It rewards operators with consistent, dense sources, a real addressable audience, and a dialed Persona Brief — and it punishes shortcuts on any of those by quietly returning per-post costs to manual levels. Diagnosed honestly before committing, those four conditions tell you in advance whether the math will work for your specific situation.
Kompozy is built around exactly this five-bucket fan-out: it ingests a source (RSS feed, uploaded file, pasted URL, or recorded input), runs it against the workspace Persona Brief, and generates the bucket spread — clipped and avatar shorts in Video, quote cards and carousels in Image, native posts and threads in Text, a long-form post in Blog, and an issue in Newsletter — then schedules the lot across the connected platforms at native cadences. The bucket allocation is configurable per source, which is how the four goal presets above are implemented in practice. The methodology and the product are the same shape because the product was designed around the methodology.
For the math above to be checkable: a default reach-preset source runs roughly 320 credits, four sources a month roughly 1,280 credits, comfortably inside Creator's 2,500-credit allowance at $49/mo. Heavier video weighting (regular avatar or AI shorts) pushes toward Pro ($299/mo, 18,000 credits), where the per-credit cost drops and the allowance stops being the binding constraint. Bring-your-own-key Founding ($39/mo) removes the credit ceiling for operators already paying for their own model APIs. The full tier comparison and the per-output credit table are on the [pricing page](/pricing); the end-to-end fan-out workflow is in the [podcast-to-social methodology](/repurpose/podcast-to-social) and the broader [content-repurposing hub](/repurpose).
The methodology is not the right fit for every operator — the four break conditions above are real and worth diagnosing honestly before committing. But for a creator or company with consistent dense sources, a genuine addressable audience, and the discipline to build one Persona Brief, the single-source fan-out is the difference between content as a labor exercise that caps at your available hours and content as a leverage exercise that caps at your source quality. The number that matters is not 140 posts a month — it is that the same four recordings, sliced natively across five buckets, cover every surface your audience uses for roughly $0.20 per finished post.
25-35 platform-native pieces from one substantive weekly source (a 45-60 minute podcast or a 15-25 minute long-form video), spread across Video, Image, Text, Blog, and Newsletter. Four sources a month produce 100-140. Thin or single-topic sources land at the bottom of the range or below it, because the multiplication can only reformat substance that already exists in the source — density of distinct ideas, not runtime, is what drives the count.
A default reach-preset source runs roughly 320 Kompozy credits (about 7 clipped shorts, 1 avatar short, 6 image cards, 18 text posts, 1 blog, 1 newsletter). Four such sources is about 1,280 credits a month, comfortably inside the Creator tier's 2,500-credit allowance at $49/mo — roughly $25 of the plan consumed, or about $0.18-0.25 per finished post. Heavy avatar or AI-short usage raises that sharply and pushes toward the Pro tier.
Labor is the dominant cost, and AI collapses it without reducing output volume once the Persona Brief is dialed. Fully manual runs $20-30 per post (32-48 operator hours a month). AI-assisted with review runs $3-5 per post (6-8 hours). Fully autonomous runs $1.00-1.50 per post (about 2 hours). The decisive jump is manual to AI-assisted — an 80-85% labor collapse; autonomous adds modest dollar savings and mainly trades per-post approval for time.
One source still produces 25-35 useful outputs, but the fixed setup cost — the Persona Brief, scheduler config, and platform connections — is the same whether you feed it one source or four, so the per-piece overhead is higher and the leverage thins. The economics improve sharply at two or more sources a month because the setup amortizes across more output. Below two sources a month, a lighter-weight approach is often simpler.
Close to linearly on output, better than linearly on effort. Four sources produce 100-140 pieces; eight produce 200-280. But the Persona Brief, platform connections, and scheduler rules are written once and reused, so per-source effort falls as source count rises — the first source carries the full setup tax and the fourth is nearly free. The only thing that scales with source count is per-source review time.
Yes — the bucket allocation is configurable per source while the Persona Brief stays identical. Four presets cover most operators: maximum reach (heavy Video and Text, ~140/mo), SEO and search (heavy Blog and Newsletter, ~88/mo, higher value per piece), founder authority (heavy LinkedIn and X threads, ~112/mo), and paid-ad creative (heavy Video and Image, ~88/mo, all ad-ready). Choosing a preset is really choosing how finely to slice a fixed amount of source substance.
For a single workspace and audience, roughly 300 posts a month before audience fatigue sets in — beyond that, posting frequency outpaces what any one audience will absorb and engagement per post declines. Past that ceiling the right architecture is multiple workspaces, each with its own Persona Brief and audience, rather than forcing more volume through one. Volume is a means to surface area, not an end; over-posting a fixed audience is a net negative.
You cannot skip it without breaking the economics. The Persona Brief is the input that lets the engine apply your voice to all 25-35 outputs automatically — without it, every piece averages to the generic LLM register and needs heavy human editing, which pushes per-post review time back toward the manual tier and erases the cost advantage. It is a 30-90 minute one-time setup that amortizes across every piece you ever produce; treat it as the load-bearing fixed cost of the whole methodology, not optional polish.