TL;DR: A serious book project takes thirty to sixty hours of your time across four to eight months, even with a ghostwriter. Those hours cluster at specific moments, so protect them on your calendar. Authors who underestimate the load watch the project slip while the writer waits, and the book arrives worse than it should have.
I tell every client on the first call that a book is a months-long relationship between two adults, with honest communication both ways. The hours are where that stops being a nice sentence and turns into your calendar. You can’t hire your way out of them, and anybody who tells you otherwise is selling you a thinner book.
How many hours does a ghostwritten book demand from the author?
A ghostwritten book at my practice requires roughly thirty to sixty hours of author time across the full project, regardless of whether the engagement is full ghostwriting or AI-assisted my ghostwriting process. The hours aren’t negotiable in the sense that compressing them produces a worse book.
Authors who give the project ten hours get a book that reflects ten hours. It reads thin. It lacks the perspective only the author could supply. It disappoints the people it was meant to impress.
I learned to brief clients hard on this after one project. At the kickoff meeting I told the client it would take an hour or two of his time each week, and he said yeah, yeah, yeah. Then the project started, and he wasn’t available. Over and over, he wasn’t available. I kept writing, and every time I asked whether he’d reviewed a chapter, he said he’d get to it.
I delivered the finished book at the end. He’d never seen a page of it and hadn’t come to a single meeting after the kickoff. He said thank you very much, and that was the last I heard from him. It happens much less now because I’m very careful about the time conversation up front.
A writer can’t extract your material from someone else, because your material is in your head.Share on X
The range from thirty to sixty depends on the book’s complexity and the author’s working style. Memoir tends toward the higher end because the interview material is more serious. Business books with a clear methodology often run toward the lower end because the structure clarifies the work. Books with many living people who appear in them require more time on the relationships and decisions question. Books with extensive technical material require more verification time on the manuscript.
Where do your hours go in a ghostwritten book?
The biggest single category is interviews. They run twelve to twenty hours at the front of the project. They’re how your material gets out of your head and into the writer’s hands. The hours feel large in the moment. Each interview runs two to three hours and you’re exposed throughout. The time pays back across the rest of the project, because everything downstream is built from what came out of those sessions.
Exposed is the right word. People cry in these sessions, and when they’re embarrassed about it I tell them the feeling is part of the book. We stop, talk about something easy for a few minutes, and come back when they’re ready. That time counts too.
Chapter reviews are the next biggest category at fifteen to twenty-five hours total, spread across the middle months of the project. Each chapter you receive takes one to two hours to read carefully and another hour or so to write up real feedback. Across twelve to fifteen chapters, the hours add up to a meaningful commitment that has to fit alongside everything else you’re doing.
Structural decisions and revision rounds add another five to ten hours, often concentrated at the end. The whole-manuscript read at the end of the project is twenty to thirty hours of focused work that has to be scheduled in advance instead of fit around other priorities. Authors who try to compress that final read into stolen hours produce books with the kind of large-scale issues only fresh-eyes reading catches.
When are the busiest weeks for the author?
The hours don’t distribute evenly across the months.
The project is front-loaded with interviews in months one and two. Months three through five are steadier, with chapter reviews coming in waves of one or two per week. The end of the project, usually months seven and eight for full ghostwriting, is heavy again, with the whole-manuscript review and revision concentrated in a few intense weeks.
This pattern matters for planning. Authors who treat the project as a steady-state commitment of two hours a week throughout end up under-committing in the heavy periods and over-committing in the lighter ones.
The realistic pattern is two-week sprints of interview work at the start, two hours a week through the middle, then another two-week sprint at the end for the manuscript review. Authors who block their calendar to match this pattern finish on time. Authors who don’t block time for the heavy weeks usually slip by a month or more.
What can you not delegate in a book project?
Three categories of work in the project require the author and can’t be delegated to anyone else, including a writing partner, an executive assistant, or a co-author. The first is the interviews themselves. A writer can’t extract your material from someone else, because your material is in your head.
The second is voice approval on chapters. The judgment about whether the writing captures how you sound requires you, because nobody else knows what you sound like.
The third is the real editorial decisions about what stays in the book, what comes out, and what the book argues.
Those decisions affect what the book is, and the person whose book it is has to make them. An assistant can read a chapter and report on it. The assistant can’t decide whether the chapter belongs in the book or whether the argument it makes is one the author wants to be on record making. That decision is the author’s.
What can you delegate in a ghostwriting project?
An assistant or staff member can defensibly handle some categories of work without compromising the project.
Fact-checking specific claims in chapters, where the assistant verifies dates, statistics, and quotes against original sources. Logistics coordination for interviews and meetings, where the assistant manages calendar and call setup. Initial screenings of chapter drafts for surface issues like typos, formatting, and obvious factual errors, where the assistant flags items for the author to review.
The pattern that works is the assistant handles mechanical preparation and follow-up, while the author handles real engagement with the material. The pattern that fails is the assistant tries to handle real engagement on the author’s behalf. That produces project drift in directions the author wouldn’t have chosen. A piece on how senior professionals can integrate AI tools through their assistants covers a related version of this delegation question.
How should you plan your calendar around a ghostwritten book?
The planning move that produces successful projects is blocking the heavy weeks on your calendar at the contract signing, before any work begins. The two-week interview sprint goes on the calendar at the start of month one. A whole-manuscript review week or two go on the calendar at the projected end of the project. Those blocks are protected from other commitments, the same way you’d protect a board meeting or a client engagement.
The book on this: The Ghostwriting Advantage is 48 chapters on what the process asks of you, including the interview hours, the review rounds, and the parts nobody can do on your behalf.
The middle months can be planned more flexibly, with two hours a week reserved for chapter reviews on a recurring basis. Authors who put the recurring time on the calendar at the start of the project produce chapter feedback consistently and keep the project moving. Authors who try to fit chapter reviews around other priorities end up with the chapter-stacking problem where work waits unreviewed for weeks. A piece on ghostwriting timelines covers the schedule from the project-length angle, and the time-commitment piece is the other side of the same planning question.
What happens if you underestimate the time a book needs?
Three predictable problems emerge when authors give the project fewer hours than it needs. First is project slippage, where chapters stack up unreviewed and the schedule moves out by weeks or months. The second is voice problems. The author wasn’t engaged enough in the interviews and reviews to give the writer what the book needed, and the result reads competent and flat.
There’s a fourth, and it’s the hardest on everybody: the author goes quiet. Clients disappear in the middle of a book more often than you’d guess, which is why my contract puts a project on hold after thirty days without contact and calls it abandoned after sixty. Some come back after a couple of months. After that, a returning project starts over.
The third is the late surprise. The author reaches the end of the project, reads the manuscript with real attention for the first time, and finds structural problems that should have come out in month three.
The fix for all of them is the time commitment at the front of the project.
Block the heavy weeks, reserve the recurring hours, and treat the project as a real obligation. The hours you skip get repaid as a worse book, a longer project, or both. The authors who give it the time end up with a book that sounds like them. The ones who don’t end up with a competent, flat book with their name on the cover, and that’s a lousy thing to pay for.
