Guest booking pipeline for podcast pitching
The idea
Podcast guesting is the highest-leverage marketing channel for anyone selling expertise, and the workflow behind it is a disgrace: scrape a listicle of top 50 shows, guess emails, blast a template, track it in a spreadsheet. PR agencies charge $3-5k/mo to do exactly this motion by hand. PROSP built $128k MRR systematizing outreach on LinkedIn — same job, worse substrate, because LinkedIn bans automation accounts. Podcasting’s data layer is public RSS: contact emails sit in the feed, episode history is free, and nobody can ban you from sending a normal email.
The wedge is pitch quality plus pipeline: reference the actual recent episodes, propose concrete segment angles, and track everything from saved to aired. The $3-5k/mo agency anchor makes $39-99/mo feel like theft in the buyer’s favor.
Who pays
Authors on book tours, consultants, coaches, and founders doing launch publicity — anyone whose revenue moves when they get in front of a niche audience. $39-99/mo tiered on pitch volume. Distribution: content targeting how to get booked on podcasts searches, communities where authors and bootstrapped founders compare marketing channels, and podcast hosts themselves, who will happily share a tool that improves the pitches clogging their inboxes.
MVP scope
- Show search on Podcast Index with recency, cadence, and fit scoring
- Contact extraction from RSS owner fields
- Claude-drafted pitches referencing recent episodes with proposed angles
- Sending via the user’s Gmail with auto-cancelling follow-ups
- Kanban pipeline from saved through aired, with reply-rate analytics
- Skip for v1: booking calendar integration, media kits, agency multi-client mode, YouTube channels, response-rate benchmarking
Build GuestPipe, a podcast guest-booking pipeline app. Core flow: a user describes their expertise and target audience, then searches shows via the Podcast Index API filtered by category, language, episode recency, and estimated size (use episode count and publishing cadence as proxies). Each show card displays the contact email parsed from the RSS feed's owner and itunes:email fields, recent episode titles, and a fit score. The user adds shows to a pipeline with stages: saved, pitched, replied, scheduled, recorded, aired. For each pitch, the Claude API drafts a personalized email that references two recent episode titles and proposes three specific segment angles derived from the user's expertise profile — never a generic template. Sending goes through the user's own Gmail or SMTP via OAuth, with two polite follow-ups auto-queued at day 5 and day 12 that cancel on reply detection. A tracker dashboard shows pitches out, reply rate, and booked episodes with dates. Stack: Next.js App Router with TypeScript, Podcast Index API for show data, Claude API for pitch drafting, Postgres via Prisma, Gmail API for sending. Pages: show search, pipeline board (kanban), pitch composer, sequences and follow-up settings, analytics, billing. Non-obvious details: cache RSS parses aggressively and re-fetch feeds weekly since owner emails change rarely; score show fit by comparing episode-title embeddings against the user profile rather than category tags alone, which are junk in podcast directories. Pricing: $39/mo for 50 pitches, $79/mo for 200, $99/mo unlimited plus a second user seat for assistants.
// More Micro-SaaS ideas
-
Invoicing for freelance film crew
Freelance film crew hand-build invoices with day rates, kit fees, OT, and per diems; generates production-ready invoices from a simple call-time log.
Market read pendingWe are still researching this idea. -
Auto-generated graphics for youth sports leagues
Youth leagues wrangle Canva every single week; auto-generates schedule, matchup, and result graphics for every team straight from the fixture list.
Market read pendingWe are still researching this idea. -
Lead-first analytics for local businesses
Plausible tells local businesses pageviews, not jobs; cookieless analytics that ties visits to calls and quote forms so owners see which channel pays.
Market read pendingWe are still researching this idea. -
Restaurant websites built from the menu
Restaurant sites rot because menus change weekly; snap the menu and get a full site with schema markup, hours, and ordering links that stay in sync.
Market read pendingWe are still researching this idea.