Overview
Repurpose top-performing social posts when last week's winners deserve a second life, not a lazy copy-paste encore. This playbook reviews recent performance, identifies the posts that worked for a clear reason, and rewrites them into fresh LinkedIn and Instagram drafts with new hooks, formats, CTAs, and visual direction where useful.
It is built for social marketers, content leads, and founders who need a practical weekly batch before the next calendar locks. The output is a social post repurposing brief: source posts, performance signal, winning element, refreshed drafts, posting priority, approval notes, and any missing assets or proof.
Use it after the prior week's social results are available, when a strong post still has more to give, or when the calendar needs ideas that are already backed by audience behavior.
Why you should refresh winners without sounding recycled
The best social posts usually contain one durable thing: a sharp insight, useful proof, a relatable pain point, a strong format, or a comment-friendly question. The problem is that repeating the same wording makes the second version feel like leftovers wearing a new hat.
This playbook keeps the signal and changes the packaging. LinkedIn drafts can lean into operator lessons, practical frameworks, proof-led storytelling, or discussion prompts. Instagram drafts can become captions, carousel premises, Reel prompts, or static visual directions when the source post supports that shape.
That channel fit matters. LinkedIn's content guidance emphasizes useful, relevant, authentic posts with a strong opening, while Meta's Instagram ranking documentation shows that signals like likes, comments, saves, and profile taps help determine what appears in Feed: LinkedIn Sponsored Content best practices and Meta Instagram Feed ranking.
Juno helps by making the refresh decision less vibes-based. It looks at what actually earned attention, separates the repeatable idea from the surface execution, and gives your team drafts that feel native to each platform instead of cloned across channels.
Step-by-step
- 1Confirm the brand, active social profiles, channels in scope, review window, campaign priorities, audience segments, brand voice rules, approval needs, and the performance signals that define a top post.
- 2Review the recent social history and choose a small set of source posts with a real reason to refresh, such as strong saves, shares, comments, clicks, reach, qualified replies, or a clear audience pain point.
- 3Drop posts that only performed because of a giveaway, hiring announcement, one-off news spike, or non-repeatable visual unless the team explicitly wants that moment revived.
- 4Identify why each selected post worked by capturing the original hook, audience, topic, format, proof, CTA, and the durable element worth preserving.
- 5Rewrite each source post into 1 or 2 fresh drafts per channel in scope, adapting the angle, structure, CTA, and format for LinkedIn and Instagram rather than making minor wording swaps.
- 6Package the batch as a review-ready brief with source context, performance evidence, refreshed drafts, recommended format, visual direction, posting priority, and notes for links, claims, assets, product checks, or legal review.
Frequently asked questions
Does this rewrite every recent post?
No. It focuses on 3 to 6 source posts in a normal weekly run. Weak, accidental, or non-repeatable posts are skipped so the batch stays useful.
What if I do not have performance data?
Juno asks once for the best available source. If true ranking is unavailable, it can use recent visible posts and label the batch lower confidence so the team knows what was inferred.
Will the drafts be different for LinkedIn and Instagram?
Yes. LinkedIn drafts usually emphasize insight, lessons, frameworks, proof, or discussion. Instagram drafts translate the idea into captions, carousel concepts, Reel prompts, or visual directions when that format makes sense.
Does Juno schedule or publish the posts?
No. This playbook creates drafts and review notes. Scheduling or publishing only happens if you ask for that as a separate next step.
