Table of Contents
TL;DR: Most ghostwriting timelines you read online are wrong because they treat word count as the only variable. A serious project runs four to eight months, and the spread depends on whether the source material exists yet, whether the author is available for the interviews, how clean the structural decisions are at the start, and how many revision rounds the author requires. Here is the honest breakdown of where the months go, the conditions that push a project to the fast end or the slow end of the range, and how AI-assisted projects fit on the same calendar.
The honest range
A full ghostwriting project at my practice runs four to eight months from the contract to the finished manuscript. The range covers projects from roughly twenty thousand to one hundred seventy-five thousand words, which is the full span of what I take on. The spread inside that range is not driven by length alone. A sixty-thousand-word book with clean source material and a decisive author can finish in four months. An eighty-thousand-word book with thin source material and an indecisive author can take eight. The word count is one variable among several.
The question of where your project sits on the range matters because you are planning a launch, a speaking calendar, or a business event around the publication. The right answer to “when will it be done” depends on which factors are working for you and which are working against. So here is the breakdown of where the months go.
Month one: discovery and structure
The first month is not writing. It is figuring out what the book is, who it is for, what argument it makes, and how it should be structured. The work happens in interviews, working sessions, and outline iterations between the writer and the author. By the end of month one, the book has a working outline that the author has approved and a sample chapter that demonstrates voice, so the rest of the project knows what it is building.
Authors who underestimate this phase always regret it. The structural decisions made in month one determine whether the book holds together at the end. A project that skips this work in favor of “just start writing” usually ends up doing the structural work in month six instead, when the costs of restructuring are much higher. The four-to-eight month range assumes month one happened properly. The Book Discovery Intensive handles a more formal version of this work before any larger commitment is made, and authors who run an Intensive first usually compress their full project timeline because the structural work was already done.
Months two through five: drafting
The middle of the project is the actual writing. Chapters get drafted in sequence, the author reviews each one as it comes, revisions happen, and the manuscript builds across roughly four months of focused work. Each chapter takes one to three weeks depending on length and complexity. The author spends two to four hours per chapter on review and feedback, and the writer spends the rest of the time producing the prose.
The pace here depends heavily on the author’s response time. A chapter that goes to the author for review and comes back in three days keeps the project moving. The same chapter that sits with the author for three weeks moves the entire schedule by three weeks. Most projects that slip do so because the author got busy and the chapters stacked up unreviewed, not because the writer fell behind. Realistic scheduling builds in author availability rather than assuming it.
The final stretch: revision and finishing
The last month or two is full-manuscript revision, copy editing, and the editorial work that turns a finished draft into a published book. The author reads the whole manuscript with fresh eyes and identifies cross-chapter issues that were invisible chapter by chapter. Issues identified there get addressed by the writer. Copy editing happens, formatting decisions get made, and the manuscript becomes a publication-ready file.
This phase is often where authors who were on schedule fall behind, because the final review requires sustained attention that is easy to defer. A whole-manuscript read is twenty to thirty hours of author time, and that block has to be scheduled rather than wished into existence. Authors who plan the block in advance finish on time. Authors who try to fit it around other priorities watch the project slip by weeks.
What pushes a project to the fast end of the range
Several conditions compress the timeline. Source material that already exists, like transcripts of past talks, an existing blog with the right ideas, or a partial manuscript, gives the writer something to work from before the interviews even start. A decisive author who can make structural calls quickly without long deliberation keeps each milestone moving. A clean scope where the book is on one topic with a defined audience avoids the mid-project scope creep that often adds a month or two.
An author with protected calendar time for the project also helps significantly. The book that gets two hours of author attention every week finishes faster than the book that gets the author’s leftover time between client emergencies. None of these conditions require talent. They require planning and discipline before the project starts, which is the work the discovery phase is meant to do.
What pushes a project to the slow end
The opposite conditions stretch the timeline. Thin source material requires the writer to extract more through interviews, which takes more author time. An indecisive author who second-guesses structural decisions weeks after approving them produces real lost work. Scope that keeps shifting, where chapter five becomes a different chapter five in month four, requires redrafting that the original schedule did not include. An author with no protected calendar time produces the chapter-stack problem where work waits weeks for review.
The slow conditions are usually addressable in advance. The Book Discovery Intensive catches scope and structure problems before the project starts. A clear contract milestones the author’s review obligations, which makes the schedule honest rather than aspirational. Protected calendar time can be allocated at the start of the project rather than discovered in the middle to be missing. Authors who address these conditions honestly find their projects landing on the fast end of the range rather than the slow end.
How AI-assisted projects fit on the calendar
An AI-assisted book runs three to six months instead of four to eight, which is roughly a thirty percent compression. The compression comes from the labor split, where transcription cleanup, research summaries, and connective-section drafts run through the machine rather than through the writer’s hours. The author’s involvement stays the same: thirty to sixty hours of interviews and revision rounds, same as full ghostwriting.
The compression is real but is not infinite. Voice work still has to happen at human pace, because that is the only pace voice work can happen. Verification work on AI output adds some hours back. The structural decisions still take the same care in month one. A piece on the half-cost AI-assisted book covers the economics, and the timeline compression is the other benefit. Both come from the same labor split.
What this means for planning
If you have a publication date you need to hit, work backwards from it. Six months from launch is the latest reasonable start for a full ghostwriting project, and even that assumes the conditions on the fast end of the range. Eight months gives realistic margin. Less than four is not feasible without compromising quality. AI-assisted projects can run on three to six months from start to finished manuscript, which buys you some flexibility if you started planning later than you should have.
Authors who start late and try to compress an unrealistic schedule are the ones who produce books that read like they were rushed, because they were. A project that needs six months and gets four delivers a worse book than a project that needs six and gets six. The honest conversation about timeline at the start is the difference between a launch you are proud of and a launch you spend the next year explaining.