Before an X ghostwriter writes a founder’s first post, select a small set of representative samples and say why each belongs in the voice guide. Three to five recent, founder-approved pieces are enough to begin. Compare how the founder opens an explanation, handles uncertainty, uses technical detail and ends with a useful reader action. Then turn those observations into a one-page voice card and test it on two short drafts. A pile of links without context leaves the writer guessing.
This worksheet solves the selection problem at the beginning of the relationship. The founder ghostwriting edit example shows a later step: revising one draft after the founder supplies factual corrections. Voice calibration comes first, so later edits can distinguish a wrong fact from a sentence that simply does not sound like the founder.
Gather samples that show different jobs
Ask for material the founder actually approved: perhaps a product explanation, a response to a technical objection and a short reflection on a decision. Keep the publication date, audience, original link and any approval notes. A founder-written memo can help, but label it as internal; a recorded interview can reveal phrasing, but spoken filler is not automatically publishable copy. Do not treat an agency-written post as proof of the founder’s natural voice unless the founder reviewed and endorsed it.
Choose for range, not applause. One high-view post may have relied on a news event or an unusually sharp claim. It may be poor training material for a weekly explanation of the product. A useful set shows what the founder sounds like when making a careful technical point, acknowledging a limitation and inviting a concrete next step. If there are no written samples, interview the founder about one real product decision and have them approve a short written account before using it as a reference.
The guide also needs a boundary around identity. X’s authenticity policy allows people to manage accounts on behalf of others within its rules, while prohibiting deceptive impersonation and inauthentic activity. In a legitimate founder ghostwriting arrangement, the named founder remains responsible for the account’s identity and approves what is published in their name. A voice guide should help express that person’s real view, not manufacture a persona or an opinion they never held.
Worked example: keep two samples and reject one
Hypothetical example: Mara is a fictional founder of a developer workflow product called Tracepath. The product and all sample sentences below are invented to illustrate the worksheet; they are not Knowix client work or performance evidence. Mara wants her X account to help engineering leads understand an import review feature. Her team provides three candidate samples.
| Candidate sample | What it shows | Risk or gap | Voice-guide decision |
|---|---|---|---|
| Founder-approved explanation of why an import warning appears | Opens with the user problem, names the specific step, and says what remains uncertain | The feature description refers to an older release | Keep for structure, then link the current product guide for facts. |
| Founder-approved note about rejecting an automatic fix | Explains the tradeoff plainly and gives a reason without claiming every team has the same problem | Uses a long opening that may need trimming on X | Keep for reasoning and tone; shorten the opening, not the caveat. |
| A launch post with a strong superlative, prepared by a former agency | Punchy headline and many reactions | Founder cannot confirm approving the wording; the superlative lacks evidence | Reject as a voice reference and do not reuse the claim. |
The first two samples show a pattern: Mara starts with the reader’s workflow, states a concrete observation and explains the tradeoff. She is willing to say what the product does not decide automatically. The third post has visibility but no reliable provenance or claim support. The FTC’s advertising guidance says promotional claims should be truthful and evidence based. The writer should not carry an unsupported superlative into a new post just because it sounded memorable.
The decision is not a literary ranking. A sample can be useful for sentence rhythm while obsolete as a factual source. Another can provide a current fact but be a poor model for the founder’s tone. Save those judgments separately. Give every factual claim a current product source and an owner who can confirm it; a voice example cannot substitute for product evidence.
Copy this voice card, then fill it from approved evidence
Use a short document the founder and writer can both edit. The fields below are a template, not a claim about Mara or any real founder:
Founder and account:
Intended reader and the question this account answers:
Approved sample links, dates and what each demonstrates:
Typical opening: reader problem / observation / decision:
Sentence rhythm and level of technical detail:
Words or constructions the founder uses naturally:
Words, claims and tones to avoid:
How the founder describes uncertainty or a product limit:
Current product facts and source owner:
Examples of acceptable next steps and destinations:
Voice approver, factual approver and publishing owner:
Revision notes and date for next review:
Fill each field with an example rather than a vague adjective. “Plainspoken” is too elastic: one writer may remove the useful technical detail, while another may add casual jokes the founder never makes. “Starts with the import warning a reader saw, then explains the next action in two short sentences” gives a writer something testable. Capture a few phrases the founder likes and a few that feel false. Do not make the card so rigid that every post has the same opening.
Keep product truth in a separate, dated source list. For Tracepath, a current feature guide would define who can use the import review step, what it does and what remains manual. If the guide changes, the claim source changes even when the founder’s tone stays the same. That separation makes updates easier: the writer can revise a feature explanation without reinventing the founder’s voice.
Calibrate with two drafts before a cadence
Give the writer one approved fact and one reader question, then ask for two short draft angles. For the fictional Tracepath example, both drafts might explain why an import warning requires a human review. One could begin with the engineer’s immediate task; the other could begin with the product decision behind the warning. The founder should mark voice changes and fact changes in different comments. “I would say this more directly” is a voice note. “This warning appears only for a particular import type” is a factual correction and needs a source.
After the review, update the card with the actual accepted phrasing and rejected wording. If both drafts sound wrong, return to the samples or conduct a short founder interview; do not solve the problem by asking for more volume. If the founder likes the voice but the product claim remains unverified, hold publication until the factual owner resolves it. The ghostwriting approval workflow explains how to assign those responsibilities for ongoing work.
A useful calibration record has the approved sample, the two draft versions, comments grouped by voice or fact, the revised card and a decision on whether a recurring schedule can begin. Recheck the card when the founder’s role, product or audience changes. It should describe the current person and account, not freeze an old launch voice indefinitely.
Work directly with Knowix
Knowix can work directly with a founder and product team to select samples, build the voice card, write calibrated X drafts and run an agreed approval and publishing process. Send three to five approved pieces, current product sources, the audience question you want to answer and the people who can approve voice and facts. We can use those inputs to define a realistic first writing cycle through the founder ghostwriting service. The enquiry form below is the place to describe your project and start that conversation.
Frequently asked questions
How many founder samples should an X ghostwriter review?
Start with three to five recent, founder-approved pieces that represent different useful situations. Add a spoken explanation if the founder rarely writes, and record the sample's context and date.
Should the most popular founder post define the voice?
No. Choose samples for authentic language, current product knowledge and the intended reader task. Popularity alone does not show that a post is representative or factually reusable.
Can an interview transcript count as a voice sample?
Yes, as a supplement. Mark what is spontaneous speech, what the founder would actually publish, and any claim that requires verification before it becomes an X post.
What belongs in a founder voice card?
Record the audience, preferred opening, sentence rhythm, favored and avoided words, examples of approved phrasing, product source links, claim limits and who approves the final draft.
How do we test the guide before a writing schedule starts?
Ask the writer for two short drafts on the same approved product fact, have the founder mark voice and factual changes separately, then revise the card before approving a recurring cadence.