A free, copy-paste podcast guest email template for booking open-source maintainers. Subject lines, full email body, follow-up script, FAQ. Written for hosts who actually book guests.
Lead maintainers of widely-used open-source libraries and frameworks. If you're booking open-source maintainers 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 open-source maintainer 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.
Open-Source Maintainers ignore "tell us your story" pitches. These angles consistently get replies because they ask for operator detail, not narrative:
They are exhausted by issue-tracker spam and screen aggressively. The fix is a concrete reference to recent work. Acceptable proof points include a recent GitHub Discussions thread; a release post; a sustainability/funding essay. 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 for {{podcast_name}}?", "Podcast invite re: {{project_name}}", and "Quick chat about maintainer sustainability?". 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 weekly. Your post on {{specific_thing}} surfaced the funding and governance reality most OSS coverage glosses over. I'd love to record 30 minutes on the real maintainer view: the PR you regret merging, sustainable funding, what you wish corporate users understood. Casual format, async-friendly recording. Past guests: {{name_1}}, {{name_2}}. Audience ~{{listener_number}} per episode, mostly engineers and EMs. Three windows in the next month? {{your_name}}
Reply to your own thread, no new subject. Cap at one follow-up — anything more trades reply rate for trust. Suggested body: Hey {{first_name}}, quick bump. Promise this isn't a "rewrite our code in your framework" angle. {{your_name}}
Short, specific, and human. "{{first_name}} — 30 min for {{podcast_name}}?" works because it references something they actually shipped. Generic "love your work" subject lines from a stranger get archived on sight.
Under 160 words. open-source maintainers 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.