A podcast community is a place your listeners can actually stand โ where episodes, the discussion about them, and the people who never miss one live somewhere you own, instead of scattered across apps that report downloads and hand you nothing else. It turns an anonymous audience into a group you can name.
Podcasting has a strange gap in it. Someone gives you forty minutes of undivided attention on a commute, week after week, for two years โ and you have no idea who they are.
Downloads are not people
Your host reports download counts. A download cannot be emailed, invited to a live recording, or asked what to cover next. It is the most loyal audience in media, delivered to you as a chart.
That gap has a practical cost. A listener who has heard 140 episodes has no route to becoming anything more than a number โ not a member, not a guest suggestion, not a supporter. The relationship is real and entirely one-directional, and nothing in the podcast stack is designed to change that.
A community is the smallest thing that closes the gap: somewhere a listener can sign up, be recognised, and be reached. Everything else in this guide follows from that one shift.
Every conversation about your show is on someone else's platform
Right now the discussion about your best episode is scattered across a Spotify comment, a YouTube reply, an Apple review you cannot respond to, and a thread that will be gone by Thursday.
None of it is yours, none of it is searchable, and โ the part that stings โ none of it reaches the next listener. The sharpest reply to episode 112 sits under a YouTube clip, seen by nobody who listened in Overcast. A year later, when someone finally gets to that episode, the conversation that would have made it better is unreachable.
A per-episode discussion thread fixes something structural, not cosmetic. The argument attaches to the episode and stays findable, which means your back catalogue keeps compounding instead of decaying. This is the same owned-audience logic that applies to every creator, but podcasting has the widest gap between how loyal the audience is and how little of it you control.
A listener community is small and dense โ plan for that
Here is the expectation-setting that saves people a lot of disappointment: most of your audience will never join, and that is fine.
A show with 20,000 listeners might see a few hundred in the community. That ratio looks like failure if you were expecting a proportional turnout. It is not. The few hundred who join are the ones who show up to a live recording, suggest the guest you would never have found, correct you when you are wrong, and pay for something.
Build for that group. A listener community optimised for the devoted minority is a completely different product from one built to capture everyone โ smaller, denser, and far more useful to the people in it.
The five spaces
The structure is simple, and the split between what you publish and what listeners post matters more than the count.
| Space | Who posts | What it is for |
|---|---|---|
| Start Here | You only | The one post telling a new listener which three episodes to begin with |
| Episodes | You | A Podcast space, so audio lives in your community next to the discussion |
| Episode Discussion | Listeners | A permanent thread per episode instead of a comment that evaporates |
| Listener Chat | Listeners | The live room, for people who want to talk while they listen |
| Live Recordings | You | Recording sessions, guest AMAs, anything with an audience in the room |
Start Here earns its place. A podcast back catalogue is intimidating in a way most content is not โ nobody starts at episode one of a 200-episode show โ and telling people where to begin is the highest-value post you will write. More on the general principle in the structure guide.
It does not replace your host or your public feed
This is the most common confusion, and getting it wrong costs you reach.
Keep publishing to Apple, Spotify, and the rest through your existing host. That is where discovery happens, and a community cannot do that job. The Episodes space is where episodes live for the people who already joined โ right next to the discussion, the chat, and the live recordings.
The two jobs are genuinely different: distribution reaches strangers, community deepens the relationship with people who are already listening. Conflating them tends to produce a worse version of both. Treat the community as a listener destination, not a distribution channel, and the decision gets easy.
Monetization: why the sponsor math fails good small shows
Ad revenue is gated behind download thresholds you do not control. The consequence is perverse: a show with 2,000 devoted listeners can be unmonetizable, while a show with 50,000 passive ones is not.
Direct support inverts that. Paid membership tiers let the devoted listener support the show without you needing to clear anyone's download minimum โ you connect your own Stripe account, create tiers, and gate spaces or content to the tier that should see them. A members-only space is an access rule, not a separate product.
The platform fee starts at 3% and drops toward 0% on higher plans, with Stripe's processing fees on top. For a small dense audience that math works out very differently from sponsorship, which is the whole point โ see community monetization for the wider set of models.
What you cannot do
Three limits, all worth knowing before you start rather than after.
There is no private RSS feed. You can gate a members-only space, but members cannot plug a private feed into Overcast or Pocket Casts. Plan on members listening inside your community. If a private feed in a third-party app is essential to your premium offer, this is the wrong fit and it is better to find that out now.
You cannot import your listeners. Podcast apps do not hand over listener identities โ that is the entire problem this solves, and it also means there is no shortcut. Your community starts at zero and grows from the show.
You cannot import your Apple Podcasts reviews. They stay where they are.
Getting the first hundred in
Since you cannot import anyone, the only channel that matters at the start is the show itself โ which happens to be an unusually good one.
Say it in the episode, not just the show notes. A spoken invitation from the voice someone has been listening to for two years converts at a rate no link in a description will match. Give it a reason and a moment: "the discussion for this episode is in the community, come argue with me."
Make the first live recording the hook. Nothing converts a passive listener like being in the room while the thing they love is made. Announce it on the show, hold it in the community, and let attendance do the recruiting โ the events playbook covers the mechanics.
Then be patient in a specific way: seed the discussion yourself for the first several episodes. An empty thread under a new episode teaches listeners the space is dead. The general cold-start problem is covered in getting your first 100 members.
The bottom line
Downloads will never tell you who is listening. A community will, and the honest version of the payoff is not a bigger audience โ it is a knowable one.
Keep distribution where it is, give the discussion a permanent home, expect a small dense group rather than a proportional turnout, and let paid membership do what sponsorship will not for a devoted audience of two thousand. If you want that shape ready-made, the Podcast Community template ships with these five spaces configured.