Pitch a Podcast Host with Three Actionable Listener Takeaways

Generates a concise cold pitch email that references a creator's recent episode and outlines three practical takeaways for their audience.

You getSubject Line, email Draft and risk Check

Prompt

Prompt
Act as a media publicist specializing in creator outreach. Write a cold pitch email to a podcast host or newsletter creator proposing a guest interview. Before drafting, ask me these 4 questions and wait for my response:
1. What is the show name, creator name, and the specific recent episode or essay you liked?
2. What was one specific idea from that episode you agree with or want to expand on?
3. Who are you, and what is your specific professional background?
4. What 3 concrete takeaways or steps will their audience learn from an interview with you?

Rules:
- Keep the total email under 200 words.
- Open directly with the specific reference to their work; do not use generic flattery.
- Present the 3 listener takeaways as bullet points that start with an action verb.
- Include a low-friction call to action that does not demand an immediate call.
- Do not invent credentials, metrics, or listener counts.

Output format:
- Subject Line: (2 options, under 8 words each)
- Email Draft
- Risk Check: 1 line noting the biggest assumption made about the host's audience.

Example output

Example for: an infrastructure engineer pitching a DevOps podcast host after an incident-response episode.

Subject Line:

  • Option 1: Quick thought on your incident response episode
  • Option 2: Post-mortem followup + guest pitch for CloudOps Weekly

Email Draft:

Hi Elena,

Your recent episode with Marcus on alert fatigue hit the mark—especially the point that tier-1 on-call rotations fail when teams treat warning alerts as emergencies.

I lead reliability engineering at Veloce, where we cut false-positive alerts by 62% across 40 microservices over the last nine months. I would love to share the playbook we used with your CloudOps Weekly listeners.

Here are three practical takeaways your audience will get from an episode:

  • Audit alert thresholds by calculating signal-to-noise ratios over a rolling 30-day window.
  • Build a tiered runbook that automates non-critical ticket triage during off-hours.
  • Retrain engineering leads to conduct blameless reviews that uncover tooling failures rather than human error.

If this fits your upcoming schedule for CloudOps Weekly, let me know and I can send over a 2-minute outline. Either way, thanks for the practical show.

Best,
David Chen
Staff SRE, Veloce Infrastructure

Risk Check:
Assumes the host prefers concrete operational tactics rather than high-level engineering culture discussions.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Forces a reference to an exact episode point so the pitch never sounds like automated mass spam.
  • Restricts takeaways to action-oriented bullet points, showing immediate value for the audience.
  • Uses a low-friction close requesting permission to send an outline instead of demanding a call.

Use this in ChatGPT, Claude, or Gemini when reaching out to interviewers. Have the host's recent episode title and your 3 practical takeaways ready before you start.

Common edits

  • Swap the podcast context for a Substack essay if you are pitching a guest post or interview to a newsletter writer.
  • Add one sentence mentioning a mutual contact or shared community membership to increase response rates.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Email