Latest
What an AI Detector Score on Your Manuscript Is WorthThe One-Hour Call Before I Quote Your BookWhen a Client Thinks the Ghostwriter Used AIMonthly or Milestone: How Ghostwriting Gets BilledWhen Your Memoir Should Be a NovelWhat It Costs to Fix an AI-Written ManuscriptThe Clients Who Pay and VanishThe Quotation Marks That Get Authors SuedThe Work You Would Never Have StartedWhen Your Own Memoir Sounds Like BraggingWhat Belongs on a Copyright PageThe Hugging Face AI Agent Attack: An Operations ReadingBehind the Book: The Mysterious Island, Neb’s SideHow to Organize Decades of Memories Into a MemoirWhy Rotten Tomatoes Sucks: The Score Does Not Mean What You ThinkWhy Amazon KDP Sucks: They Terminated My Account OvernightIngramSpark: How I Publish Now and WhyWhy Fiverr Sucks for Ghostwriting: The Buyer’s SideWhy eBay Sucks Now: A Seller’s Numbers and a Buyer’s WarningThe Ghost Story TraditionThe Gothic TraditionThe Christmas Ghost Story TraditionResurrection as a Narrative StructureBooks to Give a WriterThe Beach Read ArgumentWhy It’s a Wonderful Life Failed on ReleaseWhat to Read in SpringWhat to Read in SummerWhat to Read in OctoberHow Warner Bros. Dismantled a $17 Billion Cartoon EmpireThe Imaginary Scarcity TrapThe Graph That Goes Vertical Is Usually Somebody Else’sSubstack Is Not Collapsing. The Promise Was.The Disasters That Happen to Ordinary PeopleToba: The Winter That Almost Ended UsJay Stifflemire: Nothing Ever Gets Written DownGeorgie-Ann Getton: I Forgot I Had Free WillAI Detection Cannot Be Evidence, and Publishing Is Using It That WayAI Consciousness Left Philosophy and Entered the LaboratoryThe Office Block Where the Bedrooms AreThe Web Got Fenced: What AI Search Costs Small SitesBlack Tuesday: The Web Ring War Nobody Outside It NoticedWhat the AI Visibility Industry Sells, and What the Evidence SaysBlack Tuesday: The Original ring-master.net Page, 2000Behind the Book: Peacekeeper, The Dissolution WarsBehind the Book: Real World SurvivalBehind the Book: Publish Your BookBehind the Book: ReincarnationBehind the Book: Sell Your BooksBehind the Book: Show Don’t Tell

What if it doesn’t sound like me?

This entry is part 4 of 9 in the series Ghostwriting for Skeptics

TL;DR: This is the most common fear in any ghostwriting consultation. It’s also the most preventable problem, because voice mismatch is a process failure, not a mystery. A working ghostwriter interviews you long enough to hear how you actually talk. Then he drafts in that voice, and revises with you until the page sounds like you how I capture your voice to you and to the people who know you.

Here’s what that process looks like. What to demand from any ghostwriter you consider. And the test to run on a sample chapter, before the project is too far along to fix.

The fear is worth taking seriously

You have heard horror stories. There’s the CEO whose business book reads like a corporate brochure and sounds nothing like the person who walks into a room. I’ve written about a memoir in the author’s own voice. There’s the memoirist whose autobiography reads like every other ghostwritten celebrity memoir, generic and flattened. And there’s the expert whose voice on the page bears no relationship to the voice their own colleagues recognize. Those books exist, and the fear of producing one isn’t paranoid.

The right move isn’t to dismiss the fear but to understand exactly what causes the failure and how a careful process prevents it. For more, see The Manuscript Doesn’t Sound Like Me. Now What?.

Voice mismatch happens for predictable reasons and gets prevented by predictable methods. how I capture your voice The authors who end up with books that don’t sound like them almost always worked with a writer who skipped the steps that capture voice, and the failure is visible in the process long before it is visible on the page. For more, see How long does ghostwriting actually take, and why it doesn’t depend on word count alone.

So you can spot the risk early, demand the right steps, and walk if you don’t get them.

How does voice capture fail?

A ghostwritten book ends up sounding wrong for one of three reasons, and all three are process failures instead of talent failures. The first is that the writer didn’t interview the author enough to learn the voice. They’d a few short calls, took notes, and started drafting from their own default style. The pages came out reading like the writer, not the author. The second is that the writer interviewed but didn’t record.

Voice lives in specific word choices, rhythms, and turns of phrase that human memory cannot retain accurately. Notes alone guarantee the author’s voice gets translated into the writer’s instead. The third is that the writer drafted without sharing a sample early enough for course correction. By the time the author saw the work, three chapters were in the writer’s voice, and fixing them would mean tearing up substantial work.

None of those failures are about whether the writer is talented. The most gifted writer in publishing will produce a book that sounds wrong if they skip the steps that capture voice. The least flashy writer with a disciplined process will produce a book that sounds exactly like the author. Process beats talent here, and the process isn’t a secret.

What does good voice capture look like?

A working ghostwriter who knows what they’re doing runs a process that looks roughly like this. Substantial recorded interviews early, usually several hours total, before any drafting starts, so the writer can hear how you actually talk when you’re working through real material out loud. Transcripts of those interviews kept as raw source material the writer keeps returning to throughout the project.

A sample chapter delivered early, sometimes within the first month, specifically so the author can react to whether the voice is right before more chapters are committed. Revision rounds where the author marks anything that doesn’t sound like them, with specific examples of how they’d actually say it, and the writer absorbs those notes into how they write the next stretch.

That process produces a book that sounds like the author because the writer has been listening to the author talk for hours, has the recordings to refer back to, and has been corrected early enough that voice misfires get caught before they multiply. A piece I wrote on why some books end up sounding flat and machine-generated covers the same dynamic from the AI angle, but the underlying point applies to human writers too. Voice failures are process failures, and good process prevents them.

What is the thirty-page voice test?

Here’s the single most useful test you can run on any ghostwriting engagement, and it works for any writer regardless of their reputation. After the writer has interviewed you and delivered the first sample chapter or first thirty pages, read it out loud to yourself in your normal voice. Mark every sentence you wouldn’t actually say, every word choice that’s not yours, every rhythm that feels off even if you cannot articulate why.

If the page comes back with significant marks, you have early evidence that the voice capture isn’t working, and you have it before too much has been committed to fix. A serious writer will welcome those marks, study them, and recalibrate. A writer who pushes back, defends the choices, or tells you to trust the process is the wrong writer. Voice is the author’s call, not the writer’s, and any writer worth hiring understands that completely.

The thirty-page test exposes voice problems while they’re still small enough to fix, and walking away after a bad thirty pages is a much cheaper outcome than finishing a book that doesn’t sound like you.

What to ask in any consultation

Before you hire anyone, the voice question deserves direct attention in the conversation. Ask how the writer captures voice. The answer should mention recorded interviews, transcripts, sample chapters early, and explicit revision rounds. Ask for an example of a project where the voice was right, with reference contact information if possible. Ask for an example where it went wrong, and how the writer caught and fixed it. The writer who has no examples of the latter is either inexperienced or not being honest.

Ask whether the writer is willing to deliver a sample chapter or short sample document early, at clear cost, before the larger contract begins. Some will, some won’t, and either answer can be defensible, but the writer who refuses to discuss it shouldn’t get your project. The voice question is too important to be relegated to faith.

Your role in keeping voice on track

Voice is collaborative, and the author has work to do too. The writer can capture how you talk only if you actually talk in the interviews. Authors who try to “be professional” or “sound writerly” during interviews give the writer the wrong voice to capture, and the book ends up sounding like the author’s idea of how they should sound instead of how they actually sound. Talk normally. Use the words you’d use with a friend you respected.

Tell the stories the way you’d tell them at dinner, not the way you’d tell them in a press release.

When you read drafts, mark everything that’s off, in your own words, with examples of how you’d actually phrase it. Don’t just write “this isn’t me” in the margin. Write “I’d say it this way instead,” and quote yourself. For more on capturing a client voice, hear this conversation. The more specific you can be, the faster the voice converges. A writer who has done this work for a while can correct on small amounts of feedback.

Collaboration runs short if you give the right notes and long if you give vague ones.

Frequently Asked Questions

Why do ghostwritten books sometimes not sound like the author?
In my experience it happens when the writer skips the steps that capture voice. That means too few interviews, no recordings to refer back to, or no early sample chapter that lets the author catch a problem before it spreads through several chapters. I’ve seen talented writers produce a mismatched voice because they drafted from their own default style instead of the author’s actual speech. A disciplined process prevents this regardless of how gifted the writer is, because voice mismatch is a process failure instead of a talent failure.
How does a ghostwriter capture my voice?
Through hours of recorded interviews early in the project, kept as transcripts the writer returns to throughout. A sample chapter delivered early so the author can react. Specific revision rounds where the author marks what doesn’t sound like them with examples of how they’d actually say it.
What is the thirty-page test for a ghostwritten book’s voice?
Read the first sample chapter or thirty pages out loud in your normal voice. Mark every sentence you wouldn’t actually say. If the page comes back heavily marked, voice capture is failing and you have caught it early enough to fix or to walk away cheaply.
What should I ask a ghostwriter about voice in the consultation?
How do they capture voice. Examples of projects where voice was right, with references. An example where it went wrong and how they fixed it. Whether they’ll deliver a paid sample chapter early. The writer who has no answer to those is either inexperienced or not being honest.
What if I don’t know how to describe my own voice?
You don’t need to describe it. You need to talk normally during interviews and mark what sounds wrong in drafts with examples of how you’d actually phrase the same idea. Specificity matters more than self-awareness. The writer translates your real speech into prose; your job is to keep that speech honest.

📝 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