Content Amplifier
The bottleneck isn't creation. It's distribution. You write once. Then you spend the rest of the week copying, pasting, reformatting, scheduling, and wondering which platform actually moved the needle.
The Job
When a founder or creator has produced content they believe in, help them get it in front of the right people across every channel that matters — without losing 8–12 hours a week to platform-switching, format adaptation, and analytics fragmentation.
| Trigger Event | Current Failure | Desired Progress |
|---|---|---|
| Content created | Stays in one place or gets manually copy-pasted | One create → many platforms, adapted per channel |
| Post ready to ship | Platform-switching fatigue (daily, high) | Single workflow, multi-platform dispatch |
| Format differs by channel | Per-post adaptation (medium effort) | Auto-adapt to platform norms |
| Need to schedule | Weekly scheduling overhead (medium) | Batch schedule, forget it |
| Want to learn what works | Analytics fragmented across 4+ dashboards (weekly, high) | Unified view, learnings fed back |
| Brand consistency | Content inconsistency across channels (ongoing, high) | One voice, many formats |
The job: "I need my content to reach people wherever they are, without me being everywhere."
The hidden objection: "What if the adapted version sounds wrong?" The system must preserve intent while fitting form.
Strategic Fit
CRM + Content = complete customer acquisition funnel.
| Funnel Stage | Content Amplifier | CRM |
|---|---|---|
| Attract | Content reaches the right audience | — |
| Engage | Multi-platform presence builds familiarity | — |
| Convert | — | Deals, pipeline, proposals |
| Retain | — | Contacts, activity, follow-up |
Content Amplifier owns Attract and Engage. Sales CRM owns Convert and Retain. Together they close the loop from awareness to revenue. Any venture doing B2B needs both.
Why Now
| Force | Evidence |
|---|---|
| Creator economy | 50M+ creators, most are solo or small teams |
| Platform fragmentation | 4+ platforms matter for B2B: LinkedIn, X, newsletters, blogs |
| AI-native opportunity | Format adaptation, scheduling, and analytics can be automated |
| Distribution gap | Dreamineering capabilities show Distribution at Level 1 (ad-hoc) — a critical gap |
The Flow
Content created
→ Adapted per platform (format, length, tone)
→ Scheduled (batch, optimal timing)
→ Distributed (LinkedIn, X, newsletter, etc.)
→ Analytics tracked (engagement, reach, conversion)
→ Learnings fed back (what works, what to double down on)
LinkedIn-first approach for B2B. The job is most acute for founders selling to other businesses. LinkedIn is the primary channel; other platforms extend reach.
Feature / Function / Outcome
Every row maps a feature to the function it performs and the outcome the user experiences. All items are Gap or Pending — this capability is in the backlog.
| # | Feature | Function | Outcome | State |
|---|---|---|---|---|
| 1 | Content ingestion | Accept draft from editor, notes, or paste | Single entry point for any content | Gap |
| 2 | Platform adapters | Transform content to fit each channel's norms | One create → many formats, no manual reformat | Gap |
| 3 | LinkedIn publisher | Publish to LinkedIn with optimal formatting | B2B primary channel covered | Gap |
| 4 | X (Twitter) publisher | Publish to X with thread/character adaptation | Second B2B channel | Gap |
| 5 | Newsletter integration | Push to Substack, Beehiiv, or similar | Email list growth | Gap |
| 6 | Scheduling engine | Batch schedule across platforms | Set and forget, no daily platform switching | Gap |
| 7 | Analytics aggregation | Pull engagement data from all channels | One dashboard, not four | Gap |
| 8 | Learning feedback loop | Surface what performed, suggest what to repeat | Content strategy improves over time | Gap |
| 9 | Consistency checker | Ensure voice and key messages align across adaptations | Brand coherence across channels | Gap |
| 10 | Source-to-distribution link | Trace which platform drove which outcome | Attribution, not guesswork | Gap |
Business Dev
| Layer | Decision | Initial Assumption | Evidence to Collect |
|---|---|---|---|
| ICP | Who buys first? | Solo founders and small teams doing B2B, already creating content, drowning in distribution mechanics | 10 interviews where distribution pain is named unprompted |
| Offer | What do we sell? | "Create once, distribute everywhere" — time back for creation | First post distributed to 2+ platforms within 7 days |
| Pricing | How do we charge? | Usage-based or seat-based, TBD | Willingness-to-pay interviews |
| Channel | How do we reach them? | Content about content — meta distribution | 5 qualified demos/month from content-led pipeline |
| Conversion | What proves value? | Content distributed to 2+ platforms from single create | Activation: multi-platform dispatch > 60% of creates |
| Retention | Why do they stay? | Weekly time saved compounds; analytics inform next content | Weekly active distribution, not just creation |
Existing Engineering Assets
Before building new, wire what's dormant. The agency lib already has two workcharts and an algorithm that serve this PRD.
| Asset | Location in Agency Lib | What It Does | Status |
|---|---|---|---|
| Marketing Strategy Workflow | libs/agency/src/lib/workcharts/marketing-strategy-workflow/ | Market analysis, channel recommendations, KPI definition, budget allocation | Built, not wired to any UI |
| Marketing Loyalty Workflow | libs/agency/src/lib/workcharts/marketing-loyalty-workflow/ | Point calculation, attribution splits, access tier progression | Built, not wired to any UI |
| SPCL Scoring Algorithm | libs/agency/src/lib/algorithms/content-strategy/spcl-scoring/ | Content quality scoring via calculateSPCL() | Built, not wired to any UI |
| LinkedIn Composer | apps/dreamineering/drmg-sales/ Settings > Marketing | LinkedIn post composer | Live, manual, no strategy workflow |
| Resend Integration | apps/dreamineering/drmg-sales/ | Email compose + webhook tracking | Live, no distribution workflow |
Wiring Jobs (CONNECT, don't CREATE)
| # | Wire This | To This | Job Served | Effort |
|---|---|---|---|---|
| 1 | SPCL Scoring algo | Content quality gate before publish | Feature #9 (Consistency checker) | 2 days |
| 2 | Marketing Strategy Workflow | Content Amplifier UI surface | Features #2, #6, #8 (Adapters, Scheduling, Learning) | 1 week |
| 3 | Marketing Loyalty Workflow | Engagement tracking surface | Feature #10 (Source-to-distribution link) | 2 days |
Principle: The Content Amplifier PRD was written as if starting from zero. Three of the ten features have dormant engineering already built. Wire those first.
Commissioning
| Component | Schema | API | UI | Tests | Status |
|---|---|---|---|---|---|
| Content ingestion | Pending | Pending | Pending | Pending | 0% |
| Platform adapters | Pending | Pending | Pending | Pending | 0% |
| LinkedIn publisher | Done | Done | Done | Pending | 50% |
| X publisher | Pending | Pending | Pending | Pending | 0% |
| Newsletter integration | Partial | Partial | Pending | Pending | 15% |
| Scheduling engine | Pending | Pending | Pending | Pending | 0% |
| Analytics aggregation | Pending | Pending | Pending | Pending | 0% |
| Learning feedback loop | Pending | Pending | Pending | Pending | 0% |
| Consistency checker (SPCL) | Done | Pending | Pending | Pending | 15% |
| Source-to-distribution link | Pending | Pending | Pending | Pending | 0% |
| Marketing Strategy WC | Done | Done | Pending | Pending | 30% |
| Marketing Loyalty WC | Done | Done | Pending | Pending | 30% |
Pre-existing: LinkedIn posting skill extracts posts from articles. Manual. No scheduling, no multi-platform, no analytics. Content Amplifier systematises what the skill does ad-hoc. LinkedIn composer and Resend integration are live in drmg-sales Settings > Marketing.
Risks + Kill Signal
| Risk | Mitigation |
|---|---|
| Adapted content loses nuance or sounds generic | Human review gate before publish; preserve key phrases and CTAs |
| Platform APIs change or restrict access | Abstract adapters; design for swap-out |
| Users create but never distribute | Activation metric: first multi-platform dispatch within 7 days |
| Analytics fragmentation just moves inside the tool | Start with 2–3 platforms; prove value before expanding |
| Scheduling creates a false sense of "done" | Learning loop must feed back; distribution without measurement is noise |
Kill signal: If content is created but never distributed to more than one platform, the tool is a fancy text editor. Multi-platform dispatch is the activation metric.
Mycelium Context
Capability: Content distribution primitive.
Currently growing in: Dreamineering — where the pain is acute (meta articles, LinkedIn, distribution gap at Level 1).
Any venture doing B2B needs multi-platform presence. Stackmates, Prettymint, Howzus, TouchForFun — all would benefit from a shared distribution layer. Build once in Dreamineering, promote to platform when proven.
Success Criteria
| Type | Criterion | Threshold |
|---|---|---|
| Functional | Create content and dispatch to 2+ platforms | Under 5 minutes from draft to scheduled |
| Functional | Adapted versions preserve core message | Human review confirms intent preserved |
| Outcome | Weekly time saved on distribution | >= 4 hours vs manual |
| Outcome | Multi-platform dispatch rate | >= 60% of creates |
| Outcome | Analytics visible in single view | All connected platforms in one dashboard |
Next Steps
1. Validate distribution pain — 10 founder interviews, unprompted naming of platform-switching fatigue
2. Define platform adapter contract — what does "adapted" mean per channel?
3. LinkedIn-first prototype — one create → LinkedIn + one other platform
4. Prove activation — first user dispatches to 2+ platforms within 7 days
5. Add scheduling, then analytics — complete the loop
Smallest move: One founder creates content in their usual way, runs it through an adapter, and publishes to LinkedIn and X from a single flow. That proves the job.
Context
- Jobs To Be Done — The job is distribution, not creation
- Validate Demand — Awareness levels and kill signals
- Dreamineering Capabilities — Distribution at Level 1, the gap this closes
- Sales CRM & RFP — The Convert/Retain half of the funnel
- Business Development — From validation to plan
- Mushroom Caps — Ventures that need this capability
- Phygital Mycelium — The capability layer