Podcast guest pitch template for indie hackers
A free, copy-paste podcast guest email template for booking indie hackers. Subject lines, full email body, follow-up script, FAQ. Written for hosts who actually book guests.
Who this template is for
Solo and small-team SaaS builders working without venture funding. If you're booking indie hackers 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 indie hacker 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.
Episode topic angles that land
Indie Hackers ignore "tell us your story" pitches. These angles consistently get replies because they ask for operator detail, not narrative:
- The product that failed before this one
- Real revenue numbers and stack costs
- How they balance the day job and the build
- The marketing channel that finally worked
The specific reference you need before sending
They love podcasts but get burned by hosts who only want a 'how I made $10K in a weekend' story. The fix is a concrete reference to recent work. Acceptable proof points include a recent build-in-public tweet; an MRR milestone post; a Reddit or Indie Hackers thread. 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.
Subject line options
Three subject lines built for under 55 characters, lowercase, no clickbait: "{{product_name}} — 30 min for {{podcast_name}}?", "Quick podcast invite re: the {{milestone}} post", and "Loved the {{specific_thing}} thread". Each is short enough to render fully on mobile and specific enough to clear pattern-matching delete.
The full cold-pitch template
Hey {{first_name}}, I run {{podcast_name}} — {{audience_short}} listen weekly. Your {{milestone}} post showed up in my feed and the part about {{specific_thing}} is the unsexy operator detail more shows should cover. Want to do a 30-minute conversation on what actually got you here? Not the highlight reel — the channel that didn't work, the pricing that broke, the support load you didn't expect. Casual format, async-friendly recording, I edit it tight. Audience is ~{{listener_number}} per episode, mostly other builders. Past guests: {{name_1}}, {{name_2}}. Open to it in the next 2 weeks? {{your_name}}
The follow-up (send 5–7 days later)
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 — if the timing's off no worries, I'll watch for the next milestone post and re-pitch. If it's not off, I have slots Tuesday and Thursday next week. {{your_name}}
Frequently asked questions
What's the best podcast guest email subject line for indie hackers?
Short, specific, and human. "{{product_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.
How long should a cold podcast pitch to a indie hacker be?
Under 160 words. indie hackers scan in under 8 seconds — anything longer is a delete. The template above is intentionally tight: hook, ask, format, close.
How many follow-ups are okay when pitching indie hackers?
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.
How do I find a indie hacker's email address?
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.