Pull the spine first: one argument, three reshapes, never cross-post
LinkedIn wants the lesson, X wants the build, IG wants the proof
Each platform gets a different hook from the same source paragraph
Schedule the whole week in one 40-minute block, then walk away
One blog post turned into a LinkedIn post, an X thread, and an Instagram carousel pulled 4,100 views across three feeds last week. I wrote the article once. The three social pieces took 40 minutes total. Here is the exact flow I use, and why cross-posting the same text everywhere fails.
Stop Cross-Posting, Start Reshaping
The mistake almost everyone makes is copy-paste. They write a blog post, grab the intro, drop it on LinkedIn, paste the same lines into X, and slap a screenshot on Instagram. Then they wonder why each one gets 12 likes.
The reason is simple. Each platform rewards a different shape of the same idea. LinkedIn readers scroll for a takeaway they can repeat in a meeting. X readers want to watch you think out loud, step by step. Instagram readers want a visual they can swipe through in eight seconds without reading much at all. Same argument, three completely different containers.
So the first move is not writing. It is extraction. I open the blog post and find the spine, which is the single sentence that the whole article is trying to prove. Not the topic, the claim. If the article is "SEO for Indie Creators," the topic is SEO but the spine might be "ranking pages beat viral posts because they earn for two years." That spine is the only thing all three platform pieces share.
I write that spine at the top of a blank note. Then I list the three or four supporting beats underneath it, the ones the article uses to make the case. For a 1,800 word post that is usually four beats. These beats become my raw material. I do not reuse sentences. I reuse the logic.
This is the part that separates a repurpose flow from a spam flow. When you reshape instead of copy, the LinkedIn version and the X version can both link back to the full article without feeling redundant, because neither one is the article. They are two arguments for reading it.
I learned this the hard way after months of cross-posting identical blocks and watching engagement flatline. The fix was not better writing. It was accepting that one piece of content is actually a source file, not a finished product. If you want the video version of this same idea, How to Repurpose One Video into 10 Pieces of Content with AI covers the equivalent flow for footage instead of text. Different inputs, same principle: extract the spine, reshape per channel.
The LinkedIn Version: Lead With the Lesson
LinkedIn rewards the takeaway up front. Nobody on LinkedIn is reading to be surprised at the end. They are scanning for a line worth saving.
So my LinkedIn version always opens with the spine, rewritten as a flat statement. From the SEO example: "Ranking pages earn for two years. Viral posts earn for two days. I keep choosing the slower one." That is line one. No throat-clearing, no "I've been thinking a lot about."
Then I structure the body as a short story or a list of three. LinkedIn formatting matters more than the words. One sentence per line. White space between every thought. The feed truncates around three lines, so the first three lines have to earn the "see more" click. I rewrite those three lines four or five times before I move on, because they do 80 percent of the work.
The middle is two of my four beats from the spine note, written as lessons I learned rather than facts I know. "I shipped 30 viral attempts before I understood this" beats "viral content is unreliable." Specifics and numbers. I pull real numbers from the article wherever I can. A LinkedIn post with one concrete figure outperforms a post full of advice.
The close is a single question. Not "what do you think," which gets nothing, but a specific fork. "Are you building for next week or next year?" That gives people something to answer in one word.
I drop the blog link in the first comment, not the post body, because LinkedIn suppresses posts with outbound links. The comment trick keeps reach while still routing traffic. I have watched the same post get triple the views when the link sits in comments instead of the caption.
The whole LinkedIn version runs maybe 180 words. It took longer to write than the X thread because LinkedIn is unforgiving about flabby lines. Every word has to defend its spot. If you want the reasoning behind shipping in batches instead of daily, Why I Ship Blog Articles in Clusters of 3 explains the cadence I build all of this around.
The X Thread: Show the Build, Not the Bow
X is the opposite of LinkedIn. LinkedIn wants the conclusion. X wants the process, the receipts, the "here is exactly how" walkthrough that reads like you are figuring it out in real time.
So my X thread takes the same spine but reorders it. The hook tweet is a result or a tension, never the lesson. "I posted the same blog to 3 platforms. One got 4,100 views. The other two got 30 combined. Here's what I changed." That sets up a thread people stay for because they want the resolution.
Then each beat from my spine note becomes one tweet. I keep tweets to two or three short lines. The thread is the only format where I can be granular, so I add the steps the blog post had to skip for length. Numbers, tool names, the exact order I did things. X readers reward specificity harder than any other platform. A vague thread dies in the first two tweets.
I cap most threads at six or seven tweets. Past that, the drop-off gets brutal. The last tweet always restates the spine as a one-liner and links the full article, because by then the reader trusts me enough to click. On X the link can go in the final tweet without much penalty, unlike LinkedIn.
The reshaping work here is turning declarative blog prose into conversational fragments. The blog says "I tested four scheduling tools." The thread says "Tested 4 schedulers. Three were bloated. One did the one thing I needed." Shorter, punchier, more opinionated. X tolerates and rewards a sharper voice than LinkedIn does.
For scheduling all of this, I run the queue through Buffer so the thread, the LinkedIn post, and the carousel all go out on staggered days from one dashboard. I do not post live. Posting live means I am at the mercy of whatever mood I am in. Queuing means the week ships whether I feel like it or not. My full automation stack lives in I Automated 90 Percent of My Content Pipeline With 4 Tools if you want the rest of the rig.
The Instagram Carousel: Make the Argument Visual
Instagram is the platform where the words almost stop mattering. A carousel lives or dies on slide one, the cover, which has to stop the swipe with a single bold line. Everything after that is momentum.
I take the spine and turn it into a six-to-eight slide arc. Slide one is the hook as a big statement: "1 blog post = 3 platforms = 0 extra writing." Slides two through six are one beat each, one idea per slide, almost no body text. Maybe a headline and one supporting line. The carousel is a slideshow, not an essay, and people swipe at speed.
The design has to be consistent. Same font, same two colors, same layout grid on every slide so it reads as one set. I build the slide backgrounds and any supporting visuals in Magnific when I need clean upscaled imagery that holds up at full resolution in the feed. Blurry slides get skipped. Sharp slides get saved, and saves are what Instagram actually rewards.
The last slide is the call to action, but soft. "Full breakdown on the blog, link in bio." Instagram punishes outbound links worse than any platform, so the carousel is a top-of-funnel grab. I am not expecting clicks. I am expecting saves and a couple of follows from people who liked the format.
The reshape here is the hardest, because text-heavy blog logic has to compress into eight visual beats. I cut ruthlessly. If a beat needs three sentences to land, it does not belong in a carousel, it belongs in the X thread. The carousel only carries ideas that survive being reduced to one line plus a graphic.
The caption gets one job: repeat the cover hook and ask for the save. "Save this for your next repurpose session." That single instruction lifts saves more than any clever caption. The visual already did the persuading. The caption just tells people what to do with it. The full deck takes about 15 minutes once the spine note exists, because I am arranging, not inventing.
Bottom Line
One blog post is not one piece of content. It is a source file. Pull the spine, the single claim the whole article proves, then reshape it three ways instead of copying it three times. LinkedIn gets the lesson up front. X gets the step-by-step build. Instagram gets the visual argument in eight swipes.
The whole flow is 40 minutes once the article exists, and most of that is the extraction note that all three pieces share. Write the spine and the four beats once, and the reshaping is fast because you are arranging, not creating.
Schedule the week in one block so it ships regardless of your mood. Then move on to the next article. This is the repeatable system I run every cluster, and it is one slice of the larger operating manual in the Claude Blueprint if you want to see how the writing, the repurposing, and the scheduling fit into one solo pipeline. Start with your next post. Find the spine before you write a single social caption.
This article contains affiliate links. If you sign up through them, I may earn a small commission at no extra cost to you. (Ad)
Top comments (0)