Turn one blog post, webinar, or case study into publish-ready posts for LinkedIn, X, and email with platform-specific formatting and visual briefs.
Share the source content and name the platforms that matter. The flow returns a full set of platform-ready posts: LinkedIn content in a mix of formats, X threads with hooks built for the feed, an email newsletter section, and visual briefs for posts that would work better with a graphic.
A repurposing set built with this flow covers three layers per platform. LinkedIn posts come in a mix of formats: a long-form text post for thought leadership, a carousel outline for visual storytelling, and a poll or question post for engagement. X threads open with hooks designed to stop the scroll, with each follow-up tweet self-contained enough to work if someone sees it in isolation. The email section is a drop-in block for an existing newsletter, not a standalone send. For any post that would land better with a visual, the set includes a brief describing the subject, composition, and text overlay.
Repurposing is not reformatting. A LinkedIn post that reads like a shortened blog excerpt underperforms because it ignores how people consume content on LinkedIn: scanning for bold hooks, expecting line breaks, responding to direct questions. The same content on X needs a different structure entirely, with a standalone hook tweet that earns the click to expand. Each platform has conventions that signal "this was written for here," and content that follows those conventions gets more reach than content the team just cut down and reposted.
The first draft covers the key points but the voice isn't quite right for one platform. Maybe the LinkedIn posts feel too corporate, or the X threads need a lighter touch. This refines the tone without starting over.
The LinkedIn posts need to feel more like a team lead sharing lessons learned, not a brand account broadcasting. Rewrite them with the same key points but in a warmer, conversational tone.
The content set is ready, but the team needs to know when to publish each piece. This creates a two-week schedule that spaces posts across platforms and suggests timing for each.
Create a two-week posting schedule for everything you just created. Space the posts so no single platform gets more than one piece per day, and suggest the best day and time for each post based on platform engagement patterns.
The original set covered LinkedIn, X, and email. This adds another platform using the same source content and voice, with formats tailored to the new channel.
Now adapt the strongest pieces for Instagram. Create 2-3 Instagram posts: a carousel with slide-by-slide copy, a Reels concept with a hook and script outline, and a single image post with caption. Include visual briefs for each.
Content repurposing is a weekly task for most teams: new source material, same platforms, same voice, same audience. A Juma project keeps the brand context and platform conventions in one place so every repurposing set comes out publish-ready without re-explaining the rules. If the client project already exists, add these items to it.
Brand Voice Guide
How the client sounds across platforms: tone, vocabulary, what to avoid. With this in the project, every repurposed post comes out in the right voice from the first draft. No rounds of tone corrections.
Audience Profile
Who the content reaches: roles, industries, pain points, and how technical or accessible the language should be. This shapes how the same blog post gets translated differently for a LinkedIn audience versus an email subscriber list.
Platform Playbook
Which platforms the client uses, at what cadence, and in what formats. LinkedIn gets text posts and carousels, X gets threads, email gets newsletter sections. The playbook also sets defaults for how many pieces per platform.
LinkedIn Post Examples
A few real posts that represent what good looks like for this brand on LinkedIn. These serve as structural references, so repurposed posts match the hook style, formatting, and tone the team has actually published.
X Thread Examples
Same idea, different platform. Threads have their own conventions: hook tweets, self-contained follow-ups, lighter CTAs. Examples keep the format tight.
Add a short description to each knowledge item in the project's info field so Juma knows what each file contains and when to use it. For example:
