How Much Time Does a Founder Actually Need to Spend on Their Podcast Per Week?

The number people quote is recording time. An hour of conversation, ninety minutes with setup and small talk. It's the visible part, so it's the part that anchors.

It's also the smallest part.

I can usually tell within the first thirty seconds of opening a file whether I'm looking at a two-hour edit or a five-hour one. Not from the content — from the noise floor, whether the guest is wearing headphones, whether there's a hard surface behind them. That judgement has nothing to do with how good the conversation was, and everything to do with how long my week is about to become.

The published estimates line up with what the work feels like. The Podcast Host puts a one-hour recording at roughly two hours of editing at baseline, rising to three-to-five hours for a highly produced episode with music, per-track compression and EQ. Rachel Corbett goes further: four to five times the length of the recording. Produce Your Podcast reckons three to five minutes of work per finished minute, which turns a half-hour show into an afternoon.

Even the optimistic end doesn't rescue the "few hours" claim. Ollar Studios suggests two to four times episode length if you're only cutting filler and balancing levels.

And all of that is editing alone. It excludes booking the guest, preparing, writing the notes, cutting clips, and putting the thing out.

Once you add those, Rise25's breakdown lands at 5–12 hours per episode even with parts outsourced. Their repurposing analysis is harsher: transcription, blog writing, social, distribution and promotion can run to 10–20 hours.

So: eight to twenty hours a week for a self-managed weekly show. Call it a second job with worse hours.

The bit everyone underestimates

It isn't the editing. Founders expect editing to be slow.

It's the guest admin. Rise25 puts coordination at three to six hours per confirmed guest — scheduling, prep notes, calendar changes, tech checks, chasing. That figure looks high to me for someone with an established network and a decent booking link. Halve it and the point survives intact.

Every guest generates a thread. A reschedule. A "sorry, can we push to Thursday". A "what should I prepare?" the night before. None of it is difficult and all of it is attritional, and it is the single most common thing I see quietly kill a show. Nobody quits podcasting because the edit was hard. They quit because there were four unanswered emails about episode nine and it was easier not to look.

Preparation is the other one, and it's the one worth protecting. Forty-five minutes to two hours, depending on whether you're reading a book or skimming a bio. It's the biggest single determinant of whether the episode is worth anyone's time, and it cannot be faked. Listeners can hear an unprepared host inside two minutes.

Weekly show, 45–60 minute episodes, interview format. Here's what the week looks like depending on how much you keep.

Doing everything, publishing audio, one LinkedIn post, moving on:

That's the floor. Not a few hours. More than a full working day, every week, forever.

Doing everything, plus the repurposing that actually compounds:

Nearly two working days. I've never seen a founder sustain this alongside running a company. Not once. People manage it for a quarter, occasionally two, and then something has to give and it's always the podcast.

Keeping the conversation, the guests and the prep, handing over the rest:

The "few hours a week" line isn't a lie. It's describing this last table. The people quoting it run produced shows and have forgotten that the reader is picturing the first one.

There's a reason I keep pushing on the arithmetic rather than the strategy. Podcasting has a worse survival rate than almost any other channel a business might try, and the cause is boringly consistent.

Analysis of Podcast Index data reported by AshMedia found that of 4.69 million indexed titles, only 10–11% are still publishing. A quarter released exactly one episode. Another tenth stopped at two. Just 36.5% ever reached ten. Forbes, citing Podnews in January, put the drop-off after episode three and named the cause as burnout and underestimating the work.

I should say the data isn't unanimous, because pretending otherwise would be convenient and wrong. WhichPodcast's survival research, looking at 22,451 shows already in their database, found 92% reached ten episodes, with the real attrition later — around 56% still going at episode 100.

Those two findings are almost opposites. The difference is what counts as a podcast: one dataset includes every RSS feed anyone ever generated, the other looks at shows that had already established themselves. I find the second more useful for anyone reading this, because you're not going to abandon it after one episode. You'll abandon it at episode twenty-two, in a quarter when everything else is on fire, and it'll be the only thing on your list with no external deadline attached.

Podbean's account of why podcasters quit matches what I see: people go all-in early — recording, editing, detailed notes, social — on top of a full job, and the workload produces exhaustion instead of momentum.

For a founder the cost isn't a lapsed hobby. AshMedia frames it as a consistency problem rather than a budget one, arguing the case for outsourcing is about protecting consistency most solo producers can't maintain. I'd put it more bluntly. A show that stops at episode eight has spent your money, used up goodwill with every guest who gave you an hour, and left a public, dated artefact of something your company started and couldn't finish.

If you want to know which task breaks first, it's the edit. Not because it's the hardest, but because it's the only one with nobody waiting at the other end. A guest booking has a person attached to it. A recording sits in the calendar. The edit is four hours alone with a file that nobody is chasing you for — so it slips to Sunday, then to next week, and then into the gap where the show used to be.

This is the question I'd actually work through before choosing a frequency, because the hours aren't interchangeable.

Four things are yours.

The conversation, obviously. That's the product.

The guest list, which for most founder-led B2B shows is the strategy rather than a supporting detail. Fame's analysis of B2B podcast returns makes the point that first-year value comes through the guests rather than the audience, and that matches what I see: the show works because of who agreed to come on it, long before download numbers mean anything. If you're inviting target accounts and people you want to know, that invitation carries your name. Handing it to an agency to fire out on autopilot destroys the only reason it works.

Editorial direction. What the show is, who it's for, what a good episode sounds like. You can delegate execution. Taste, no.

And preparation, partly. I can hand a host a research brief and a set of questions. I can't read it for them.

Everything else should go, roughly in this order: editing first, because it's the biggest block of hours and the most skill-dependent; then show notes and chapters, which take longer than anyone expects and are done badly on most shows; then clips and repurposing, which is an enormous time sink and highly systematisable; then publishing admin; then scheduling, which removes the most attritional part of the whole thing.

Take the first table, and mark every row either yours or not. What's left in the second column is your brief. The total is what it's worth paying to get back — and if you want that expressed in money rather than hours, our editing cost calculator does the sum.

Plenty of people will, and some of them should. A few choices change the maths more than any software will.

Batch record. This is the one that genuinely moves the needle. Block a day, record three or four episodes back to back. The Podcast Consultant notes most successful podcasters batch three to four per session, with vocal fatigue setting the ceiling rather than the clock. You stop paying the weekly cost of getting into podcast mode, you set up once instead of four times, and — as Rachel Corbett points out — you build a buffer, so flu or a bad fortnight doesn't break the streak.

It's a poor fit for anything news-reactive, and getting four guests into one Thursday is materially harder than getting one. Worth it anyway.

Record video whether or not you want video. Content Allies puts full video production at around 77% more expensive than audio-only, which sounds like an argument against it. It isn't, if you keep it simple. One camera, decent light, no crew.

The reason is that the alternative is worse. Deciding at month eight that you want YouTube and clips, and finding your entire back catalogue is audio-only, costs far more than a camera pointed at your desk ever would. You can throw video away. You can't retrofit it.

Fix what goes into the edit. Nearly every hour of remedial work traces to something that went wrong at the recording end. Laptop microphones. Tiled kitchens. No headphones, so the guest's track has your voice bleeding through it and every question needs surgery. A five-minute tech check the week before saves more editing time than any plugin, and our guide to podcast audio quality covers the parts software genuinely can't fix.

Publish less often. If the numbers say weekly doesn't work, go fortnightly. Do not run a rushed weekly show instead — that's the version that stops in March. A show that turns up reliably twice a month for three years is worth more than one that publishes eight times brilliantly and vanishes, and it isn't close.

Here's the exercise, and it takes twenty minutes.

Write out the tasks. Put hours against each one, honestly, including the guest admin you're tempted to round down. Mark what's genuinely yours. Multiply by the frequency you're considering.

Then picture month nine. A bad quarter, a board meeting the same week, and an episode that hasn't been edited. Would you still do it?

If yes, you've got a sustainable show and you don't need me. If no, that isn't a motivation problem and it won't be solved by wanting it more. It's a scope problem, and scope problems have solutions — fewer episodes, or fewer of the tasks.

The founders whose shows are still going after three years almost all worked this out early. They kept the conversation and the guest list, gave away the rest, and stopped treating the production hours as a test of commitment.

If you want to talk through what that looks like for your show, get in touch.