How Long Should a Podcast Episode Be? A Guide for Business Podcasts

Quick take:

If you're publishing 45, 60, or 90 minute episodes because that's simply what you think a podcast is supposed to look like, I'd question that. Especially if the podcast exists to build authority for your business. Your listener might not be looking for company on a long drive, they might be a prospective client who clicked because an episode addresses the exact problem they're dealing with, and now you're asking them for 57 minutes.

Sometimes that's justified. Often it isn't.

Maybe the finished episode needs nine minutes, maybe 17, maybe the subject deserves 40. The point isn't hitting an arbitrary number. The idea should determine the runtime.

Part of the problem is what we've learned a podcast is supposed to be. Many of the shows that shaped the medium are built around long conversations with prominent hosts or guests, an hour is normal, two isn't unusual. But those shows often have a different job. Someone isn't clicking because they need an answer to one question, they like the host, they want company on a commute. Nothing wrong with that. It's probably just not the primary job of a founder podcast.

Say an architecture studio publishes What Should You Know Before Starting a Luxury Home Renovation. Someone finds it because they're considering a renovation, not looking for entertainment, they're evaluating something expensive and they have a question. Do they need 52 minutes? Maybe.

For a niche founder podcast, particularly a solo show, I like a simple constraint: can this idea be useful in 10 to 15 minutes. Not rushed, not superficial, useful. Say a wealth manager records How Much Cash Should You Keep Outside Your Investments. That's a clear question. As a listener I don't need eight minutes introducing the subject, seven minutes of background, and a tangent about a client from five years ago before the answer shows up at minute 23.

Answer the question. Explain the nuance. Give an example or two. Say where people tend to get it wrong. Finish. Maybe that's nine minutes, maybe 15. The constraint just forces a check on whether the episode is focused enough.

There's an assumption underneath long expert podcasts worth questioning. We associate length with depth, if I explain something for an hour I must be showing more expertise than someone who talks for 13 minutes. I don't think that's true. Expertise can also sound like knowing what matters and what doesn't.

Say an architect explains in 13 minutes why one particular decision routinely delays a renovation by six months. I finish understanding something I didn't 15 minutes earlier, and expertise got demonstrated without needing to teach me everything they know first. Then I might notice Why Your Renovation Budget Changes After Construction Starts, then When Should You Hire an Interior Designer vs an Architect. Now I've spent about 40 minutes with this person's thinking, entered through three separate problems I care about.

This is where length stops being a production decision and becomes a publishing one. Say a plastic surgeon records one 70-minute episode called Everything You Need to Know About Facelifts. Probably plenty of useful information in there. But split it apart:

Now there are five entry points into the doctor's expertise instead of one, five specific questions, five potential search opportunities, five pages a prospective patient might find or send to someone else. That's a lot closer to a publishing library than a single definitive episode.

This is why I don't automatically love the giant ultimate guide episode for an expertise-driven show. Inside a 75-minute episode called The Ultimate Guide to Building a Custom Home might be six different reasons for someone to discover you: when to hire an architect, what should happen before a construction quote, why the budget changes during construction, which decisions cause the biggest delays. If those are all buried inside one giant episode, the listener has to do the work of finding them. I'd rather make that editorial decision for them.

We've made podcast production heavy. Find the guest, research them, schedule, record for 75 minutes, edit, review, create promotional assets, get approvals, publish, start again. Then everyone concludes the podcast takes so much time. Sometimes it does. Sometimes that's just how it got designed.

Compare that with a founder who sits down once or twice a month and records four focused 10 to 20 minute episodes. Completely different publishing operation. If the goal is a library that compounds over years, that matters. A great podcast that disappears after eight episodes never gets the chance.

I don't want to replace podcasts should be an hour with founder podcasts should be 15 minutes, that's just another arbitrary rule in different clothes. If a conversation gets considerably more interesting at minute 30, keep going. If a case study truly requires 35 minutes, make it 35. A show can have a 12-minute episode this week and a 38-minute episode next week, nothing's gone wrong. Start with the idea, not the runtime.

Before recording, finish this sentence:

By the end of this episode, the listener should understand ___.

If you can't complete it clearly, the episode is probably too broad. If you can, ask how much time is needed to deliver that, which gives you an editorial constraint instead of an arbitrary runtime.

"By the end of this episode, the listener should understand why getting an accurate renovation quote before completing the design is difficult" sounds like an episode.

"By the end of this episode, the listener should understand luxury home renovation" is a category, not an episode, and trying to squeeze a category into one recording is exactly how you end up with something enormous.

I'd treat interviews a bit differently, since part of their value comes from exploration and chemistry rather than answering one tightly defined question. I wouldn't cut an excellent conversation at 20 minutes because a spreadsheet says the target's been hit. But I'd still question whether every guest automatically deserves an hour. If the conversation delivered what it promised at minute 34, stretching to 60 doesn't earn anything extra. What are the additional minutes doing, that's a useful question regardless of format.

No, not if it delivers something useful. For an expertise-driven show, a focused ten-minute answer can make the catalog easier to explore, someone discovers one question, then another, instead of committing to a 90-minute manifesto. That matters especially when the podcast also feeds a searchable publishing library, since one focused episode becomes one focused article a lot more easily than a sprawling conversation about everything does.

There isn't one universal answer. But for a founder or business podcast, particularly a solo expertise-led show, I'd start by testing 10 to 20 minute focused episodes rather than assuming 45 to 60 minutes is the minimum, then let individual ideas break that rule when they earn it.

The goal isn't a short podcast. It's every episode being as long as it needs to be, and no longer just because convention said so. Go back to that 57-minute episode. What are the extra 40 minutes doing? If they're making it better, keep them. If they're there because serious podcasts are supposedly long, cut them.

How long should a podcast episode be? There's no universal ideal length. For a focused solo business podcast, 10 to 20 minutes can be enough to answer one specific question with useful context and examples. Interviews, case studies, and complex subjects may need considerably longer. The subject should determine the runtime.

Is 10 minutes too short for a podcast? No. A 10-minute podcast can work particularly well when each episode answers a specific question. A short episode only becomes a problem when the subject feels rushed or incomplete.

Is 30 minutes a good podcast length? Yes, if the idea truly needs around 30 minutes. Instead of optimizing for a predetermined length, define what the listener should understand by the end and use the time necessary to deliver that.

How long should a solo podcast episode be? For expertise-led solo podcasts, testing whether an idea can be delivered properly in around 10 to 15 minutes works well. Some will finish sooner, some need 20 to 30 minutes. Focus matters more than hitting an exact runtime.

Should every podcast episode be the same length? No. A consistent format helps listeners know what to expect, but individual episodes don't need identical runtimes. A focused solo episode might run 12 minutes while an in-depth interview runs 40. The difference should reflect the content, not an arbitrary production target.

Founder Publishing — How Long Should a Founder Podcast Episode Be?

In the episode, I explain why I use the 10–15 minute test for focused founder episodes, how shorter episodes can create more entry points into your expertise, and when I think longer conversations absolutely deserve to stay long.

Episode length is only one part of the system.

The Founder Podcast Authority Audit looks at your positioning, editorial strategy, packaging, discoverability, publishing system and commercial path to identify where your biggest gaps actually are.

Take the Founder Podcast Authority Audit →