The direct answer: how long should your author podcast be?
Most author solo episodes land best between 15 and 30 minutes, most guest interviews between 30 and 60 minutes, and most co-hosted conversations between 20 and 45 minutes. These spans are widely used planning conventions, not rules imposed by any listening platform. A 3,000-word script read at a conversational 150 words per minute runs about 20 minutes, which sits comfortably inside the solo convention. Budget two to three times the finished runtime for recording plus editing, so that same 20-minute episode needs roughly 40 to 60 minutes of production time.
Why episode length decides whether listeners finish
Completion rate shapes everything about a young author show. A listener who finishes an episode hears the book mention near the end, remembers the show favorably, and lets autoplay carry them into the next installment. A listener who quits halfway hears none of that. Length is the single easiest lever a new podcaster controls, because topic and delivery take months to improve while runtime can be fixed before the next recording session.
Short episodes get finished. A commuter can complete a 20-minute solo show in one car ride, one walk, or one dishwashing session. That single-session completion matters more than most beginners expect, because podcast apps track and reward shows that people actually finish. When episodes routinely run past 45 minutes without a guest earning that time, abandonment climbs and the show trains its own audience to sample rather than stay.
Length also signals respect for attention. Authors sometimes assume that a longer episode proves seriousness, as though a 90-minute recording demonstrates deeper expertise than a tight 22-minute one. Listeners read the signal in reverse. A focused episode tells a busy reader that the host prepared, cut the weak material, and kept only what serves the promise in the title. An overstuffed episode tells them the host recorded until tired.
None of this means every episode must be short. Interviews with substantive guests earn longer runtimes because the guest brings stories and credentials the audience cannot get elsewhere. Serial fiction and chapter-by-chapter read-alongs earn longer runtimes because the audience arrived specifically to stay inside the narrative. The principle stays constant across formats: the episode should be exactly as long as its promise requires, and one minute longer than that starts costing listeners.
How the tool math works, step by step
The calculator uses one core formula plus three lookup conventions. The formula converts a script into time. The conventions judge whether that time fits the chosen format. Understanding both layers lets you trust the verdict and adjust inputs intelligently instead of guessing.
The core formula divides script words by speaking pace. Runtime in minutes equals the word count divided by words per minute. With the default pace of 150 words per minute, a 3,000-word script gives 3,000 divided by 150, which is exactly 20 minutes. A 1,500-word outline gives 1,500 divided by 150, which is 10 minutes. A 7,500-word interview outline gives 7,500 divided by 150, which is 50 minutes. Every worked number on this page comes from that same division, so you can reproduce any result with pencil and paper.
Speaking pace defaults to 150 words per minute because that rate matches relaxed, clearly enunciated nonfiction delivery in English. The tool accepts values from 100 to 200. Values outside that range get clamped to the nearest edge, since anything slower usually indicates a reading problem and anything faster usually indicates a measurement error. Your personal pace is a planning assumption you refine by timing yourself, and the page below explains a one-minute test that nails it down.
Against the computed runtime, the tool checks the format band. Solo episodes compare against 15 to 30 minutes. Interviews compare against 30 to 60 minutes. Co-hosted episodes compare against 20 to 45 minutes. A runtime inside its band earns a passing verdict. A runtime below its band earns a short warning, unless the topic depth is set to quick tip and the runtime reaches at least 5 minutes, in which case the tool accepts deliberate brevity. A runtime above its band earns a long warning with instructions to trim or split. Anything past 90 minutes fails outright, because no standard author format supports that length for a single regular episode.
The editing budget multiplies the finished runtime by two and by three, then presents the span. A 20-minute episode shows 40 to 60 minutes of production. A 50-minute interview shows 100 to 150 minutes. This multiplier is an illustrative planning assumption, clearly labeled wherever it appears, and it covers both the recording session and the edit: re-takes, silence removal, leveling, show-note writing, and uploading. Interviews cluster near the triple end because guest audio needs cleanup that solo recordings never require.
Solo episodes: the 15 to 30 minute convention
Solo is the default format for author podcasters, and the 15 to 30 minute band reflects how solo listening actually works. One voice must carry the entire episode, which demands more from the listener than a conversation does. Fifteen minutes is enough room for a cold open, one substantial teaching block with a story, a book mention, and a close. Thirty minutes allows two full teaching blocks with examples. Past thirty minutes, a single voice starts sounding like a lecture unless the host is unusually dynamic.
Solo rewards preparation density. Because there is no guest to react against, every minute must be written or tightly outlined in advance. Hosts who outline only three bullet points and improvise for half an hour usually produce twenty minutes of repetition wrapped around ten minutes of content. Hosts who draft a full script or a detailed beat sheet deliver twenty minutes where nearly every sentence earns its place. The word count input is therefore doing double duty: it times the episode and it forces the preparation that makes solo work.
If your solo calculation lands under 15 minutes, first check the depth setting. A genuine quick tip of 5 to 12 minutes is a legitimate episode shape, and the tool says so explicitly. If the episode was meant to be a deep dive, add one worked example from your own books, answer one listener question on the topic, or merge two thin outlines into a single stronger show. If the calculation lands over 30 minutes, cut the weakest main block first; authors consistently overestimate how much of their material the audience needs and underestimate how much a single clear idea can carry.
Interview episodes: the 30 to 60 minute convention
Interviews earn a longer band because two voices create natural variety, and because guests bring material the host could never generate alone. Thirty minutes is the practical floor: anything shorter rarely justifies the scheduling, research, and audio cleanup a guest requires. Sixty minutes is the practical ceiling for a standard author interview, past which even strong conversations sag unless the guest is exceptional. The tool judges interview runtimes against this 30 to 60 minute span.
The word math works differently for interviews. Hosts rarely script a guest conversation word for word. Instead, enter the word count of the prepared outline plus the host questions, then treat the result as a floor rather than a ceiling, because guest answers expand every segment unpredictably. A 4,500-word interview outline at 150 words per minute computes to 30 minutes of host-side material, and guest responses typically carry the finished episode to 40 or 50 minutes. Experienced interviewers therefore aim the computed runtime at the lower half of the band and let the guest fill the rest.
Pre-interviews protect the band. A fifteen-minute call with the guest a week before recording reveals which questions produce stories and which produce one-sentence answers. Cut the dead questions before recording day and the episode lands inside the convention without painful post-production surgery. Record for the full hour if the conversation is strong, then edit ruthlessly; deleting a flat ten-minute stretch in the edit chair is always easier than wishing you had asked one more good question.
Co-hosted episodes: the 20 to 45 minute convention
A regular co-host sits between solo and interview. The banter supplies variety like an interview, but the familiar dynamic needs less setup than a guest appearance, so episodes can open faster. Twenty minutes gives two partners room for a cold open, two discussion blocks, and a shared recommendation segment. Forty-five minutes accommodates a deeper topic with genuine disagreement, which is the format at its best. Past 45 minutes, even good chemistry starts meandering, because neither host feels the time pressure a guest creates.
Co-hosted shows fail on length more often than the other formats. Two friends talking enjoy themselves, and enjoyment masks the moment the episode should have ended. The segment plan in the tool output exists largely to prevent this drift: when both hosts can see that main block two ends at the 28-minute mark, wrapping up becomes a shared obligation instead of one partner awkwardly playing timekeeper. Agree before recording who calls the transitions, and honor the minute marks even when the conversation feels good.
Word counts for co-hosts work like interview outlines. Script the cold open and the CTA word for word, outline the discussion blocks as bullet beats with target minutes, and let the computed runtime represent the planned skeleton. If the skeleton already exceeds 45 minutes before anyone speaks, the topic is two episodes wearing a trench coat. Split it now, while splitting costs nothing, rather than in the edit where it costs an evening.
Topic depth: quick tip, deep dive, or serial chapter
Depth tells the tool what the episode is trying to be, and it changes how borderline runtimes get judged. A quick tip delivers exactly one idea with one example and one action, and it is allowed to be short on purpose. A deep dive teaches a full topic with stories, objections, and nuance, and it needs the room its format band provides. A serial chapter continues an ongoing narrative or course, and its length should stay consistent from installment to installment so subscribers know what to expect.
Quick tips deserve deliberate use, not default use. A weekly five-minute tip between longer monthly deep dives keeps a feed alive during busy writing months. A feed of nothing but quick tips struggles to build loyalty, because listeners subscribe to shows that change their thinking, and single tips rarely do that alone. Mark an episode as a quick tip only when it keeps one promise completely; a thin deep dive mislabeled as a tip still disappoints, just faster.
Serial chapters need the most discipline of the three. Listeners experience a series as one long promise, so episode three running 40 minutes after episodes one and two ran 20 breaks an implicit contract. Decide the installment length before recording chapter one, enter the representative word count in the tool, and hold every subsequent chapter to the same band. When a chapter outline computes far outside the established length, that chapter contains two installments and should be divided at its natural cliffhanger.
Reading the tool output
The results panel answers four questions in order. First, the verdict states whether the computed runtime fits the format, using plain language and naming the exact minute count. Second, the metrics row shows the estimated runtime, the format band, the speaking pace, and the editing budget, each with a hint explaining its basis. Third, the segment table lays out every block of the episode with lengths, start times, and coverage notes. Fourth, the recommendations list gives the next two actions for the specific verdict, whether that means recording as planned, trimming, splitting, or expanding.
The editing note beneath the recommendations deserves a second read. It restates the 2 to 3x multiplier as an illustrative planning assumption and invites you to replace it with your own measured ratio after three episodes. That invitation is the difference between a generic calculator and a personal system. Track your real numbers — recording minutes and editing minutes per finished minute — and within a month you will plan production schedules no generic tool can match.
Run the tool once per episode during planning, not once per show. Formats drift, outlines bloat, and guest answers expand. A thirty-second recalculation before recording day catches the solo outline that quietly grew to 38 minutes and the interview prep that only supports 22. The cheapest edit is the one made in the outline.
The segment plan, block by block
Every generated plan follows the same architecture: cold open, intro with roadmap, one to three main blocks, book CTA, outro. The minute marks always sum exactly to the computed runtime, with the main blocks absorbing whatever time remains after the fixed segments. Short episodes get one main block; episodes from 18 minutes up get two; episodes from 40 minutes up get three. This section explains what belongs in each block and why the order rarely changes.
The cold open runs about ninety seconds in episodes over ten minutes, or about ten percent of shorter shows. Its job is the hook plus the episode promise in one or two lines. Open inside the topic, not before it: a striking sentence from your own experience, the surprising result, or the question the episode answers. Never open with housekeeping, greetings, or a theme song that delays the substance. Listeners decide within the first minute whether to stay, and the cold open is that minute.
The intro and roadmap run about the same length as the cold open. Name who you are in one clause, who the episode serves in one clause, then preview the blocks ahead in the order they will appear. This roadmap pays off twice: it orients first-time listeners, and it creates open loops that pull existing listeners forward. Keep biography minimal; the guest-free author show earns credibility through the teaching, not through credentials recited up front.
Main blocks carry the teaching, story, or interview questions. Two-block episodes typically split into problem then solution, story then lesson, or questions part one then part two. Three-block episodes add a middle movement: angle, counterpoint, payoff. Each block should keep a single promise that you could state in one sentence. If a block needs two sentences to describe, it contains two blocks and should be divided.
The book CTA sits after the final main block, roughly two-thirds through the episode, and runs about two minutes in full-length shows. Give exactly one action tied to the episode topic: the novel the technique came from, the nonfiction book that goes deeper, the reader magnet that continues the lesson. One action converts; three actions diffuse. Script this segment word for word even if nothing else is scripted, because unscripted pitches ramble and rambling pitches fail.
The outro runs about a minute and closes three loops: a one-sentence recap of the promise kept, credits for guests or sources, and a preview of the next episode. The preview is the most neglected thirty seconds in amateur podcasting. Telling listeners the next title and its promise converts a finished episode into a subscribed habit, while a vague see-you-next-week converts it into nothing.
Worked numbers, set one: the 3,000-word solo deep dive
Take the tool defaults: solo format, deep-dive depth, 150 words per minute, 3,000 script words. The division gives 3,000 divided by 150, which equals 20 minutes exactly. Twenty minutes sits inside the 15 to 30 minute solo convention, so the verdict passes. The editing budget multiplies 20 by two and by three, giving 40 to 60 minutes of production time.
The segment plan for this episode allocates ninety seconds to the cold open starting at 0:00, ninety seconds to the intro starting at 1:30, two main blocks of seven minutes each starting at 3:00 and 10:00, a two-minute book CTA starting at 17:00, and a one-minute outro starting at 19:00. Add those segments — 1.5 plus 1.5 plus 7 plus 7 plus 2 plus 1 — and the total is 20 minutes. Every mark tells the host where to be at every moment of the recording.
Notice what the numbers imply about preparation. Seven-minute main blocks at 150 words per minute each require roughly 1,050 spoken words, so each block needs about a thousand words of script or a beat sheet dense enough to sustain seven minutes of precise talking. Hosts who discover their outline only supports four minutes per block have learned, before recording, that the episode runs short — which is exactly the failure the tool exists to catch early.
Worked numbers, set two: the 7,500-word interview outline
Change the inputs to interview format, deep-dive depth, 150 words per minute, and 7,500 outline words. The division gives 7,500 divided by 150, which equals 50 minutes. Fifty minutes sits inside the 30 to 60 minute interview convention, so the verdict passes. The editing budget gives 100 to 150 minutes of production, reflecting the guest-audio cleanup interviews demand.
The segment plan scales up: the same ninety-second cold open and intro, then three main blocks dividing the larger middle, the two-minute CTA, and the one-minute outro. Three question movements fit naturally — the guest origin story, the craft discussion, the advice round — each with its own start time so the host can pace the conversation live. If the guest gives short answers and the recording wraps at 38 minutes, the episode still lands inside the band and the plan still describes what aired.
Compare the production cost honestly. One hundred to 150 minutes per interview episode means four monthly interviews consume roughly seven to ten hours including scheduling and correspondence. Authors considering a weekly interview show should multiply before committing: 50 episodes a year at this length is a part-time job. A biweekly or monthly interview rhythm, supplemented by shorter solo episodes, sustains most author shows far longer than an ambitious weekly schedule that collapses by spring.
Illustrative hypothetical example one: the cozy mystery tip show
The following example is illustrative and hypothetical, with invented numbers chosen to show the method rather than describe any real podcast. Imagine a cozy mystery novelist who records solo quick tips about plotting, releasing one short episode each Tuesday. She drafts 1,050 words of script, speaks at a measured 150 words per minute, and selects solo format with quick-tip depth.
The tool divides 1,050 by 150 to get 7 minutes. Seven minutes falls below the 15 to 30 minute solo convention, but because the depth is set to quick tip and the runtime clears 5 minutes, the verdict passes with a note that the brevity is deliberate. The editing budget shows 14 to 21 minutes of production, which the novelist can complete in a single lunch break. The segment plan gives her one main block of about four minutes between the compact open and the CTA, which matches a one-idea episode perfectly.
Her CTA strategy fits the shape. Each tip ends by pointing at the novel where the technique appears in action, rotating through the backlist across weeks. Because the episodes are short, listeners actually reach the CTA instead of abandoning midway, and because the tips are genuinely useful, the pitch feels like a continuation rather than an interruption. The hypothetical lesson: short episodes convert better than long ones when the promise is small and fully kept.
Illustrative hypothetical example two: the memoir co-hosts and their serial
This second example is also illustrative and hypothetical, with invented figures demonstrating how serial planning works. Picture two memoirists who co-host a show chronicling their parallel book projects across a twelve-part series. They outline each installment at 4,500 words, speak at 150 words per minute, and select co-host format with serial depth.
The tool divides 4,500 by 150 to get 30 minutes. Thirty minutes sits inside the 20 to 45 minute co-host convention, so the verdict passes. The editing budget shows 60 to 90 minutes per installment, and twelve installments imply roughly 12 to 18 hours of total production — a number the pair can schedule across a quarter. The segment plan gives two main blocks of about eleven minutes each, which maps neatly onto the two authorsAlternating updates plus one shared craft discussion.
In week seven, one partner drafts an 8,000-word outline covering a dramatic revision crisis. Entered into the tool, 8,000 divided by 150 gives about 53 minutes, which exceeds the 45-minute co-host ceiling and earns a long warning. Following the recommendation, the pair splits the material at its natural cliffhanger — the moment the revision collapses — into two 26-minute installments. The hypothetical lesson: serial consistency is a promise to subscribers, and the tool catches the installment that would have broken it before recording day.
Finding your true speaking pace
The 150 default is a starting assumption, not a prescription, and personalizing it takes one minute of effort. Print or open 150 words of your own prose — about half a typical manuscript page — and read it aloud at your natural podcast delivery while timing yourself. If you finish between 55 and 65 seconds, the default fits you. If you finish in 50 seconds, your pace is closer to 180 and every runtime in the tool will run short for you until you update the input. If you need 70 seconds, your pace sits near 130 and scripted episodes will run long.
Re-test under recording conditions, because performance pace differs from practice pace. Adrenaline speeds most beginners up by ten to fifteen percent in their first sessions, then relaxes toward normal by episode five. Nervous fast talkers should enter a pace ten points higher than their calm reading test for the first month. Deliberate dramatic readers, especially fiction authors performing scenes, should enter a pace ten to twenty points lower, since pauses and emphasis consume time the raw word count cannot see.
Outlines need a different conversion than full scripts. A bullet outline compresses many spoken words into few written ones, so dividing outline words by 150 underestimates the episode. As a working rule, treat each detailed outline bullet as roughly one spoken minute and each bare topic phrase as thirty seconds, then sanity-check the total against the tool result. After two or three episodes, compare your predicted runtimes against the finished audio and derive a personal outline-to-minutes ratio that replaces the generic rule.
The 2 to 3x editing budget, explained
Beginners consistently estimate production time as equal to episode length, as though a 20-minute show takes 20 minutes to make. The 2 to 3x multiplier corrects this by accounting for everything around the finished audio. Recording itself usually takes 1.2 to 1.5 times the finished length, because of re-takes, pauses, throat clearing, and moments where the host stops to rethink a sentence. Editing takes another 1 to 1.5 times for cutting mistakes, removing long silences, leveling volume, adding the intro music, and writing show notes with links. Uploading, scheduling, and promotion add a final layer that belongs in the calendar even though it is not strictly audio work.
Solo episodes cluster near double. A practiced solo host with a full script, a quiet room, and a simple template can record a 20-minute episode in 25 minutes and finish it in another 20, landing near 45 minutes total. Interviews cluster near triple. Guest tracks arrive with different microphones, different rooms, and different noise floors, so cleanup, cross-talk removal, and leveling add an hour the solo host never spends. Remote recordings with connection glitches cost more still, which is why experienced interviewers record backup tracks and budget at the high end.
Use the multiplier for scheduling, then outgrow it with data. Block the full assumed window on your calendar for the first three episodes — for a 20-minute solo show, a full hour per episode. Record the actual start and finish times of recording and editing separately. By episode four you will know whether your personal ratio is 1.8, 2.4, or 3.1, and from then on your own number replaces the illustrative assumption everywhere in your planning. Authors who skip this measurement keep wondering why podcasting eats their writing mornings.
Placing the book CTA for maximum response
One clear call to action outperforms three vague ones in nearly every author context, and placement matters as much as wording. The tool positions the CTA after the final main block, roughly two-thirds through the episode, because that moment combines maximum trust with remaining attention. The listener has received the full lesson, feels grateful, and still has a few minutes left. Asking at this point converts gratitude into clicks.
Opening-minute pitches invert this logic and usually fail. A book mention before any value has been delivered asks the listener to trust an unproven host, and it teaches the audience that the show exists to sell rather than to serve. Pre-roll sponsor reads work for established shows with large audiences; for a growing author show, the opening minute should spend credibility, not extract it. Mention the book early only as landscape — a clause inside the intro, such as the novel the example comes from — and save the actual ask for the CTA block.
Script the CTA word for word and keep a log of variants. Write the exact forty to sixty seconds of spoken pitch, including the title, the one-sentence hook, and the precise destination such as the book page or the reader magnet signup. Read the same script for four episodes while noting click-through, then test one changed element — a different hook, a bonus chapter offer, a limited-time price — for the next four. Authors who treat the CTA as an experiment double its performance within a season; authors who improvise it every week never learn what works.
Edge cases and failure modes
Zero-word inputs produce an informational result rather than a verdict, and that is intentional. An empty outline cannot be timed, so the tool asks for the drafted or outlined count instead of guessing. Do not enter aspirational word counts — the episode you wish you had written — because the segment minute marks will describe an episode that does not exist. Enter what is actually drafted, read the verdict on reality, and let a short warning motivate the additional preparation rather than hiding it.
Extreme paces usually indicate input errors worth checking before trusting the output. A pace of 100 words per minute describes unusually slow, heavily paused delivery; if you entered it accidentally while meaning 160, every runtime will read far too long. A pace of 200 describes auctioneer speed no listener enjoys for twenty minutes; if reached by a typo, every runtime will read far too short and thin episodes will falsely pass. When a verdict surprises you, verify the pace input first, the word count second, and the format selection third.
Guest episodes break word math in predictable ways, and planning for the break prevents disappointment. Talkative guests expand a 30-minute plan into 55 minutes of gold that needs only light trimming — a pleasant problem solved by keeping the recorder running. Reticent guests compress the same plan into 22 minutes of short answers, landing below the interview floor through no fault of the preparation. The defense against reticence is over-preparation: twelve questions for a 30-minute slot, ranked by priority, so the host never runs dry while the guest warms up.
Series and seasons introduce a consistency failure that single-episode planning misses. An audience that subscribes during a run of tight 20-minute solos feels betrayed by a sudden unedited 70-minute conversation, even if the conversation is good. The betrayal is about violated expectations, not quality. Guard the feed by running returning formats through the tool every time and by labeling deliberate exceptions clearly in the title, so listeners choose the long episode instead of stumbling into it.
Equipment and environment failures masquerade as length problems in the edit. A room with echo, a microphone that picks up street noise, or a guest recording on a laptop across the room all inflate editing time far past the 3x ceiling, because cleanup passes multiply. When production consistently exceeds the budget, audit the recording chain before blaming the plan: a treated corner, a closer microphone, and a pre-recording level check often return the ratio to normal faster than any workflow tweak. The tool assumes clean source audio, and no segment plan survives a noisy original.
Burnout is the final failure mode, and length discipline is its prevention. Hosts who commit to weekly hour-long interviews usually love episodes one through six and dread episode ten, because each installment costs half a writing day. The sustainable author show matches its ambitions to its calendar: a biweekly 20-minute solo or a monthly 45-minute interview, produced for years, builds a larger audience than a spectacular weekly show abandoned by spring. Choose the cadence you can hold during deadline months, then let the tool keep each episode inside the band that cadence allows.
Questions authors ask next
How strictly should the format bands be treated? Treat them as strong defaults with explicit exceptions. A solo host with a proven, engaged audience can hold listeners for 40 minutes when the topic earns it, and a celebrity guest can carry 90. New shows earn no such latitude, because unfamiliar listeners grant no benefit of the doubt. Stay inside the band until download and completion data — not enthusiasm — tells you the audience wants more.
Does episode length affect discoverability? Indirectly, through completion and follow behavior. Listening platforms observe whether episodes get finished and whether listeners play the next one, and shows with strong retention earn more recommendations. Length influences those behaviors but does not directly rank anything. A brilliant 50-minute interview outperforms a mediocre 20-minute solo everywhere it matters; the bands optimize the odds, they do not override quality.
Should seasons have uniform lengths? Within a single series, yes, aim for consistency inside a ten-minute window. Subscribers build habits around expected commitment, and uniform installments respect that habit. Across different show lines — for example a monthly deep dive plus occasional quick tips — variety is fine as long as titles signal which is which. Label short episodes clearly so subscribers seeking the full show can skip without annoyance.
How do fiction and nonfiction author shows differ? Nonfiction teaching compresses well into solo deep dives, because lessons have natural outlines and takeaways. Fiction shows lean toward read-alongs, scene breakdowns, interviews with other writers, and serial narration, which run longer and looser. Both benefit from the same segment architecture; the fiction host simply fills main blocks with story and craft discussion instead of instructional steps.
What about video versions of episodes? Recording cameras alongside audio changes pacing and preparation but not the underlying math. Spoken words still convert at roughly the same rate, so the runtime estimate holds. Video adds setup time, lighting checks, and heavier editing, pushing the production multiplier above triple — an important scheduling note for authors syndicating to video platforms. Plan the audio episode first with this tool, then add the video overhead separately.
When should a show change its format? When the numbers or the host demand it, whichever comes first. Persistent short warnings across solo episodes suggest the host thinks in conversations and should add interviews or a co-host. Persistent long warnings suggest the material wants serial treatment or the host needs stricter outlining. Audience requests for a missing shape — guests, shorter tips, deeper dives — confirm what the verdicts already whispered.
Where the work continues
A podcast builds the audience, but finished audiobooks capture the revenue that audience creates, and listeners who trust your voice convert naturally into audiobook buyers. The Audiobooks destination at /create-audiobook carries this planning forward into narration decisions, production options, and distribution steps for turning manuscripts into sellable audio. Use the episode lengths and pacing numbers you calculated here as your baseline, then continue into audiobook production with realistic expectations already in hand.
A recording-week routine that holds
Turn the tool into a weekly habit with a simple sequence. Draft or outline the episode early in the week and enter the real word count, pace, and format the moment the draft exists. Read the verdict and adjust the outline the same day, while changes cost minutes instead of editing hours. Record from the printed segment plan with its minute marks visible, glancing at the clock only at block boundaries. Edit inside the budgeted window, publish with the scripted CTA, and log the actual production minutes beside the estimate. Within a month, the routine runs itself, and episode length stops being a question and becomes a standard your show is known for.