The raw material is conversation, not a brief.
A topic brief produces topic coverage. It captures what to talk about. What it rarely captures is how a specific person would actually talk about it — the angle they'd take, the claim they'd qualify, the comparison they find obvious that others don't. That information lives in conversation, not in documents.
The most important questions in a ghostwriting input session are the follow-up questions. "Why does this matter?" surfaces motivation that the brief omitted. "What did you actually see happen?" turns a principle into a specific situation. "What would most people get wrong about this?" forces a real position rather than a safe one. These questions bring judgment to the surface — the raw material that makes writing sound like a real person thinking out loud.
Teams that skip structured conversation and rely on briefs produce posts that cover the topic correctly and miss the person entirely. The brief gets the substance right. The conversation gets the voice right. Both are necessary; neither replaces the other.
Voice gets documented.
Voice documentation is not a style guide. It is a working record of how a specific person communicates — the phrases they reach for naturally, the qualifications they always include, the claims they would never make because they find them too strong or not quite accurate, the sentence rhythms that feel right to them and the ones that feel off.
Building that record takes time and deliberate attention. The first few weeks of a ghostwriting relationship produce approximations. As the writer absorbs more of the person's real communication, makes mistakes, receives specific corrections, and sees which drafts require the least revision — the voice profile sharpens. A well-maintained profile after six months looks nothing like the initial version. It has specificity that only comes from experience with the person.
The documentation serves a functional purpose: it allows the team to maintain consistency even as writers change, as the engagement grows, or as the editorial process involves multiple people. Without explicit documentation, voice fidelity is a function of individual memory, which degrades and doesn't scale.
Editing needs responsibility.
The editing step in a ghostwriting process is not about polish. It is about the intersection of quality and responsibility. A post can be well-written and still wrong in ways that matter: a claim the founder can't substantiate, a framing that a competitor or regulator could challenge, a position that the founder holds in private but isn't ready to hold publicly.
Catching those issues is the editor's job — not in the abstract, but with knowledge of the specific person, their industry, their relationships, and the stakes attached to what they say publicly. That knowledge doesn't come from the brief. It comes from a close working relationship with the client and a genuine understanding of what each post does to their professional standing.
Approval is not the end of this responsibility. A well-functioning approval process trains the client to review substantively rather than quickly. When founders read drafts carefully and push back specifically — this doesn't sound like me, this claim isn't quite right, I'd never say it this way — the process improves. When approval is rubber-stamped, the process atrophies, and the posts start to drift away from the person.
The process improves with every cycle.
Ghostwriting relationships that work well improve consistently over time. Each approval cycle — what was accepted without comment, what was flagged, what was rewritten significantly — teaches the team something specific about the person's voice and risk tolerance. Good processes capture those lessons explicitly rather than relying on writers to remember them.
After six months of structured cycles, a well-functioning ghostwriting relationship should produce drafts that require minimal revision. The founder should read the posts and feel accurately represented — not just covered on the topic, but expressed in a way that sounds like them. When that happens, the process has achieved its actual goal: translation, not just production.
That distinction — translation versus production — is the right way to think about what a good ghostwriting process is. Production fills a content calendar. Translation makes a person's real thinking accessible and repeatable in public. The first is a service. The second is a reputation investment.
Frequently asked questions.
How does a ghostwriter learn a founder's voice?
Through structured conversation, observation, and deliberate correction cycles. The first input sessions establish the broad parameters. Drafting and receiving specific pushback reveals the nuances. Over time, the writer builds an increasingly accurate model of how the person thinks and communicates. This is not a passive process — it requires the founder to engage substantively with approvals, explaining why something doesn't fit rather than just rejecting it. The correction is the teaching.
What should a founder prepare before a ghostwriting input session?
Nothing elaborate. The most useful preparation is a mental inventory of what happened in the last week or two: a decision made, a conversation that revealed something, a situation where conventional wisdom didn't apply, a mistake and what it showed. That material is richer than any prepared "content topics." The ghostwriter's job is to ask the questions that draw it out. The founder's job is to show up with enough recent experience to draw from.
How many input sessions does a ghostwriting process typically need per month?
One structured session of 30-45 minutes per week is enough for most founder profiles publishing two to three times weekly. Less than that typically produces thin posts that don't sustain the voice. More than that is usually unnecessary if the session is well-structured. The key variable is not the duration but the quality of the questions — whether the session surfaces real thinking or just confirms planned topics.
Keep reading in the library.
Builderz System
Visibility has to become trust.
Builderz builds LinkedIn systems for founders and executives who want to become clearer in the market, not louder.