There is a specific feeling I want to describe.
It is Sunday night. Your episode goes out Tuesday. You open your calendar and there is nothing on it. No guest booked. No guest invited. No guest in sight.
That is not a scheduling problem. That is a small, cold panic, and if you have run a show for any length of time, you have felt it.
I felt it more often than I will admit. The strange part is that I knew plenty of people who would have said yes. I just had not asked any of them yet, because asking was something I only did when I was already out of guests.
That is the whole mistake. I treated booking as an emergency instead of a habit.
Why the Calendar Goes Empty
The calendar does not empty because you ran out of interesting people. The world is full of them.
It empties because you only think about guests when you need one this week.
Booking from panic is the worst way to book. You take whoever is available instead of who is right. You write a rushed invite that sounds rushed. You say yes to a mediocre fit because Tuesday is coming and Tuesday does not care about your standards.
And the guest can feel it. An invite sent in a panic reads like an invite sent in a panic.
The fix is not working harder the week of. The fix is never letting the well run dry in the first place.
A full calendar is not luck. It is a leftover from work you did weeks ago.
A Pipeline Is Just Guests at Different Stages
Here is the idea, and it is not complicated.
A pipeline is a steady list of future guests, each one sitting at a different stage of the journey from idea to published.
The mistake most of us make is thinking of guests as either booked or not booked. Two states. On or off. But a real pipeline has many people moving through it at once, all at different points, and that is exactly what keeps the panic away.
When ten people are spread across the stages, the one guest who cancels does not blow up your month. There is always someone right behind them.
You stop asking "who is my next guest" and start asking "who is moving, and who is stuck." That is a much calmer question.
A pipeline turns booking from a scramble into a flow.
The Stages, Walked Through
Let me walk through the stages I actually use. Picture each guest as a person moving from left to right.
It starts as an idea. Just a name. Someone you heard on another show, an author whose book landed on you, a friend of a guest who sounds fascinating. They have not been contacted. They are simply on the list, which is more than most of your best future guests ever get.
Then they become invited. You reached out. The ask is sitting in their inbox and the ball is in their court. This stage is where I used to lose people, because I would invite someone, hear nothing for a week, and quietly forget I ever asked.
Then booked. They said yes and there is a date. This feels like the finish line. It is not. It is the middle.
Then recorded. The conversation happened. The file exists. And here is where a lot of podcasters mentally check out, because the hard part feels done.
Then published. It is live. The link works. The guest can share it.
And then, the stage almost everyone skips, follow-up. Did you send the clips you promised? Did you thank them? Did you stay in touch, or did they vanish from your world the moment the episode shipped?
That last stage is not the end of the pipeline. Done right, it feeds the front of it, because a guest you treated well introduces you to the next three ideas.
The pipeline is not a line. It is a loop.
Keeping It Full
A pipeline only works if it stays full, and full is a habit, not an event.
So I keep a simple rule. Every time one guest moves forward a stage, I add one new idea at the front. Recorded someone today? Drop a new name in the idea column before you close the laptop. The pipeline refills itself if you make refilling part of the rhythm.
The richest source is the people already in it. At the end of a good recording, I ask one question: who else should I be talking to. A guest who just had a great hour with you is the warmest introduction you will ever get. That single question has fed more of my calendar than any cold outreach ever did.
And once a week, I look at who is stuck. Who got invited a month ago and never heard back. Who recorded but never got their clips. Stuck guests are not lost guests. They are just waiting for you to notice them.
The goal is never a packed week. It is a calm month, because you can already see who is coming.
You do not run out of guests because the world ran out of people. You run out because you stopped looking ahead.
That looking ahead is exactly what I built PodGlue to make easy.
Every guest in one place, sitting at a clear stage, from a name you jotted down to someone you recorded last spring and owe a follow-up. You can see who is moving and who is stuck, at a glance, without holding it all in your head. We call it podcast relationship management, and an empty calendar is the problem it quietly solves.
PodGlue is in beta right now. If Sunday-night panic sounds familiar, come build the pipeline that ends it: podglue.com/join.
Junaid Ahmed is the host of Hacks and Hobbies and the founder of PodGlue. He arrived in the US in 1995, has spent 30 years in video and AV, and has stared at more than one empty calendar over 700-plus episodes.
Ready to make every episode compound?
PodGlue is the operating system for relationship-driven podcasters.
Get Started FreeRelated reading
How to Manage Your Podcast Guests Without Losing Track
Nobody teaches podcasters how to keep track of the humans behind the episodes. After 700+ episodes, here is the simple system I wish I had built on day one for managing podcast guests as relationships, not bookings.
Notion for Podcast Guest Management: Does It Hold Up?
Can you run your podcast guests out of Notion? Yes, and here is roughly how. I walk through building a guest database in Notion, where it genuinely holds up, and the point where a busy show starts to strain against it.
The Best Way to Track Your Podcast Guests
The best way to track your podcast guests is the one that survives the moment you get busy. I walk the ladder of methods, from memory to a real relationship tool, and show you which one fits where you actually are.