Turn your voice guide into writing decisions
Build a founder voice guide from examples, writing choices, and a repeatable comparison, while keeping product facts separate.
The short version
- Make the writing choices visible. Keep voice preferences, but show examples of what the founder would change and why.
- Use permitted writing samples and source notes. A believable voice does not make an unsupported claim true.
- Test the same briefs with and without the guide. Compare source fidelity, point of view, clarity, and editing effort.
- Update the guide when a repeatable editorial decision emerges. Avoid turning every one-off preference into a permanent rule.
A founder voice guide is more useful when it explains writing decisions. Keep the broad preferences, such as direct or conversational, but add examples of what those preferences mean in a sentence. Then test whether the guide reduces the edits needed on a real brief.
For a small B2B SaaS team, the aim is to take writing off the founder’s plate while keeping their ideas recognizable. That requires more than matching vocabulary. The writer needs to understand what the founder believes about the product, which tradeoffs matter to buyers, and which claims the available evidence supports.
Start with writing the founder recognizes
Choose a few permitted samples that reflect how the founder explains an idea clearly. A published post, an email you can reuse, or an approved transcript can work. Prefer material relevant to the audience you are writing for. Private conversations shouldn’t become public anecdotes merely because a model can read them.
Read the samples alongside the founder’s edits. What did they remove? Where did they add detail? Was the change about voice, an inaccurate fact, or a different point of view? Those are separate problems, and the guide should make the difference visible.
The customer-interview workflow covers gathering useful source material. Here, turn recurring editorial choices into instructions another writer can apply.
A founder might use short sentences in a LinkedIn post and longer explanations in a product article. Preserve that difference. A single rule about sentence length can become restrictive if it is copied across every channel without context.
Separate voice from the facts behind it
Keep a voice guide and a product-fact record distinct. The voice guide can explain tone, examples, word choices, and how the founder argues a point. The fact record should establish what the product does, its limits, and the source for any result.
Google’s helpful-content guidance asks whether content is trustworthy, provides useful information, and identifies its author clearly. Writing that sounds familiar can still fail those checks. Don’t accept a confident sentence as evidence of a working feature.
In the brief, attach the facts the piece is allowed to use. When a claim is missing, have the writer flag it instead of filling the gap. If the founder’s view has changed, update the point of view separately from the style preferences.
The content system guide covers the larger production process. Voice is one input to that process; it doesn’t replace source checks, editorial judgment, or the publishing handoff.
Show the decision with an example
Use a small before-and-after example and explain the reason for the edit. The following lines are constructed teaching examples, not observed model output or a founder quote.
For this exercise, assume a fictional integration copies approved CRM contacts to a newsletter list every morning and records failed transfers for review. Those are supplied teaching facts, not claims about a real product.
Before “Our integration makes your team more efficient.”
After “Approved CRM contacts reach your newsletter list each morning. Failed transfers appear in a review queue.”
The revision replaces a broad benefit with behavior the reader can evaluate. Its short sentences also make the failure condition easy to see. Use that voice choice only if it fits the founder’s permitted writing samples. A real draft needs verified product facts before it can make either promise.
The voice decision might be to explain the mechanism before describing the benefit. The fact decision is whether the mechanism is accurate. Keep both checks visible so a writer doesn’t learn that adding specificity means inventing details.
Record the recurring choices in a short guide:
- Who the piece addresses and what they already know
- How the founder explains a disagreement or tradeoff
- Words or phrases the founder routinely edits
- Examples of openings, explanations, and next steps
- Claims that need a source or should remain unresolved
Don’t treat this as a universal template. A founder who teaches through a detailed example may need a different structure from one who leads with a concise opinion. The sample and the reason for the edit matter more than a label such as authentic.
Put the guide into a clear workflow
Draft from the brief, compare the draft with the source facts, and then assess the voice. Those steps can be separate even when AI assists with each one. Keep the founder’s point of view attached so an editor can see whether the argument changed.
Anthropic’s workflow guidance describes dividing a task into explicit steps with intermediate checks. For this writing job, that makes it possible to catch a changed product claim before spending time polishing its tone. It doesn’t guarantee that every draft will pass.
The AI content review article covers checking the draft before refining sentences. Use that review to separate a sourcing problem from a voice problem. A missing example may require a better brief; a repeated phrase may require a clearer writing instruction.
Test the guide against the same briefs
Choose several briefs with different demands, such as an opinion, a product explanation, and an answer to a buyer question. Use the same source material when comparing versions written with and without the guide. Record the model or writing process used and the review date.
Compare the founder’s view, factual fidelity, readability, and the edits needed before publication. Note where the guide helped and where it made the draft worse. A recognizable phrase isn’t enough if the argument has become generic or the writer introduced an unsupported claim.
NIST’s AI risk-management framework treats trustworthiness as a consideration across design, use, and evaluation. For this exercise, define the checks before accepting the output.
Improve one recurring edit this week
Take one draft and its edited version. Identify a change the founder makes repeatedly, write the reason in plain language, and add a permitted example. Try that instruction on another brief before making it a standing rule.
The free founder LinkedIn content guide includes a voice profile and idea worksheets. Founder-Led Content uses your ideas, point of view, and voice to handle writing and LinkedIn scheduling, posting, and reporting.