Skip to content

Add Podcast Strategist - Marketing Division#140

Open
Subhodip-Chatterjee wants to merge 3 commits intomsitarzewski:mainfrom
Subhodip-Chatterjee:add-agent-marketing-podcast-strategist
Open

Add Podcast Strategist - Marketing Division#140
Subhodip-Chatterjee wants to merge 3 commits intomsitarzewski:mainfrom
Subhodip-Chatterjee:add-agent-marketing-podcast-strategist

Conversation

@Subhodip-Chatterjee
Copy link
Contributor

What this agent does

The Podcast Strategist covers the full podcast lifecycle: show positioning, content engine development, platform discoverability, guest strategy, community building, and monetization architecture.

Why this agent is needed

The Marketing Division has platform specialists for TikTok, Instagram, Twitter, Reddit, and App Store — but no agent for podcasting, which is one of the fastest-growing owned-media channels with distinct strategy requirements around audio-specific algorithms, consumption metrics, and CPM-based monetization.

What it adds

  • Show Bible and episode brief frameworks
  • 4-phase workflow from concept to monetization
  • Platform algorithm optimization (Spotify, Apple, YouTube Podcasts)
  • Guest outreach and management system
  • Hook engineering and episode structure guidance
  • Sponsorship ladder and premium feed monetization strategy
  • Quantified success metrics (consumption rate, subscriber velocity, CPM benchmarks)

@msitarzewski
Copy link
Owner

Hey @Subhodip-Chatterjee — a Podcast Strategist is a great addition, we don't have one yet!

The frontmatter needs fixing though — it's currently formatted as a markdown table instead of YAML. It should look like:

---
name: Podcast Strategist
description: Expert podcast marketing specialist focused on audience growth...
color: purple
emoji: 🎙️
vibe: Turns conversations into communities and episodes into growth engines.
---

The emoji and vibe fields are required for all agents. Check any existing agent file for reference.

Content quality is solid — looking forward to the update!

@Subhodip-Chatterjee
Copy link
Contributor Author

Thanks for the feedback! I've fixed the frontmatter formatting to YAML and added the required emoji and vibe fields. The update has been pushed to the repository. Please take a look when you get a chance.

@msitarzewski
Copy link
Owner

Hey @Subhodip-Chatterjee — thanks for iterating on this. There's an issue though: the file now has two complete agents stacked on top of each other — your new general-market Podcast Strategist and the existing China-focused one that was already in the file. The frontmatter is duplicated too (two descriptions, two emojis, two vibes).

These actually serve two different markets, so let's split them into two files:

  1. marketing/marketing-podcast-strategist.md — your new general/global podcast strategist (Spotify, Apple Podcasts, YouTube). Remove the China-specific content from this file.

  2. Leave the existing China-focused content alone — it's already on main as a separate agent. Your PR should only touch the new general-market file.

For the frontmatter on the new file, make sure there's only one set:

---
name: Podcast Strategist
description: Expert podcast growth specialist focused on show positioning, audience development, content strategy, and monetization...
color: purple
emoji: 🎙️
vibe: Turns conversations into communities and episodes into growth engines.
---

Also needs a row in the Marketing Division table in README.md — you know the drill from #180. 😄

@msitarzewski
Copy link
Owner

Quick follow-up on naming — the existing China-focused agent already lives at marketing-podcast-strategist.md. Your new global one needs a different filename. Something like:

  • marketing/marketing-global-podcast-strategist.md with name Global Podcast Strategist

Or we could rename the existing China one to marketing-china-podcast-strategist.md and give yours the original name. Up to you — just let me know which direction and I can help sort out the rename if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants