Robert Kennedy III is a podcaster and visibility coach. He's based near me in Northern Virginia. We know each other — not just as names in a network, but as people who've actually talked.
I showed him the full PodGlue demo a few days ago.
I walked him through everything. 701 episodes imported. The Forge pulling narrative threads, books mentioned, chapter markers, follow-up ideas — all from the transcript alone. The social calendar. The newsjacking feature, where I pulled up a breaking AI story in real time and built a full episode blueprint from it while he watched.
He called that one powerful. Simple word. He meant it.
But the moment that stuck with me wasn't the AI demo or the manuscript builder.
It was when I explained the guest email workflow.
Every time an episode moves through a stage — recorded, in post-production, published — an automated email goes to the guest. Not a generic blast. A personal-feeling touchpoint tied to where their episode actually is. By the time the episode is live, your guest has heard from you at least seven times.
RK3 got it immediately.
He runs a Monday morning show. He has an admin who manages it. As soon as I showed him the guest portal — the guest gets their own link, downloadable clips, social copy ready to go — he was already thinking about how his team would use it rather than him needing to touch it.
That's the right instinct. That's how this is supposed to work.
Here's the thing most podcasters don't say out loud: after the episode goes live, the relationship with that guest basically ends.
You hit publish. You move on to the next recording. The guest gets a "thanks for coming on" message if they're lucky. Then silence.
Seven, fourteen, thirty days later — that person has moved on too. The episode is somewhere in a feed. The connection you made during that conversation? It's fading.
And your guest list — which took you years to build — is sitting there completely untended.
RK3 also coaches people who are scared of being on video or speaking publicly. When I showed him the live vibe coaching in the studio — real-time AI feedback on your energy, pace, and tone as you record — he immediately connected it to his work. His clients need that kind of mirror. The feedback loop that tells you you're trailing off, or you've been in the same flat energy for three minutes.
He already uses AI voice coaching for public speaking. This was the same idea, built for podcasters.
That's the thing about showing this to someone who's actually in the work. They don't just evaluate features. They map them back to real problems they're already solving.
At the end of the call, RK3 said something that stayed with me.
"Even as you're doing videos — if you're doing a video with somebody talking about your product, those are powerful."
He offered to hop back on and record a video version of what we just did.
That offer came from the relationship. Not from a funnel. Not from a pitch. From a conversation between two people who've built enough trust to say "I see what you're doing, and I want to help."
That's what good podcast guest relationship management actually produces. Not just a published episode. A real connection that compounds over time.
Most podcasters think the episode is the product.
It's not. The episode is the proof. The relationship is the product.
Your guest came on because they trusted you with an hour of their time. That trust doesn't expire when the episode drops — but it does fade if you don't tend to it.
Seven touchpoints over the lifecycle of one episode isn't annoying. It's respectful. It's saying: I remember you were here. This episode matters. You matter.
That's what RK3 understood in about thirty seconds.
If you're managing a show and you're still tracking guest relationships in a spreadsheet — or worse, not tracking them at all — that's the gap. Not your content quality. Not your mic. The follow-through.
PodGlue is built to close that gap. It's in beta now. If you're a relationship-focused podcaster ready to stop letting good conversations disappear into a feed, it's worth a look.
Link in the description.