# Turn one piece of work into a month of posts A repeatable pass from a single long-form piece to a scheduled calendar, without a content team. **Time:** 20 minutes **What you'll have when you're done:** A month of scheduled social posts drawn from one piece of source content, each one built around a distinct claim instead of a paraphrase of the whole thing. **Before you start:** - Any AI chat tool you're allowed to use - One finished long-form piece: a guide, a webinar recording or transcript, a case study, a long report - Wherever you actually schedule posts, even if that's just a shared calendar ---The usual approach to "turn this into social posts" produces five posts that all say the same thing in slightly different words: a paraphrase of the whole piece, five times. That's not a month of content, it's one idea wearing five outfits, and anyone who sees more than one of them notices. A long-form piece worth writing usually contains several distinct, separable claims. The method here is pulling those out individually, so each post earns its own reason to exist instead of reintroducing the same one. --- ## Step 1: extract the claims, not a summary ``` Here is a long-form piece: [paste it, or a transcript if it's a webinar] List every distinct, standalone claim, statistic, quote, or insight in this piece that could stand on its own outside the full context. For each one, note what part of the piece it comes from. Don't summarize the piece as a whole. I need the individual pieces it's made of. ``` A 2,000-word guide usually yields ten to twenty of these. A webinar transcript often yields more, since spoken answers tend to contain complete thoughts that read fine detached from the surrounding conversation. --- ## Step 2: sort by audience and format, not just topic Not every claim fits every channel, and not every claim is worth a full post. Sort what came back from step 1 into three piles: **Standalone posts.** A claim strong enough to carry a post by itself, needs no other context from the source piece. **Needs setup.** A claim that only makes sense with a sentence of context first, still one post, just a slightly longer one. **Not worth its own post.** True and in the source, but too minor or too dependent on surrounding detail to stand alone. These can become a follow-up comment or a line in a roundup post instead of a full post of their own. --- ## Step 3: draft each post around its one claim ``` Claim: [paste one from your "standalone" or "needs setup" pile] Platform: [where this is going] Voice: [paste a couple of sentences from your existing published posts, so the tone actually matches, rather than describing the tone in the abstract] Write one post built entirely around this claim. Don't reintroduce the whole source piece, this claim is the point of this specific post. ``` One claim per prompt, the same discipline as elsewhere in this workflow. A batch request to "turn all of these into posts at once" tends to blur the claims back together into the paraphrase problem this method exists to avoid. --- ## Step 4: build the calendar around variety, not just volume Before scheduling, look at the full set of drafted posts together and check for repetition you couldn't see one at a time: two posts making almost the same point in different words, or every post using the same opening structure. Space out anything that repeats, and vary the opening line across posts scheduled in the same week. Then schedule, spacing posts so a stat-heavy one and a more conversational one alternate, rather than running five similar posts back to back. --- ## When it breaks **Step 1 returns claims that are really just section headers restated, not actual standalone facts.** That usually means the source piece itself is light on specific claims, more structure than substance. Worth knowing before the month of content gets built on it, not after posts start underperforming. **Two "standalone" claims turn out to depend on each other to make sense.** If a post doesn't land without the context of a claim you extracted separately, move it to "needs setup" and combine the two rather than forcing it to stand alone. **Every drafted post still sounds the same, even with different claims.** That's a voice-matching problem, not a claims problem. Feed it more of your actual published posts in step 3 rather than a description of your brand voice; matching actual sentences works better than matching an adjective list. **The source piece only really contains one strong claim.** Not every piece holds a month. Padding four weak posts around one good one produces a worse month than three good posts and an honest gap. Say so, and either find a second source piece or shorten the calendar. --- ## What to try next Keep the claims list from step 1 even after the month's posts are scheduled. The claims that got sorted into "not worth its own post" are often exactly the material a second, smaller piece, a follow-up post or a comment thread, gets built from later.

Next