Latest
What You Have to Decide Before Anybody WritesWriting It Before You Need ItCross Training Covered Everything Except the Role That Mattered MostBehind the Book: You Don’t Own Anything AnymoreBehind the Book: The Woke VirusBehind the Book: Galactic InvasionWhat’s New at The Writing King: Week of November 8, 2026Alexander Zhidkov: Decision MakingJessi Szurek: Expand Your RangeYou Don’t Own Anything AnymoreThe Budget Decided How My Department Was ShapedWhy Your Competitor’s Book Is Working and Yours Would NotWhy Are These Guys Smiling? A Business Book That Became a Wrestling MemoirPangram Wants to Decide Who Gets PublishedWhat You Have Enough Material For Right NowWhen a Book Is the Wrong ToolThe Woke VirusGalactic InvasionChatGPT Turns Four: From a Free Research Preview to GPT-6What’s New at The Writing King: Week of November 1, 2026Diwali: The Festival of Lights and the Story Behind the LampsHow Much Water and Power Does Heavy AI Use Take? I Ran My Own NumbersBad Boys: Ride or Die (2024)Vesuvius Day: The Teenager Who Wrote Down Pompeii’s Last DayAnti-Communism Week: Remembering the Writers Communism SilencedVoyager 1 One Light-Day: Fifty Years to Travel One Day of LightVellum Added an Optional AI Feature. A Pile-On Killed It in a Day.Are AI Subscriptions Losing Money? The Gym Membership Math Says NoAI Terms Every Writer Should Know, and Why Each One MattersWorking While Sick: What 24/7 On Call Cost MeHe Banned AI From His Writing Group. His Own Cover Got Called AI Slop.Who Writes the Fake Fan Mail Authors Get? Inside the Scam CompoundsSMS Appointment RemindersJoe Rockey: Ghostwriting His BookDarrell Stern: Stop Being Invisible, Become UnmissableFree BooksHow to Turn Your Expertise Into a Book People Want to Read | The Expert MethodWhat’s New at The Writing King: Week of October 25, 2026Challenger Remembrance Day: The Engineer Who Wouldn’t SignJoel Salomon: The Truth About MoneyReddit Is Putting Up a Login Wall. Wikipedia Won’t Be Far Behind.Victoria Chemko: The Body Is the First TechnologySir Patrick Stewart: A TributeA Year in the Bank: ADHD, Face Blindness and the Freedom to Walk Out | The Impossible Puzzles Show, Episode 326A Yale Economist Says We Won’t Be Missed. He Forgot the Bread Line.Walter Koenig: A TributeAI Has Paid Off Outside Tech. Apollo Is Reading the Wrong Scoreboard.I Don’t Post Bad ARC Reviews. I Send the Author a Note.The Little Red Book of Stuff That Works!Your Kids Are Your Own Fault

The Most Common Way a Book Dies

TL;DR: After 54+ ghostwritten books, the three deaths I plan against have nothing to do with the draft. The first is silence: the client stops answering and the project stops. The second is the finished manuscript that never publishes, sitting in a folder while the author gets ready. The third is the book that publishes and does nothing. All three were decided in the first conversation, by a goal that never existed, couldn’t be reached, or needed an audience nobody intended to build. So I spend the most care on that conversation, and I say so when a book can’t get there.

Free tool: How long would your book take, how big is it, and should you hire a ghostwriter or write it yourself? The Book Planner answers all three.

Plan my book →

Books die three ways, and none of them involves the draft. I’ve written 54+ books for other people, and the deaths I plan against hardest are silence, a folder, and a quiet launch. Each one looks like a different problem. Each one has the same cause, and it was present in the first conversation.

All three are painfully avoidable. The author does the hard part, the talking and the remembering and the paying, and then the book dies of something one honest conversation at the start would have caught. Losing a project in the first hour is better for everyone than watching it die a year later in somebody’s drafts folder.

I’ve written 54+ books for other people, and the deaths I plan against hardest aren’t bad chapters.
Share on X

Think of a book as a seed. It can fail to sprout, it can sprout and never break the surface, or it can break the surface and produce nothing. A gardener who blames the seed for all three hasn’t looked at the soil. The soil is the goal.

How does a ghostwriting project stop?

The interviews go well. Then an email goes unanswered, then another, and there’s no argument or complaint to explain it. The project just stops, and nobody decides to stop it. Clients disappear mid-book often enough that my contract spells it out: thirty days without contact puts the project on hold, and sixty means it’s abandoned. I rank silence as the most common death of all, because it leaves no wreckage. Nobody has to say the book is dead. It just never gets mentioned again.

Usually the goal never existed. A book started because someone said you should write a book has nothing pulling it forward when the weeks get busy, and the first slow month wins. The books that finish carry a reason the client can say out loud, and when the slow month comes, the reason is what answers the next email.

Why does a finished manuscript never come out?

The cover slips. The final approval never lands. A round of revisions turns into a second round, then a decision to wait for a better time, and the manuscript sits in a folder for a year while the author gets ready. The money is spent and the work is complete, and that’s the most demoralizing failure there is, because there’s nothing left to do except the thing the author isn’t doing.

This one is a goal problem too, in disguise. The author wanted a book but hadn’t decided what it was for, and a book with no job has no deadline. There’s no reader waiting, no event to launch at, no reason this month beats next month. So next month wins, every month.

What happens when a book publishes and does nothing?

It’s out, it’s fine, and no speaking, no inbound, and no readers follow. The author posts about it, a few dozen people react, and that’s the launch. The book was the same book. The variable was whether anyone planned for the day after it printed, and nobody had, because the plan was to write the book and see what happened.

The authors I feel worst for are in this group, because they did finish. They wrote a good book, spent the money, and the silence told them that books don’t work. Nobody told them before the first interview that a launch needs an audience, and whoever took that project on owed them that conversation.

A good book with no plan is the quiet failure, and it teaches the wrong lesson. The author concludes that books don’t work, when what didn’t work was a launch to an audience that had never been built. The case studies show what a planned launch produced for books that were no better written than the ones that died unnoticed.

What do the three most common ways a book dies share?

The first conversation decided all of them. No goal, or a goal a book can’t reach, or a goal that needed an audience nobody intended to build. The writing was never the problem. In every case I can think of, the manuscript was fine, and the manuscript wasn’t what killed the book.

That’s why I spend the most care on that conversation.

A good book with no plan is the quiet failure, and it teaches the wrong lesson.

What’s the book for? Who’s it for? What has stopped you? When the book can’t get there, I say so, and the project waits until it can. A writer who takes the money anyway is selling a manuscript with no book behind it, and the manuscript will be delivered on time to a project that was already dead.

The three common ways a book diesThree causes of a failed book, each decided in the first conversation: no goal at all, a goal a book cannot reach, and a goal that needed an audience nobody intended to build. In every case the manuscript was fine. The writing was never what killed the book.Three ways a book diesAll three were decided in the first conversationNo goalNobody said what the book isforA goal a book can't reachAnd nobody said so before thework beganNo audienceThe goal needed readers nobodyintended to buildIn every case the manuscript was fine. The first conversation decided all three.
The three common ways a book diesThree causes of a failed book, each decided in the first conversation: no goal at all, a goal a book cannot reach, and a goal that needed an audience nobody intended to build. In every case the manuscript was fine. The writing was never what killed the book.Three ways a book diesAll three were decided in the firstconversationNo goalNobody said what the book is forA goal a book can't reachAnd nobody said so before the work beganNo audienceThe goal needed readers nobody intended tobuildIn every case the manuscript was fine. Thefirst conversation decided all three.

How do you prevent the silent death?

Give the client a job. Projects die of silence when the client has nothing to do between sessions and drifts. Projects survive when the client is building the audience, drafting the launch plan, or lining up the people who will receive the book, because those tasks keep the book present in his week. The recurring goal conversation, fifteen minutes in the middle of an interview, always produces that job.

And name the goal out loud, early, in words the client can repeat. A goal he can say is a goal he can defend to himself in the slow month.

A goal that lives in the writer’s notes does nothing for him at 11 p.m. when the email is waiting. I’d have every client say it in one sentence before the first interview, and if he can’t, the project isn’t ready to start.

How do you prevent the folder?

Attach the book to a date that’s not the author’s.

A speaking engagement, a board meeting, a conference, a client’s fiscal year. A book with an external deadline comes out, because someone other than the author is waiting for it. (See the free Book Planner) A book with only an internal deadline waits for the author to feel ready, and authors don’t feel ready.

That date should exist in the first conversation. If the author can’t name an event the book is for, the book is at risk of the folder before a word is written, and the conversation should produce one before the project starts. The guide to ghostwriting covers the questions that bring it out.

How to keep a book from dying
Move When Why it works
Say the goal in one sentence Before the first interview A goal he can say is one he can defend in the slow month
Ask what the book is for and who it is for First conversation No goal, or an unreachable one, kills the book early
Give the client a job Between sessions Building the audience keeps the book present in his week
Hold the recurring goal conversation Mid-interview, fifteen minutes It always produces the client’s job
Attach the book to an external date First conversation Someone other than the author is waiting for it
Plan for the day after it prints Before writing starts A launch needs an audience that was built in advance
Say so when the book cannot get there Before the money moves The project waits until it can do the job

My take

Bad writing almost never kills a book. The first conversation does. No goal, a goal a book can’t reach, or a goal that needs an audience nobody plans to build, and the book is dead before the first chapter. Say your goal in one sentence before the first interview. If you can’t, you’re not ready to start. Then take a job for the months in between, because projects die when the client has nothing to do.

Why is the goal the soil and the manuscript the seed?

I keep the seed because the metaphor assigns blame correctly. The seed is the manuscript, and the manuscript is almost never the problem. The soil is the goal, the audience, and the reason, and the soil is prepared before planting or not at all. A gardener who prepares the soil gets a plant from an ordinary seed. A gardener who doesn’t gets nothing from a perfect one.

Most of the effort in this business goes into the seed, and most of the failures come from the soil. Writers love talking about craft because craft is what they’re good at, and I understand the pull.

A writer who polishes the seed and never asks about the soil is still billing a client for a book that was dead before the first interview. Fixing that imbalance is what the first hour is for.

Find out whether your book has a reason to finish, publish, and reach readers before the money moves. The Book Discovery Intensive is that conversation. Most books pass. Some need a different book first, and it’s better to learn that in an afternoon than in a folder a year later. Connect with me on LinkedIn and tell me where your book is stuck. Part of The Ghostwriting Hub.

If a writer takes your money without asking what the book is for, who’s waiting for it, and what date it has to exist by, that writer has already failed you, however good the prose turns out. Ask those questions yourself if nobody asks them for you, because a finished manuscript nobody reads is a miserable way to learn that a book needed a reason.

From the author
Publish Your Book by Richard Lowe

Publish Your Book
Finished manuscripts die in a drawer. Publish Your Book is my self-publishing guide, with five platforms compared, so yours gets out and in front of readers.

Frequently Asked Questions

What is the most common reason a ghostwriting project fails?
The client goes silent. Emails go unanswered and the project stops without an argument or explanation. It usually means the goal was never real enough to keep the book going through a busy month.
Why do finished manuscripts never get published?
The author had no defined purpose for the book, so there was no deadline and no reader waiting. Revisions and cover decisions slip month after month while the author waits to feel ready.
Why do some published books produce no results?
Nobody planned for the day after publication. Without an audience built in advance and a launch plan, a good book publishes into silence, and the author wrongly concludes books don’t work.
How do you keep a book project from stalling?
Give the client a job between sessions, name the goal in words he can repeat, and attach the book to an external date like a speaking engagement or conference so someone other than the author is waiting for it.
Should a ghostwriter turn down a project?
Yes, when the book can’t do what the client wants. Saying so before the money moves prevents all three deaths. Taking the money anyway sells a manuscript to a project that’s already dead.

About the Author
Richard Lowe, professional ghostwriter

Richard Lowe is a professional ghostwriter and author with 113+ books authored and 54+ ghostwritten. Before writing full time he spent 33 years in enterprise technology, including 20 years as Director of Computer Operations and Technical Services at Trader Joe's. He writes nonfiction, fiction and memoir, and works with executives and experts on books that build authority.

More about Richard Lowe →

Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

0 comments

No comments yet. Yours can be the first.

Was this useful?

Leave a comment