Guest booking for interview podcasts
Guest booking for interview podcasts is a SaaS idea for hosts of weekly interview podcasts and small production teams, priced to test at $19 a month per show. Booking one guest takes a dozen emails: the pitch, the date, the bio, the photo, the questions, the release form. With it, podcasters run their guest pipeline from first invite to signed release form, with prep questions and reminders handled.
. A starting point we wrote, not market research: run the 7-day test before you build.
What problem does it solve?
Booking one guest takes a dozen emails: the pitch, the date, the bio, the photo, the questions, the release form. Details get lost and guests show up unprepared.
Why now: Video podcasts need more prep per episode, and small teams book guests weeks ahead across time zones.
What do they use today?
Hosts manage each guest in a separate email thread, with a calendar invite, a shared document for questions and a form sent as an attachment. Someone keeps a spreadsheet of who has done what.
How does it work?
A host adds a new guest to the pipeline and emails them a link to the guest page. There the guest picks a recording date, adds a bio and photo, answers the prep questions and signs the release form online. Reminder emails go out before the recording, and co-hosts and producers follow each guest from pitched to published in one shared view.
What goes in the first version?
- A guest pipeline from pitched to published
- A guest page with date booking, bio, photo and prep questions
- A release form guests sign online
- Reminder emails before the recording
- A shared view for co-hosts and producers
Who pays, and how much?
- Who pays
- Hosts of weekly interview podcasts and small production teams
- Price to test
- $19 a month per show
A price per show matches how hosts think, since each show has its own guests, schedule and team. Co-hosts and producers share the show’s view, so there are no seats to count.
How to test it in 7 days
- 1Ask in r/podcasting how hosts manage guest logistics.
- 2Interview five hosts of weekly interview shows.
- 3Book one guest for a host with a mock-up and ask what was missing.
Where to find the first customers
- r/podcasting
- Podcast host groups on Facebook
- Podcast production agencies
What are the risks?
- Free scheduling tools cover part of the job.
- Hobby podcasters rarely pay, so aim at shows with sponsors.
How to build it on shipanysaas
4 of the parts it needs are already in the kit. Get the kit, open it in Claude Code, Codex or Cursor, and paste the starting prompt.
- Already in the kit
- Sign-in
- Teams and roles
- Billing
- Emails
- You build
- Guest pipeline board
- Guest page with booking and uploads
- Online release form
See the starting prompt
You are in a fresh copy of the shipanysaas starter kit, a pnpm and Turborepo monorepo: the Next.js web app is in apps/web and the Supabase database, with its migrations, in apps/web/supabase. Help me build the first version of Guest booking for interview podcasts. Read AGENTS.md first, then the AGENTS.md in every folder you work in: the kit's rules there win over your defaults. When a skill in .agents/skills (also in .claude/skills and .cursor/skills) matches a task, use it. ## The product - What it does: Podcasters run their guest pipeline from first invite to signed release form, with prep questions and reminders handled. - Who pays: Hosts of weekly interview podcasts and small production teams - Their problem: Booking one guest takes a dozen emails: the pitch, the date, the bio, the photo, the questions, the release form. Details get lost and guests show up unprepared. - Price to test: $19 a month per show (a plan in apps/web/config/billing.config.ts) ## Build only this first version 1. A guest pipeline from pitched to published 2. A guest page with date booking, bio, photo and prep questions 3. A release form guests sign online 4. Reminder emails before the recording 5. A shared view for co-hosts and producers ## Already in the kit: reuse it, never rebuild it - Sign-in: email and password or Google, plus magic links and passkeys you can switch on - Teams and roles: team accounts with members, roles and invitations - Billing: Stripe or Lemon Squeezy subscriptions, per seat or usage-based, and one-off payments - Emails: transactional email through Resend or Nodemailer ## New code it needs - Guest pipeline board - Guest page with booking and uploads - Online release form ## How to work 1. Plan first: list the database tables (with row-level security, so each team only sees its own rows), the pages and the server actions for the first feature. Then stop and wait for my OK. 2. Build one feature at a time with the kit's own UI and form components, with a migration for every schema change and user-facing text in the translation files. 3. After each feature, run the verification steps in AGENTS.md, fix what they find, and tell me what you built and what comes next. ## Rules - Ask me before you add a dependency, delete a file, or change sign-in, billing or the admin panel. - Leave the parts of the kit this product doesn't use as they are. Done when every first-version feature works for a signed-in team and the AGENTS.md checks pass.
Guides for the parts it uses
Want ideas for your own skills?
The free generator writes three while you watch, each with a plan and a starting prompt. Or paste this idea into it for two sharper versions.
More ideas: Creators
Member directory and event sign-ups for clubs
Alumni groups, hobby clubs and small associations keep one member list, a private directory and event sign-ups.
Listener questions inbox for podcasts
Podcasters collect listener questions and voice messages from one link, tag the best ones, and plan them into episodes.
Guest writer pitches and drafts for newsletters
Newsletters that publish guest writers collect pitches through one form, review them as a team, and track drafts to publication.