Juma is the content repurposing tool that turns one blog post, webinar, or case study into publish-ready posts for LinkedIn, X, and email.
Paste a blog post, drop in a transcript, or share a URL. Juma reads the source material and builds a full content repurposing set: LinkedIn posts in multiple formats, X threads with platform-native hooks, and an email newsletter section. Each piece is written for how people actually read on that platform, not just cut down from the original.
The first draft carries the voice of the source material. That works for some platforms and needs adjustment for others. LinkedIn audiences respond to direct questions, X audiences respond to sharper, shorter phrasing, and email has its own register.
Use this step to shift the tone on one platform without touching the rest. Describe the change in plain language:
Paste a post that represents the right voice and Juma will match it. The adjusted posts replace the original draft for that platform only.
A strong content set only works if the team knows when to publish each piece. Posting everything at once dilutes reach and competes with itself. This step builds a two-week schedule that spaces posts strategically across all platforms.
The schedule accounts for:
The output is a clean table the team can copy into a content management tool or share with a client for sign-off.
The original set covers LinkedIn, X, and email. If the client uses Instagram, YouTube, or another platform with distinct format conventions, use this step to extend the set without starting over.
The Flow uses the same source content and brand voice from the original session. Describe the new platform and the formats that matter:
The existing set stays untouched. The new platform content is returned as a separate block.
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.
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:
Content repurposing with Juma saves 3 to 5 hours per piece compared to manual adaptation. Most teams spend that time rewriting the same ideas in different tones and adjusting formatting per platform. With this Flow, a full repurposing set for LinkedIn, X, and email comes back in one session, ready to review.
The time saving compounds across a content calendar. A team that repurposes one piece per week saves 10 to 15 hours per month without reducing the volume of content they publish. Most teams spend 20 to 30 minutes reviewing and finalizing the output before it goes out.
Setting up a Juma project with brand context stored in place reduces that review time further. The first draft gets closer to publish-ready with each session because Juma is working from stored brand rules rather than instructions re-typed into every prompt.
A content repurposing set includes platform-native posts for every channel in the brief. For LinkedIn: a long-form text post, a carousel outline, and a poll or question post. For X: a thread with a scroll-stopping hook and self-contained follow-up tweets. For email: a drop-in newsletter block. Visual briefs are included for any post that needs a graphic.
Each format is built for how people read on that platform, not adapted from the original. LinkedIn posts use bold opening lines and paragraph breaks for scanning. X threads open with a hook that works in isolation. Email sections match the length and structure of a mid-newsletter entry, ready to paste in without reformatting.
For any post that would perform better with a visual, the brief describes the subject, composition, and text overlay so a designer or image generation tool has clear direction.
Blog posts, webinar transcripts, case studies, and long-form articles all produce strong repurposing sets. The key factor is specificity: content with named examples, concrete data points, or direct quotes gives Juma material that produces distinctive posts. Paste the full content rather than a summary to get the best output.
Summaries strip out the details that make each platform post stand out. A case study that names the client, describes the problem, and shares a specific result will repurpose into stronger LinkedIn posts than a general explainer with the same word count.
For webinars, paste the full transcript or the key sections rather than notes. For URLs, Juma reads the full page directly. This works equally well when repurposing content for social media as it does for email: the same source produces a full cross-channel set. Any content with a clear argument, a narrative, or specific recommendations is a strong candidate. Content that is primarily a list of definitions or a product overview will produce thinner output and may need more guidance in the prompt.
AI content repurposing adapts source material to each platform's specific reading conventions rather than reformatting the same text. LinkedIn posts use bold hooks and deliberate line breaks for people scanning quickly. X threads open with a standalone hook tweet, with each follow-up carrying one self-contained idea. Email sections are structured as drop-in newsletter blocks with a brief intro, core point, and CTA.
The distinction matters because repurposing is not reformatting. A LinkedIn post that reads like a shortened blog excerpt underperforms because it ignores how people consume content there. The same content on X needs a different structure entirely: a hook tweet that earns the click, followed by self-contained tweets that add one idea each.
Juma applies platform conventions by default. The result is output that reads like it was written for each platform because it was, not content the team cut down and reposted.
Teams build a repeatable weekly workflow by storing brand rules in a Juma project once. The structure stays the same each session: share new content, confirm the platforms, review and publish. With a Brand Voice Guide and Platform Playbook in the project, the first draft comes back in the right voice and format without additional prompting.
For agency teams managing multiple clients, a separate project per client keeps brand rules isolated. One client's voice, platform preferences, and post examples never affect another's output. New team members can run the Flow without a client briefing because the project context handles it.
Teams that use this as a standing content repurposing tool report that review cycles shorten over time. The more sessions a project accumulates, the tighter the first draft. A team repurposing weekly that saves 30 minutes per session on review recovers more than 26 hours per year on a one-time project setup.
