A free, copy-paste podcast guest email template for booking product managers. Subject lines, full email body, follow-up script, FAQ. Written for hosts who actually book guests.
Senior PMs, group PMs, and CPOs at product-led companies. If you're booking product managers as podcast guests — for an interview show, narrative show, or panel format — this template is built for the cold first touch when you don't have a warm intro.
Every winning podcast guest email to a product manager cites something concrete the guest made in the last 60 days. The template below structures that reference around a 30-minute recording ask in under 160 words.
Product Managers ignore "tell us your story" pitches. These angles consistently get replies because they ask for operator detail, not narrative:
They're inundated with 'tell us your roadmap' pitches that go nowhere. The fix is a concrete reference to recent work. Acceptable proof points include a Lenny's Newsletter mention; a Reforge post or course; a recent Notion or Figma teardown they shared. If you can't find one of those within the last 60 days, this is the wrong week to pitch this guest — wait until they ship something new.
Three subject lines built for under 55 characters, lowercase, no clickbait: "{{first_name}} — 30 min on the {{feature_name}} kill", "Podcast invite re: your discovery post", and "Quick chat for {{podcast_name}}?". Each is short enough to render fully on mobile and specific enough to clear pattern-matching delete.
Hi {{first_name}}, I host {{podcast_name}}, {{audience_short}} listen during commutes. Your post on killing {{feature_name}} was the cleanest articulation of "we shipped the wrong thing" I've read in months. I'd love to record 30 minutes on the post-mortem: what the data showed, the internal politics of the kill, what your discovery process looks like now. Casual, async-friendly, we cut the rambling. Audience ~{{listener_number}} per episode, mostly PMs and product leaders. Past guests: {{name_1}}, {{name_2}}. Three windows in the next month? {{your_name}} {{podcast_url}}
Reply to your own thread, no new subject. Cap at one follow-up — anything more trades reply rate for trust. Suggested body: Hi {{first_name}}, gentle bump — happy to scope it to a smaller topic (e.g. just the discovery process) if 30 min on the kill feels heavy. {{your_name}}
Short, specific, and human. "{{first_name}} — 30 min on the {{feature_name}} kill" works because it references something they actually shipped. Generic "love your work" subject lines from a stranger get archived on sight.
Under 160 words. product managers scan in under 8 seconds — anything longer is a delete. The template above is intentionally tight: hook, ask, format, close.
One follow-up about 5–7 days after the original is the practical maximum. After that, you're trading reply rate for trust. Add the prospect to a 6-month re-pitch list instead of sending a third email.
Check their personal site (/about, /contact, footer), LinkedIn contact info, and recent newsletter reply-to address. If nothing surfaces, an email finder like Hunter or Apollo plus a verifier like NeverBounce is the standard playbook.