> ## Content Index
> Fetch the complete content index at: https://dallas-test.ghostarch.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Writing in a Client's Voice: Your Ghost Blogging Superpower
- URL: https://dallas-test.ghostarch.com/writing-clients-voice-ghost-blogger/
- Published: 2026-09-21T19:53:00.000Z
- Updated: 2026-09-21T19:53:00.000Z
- Author: Admin
- Tags: Freelance Writing, Ghostwriting, Content Strategy

Writing in a Client's Voice: Why Most Ghost Blogger Style Guides Miss the One Thing That Actually Causes Drift

Here's a scene that plays out for almost every ghostwriter sooner or later, so I'll flag it up front as a composite drawn from patterns across the work, not one specific client: a founder hands back a draft and says, "This is good writing. It's just not me." He's not wrong, and he's not being difficult. In the interview, he talked in fragments: half-finished thoughts, "look," "honestly," "here's the truth" doing most of the connective work between ideas. The draft cleaned all of that into complete, tidy sentences. Grammatically, it's an upgrade. As his voice, it's a stranger wearing his byline.

What matters is understanding why that happens, because the "why" is what actually stops it from happening again. Voice drift isn't a discipline problem. You don't fix it by concentrating harder. Your own sentence-generation habits run on autopilot, and autopilot defaults to whatever patterns you've reinforced most, which is your own writing, not theirs. Every editing call you make without something concrete to check against drifts back toward your baseline. A style guide isn't an organizational nice-to-have. It's the only thing strong enough to compete with that pull.

**Being a Good Writer Is Exactly What Puts You at Risk Here**

The instinct that makes you good at this job, hearing when a sentence runs too long, sensing where a paragraph needs tightening, is the same instinct that quietly overwrites a client's voice if you let it run unsupervised. Say your client talks in short bursts. You tighten one of their rambling sentences into something crisper. It feels like competence while you're doing it. To the client, it just reads as off. Often they can't even name what's wrong, because recognizing your own voice is mostly unconscious, even for the person whose voice it is.

That's why a cheat sheet isn't something you check when you're unsure. You need it most exactly when you feel most confident, because that's when your own instincts are loudest and hardest to override.

**Where You Pull the Sample From Decides Whether the Sheet Works**

Written material has usually already been through someone else's editing pass. Build a cheat sheet from a client's About page or their best LinkedIn posts, and you're often reverse-engineering a previous ghostwriter's choices, not the client's actual patterns. Unscripted speech and low-stakes casual writing hold up better, because nothing stands between the thought and the output. A call transcript beats a polished writing sample for one simple reason: it's closer to the source.

Ranked by how unfiltered the material is:

- Call or voice memo transcripts (least filtered, most reliable for rhythm and habitual phrasing)
- Casual emails or Slack messages
- Comments they've left on other people's posts
- Old blog posts they wrote themselves, before they started delegating

From whichever source you can get your hands on, pull four things onto one page.

1. **Vocabulary tics.** The five words or phrases they default to. "Folks" versus "team." "Build" versus "create." These small, repeated choices carry more identifying signal than structure does, because a skilled writer can approximate structure on instinct. Word choice is much harder to fake without a reference sitting in front of you.
2. **Sentence rhythm.** Read three of their paragraphs out loud. Short and declarative, or does it wind through a few qualifiers before landing? As a rough gut check from years of doing this, tight conversational writers often run shorter than you'd expect on paper, and the story-first, warm talkers run noticeably longer. You don't need a precise number, you need to know which side of that line your client sits on, so you know which direction your own default needs to shift.
3. **Opinion strength.** Hedger ("it might be worth considering") or declarer ("this is the only way")? Writers default hardest to their own habit here, because hedging often feels like the safer choice on the page. Hedge on behalf of a declarer and the copy goes mushy, even with every sentence technically clean, because you've changed their relationship to the claim, not just the wording.
4. **The one hard "never."** Every voice has a line it doesn't cross: no swearing, no jargon like "synergy," no exclamation points, never opens with a question. This is the single highest-value item on the sheet, because it's binary. Rhythm and vocabulary are matters of degree, easy to drift on slowly without noticing. A "never" rule is either broken or it isn't. That makes it the fastest thing to check a draft against when you're short on time.

**Same Argument, Two Voices: A Composite Example**

This example is built from patterns across ghostwriting work generally, not any one client. Take a single idea, remote teams losing hours to async miscommunication, and run it through two different cheat sheets.

Client A: operations exec, blunt and data-first. The sheet says short sentences, no metaphors, lead with the number, never say "I feel," always say "the data shows." In voice: "Remote teams lose real hours every week to async miscommunication. That's not a guess, that's from internal surveys we've run. Fix the handoff, and you fix most of the problem."

Client B: startup founder, warm and story-first. The sheet says longer sentences, frequent "I," a personal struggle before the stat, sections that end on a question. Same core claim: "I used to think our remote team's problems were about tools. Slack, Notion, whatever. Then I actually watched where projects stalled, and it wasn't the tools at all, it was the gap between when someone finished their part and when the next person even knew to start. What's that gap costing you right now?"

The underlying claim never changed. Only the delivery did. Swap these two drafts between clients and both would reject them, correctly, and neither could fully explain why beyond "doesn't sound like me." That inarticulate rejection is itself useful information: it tells you the mismatch lives below the level of content, so content-level fixes won't touch it. Only voice-level ones will.

**Why Drift Shows Up Around Paragraph Three, Specifically**

The failure point clusters where it does for a reason, it's not random. In paragraph one, you're actively cross-checking the cheat sheet because you know you're establishing voice. By paragraph three or four, you've built up enough momentum to shift into flow-writing. That's a different mode entirely: you stop referencing outside constraints and start running on your own generative patterns, because that's faster and feels more natural. Your own rhythm doesn't creep back in slowly. It comes back the moment you stop actively holding it off, which is precisely when you stop checking the sheet.

So the fix is direct: keep the cheat sheet physically visible for the entire draft, not just at the start, and aim your self-check specifically at paragraphs three through five instead of reading the whole piece with the same level of attention throughout. You're not hunting typos there. You're hunting the exact point where your own rhythm starts showing through theirs.

**When "Doesn't Sound Like Me" Isn't Actually About the Cheat Sheet**

If a client keeps sending back vague "not quite" notes after you've built and followed a solid cheat sheet, resist the urge to keep guessing in the same direction. That just burns revision rounds without giving you new information. Instead, ask for a direct line-by-line markup: "I wouldn't say it this way, I'd say it like this." That question turns a feedback loop running on your inference of their preferences into one running on their actual word choices, which tells you far more than a general note like "make it punchier" ever will.

It's also worth checking whether the complaint is about voice at all. Sometimes "doesn't sound like me" really means "I don't agree with this take," a substance problem dressed up as a tone complaint, and no amount of rhythm-matching fixes that. Just ask: "Is this the wrong tone, or the wrong opinion?" That question forces a diagnosis before you attempt a fix, instead of guessing at the category and revising in the wrong direction.

**Why Similar-Sounding Clients Are Your Highest-Risk Combination**

Write for a few clients whose general register sounds alike on the surface, say, two direct, no-nonsense executives, and the risk of one voice bleeding into the other is higher than with clients who sound nothing alike. Your brain files "direct executive voice" as one bucket unless you force a distinction at the word-choice level. Two cheat sheets that both say "short sentences, no hedging" can look nearly identical at a glance, but the real boundary between them lives in the specific phrases each one would never touch. Keep each sheet in its own labeled doc, and reread the right one immediately before every session, even for a client you wrote for yesterday. The risk here isn't memory fading over weeks. It's the most recent similar voice you used quietly bleeding into the next one.

**What to Do Before Your Next Draft**

Before your next assignment, or before revising something that got vague pushback, pull one real, unscripted sample and build the one-page sheet: five vocabulary tics, a sense of their sentence length, hedge-or-declare tendency, one hard never. Keep it visible while you write, not just open before you start. When you self-edit, put your attention on paragraphs three through five first, since that's where your own patterns tend to sneak back in. And if the feedback still isn't landing after all that, stop guessing and ask for a line-by-line markup. One round of that will tell you more than three rounds of "close, but not quite."

This isn't a talent some writers are born with. It's ear training, and it comes down to knowing exactly four things to listen for, and exactly where in a draft you're most likely to stop listening.