How to Brief a Ghostwriter So Content Sounds Like You (2026)

TL;DR: Ghostwriting fails at the brief, not at the writing. The founders whose content sounds like them don't hand over a topic — they hand over a raw take. Brief the input, not the output. Give your ghostwriter three things: a Voice Doc (who you are and how you talk), an Idea Feed (what you actually think this week), and a Review Loop (how you correct drift fast). Run a 20-minute voice download instead of writing a sample post, and stop editing for grammar — edit for whether it's a thing you'd say. Do that and "it doesn't sound like me" stops being a problem you have.

Here's the question almost every founder asks after their third ghostwritten draft: "Why doesn't this sound like me?"

It's the wrong question. The draft doesn't sound like you because you never gave the writer anything that sounds like you. You gave them a topic. "Write something about our Series A." "Do a post on hiring." A topic is not a voice. A topic is a Wikipedia prompt, and Wikipedia is exactly what you got back.

The problem was never the writer's talent. It's the brief. Great ghostwriting is a capture problem long before it's a writing problem — the raw material has to come from your head, in your words, before anyone can shape it. Get the brief right and the drafts start landing on the first pass. Get it wrong and you'll spend six weeks rewriting sentences and conclude, incorrectly, that ghostwriting doesn't work for you.

Why "it doesn't sound like me" is a briefing failure

Think about what actually makes your writing sound like you. It isn't sentence rhythm or word choice — those are downstream. It's the specific opinions, the numbers only you know, the customer sentence you can't stop thinking about, the take you'd defend at a dinner. Voice is a byproduct of having something particular to say. Strip that out and even a brilliant writer can only produce competent, generic prose.

When you brief with a topic, you've deleted everything particular before the writer starts. They're forced to fill the gap with the internet's consensus view — which reads like everyone and therefore like no one. This is the same reason raw AI output plateaus: not enough proprietary input going in. We covered the mechanics of that in our piece on how to write a LinkedIn post that doesn't sound like AI, and the fix is identical for humans and models — feed in the specific stuff.how to write a LinkedIn post that doesn't sound like AI

So the real definition of a good brief: a package of raw, unpolished, specific material that only you could have produced. Not a topic. Not a title. A take with the evidence attached. Reframing ghostwriting as voice capture rather than word production is the whole game, and it's worth reading the longer argument for that shift.reframing ghostwriting as voice capture

Brief the input, not the output

Call it the Raw Input Rule: never send your ghostwriter a topic when you could send them a take. The difference is stark.

• Weak brief (a topic): "Write a post about why hiring senior people early is smart."
• Strong brief (a take): "We hired a VP Sales at 8 people and it was a disaster — he needed a machine to run and we didn't have one yet. I'd tell any founder under 20 people to hire a senior IC who'll cold-call, not a leader who'll build slides. Cost us four months and a $180k comp package to learn that."
• The first produces a LinkedIn post that 10,000 other people could have written. The second could only be yours — it has a scar, a number, and a contrarian rule baked in.

The strong version took forty seconds to say out loud. That's the unlock: you don't write the brief, you talk it. Most founders can't face a blank compose box but can talk for three minutes about a decision they just made. Your ghostwriter's job is to turn the talking into the writing — but they can only do that if you give them the talking.

The Founder Brief Stack

A durable briefing system has three layers. Miss any one and the drafts drift. I call it the Founder Brief Stack: the Voice Doc, the Idea Feed, and the Review Loop.

Layer 1: The Voice Doc

This is the one-time (then lightly maintained) artifact that tells your writer who you are on the page. It's not a personality quiz. It's a working style guide with teeth. A good Voice Doc includes:

• Ten to twenty of your own past posts, emails, or Slack messages you'd be happy to have quoted — the raw sample of how you actually talk.
• Your non-negotiable opinions: the three to five hills you'll die on in your space. This is what gives future posts a spine.
• Words and phrases you say (and ones you'd never say). "I say 'ship,' never 'leverage.' I never use the word 'thrilled.'"
• Your rules of engagement: no engagement bait, no fake vulnerability, never dunk on a named competitor, always concede the other side has a point.
• Sentence-level tells: short paragraphs, one idea per line, a dry aside in parentheses, no exclamation marks.

The Voice Doc is what separates a ghostwriter from a content mill. If a writer or agency starts producing before building one, that's a red flag worth knowing about before you sign — we list the rest in our guide to hiring a LinkedIn ghostwriter.hiring a LinkedIn ghostwriter

Layer 2: The Idea Feed

The Voice Doc tells the writer how you sound. The Idea Feed tells them what you think this week. This is the layer founders skip, and it's the one that actually keeps content alive. Voice without fresh input goes stale in a month — you get well-written posts about nothing.

The Idea Feed is a lightweight, always-on capture habit. It doesn't need to be polished. It needs to exist. Feed it:

• Decisions you made this week and why — the trade-off is the post.
• Numbers you saw: a metric that moved, a benchmark that surprised you, a cost you didn't expect.
• Customer sentences: the exact words a prospect or churned user used. Verbatim beats paraphrase every time.
• Questions you got asked more than once — each repeated question is a post someone is searching for.
• Things you disagree with: a take on your timeline that's wrong, and the reason it's wrong.

One customer call can fill a week of Idea Feed on its own if you mine it properly — the transcript is a goldmine of exact phrasing, objections, and aha moments. We broke the whole workflow down in how to turn a customer call into a week of content.how to turn a customer call into a week of content

Layer 3: The Review Loop

The third layer is how you correct drift, and it's where most founder-writer relationships quietly die. Founders review drafts like an English teacher — fixing commas, swapping words, rewriting sentences — and the writer learns nothing except that you're annoying to work with. Line-editing doesn't transfer signal. It just produces a version you rewrote yourself, which defeats the point.

Review for one thing instead: is this a thing I would actually say? Then tell the writer why, in categories, not commas:

• "The opinion is too soft — I actually think this is a mistake, not just 'worth considering.'"
• "This example is generic. Use the real one: the deal we lost last quarter."
• "This sounds like a marketer wrote it. I'd never say 'unlock value.'"
• "Right take, wrong evidence — the number that matters is retention, not signups."

Feedback in categories teaches the writer your judgment, so next month's drafts need less correction, not the same amount. That's the compounding you're paying for. A good ghostwriter is really an operator who runs this loop for you — closer to a chief of staff for your content than a freelance typist. We made that case in our piece on the founder content operator.the founder content operator

How to run a 20-minute voice download

The single highest-leverage briefing habit is a recurring voice download: 20 minutes, talking, recorded, transcribed, handed over. It replaces the mythical "just write me a sample post" step that never happens because you're busy. Here's the exact sequence:

1. Block 20 minutes and hit record — voice memo, Loom, or a call with your writer. Talking, not typing, is the whole point.
2. Start with what you decided this week. Walk through one real decision, the options you weighed, and why you chose what you chose. Don't editorialize — just narrate.
3. Name one thing you disagree with. Someone said something wrong on your timeline or in a meeting. Say what, and say why they're wrong.
4. Read out one customer sentence verbatim. The exact words, not your summary of them. This becomes a hook.
5. Give one number and what it means. A metric, a cost, a benchmark — and the one-line implication for someone like you.
6. Answer the question you keep getting asked. Say it the way you'd say it to a founder over coffee, not the way you'd write it.
7. Stop at 20 minutes. Send the recording or transcript to your writer as the brief. That's it — no document to write.

One 20-minute download reliably yields three to five posts. Do it weekly and you've solved the input problem permanently — the writer never starts from a blank box, and neither do you.

What a great brief actually contains

If you want a checklist to hand your team or your agency, a complete brief for a single post has five parts:

• The take: the actual opinion in one blunt sentence, stronger than feels comfortable.
• The evidence: the number, story, or customer quote that earns the take.
• The audience: who this is for and what they'll do differently after reading.
• The rule: the transferable lesson a reader can screenshot and apply.
• The line not to cross: anything off-limits — a client you can't name, a metric you won't share, a competitor you won't attack.

Notice what's not on the list: a headline, a word count, a hook formula, a hashtag strategy. Those are the writer's job. Your job is the raw material only you have. If you're doing the writer's job in the brief, you've hired the wrong person or briefed the wrong way.

What NOT to do

The predictable ways founders sabotage their own ghostwriting, each one a fixable briefing habit:

• Briefing a topic, not a take. "Do a post on culture" guarantees a generic post on culture. Every time.
• Reviewing for grammar instead of truth. If your edits are commas and synonyms, you're rewriting, not directing.
• Approving drafts you're lukewarm on. Lukewarm approval trains the writer to aim for lukewarm. Only ship posts you'd defend.
• Going dark for three weeks, then dumping ten topics at once. The Idea Feed works because it's continuous, not batched in a panic. This is the same cadence failure that stalls most founder content.
• Outsourcing the opinion. You can outsource the writing, the editing, the scheduling. You cannot outsource what you believe — that has to come from you, every time.

The through-line: you're not hiring someone to think for you. You're hiring someone to make your thinking legible, consistent, and shipped — which is exactly why the brief is the part you can't delegate.

Frequently asked questions

How do I brief a ghostwriter so the content sounds like me?

Brief the input, not the output. Instead of giving a topic, give a raw take: your actual opinion, plus the number, story, or customer quote behind it. Build a Voice Doc so the writer knows how you talk, keep an Idea Feed of fresh raw material, and review drafts for whether they're true to you, not for grammar. The fastest way to supply raw material is a recorded 20-minute voice download rather than a written brief.

What should a ghostwriting brief include?

A complete single-post brief has five parts: the take (your opinion in one blunt sentence), the evidence (the number, story, or quote that earns it), the audience (who it's for and what they'll do differently), the rule (the transferable lesson), and the line not to cross (anything off-limits). It should not include headlines, hooks, or word counts — those are the writer's job.

Should I write a sample post for my ghostwriter?

No — most founders never get around to it, and it's the wrong artifact anyway. Record a 20-minute voice download instead: talk through a decision, a disagreement, a customer sentence, and a number. Talking removes the blank-page friction and gives the writer your real cadence, which a labored sample post usually hides.

How often should I brief my ghostwriter?

A weekly 20-minute voice download is the sweet spot — it keeps the Idea Feed fresh and yields three to five posts per session. The failure mode is going quiet for weeks and then batch-dumping topics; content briefed in a panic reads like it. Small and continuous beats large and sporadic.

Why does my ghostwritten content sound generic?

Almost always because the brief was generic. If you hand over a topic, the writer fills the gap with consensus opinion, which reads like everyone and therefore like no one. Generic in, generic out. Add your specific opinions, real numbers, and verbatim customer language and the same writer produces something only you could have said.

How much should I expect to be involved if I hire a ghostwriter?

Plan for roughly 20-30 minutes a week of input (the voice download) plus a quick review pass on drafts. You can delegate the writing, editing, and scheduling, but not the raw opinions — those have to come from you. A good operator minimizes everything except that irreducible input. For a fuller cost-and-time picture, see our breakdown of what a LinkedIn ghostwriter costs.what a LinkedIn ghostwriter costs

How do I give feedback without rewriting the whole draft?

Give feedback in categories, not commas. Instead of fixing individual words, name the pattern: the opinion is too soft, the example is generic, the tone sounds like a marketer, the evidence is wrong. Category feedback teaches the writer your judgment, so next month's drafts need less correction — line-editing teaches them nothing.

The shorter version

Ghostwriting doesn't fail at the writing. It fails at the brief. If your drafts don't sound like you, it's because you handed over topics instead of takes — and no writer can manufacture opinions you didn't give them. Brief the input, not the output. Build a Voice Doc, keep an Idea Feed, run a tight Review Loop, and replace the sample post that never gets written with a 20-minute voice download that does. Do that and "it doesn't sound like me" stops being your problem.

This is exactly the machine we run for founders at Invisible Keyboard — the voice capture, the weekly download, the review loop — so your content ships in your voice without you touching a compose box. If you'd rather have it operated than build it yourself, that's what we do.what we do