Running a podcast booking agency is a logistics business dressed up as a creative one. The pitch is "we get our clients on great podcasts." The actual work is sourcing hosts, tracking outreach, negotiating dates, prepping guests, and doing it all again next week for the next client.
Agencies that scale past two or three clients do not scale by hiring more VAs. They scale by running operations as a real system.
The Operations Problem for Podcast Agencies
The agency runs three parallel tracks for every client:
- - Sourcing. Finding shows that fit the client's topic, audience size, and format.
- - Outreach. Pitching hosts, following up, negotiating dates.
- - Delivery. Prepping the guest, confirming logistics, showing up, following up after.
Each track is its own operations problem. Without a system, the typical failure modes are:
- - Outreach spreadsheets shared across VAs, one client overlaps with another, the same host gets pitched twice in the same week.
- - Hosts reply and the VA takes days to respond because nobody owns the inbox.
- - Dates get booked but never make it into the guest's calendar.
- - Prep documents get sent hours before the interview instead of days before.
- - After the episode airs, nobody tells the client, nobody grabs the audiogram, nobody reposts.
Every one of these is a trust problem with the client. They hired the agency so they would not have to track any of this.
The System We Build
Five modules. Each one maps to a real bottleneck.
1. Show sourcing. A sourcing pipeline that pulls shows by topic, audience size, host geography, and recency of episodes. Hosts get verified before outreach, because dead shows and abandoned hosts burn sender reputation. Sourcing outputs a clean list per client per week. Every show goes through a fit filter before it gets pitched.
2. Pitch sequences. Four to six touchpoints. Minimum multi-day delay between steps. Personalization pulled from recent episodes, not generic praise. Spintax on subjects. First email is short, specific, and includes one concrete reason the guest fits this show. Follow-ups reference the first pitch without repeating it.
3. Reply handling. Every reply routes to a defined queue. Positive replies get a booking link within hours. Date-negotiation replies get handled by a single operator with visibility into the guest's calendar. No-thanks replies go to a long-term suppression list. Out-of-office replies get rescheduled.
4. Episode prep. Confirmed bookings trigger a prep workflow. Guest gets a prep doc 48 hours before. Host gets a reminder with the guest's bio and talking points. Day-of reminder one hour before with the direct join link. Post-interview thank-you within 24 hours.
5. Post-episode. When the episode airs, the system captures the link. Client gets notified. Audiogram and social assets get queued. Metrics get logged in the client dashboard. Nothing lives in a VA's head.
What Changes After
The agency stops losing bookings to operational sloppiness. Host reply rates go up because pitches are specific and follow-ups are on time. Guest no-shows drop because prep is structured. Clients see a dashboard instead of asking for a weekly update.
Capacity per operator roughly doubles. A single booker who used to manage a handful of clients manually can manage many more on the system because the repetitive work stops happening in their head.
Common Objections
"Our hosts want personal pitches, not automated ones." Agreed. The system does not write generic pitches. It provides the operator with the right show at the right moment and pre-filled personalization pulled from recent episodes. The human still approves every first-touch message.
"We already use a CRM." The CRM is one layer. The question is what feeds it, what follows up on every stage, and what triggers the prep and post-episode workflows. A CRM with no workflows on top is a filing cabinet.
"We have VAs who do this." They can keep doing it. On the system, they move faster, make fewer mistakes, and you can actually see what they did last week. If you ever replace them, the knowledge stays.
"Our clients are all different." The client profile is different. The operational sequence is the same. Source, pitch, book, prep, deliver, follow up. That stack does not change per client.
When This Makes Sense
This makes sense when you have at least a few active clients on monthly retainers, you do dozens of host pitches per client per month, and you want to add clients without proportionally adding headcount.
This does not make sense when you have one client and you enjoy doing the work yourself, or your clients are all on one-off PR campaigns rather than recurring booking retainers.