How to Keep a Company Podcast Going Past Episode Ten

How to Keep a Company Podcast Going Past Episode Ten

How to Keep a Company Podcast Going Past Episode Ten

The launch goes well, then month four arrives. Here is why company podcasts quietly stop publishing, and what keeps one going through the year.

By Will Nash
17 September 2026

The launch went well. Four episodes out, the partners enjoyed it more than they expected to, the announcement posts did respectably. Then somewhere around month four the recording slot gets moved, and then moved again, and the show has not published for six weeks.

Almost no company podcast is cancelled in a meeting. It stops because the work quietly loses to something more urgent, week after week, and the warning signs are visible months before anyone says the word out loud.

The launch backlog hides your real production rate

Most teams bank three or four episodes before launch. That is sensible, and it also conceals the one thing you most need to know: how fast you can make episodes while doing the jobs you were already doing.

The buffer runs out somewhere around episode six, and only then do you find out your true rate. If it is slower than the cadence you announced, you are now visibly behind on a promise you made in public.

The fix is unglamorous. For the first couple of months, publish at the rate you can sustain without touching the backlog. Keep the banked episodes for holidays, illness, and the week everything goes wrong, which is what a buffer is for.

Cadence is a promise you make to your own team

Weekly is roughly fifty rounds of the same work in a year. Monthly is twelve. Firms choose weekly because it feels like it will build an audience faster, and then discover they have committed to a workload rather than bought an audience.

Fortnightly is unfashionable and survives much better. A show that publishes every two weeks for two years will beat a weekly show that stops in April, on every measure anyone actually cares about.

Seasons are easier to keep than open-ended runs

Commit to eight episodes with a stated end, then take a break. You get a natural review point, a reason to talk about the show twice rather than once, and you remove the low-grade guilt of an empty week.

Ending a season is a decision your audience can hear. Fading out is not.

One owner, and a handover that exists on paper

Most company podcasts are held up by a single person who cares about them. When that person changes role or leaves, nobody else knows how the thing gets made, and reconstructing it is more effort than quietly letting it go.

Write the process down while it is still boring to write down. Who books guests, who writes, where the files live, what the publishing steps are, which accounts hold what. It is the least interesting hour you will spend on the show and the one most likely to keep it alive.

Give it a result a senior person can repeat

A show with no visible return is the first line questioned when budgets tighten. It does not need a sophisticated attribution model to survive. It needs one honest sentence a partner can say in a meeting about who listened or what conversation it started.

Firms that report nothing get asked why they are still doing it, and they rarely have a good answer ready.

Cut the work before you cut the cadence

When it gets hard, teams reach for the episode count first. Often the better move is to reduce the production burden instead: shorter episodes, a simpler format, fewer demands on senior diaries, or building episodes from material your experts have already written rather than booking more studio time.

Your audience notices the gaps in the schedule. It does not notice how the episode was made.

When stopping is the right answer

If you are ten episodes in and cannot say who the show is for, or nobody inside the firm has used it for anything, ending it deliberately is a better outcome than a slow fade.

Record a short final episode, say the season is closing, thank the people who took part, and leave the archive up. A clean ending protects the credibility that a silent feed slowly erodes.

In short

Publish at the rate you can genuinely sustain rather than the one that sounds ambitious. Keep the buffer for emergencies. Write down how the show gets made before you need to. And give one senior person a true sentence about what it has done. The shows that make it through a year are rarely the best produced ones. They are the ones where those four things were handled early.

We are an AI-native podcast agency, and the reason our clients keep publishing is that an episode does not depend on getting four senior people into a room on the same afternoon. We build them from what your experts have already written and thought. If month four is where your show is heading, get in touch.

Related: In-House, Agency, or AI-Native: How to Resource a Company Podcast