The Book Was Meant to Run Twenty Pages. It Grew to Seventy Without Losing His Voice.

Book Writing and Publishing Starts with Protecting the Author's Voice

| Ghostwriting a full-length business memoir for a senior industry leader meant absorbing a scope that more than tripled mid-project, while keeping one person's narrative voice consistent across dozens of profiles. Human writing and editing, not automated drafting, kept the manuscript authentically his from first outline to final proof. |

A manuscript that reads smoothly can still be hiding a project that grew far beyond its original shape. What started as a planned twenty-page book, built from an author's own notes and interviews, eventually became a seventy-page work carrying his full narrative voice, and the difference between those two drafts is where most of the real work happened.

The project was a personal book writing engagement for a senior, long-serving leader of a top-five company in the automotive components manufacturing sector. He came to the project with decades of first-hand industry experience and a set of dummy drafts he had already compiled himself: notes, interviews with other professionals in the field, and stories gathered over years. The brief was to turn that material into a finished, publishable book written in his own voice, not a generic industry account written around him.

What follows is how that book actually got made: where the original plan broke, how the team organised around a project that kept changing shape, and what review caught before the manuscript went to print.

Why This Book Writing Project Became Difficult

The first challenge was scale, and it showed up early. The book was commissioned as a twenty-page project. As work progressed, the author kept adding material he wanted included: additional stories, more industry context, more of the people he had interviewed over the years. The manuscript grew to roughly sixty pages, then to around seventy. Each expansion meant reworking existing sections rather than simply appending new ones, since new material often changed the shape of chapters that had already been drafted.

There was no fixed deadline in the usual sense. If anything, the opposite was true: the timeline kept extending because the author wanted new material folded in. That absence of a hard endpoint was its own kind of pressure, since the project had no natural stopping point to plan around.

Subject depth was the second constraint. Much of the book's value came directly from the author's own decades of experience: his read on how the automotive aftermarket had evolved, his relationships across the industry, his judgment about which stories mattered. A writer without that context could easily have missed why a particular reference or connection was significant. There was no separate subject matter expert to consult because the author was the expert, and the entire project ran on his knowledge and the material he had already gathered.

The constraints that did apply were publishing standards rather than industry regulation: proper acknowledgements, copyright clearance on every sourced interview and story, and care around plagiarism across material drawn from many different conversations. None of that showed up as a checklist item until it needed to.

The brief itself was clear at the outset but not static. As drafting proceeded, the author continued adding information he wanted represented, which meant the project ran on continuous revision rather than a single fixed scope agreed upon and left alone.

The Approach That Fell Short

The first attempt treated the original twenty page limit as fixed. The team tried to compress the author's material, his interviews, his stories, his industry observations, into that length. It did not hold up. There was simply too much material that mattered to fit meaningfully into twenty-pages, and forcing it into that space began to flatten the thing the project actually depended on: his voice.

Cutting for length is not neutral. When a manuscript is compressed too aggressively, tone and personality are usually the first casualties, because they take up more room than the facts they carry. Early drafts built to the twenty-page target read correctly, but did not sound like him.

The team made the case to the author that a longer format would serve the book better: it would preserve his voice and give the material the room it needed rather than trading depth for a page count. That conversation, more than any single edit, is what allowed the project to grow into its final shape across several rounds rather than staying artificially short.

How We Organized the Work

The workflow had three people from the team: a writer responsible for the manuscript, an editor or manager overseeing the work, and a designer responsible for layout and visual presentation.

The process was revision-led rather than fixed.

Capture the voice before writing a single page.

The very first interview was not about content; it was about how the author wanted his own voice and writing style represented on the page. That conversation set the standard against which the rest of the project was measured, and every later review circled back to it.

Write from his own material, not around it.

The author had already compiled dummy drafts from years of research, interviews, and notes. Rather than treating that material as raw input to be replaced with polished prose, the team wrote from it directly, preserving the specificity and the perspective that made it his.

Build revision into the process, not around it.

The workflow ran writer to editor to internal review, and only after that internal check did the material go to the author. The editor's review focused on flow, structure, and whether the writing matched the agreed approach to his voice. Multiple rounds of this cycle ran across the project rather than a single draft and a single revision.

Absorb growth by restructuring, not resisting.

When the author added new material, the team did not try to squeeze it into existing pages. Sections were reworked, chapters reorganised, and dummy copies revised so the additions fit naturally rather than reading as inserted afterthoughts.

What Review Caught

Two things came up in review more consistently than anything else. The first was whether the author's own narrative voice actually came through in a given passage, since that was the standard the whole project was built around. The second was factual accuracy, particularly around the industry professionals profiled throughout the book. Because much of the manuscript consists of interview-based material about other people in the field, every detail attributed to the author's account was cross-checked against his original dummy drafts and source material before it was considered final.

One specific catch stands out. Partway through the project, the author asked that certain words be removed from the manuscript entirely, including the abbreviation for electric vehicle. That meant a dedicated pass through the full text to locate every instance of the flagged terms and either remove or rewrite around them, a check that would not have surfaced from a general read through alone.

AI drafting tools were deliberately not used to write the manuscript. The author wanted the book written in a genuinely personal, human voice, and the team's own experience across the project confirmed that an automated first draft would not have captured the specificity of tone, references, and judgment that made the writing sound like him rather than a generic industry account. The manuscript was written and revised by hand throughout, from first outline to final proof.

What This Means for Anyone Commissioning a Book

A ghostwritten book built around one person's voice cannot be scoped like a standard content deliverable. Page counts and timelines should be treated as working estimates rather than fixed limits, because the material that actually makes the book worth reading rarely arrives in a shape that fits a predetermined length. The organisations that get the best results are the ones willing to let the scope grow when the material genuinely calls for it, rather than protecting an original page count at the expense of the voice the book was meant to carry.

If you are looking at a similar project, whether it is a leadership memoir, a company history, or a book built around one person's professional journey, the questions worth asking early are the same ones this project answered the hard way: whose voice is this, how will it be verified as the material grows, and who is checking it before it goes to print.

Lexiconn works on exactly this kind of writing, from ghostwritten books to long-form editorial content that has to sound like one specific person rather than a house style. If you have a project like this in front of you, you can book a meeting with us here to talk through what it would take.

FAQs

What happens when a book project outgrows its brief?

This one was commissioned as a twenty-page project and reached seventy. The scale changed early, and there was no fixed deadline in the usual sense; the timeline kept extending as the author added material. The work was reorganised around the larger shape rather than trying to hold the original plan.

How do you keep one author's voice across a manuscript that keeps growing?

By treating voice as the constraint that does not move, even when scope does. Much of the book's value came from the author's own decades of experience, so the writing had to carry his phrasing and judgement rather than a house style applied over the top.

What standards apply to a business memoir?

Publishing standards rather than industry regulation: proper acknowledgement, permissions, and the conventions a reader expects from a full-length book. That is a different review discipline from regulated marketing content.

What should someone commissioning a book expect?

That the brief will move. A book brief can be clear at the outset and still change as drafting proceeds, because the author keeps thinking. The useful question is whether the team can absorb that without losing the voice or restarting the manuscript.