New Feature: Content Repurposing Engine
Priority: 🟡 Pre-launch
Area: Content / Agents
Competitive Reference: Jasper (Content Pipelines → Adapt), Predis.ai (Resize & Repurpose), Copy.ai (Content Creation workflows)
Why This Matters
Every competitor offers content repurposing as a core feature. The idea: write a blog post once, then automatically generate 5–10 derivative assets from it. Leadmetrics generates blogs, social posts, and emails independently — but never derives one from another.
For a digital marketing agency managing 10+ tenants, repurposing a single long-form piece into platform-specific derivatives saves 3–5 hours per content piece.
What Leadmetrics Has Today
blog-writeragent generates blog posts from content briefssocial-post-writeragent generates social posts from activity contextemail-writeragent generates newsletter contentlanding-page-writeragent generates landing pages- Each agent runs independently — no agent reads another agent’s output as input
- RAG engine can ingest approved content, but no agent is prompted to “repurpose from existing content”
What Competitors Offer
| Platform | Feature | How It Works |
|---|---|---|
| Jasper | Content Pipelines → Adapt | Takes a blog post and auto-generates social posts, email subject lines, ad copy, meta descriptions — all on-brand |
| Predis.ai | Resize & Repurpose | One-click conversion: blog → carousel, blog → reel script, blog → LinkedIn post, blog → Twitter thread |
| Copy.ai | Content Creation Workflows | Automated workflow: input = blog URL, output = 10 social posts + 3 email subject lines + 2 ad headlines |
| Semrush | Content Repurposing | AI takes existing content and reformats for different channels and audiences |
Proposed Implementation
New Agent: content-repurposer
Input: Approved deliverable ID (blog post, report, etc.)
Output: Multiple derivative deliverables (social posts, email snippets, ad copy, thread, carousel script)
Repurposing Matrix
| Source | → Social Post | → Ad Copy | → Thread | → Carousel | → Landing Page | |
|---|---|---|---|---|---|---|
| Blog Post | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Report | ✅ | ✅ | ❌ | ✅ | ✅ | ❌ |
| Social Post | ❌ | ❌ | ✅ | ✅ | ❌ | ❌ |
| Newsletter | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ |
Workflow
- User approves a blog post → “Repurpose” button appears
- User selects target formats (checkboxes)
- System creates Activities for each derivative, linked to the source deliverable
content-repurposerworker runs, reading the approved content from the source- Each derivative goes through the normal review → approve → publish pipeline
Dashboard UI
- Add “Repurpose” action button on approved blog detail page
- Add “Repurpose” bulk action on deliverables list
- Show lineage: “Derived from Blog #123” on derivative posts
- New
sourceDeliverableIdcolumn onActivitymodel
Build Effort
| Step | Estimate |
|---|---|
Add sourceDeliverableId to Activity schema | Small |
Create content-repurposer worker | Medium |
| Add repurpose prompts per output format | Medium |
| Dashboard repurpose button + modal | Medium |
| Lineage display on derivative pages | Small |
Related
- Social Post Platform Publishing — derivatives need to actually publish
- CMS Publishing — blog derivatives may need CMS push
Future Enhancements
Bulk Repurposing (Post-Launch)
Allow users to repurpose multiple pieces of content at once:
Use Cases:
- “Repurpose all approved blogs from last month into social posts”
- “Convert all Q4 reports into email newsletters”
- “Transform approved content library into a social media content calendar”
Implementation:
- Add checkbox selection on deliverables list
- “Bulk Repurpose” action in dropdown
- Modal to select target formats (same as single repurpose)
- Queue all as separate jobs with shared batch ID
- Dashboard shows bulk progress tracker
- Single notification when entire batch completes
Priority: Post-launch (gather usage data first to see which paths are most used)