Turn one blog post into five channels of content.

Publish one long-form post per week. Builder’s content-distribution agent automatically repurposes it into a LinkedIn article, three X threads, a short form newsletter and a Slack community post: each rewritten for the platform’s tone and scheduled at peak engagement times.

Run Builder
AuthorMariete
AgentBuilder
Runtime~ 6 minutes
IndustryMarketing
  1. 1

    Describe the task

    Builder can take one long-form post and turn it into a full week of channel-native content: a LinkedIn article, a set of X threads, a short newsletter and a community post, each rewritten in the platform’s voice rather than copy-pasted. One writing session becomes five scheduled pieces.

    The more you tell Builder about your voice, your channels and your best times, the less editing you do after. Give it the source post, a voice note, and the channels you actually publish to, and it will match tone per platform instead of flattening everything into the same paragraph.

    Repurpose this week’s post (draft-post.md) into 5 channels: - A LinkedIn article: reframed around one sharp takeaway, first-person, ends with a soft question - Three X threads: each a different angle from the post, hook-first, 5-8 posts each - A short newsletter section: ~200 words, conversational, one link back to the full post - A Slack community post: casual, no marketing voice, invites discussion Match my voice from voice-guide.md. Don’t reuse the same sentences across channels. Schedule each at its channel’s peak window and list the times you picked.

  2. 2

    Give Builder context

    Point the run at the finished post and a short voice guide, then tell Builder which channels are in play. It reads the post once and rewrites per surface, so the LinkedIn version reads like LinkedIn and the Slack version reads like a person, not a press release.

    The voice guide does the heavy lifting. A few real examples of how you write, phrases you use, ones you never use, sentence rhythm, produce far more on-brand output than a one-line "professional but friendly."

    Required context
    The source long-form post (Markdown, doc, or a published URL)
    The list of channels to repurpose into, and roughly who each audience is
    Optional context
    A voice guide with real examples, so rewrites sound like you and not like a template
    Per-channel peak-time preferences, if you already know when each audience engages
    A scheduler connector (Buffer, Typefully, or native), so pieces queue automatically
    draft-post.mdvoice-guide.mdBuffer (optional)
  3. 3

    What Builder creates

    Builder produces five ready-to-review pieces, each written for its platform, plus the schedule it recommends. You get channel-native drafts you can approve as-is or tweak, with the source’s core idea preserved but the phrasing genuinely different across every surface.

    From Builder: Repurposed draft-post.md into 5 channel-native pieces with a recommended schedule.

    5Channel-native pieces
    3Distinct X thread angles
    0Reused sentences across channels
    Ready to schedule5 pieces
    ChannelFormatAngleSuggested time
    LinkedIn~900-word articleThe one counter-intuitive takeawayTue 8:15am
    X (thread 1)7-post threadThe mistake most teams makeWed 11:30am
    Newsletter~200-word sectionA teaser with a link to the full postThu 9:00am
    Flagged for a look2 pieces
    ChannelFormatWhy flagged
    X (thread 3)5-post threadAngle overlaps thread 1, may want to cut or merge
    Slack communityCasual postReads slightly promotional, worth softening before posting

    "Thread 3 overlaps thread 1 pretty closely, they’re both about the same mistake. Want me to merge them into one stronger thread, or spin thread 3 toward a different angle from the post so all three stay distinct?"

  4. 4

    Follow-up prompts

    Queue everything in Buffer

    With Buffer connected, Builder drops each approved piece into the right channel’s queue at the time it recommended, so the whole week publishes itself once you sign off.

    Schedule all five pieces in Buffer at the times you recommended. Put the LinkedIn article and the newsletter in the "Owned" queue and the three threads in the "X" queue.

    Add two more channels

    When a post has legs, Builder can extend the same source into formats you didn’t ask for the first time, a short video script, an Instagram carousel outline, without rewriting from scratch.

    From the same source post, also produce a 60-second video script and a 6-slide Instagram carousel outline, in the same voice, no reused lines from the other channels.

    Make it a weekly repurposing runbook

    Once the channel mix and voice are right, save it as a Builder saved runbook so every new long-form post gets the same five-channel treatment on publish.

    Save this as a runbook called "weekly-repurpose" and run it automatically whenever a new post lands in /content/published, using voice-guide.md and the same 5 channels.

  5. 5

    Tips and troubleshooting

    A voice guide beats a voice adjective

    "Friendly and professional" is what every generic post already sounds like. Three real snippets of your writing, plus a short "never say this" list, tells Builder far more and cuts your editing pass to almost nothing.

    Give each X thread a different door in

    The fastest way to sound repetitive is three threads on the same angle. Tell Builder to pull a distinct takeaway per thread, one mistake, one framework, one result, so they read as separate ideas, not reruns.

    Approve before you automate

    Run it live for a couple of weeks and edit what needs editing. Once the drafts consistently land without changes, that’s the signal to connect the scheduler and let it queue automatically.

  6. Ready to try it yourself?

    Write the post once, hand Builder your voice guide and channel list, and get five platform-native pieces scheduled at the right times, from a single publishing session.

    Run Builder