Your members are not short of interest. They are short of screen time. The person who bought your course has a forty-minute commute, a dog that needs walking twice a day, a gym session, a washing-up shift, and a school run, and in every one of those windows their hands and eyes are busy while their ears are completely free. Video cannot reach any of it. Audio can. A private podcast is simply the plumbing that puts your course into those windows, in the app they already open twenty times a week. Disclosure before we start: we make Drry, a platform that includes exactly this, so we are not a neutral narrator. Most of what follows is true whatever tool you use, and we will point at ours only where it is genuinely the answer.
What a private podcast actually is
Strip away the marketing and a podcast is one file: an RSS document listing episodes, each with a title, a description, and a link to an audio file. A podcast app reads that document every few hours and downloads anything new. That is the whole mechanism, and it has not meaningfully changed in twenty years, which is exactly why it is a good thing to build on.
A privatepodcast is the same document with two changes. First, the address is long, random, and not published anywhere, so it cannot be guessed or found. Second, the feed carries a block tag that tells Apple and the other directories not to list it, so it never appears in a search result. Members do not find it, they are given it: they copy a URL and paste it into their app under "add a show by URL", which every serious podcast app supports.
Everything else comes free, and this is the underrated part. You do not build offline downloads, a lock screen, CarPlay support, a sleep timer, variable speed, or a resume position. Apple, Overcast and Pocket Casts already built all of it, and they are better at it than any course platform will ever be. You are borrowing an app your member already trusts and already has on their home screen.
The maths of unclaimed attention
Here is the argument in numbers rather than adjectives. Take a member with a thirty-minute commute each way, five days a week. That is five hours a week of attention that no video course on earth can touch. Add two half-hour dog walks and you are at six. Now take your course: say twelve lessons at twenty-two minutes each, which is four hours and twenty-four minutes of material.
None of that requires new material. That is the whole point. The course exists, the recordings exist, and the members exist. What is missing is a format that fits the shape of their day.
Four ways to build one, and what each costs you
- A dedicated private-podcast tool. Purpose built, genuinely good at this one job, and a second subscription on top of the platform you already pay for. The real cost is rarely the money: it is that your listeners now live in a second system, wired to the first with an automation that you will discover has silently stopped working three months from now, usually when someone cancels and keeps receiving episodes.
- A public podcast with a paywall pitch. Cheap, easy, and not actually private. Fine as marketing, useless as member value, because the thing your members paid for is now free to everyone.
- Upload the audio to your course platform. Better than nothing, and it is where most people stop. The catch is that it only plays in a browser tab, which means no offline listening on the underground, no lock screen, and no automatic new-episode download. Several major platforms also cap how large a single audio file can be, which quietly rules out the workshop recordings that most deserve to be audio.
- A platform where the feed is built in. One upload, two destinations: a player inside your community and a private feed for the app. Nothing to sync, and access is decided in one place, so a lapsed member loses both at once. This is what we built, and it is the option we would pick even if we had not.
Making the audio: three routes, easiest first
Route one, strip the video you already have. Most course lessons are a person talking with occasional slides. The audio track of that lesson is a perfectly good episode on its own, and extracting it takes seconds. Listen back to the first one before you publish twelve: if it is full of "as you can see on this screen", either record a ten-second audio-only intro that sets up what they cannot see, or leave that particular lesson as video. In Drry this is one button on the lesson, which produces an mp3 and files it in your audio library as a draft for you to title.
Route two, record audio first. Once you see what people listen to, some things are better made as audio from the start: the weekly pep talk, the mindset piece, the Q and A answer that did not need a screen. These are also, conveniently, the fastest things you will ever make. A phone in a quiet room with a coat over your head genuinely sounds fine. A $60 USB microphone sounds better. Nobody has ever cancelled over room tone.
Route three, record your live calls. If you run group calls, the recording is already a workshop nobody has time to re-watch. As an episode it gets consumed. Trim the first three minutes of small talk, say one sentence at the top about what this call covered, and publish it.
The setup, end to end
- Pick the first five episodes. Not the whole course. Five is enough for someone to build a habit around, and short enough that you will actually finish the job this week.
- Order them for a listener, not a curriculum. Podcast apps show newest first by default. If your material is strictly sequential, number the titles ("01. Why most plans fail") so nobody starts at the end.
- Write descriptions people will read on a lock screen. One line on what this episode is for. That text is the only context a listener gets at 7am.
- Add cover art. A square image with a readable title. It is the thumbnail in their app and it is how your show looks like a real show.
- Tell members it exists, twice. Once at launch, once a fortnight later, and then put it in your welcome sequence for good. The single biggest reason private podcasts underperform is that half the members never learned there was one.
- Include the two-line instruction every time. Copy your link, open your podcast app, choose "add a show by URL", paste. People who have never done it assume it is complicated; it takes about fifteen seconds.
The security question, answered properly
Every coach asks the same thing: what stops a member forwarding the link to five friends? The honest answer is nothing, in the same way nothing stops them sharing a password. What you control is the blast radius, and there are three levels of it.
- One shared feed for everyone. The weakest version. A single leak means rotating the URL for your whole membership, and every member has to re-add the show.
- A unique link per member.Now a leak is one person's problem. You revoke that link, they get a new one, and nobody else is disturbed.
- A link that re-checks access on every poll. The version worth insisting on. The feed asks, each time an app refreshes it, whether this person is still a paying member. Cancel, and the episodes stop arriving with no admin from you at all. This is how Drry does it, and it is the difference between access control and an honour system.
Add the directory block tag on top, and your content is not discoverable, not indexed, and not portable to anyone who stops paying. That is a stronger position than most membership video sits in today.
What RSS cannot tell you
Here is the trade the category does not advertise. An RSS feed is anonymous by design: the app fetches a file, and no playback information ever comes back. So a podcast host can report a download and nothing more. It cannot distinguish an episode somebody finished on the train from one that auto-downloaded at 3am over wifi and was deleted unheard. If you have ever wondered why podcast analytics feel thin compared to video analytics, that is why, and no vendor can fix it without abandoning the standard.
Which is exactly what the vendors with real listening data did: they kept everyone inside their own player and gave up podcast apps. That is a real trade-off with a real cost, because the whole point was to reach the commute. The way out is not to choose. Keep a web player as the primary way to listen, where you can measure who pressed play and how far they got, and offer the feed as an addition for the members who want it in their app. You get portability for them and evidence for you, and the only reason it is rare is that most tools are one or the other by construction. On Drry the player is on every plan and the private feed is a Growth feature, so both halves are the same library.
Six weeks in, what to look at
Do not judge this on downloads. Judge it on three things. First, adoption: how many of your members pressed play at all? If it is under a third, your problem is communication, not content. Second, finishing: of the people who start an episode in the player, how many reach the end? A ten-minute episode that half your members finish is worth more than a forty-minute one that nobody does. Third, and most important, renewals among listeners versus non-listeners. That is the number that tells you whether this was a nice-to-have or the thing that saved the membership.
The short version
Your members have hours a week you are not using, and audio is the only format that fits into them. A private podcast is an ordinary RSS feed with an unguessable address and a do-not-list tag, which means offline downloads, lock-screen controls, and automatic new-episode delivery arrive for free from an app they already have. You can build the first version out of the course you already recorded, in an afternoon, by stripping the audio out of lessons that were always just you talking. Insist on a unique, revocable link per member that re-checks access on every poll, so a cancellation does not leave someone listening for free. And keep a measured web player alongside the feed, because RSS will report a download and never tell you whether anyone actually listened. Start with five episodes and tell your members twice.
If you want the mechanics rather than the strategy, our audio and private podcast page walks through the player and the feed, and how to start a paid community covers the membership this is meant to keep alive.
Questions coaches ask
What is a private podcast, exactly?
It is an ordinary podcast feed with an unguessable address that only your members get. Technically it is the same RSS document any public show publishes, so Apple Podcasts, Overcast, Pocket Casts and the rest treat it like any other subscription: episodes arrive on their own, downloads work offline, and the lock-screen and CarPlay controls come free from the app. The differences are that the URL is unique per listener and revocable, and that the feed tells directories not to list it, so nobody finds it by searching.
Can someone share their private feed link?
They can paste the URL anywhere, so treat it like a password. What matters is what happens next: if each member has their own link, you revoke that one link and nobody else notices. If your setup hands every member the same URL, one leak means rotating the feed for everybody. Ask about this before you pick a tool. Feeds that re-check the member's access on every poll are better again, because a cancelled member stops receiving episodes without you doing anything at all.
Do I need to be on Apple Podcasts or Spotify?
No, and for a paid course you actively do not want to be. Directory listing is what makes a public show discoverable, and discoverability is the opposite of the goal here: this is content people paid for. A private feed adds a block tag that tells directories not to index it, and members add it to their app by URL instead of by search. Everything else about the listening experience is identical.
Will a private podcast cannibalise my course?
In our experience it does the opposite, because the competition for your course was never another course, it was the member never starting. Audio gets played in the gaps video cannot reach, and a member who listened to four modules on their commute is far more likely to come back and watch the one that genuinely needs a screen. Keep anything visual (spreadsheets, form checks, screen shares) as video, and let audio carry the parts that were always just you talking.
How do I know if anyone is actually listening?
This is the honest weak point of RSS, and it is worth understanding before you commit. A podcast feed can tell you a file was downloaded and almost nothing else, because an anonymous pull carries no playback telemetry: an episode that auto-downloaded overnight and was never opened looks exactly like one somebody finished. If knowing matters to you, keep a web player as the primary way to listen and treat the feed as an addition rather than a replacement, so at least some of your listening is measured properly.