A Repeatable System for Booking Podcast Guests


Book podcast guests with a pipeline, not a favor list. Keep one tracker with five stages, sourced, invited, replied, booked, recorded, give every guest a next action with a date, send a four-touch follow-up over two weeks, and lock each recording with a calendar invite plus a same-day reminder. The system, not your charm, is what fills your calendar.
Most hosts book guests the way they answer texts: reactively, one at a time, from a cluttered inbox. That works for the first ten episodes. Then a guest goes quiet, you forget who you owed a reply, two recordings collide on the same Tuesday, and someone simply doesn't show. The fix is not working harder on each email. It is running booking as a small operation with a few moving parts you can see at a glance.
This is the host's side of the table. If you are the one pitching yourself onto other people's shows, the mechanics are similar but the wording flips, start with the guest-side outreach pipeline instead.
Why a booking system matters
Consistency is the single strongest predictor of whether a podcast survives. About 47% of podcasts stop at three episodes or fewer (Amplifi Media analysis), and a leading reason is the per-episode workload becoming unsustainable. For an interview show, the workload that quietly breaks you is not editing, it is the scramble to find, chase, and confirm a guest in time for the next slot.
A booking pipeline removes that scramble. When you always have three guests sourced and one booked two weeks out, you never publish a thin episode because the calendar forced your hand. You also build something compounding: every guest you book is a person with an audience, and every recording is raw material for clips. Social video and recommendations now drive discovery more than friends and family do, 57% of listeners say they rely on social media for podcast recommendations, the first time it surpassed personal referrals (InsideRadio, 2025). A guest who shares their own episode hands you their audience. A system that books eight guests a quarter is also a content engine running in the background.
The guest CRM: columns that earn their place
A "CRM" here means one spreadsheet. Google Sheets does everything you need; Notion or Airtable work if you already live there. One row per guest. The discipline is in the columns, and in refusing to add columns that do not change a decision.
| Column | What goes in it | Why it earns its place |
|---|---|---|
| Guest name + title | The person and their relevance | Your anchor for the row |
| Contact | Email or DM handle | One real human, never "team@" |
| Stage | Sourced → Recorded | The single most-used field |
| Topic angle | The one episode they'd carry | Forces a reason to invite |
| Fit score (1–3) | Audience + draw + availability | Pitch your 3s first |
| Date invited | When you reached out | Drives the follow-up trigger |
| Next action + date | "Follow up · Jul 5" | Tells you what to do today |
| Notes / outcome | Reply quotes, record date, links | Memory for next quarter |
Eight columns. The one most hosts skip is the fit score, a 1-to-3 rating that blends three things: how much their audience overlaps yours, how strong a draw they are, and how reachable they seem. Sort descending and invite your 3s while your best angles and energy are fresh. The other load-bearing column is "next action + date." Every active row must always carry one, even if the action is "wait, re-check Aug 1." A blank next-action cell is a dropped guest, and the tracker's entire job is to make dropped guests visible before they go cold.
Before you ever fill the topic-angle column, do the homework. A specific, researched invite converts far better than a templated one, research the guest in under 90 minutes so your first email names the exact episode only they could record.
The five stages, defined hard
A stage is only useful if it means exactly one thing. Fuzzy stages, "kind of interested?", are why pipelines rot and why you double-book. Five stages, each with a definition you cannot wriggle out of.
- Sourced. The person is on your list with a real contact, a fit score, and a drafted topic angle. Nothing sent. This stage exists so you can batch research separately from sending, far more efficient than doing both in one sitting.
- Invited. Your tailored email is sent and the date is logged. The next-action cell auto-becomes "follow up · day 4."
- Replied. A human responded, yes, no, "maybe later," or a question. A "no" still counts as replied; move it to a closed sub-status, not back to invited. A clean "no" keeps your active count honest.
- Booked. A recording date is on a calendar and a calendar invite has gone out. Not "they're keen." A date with an accepted invite. Until then it is still Replied.
- Recorded. You both showed up and recorded. Work now shifts to editing, promotion, and the thank-you note. Send your interview questions in advance so the guest arrives warm, see how to ask questions that get real answers.
The follow-up cadence: four touches, then stop
Most "yes" replies arrive on the second or third contact, not the first, busy people miss a single email, they are rarely rejecting you. The skill is following up enough to be remembered without becoming the host who can't take a hint. Four touches over two weeks, then you stop and re-source.
- Day 0, the invite. Specific subject line, one named topic angle, one sentence on why them, one clear ask with two proposed dates. Short.
- Day 4, the gentle bump. Reply to your own thread. Two lines: "floating this back up, would [date] or [date] work?" No guilt, no "just following up again."
- Day 9, a new angle. Don't repeat the same email. Add something: a recent clip of theirs you loved, a second topic you could cover, or a note that you'll keep the slot flexible. Give them a fresh reason.
- Day 14, the graceful close. "I'll stop cluttering your inbox, the door's open whenever the timing's better." Then move the row to closed and set a re-source date 90 days out. This last note converts more often than people expect, because it removes the pressure.
Keep your tone host-appropriate throughout. You are extending an invitation, not asking for a job, host etiquette is the difference between a guest who says yes and one who quietly files you under spam.
The scheduling flow that kills no-shows
No-shows are almost never a guest deciding to ghost you. They are a calendar event that never got created, a time-zone slip, or a recording the guest genuinely forgot a week after agreeing. Each of those is a process failure you can engineer out. Three steps, every time.
- Send a real calendar invite the moment a date is agreed. Not "I'll pencil it in." A proper invite the guest accepts, with the time zone spelled out ("3pm Eastern / 8pm London"), the recording link inside, the expected length, and a one-line "what to expect." A booking page like Calendly or SavvyCal does this automatically and removes the back-and-forth entirely; for many shows it's worth the setup. The accepted invite is what turns "Replied" into "Booked" in your tracker.
- Confirm 48 hours out. A short message: the link, the time in both your zones, and one logistics line ("camera on, headphones help with echo, no prep needed"). This is also where you flag your audio/video basics so they don't arrive on a phone in a wind tunnel.
- Remind the same day. One line, two to three hours before: "Looking forward to it, here's the link again." Half your saved no-shows are just this message. People are busy; a same-day nudge is a courtesy, not a pester.
Build a guest-info doc you can paste into step two every time, link, gear notes, length, topic recap, and a short bio request. Reusing it makes the professional version of this take under a minute per guest.
Common mistakes hosts make
- Treating the inbox as the system. Threads bury, replies get lost, and you cannot see how many guests are in flight. The tracker is the source of truth; email is just where conversations happen.
- Inviting cold with a template. A generic "I'd love to have you on my show" reads as spam to anyone with a following. Name the specific episode only they could record. The fit score and topic-angle columns exist to force this.
- No date, but you mark it booked. "They're interested" is not booked. Without an accepted calendar invite, it belongs in Replied, and you should keep sourcing.
- One follow-up, then silence. You quit right before the touch that converts. Four touches, spaced, each adding something. Then stop cleanly.
- Skipping the same-day reminder. This is the cheapest no-show insurance there is, and the step hosts cut first. Don't.
- Forgetting the post-record loop. A guest who had a good time and got a clip to share is your best source of the next guest. Send the thank-you, send the clips, and ask who else you should talk to. (Build the questions that produce shareable moments with follow-up questions and active listening.)
Tools that fit the flow
You can run this entire system in two free tools: a spreadsheet and Gmail. Add a scheduling app (Calendly, SavvyCal, or Cal.com) once the calendar invite step starts eating your time, it pays for itself the first month you book more than four guests. A shared sheet plus a booking link covers a solo host or a small team comfortably; a guest who knows what to expect also behaves better on the day, which is where guest etiquette and a clear info doc do quiet, compounding work.
The last tool in the chain is whatever turns the recording into clips. Every booked guest is a person with an audience and a recording is a week of social posts waiting to be cut, that is the discovery flywheel the 57% social-recommendation number points at. Cut the clips the same week you record, while the guest is still excited to share.
Frequently asked questions
How far in advance should I book podcast guests? Aim to keep one guest booked two to three weeks out and three more sourced behind them. That buffer means a cancellation never forces a thin episode, and it gives guests enough lead time to say yes without you chasing. For very in-demand guests, four to six weeks is normal, start that conversation early.
How many guests should I invite to fill one slot? Plan for roughly one recording per three to five cold invites, then adjust to your own reply rate after your first month of data. Warm intros convert far higher. Track date-invited and outcome in your CRM so you can compute your real ratio and reverse-engineer how many invites a month your publishing schedule needs.
What's the best way to prevent podcast guest no-shows? Send an accepted calendar invite the moment a date is set, confirm 48 hours out, and send a same-day reminder a few hours before. Spell out the time zone in both directions and put the recording link in every message. Most no-shows are forgotten events or time-zone slips, not ghosting, and all three are preventable.
Should I pay podcast guests? For most interview shows, no, guests come for reach, relationships, and a clip to share, not a fee. The exception is when you want a specific expert whose time is genuinely scarce, where an honorarium can make the difference. Lead with the value of their episode and the audience, not with money.
Do I need a CRM, or is a spreadsheet enough? A spreadsheet is enough for almost every show. The value is in the eight columns and the stage discipline, not the software. Move to Notion, Airtable, or a real CRM only when multiple people book guests at once or you're running several shows, until then, a tool you have to maintain is a tax on time better spent inviting.