·3 min read·By Andrea Borghi

Build a content repurposing AI agent in a weekend

Dogfooding, not a demo — every post here was generated, approved from an email, and published by ContentFlows itself. See the proof

Build a content repurposing AI agent in a weekend

Most marketing teams know the pain: one good webinar becomes a YouTube cut, a LinkedIn carousel, three X threads, a newsletter teaser, and a blog post — and by Friday nobody can remember which version said what. The fix isn't more hands. It's a small content repurposing agent that watches your long-form source, classifies each segment, and pushes finished drafts to the channels that fit. You can stand one up in a weekend, and you don't need a machine learning team to do it.

Start by picking one source you already produce reliably — a weekly podcast, a recorded customer call, a long-form blog draft — and one destination you want to feed first, like LinkedIn posts or a newsletter. Resisting the urge to automate everything on day one is the single biggest predictor of whether the project ships. A focused agent that turns one podcast into three LinkedIn posts beats a sprawling pipeline that produces nothing.

Next, build the segmentation step. Audio and video work best when you transcribe first, then split the transcript on natural pauses and topic shifts. For text, chunk by heading or by a simple sliding window of 500 to 800 tokens. The goal is to give downstream prompts a self-contained idea, not a paragraph pulled out of context. Without clean segmentation, even the best model hallucinates and your brand voice drifts within the first month.

Then comes the repurposing prompt, which is where most weekend builds quietly fail. Don't write one giant instruction that asks for a LinkedIn post, a tweet thread, and a newsletter at the same time. Write one prompt per output type, each grounded in a few short examples of your real past content. Two or three examples per format is usually enough to lock in tone, length, and structure. Keep the system prompt version-controlled and treat changes to it like product changes — diffed, reviewed, and revertible.

Before you call it done, wire in two unglamorous safeguards. First, a human approval queue. Even a confident model will occasionally invent a quote, misattribute a stat, or pick the wrong hook. Every output should land in a draft state until a person signs off. Second, a feedback loop that records which drafts get published, edited, or deleted. After a few weeks you'll have a labelled set you can use to tighten prompts, prune weak formats, and retire the agent's worst outputs.

Ship the smallest version that runs end to end, then iterate against real usage data. Within a month you'll have a pipeline that takes a single piece of source content and turns it into a week's worth of channel-ready drafts — with a human in the loop where it matters. If you want a head start, our content automation platform includes a starter template for exactly this workflow, with the segmentation, prompt library, and approval queue already wired together so you can go from signup to first published draft before the weekend is over.

Written by Andrea Borghi, Founder, ContentFlows.