# Founder brand voice reference

Use this document with a B2B founder and their LinkedIn writer. Copy Part 1 for an engagement; Part 2 is a fictional completed example. Replace placeholders and retain unresolved questions rather than guessing.

This reference records approved writing choices across assignments. It does not replace an assignment brief, establish the company's positioning, verify a claim or authorize publication. Use only material the founder is entitled to share, and follow the team's source-storage and AI-use permissions.

## Part 1: Blank template

### Reference and permission

- Founder and role: [Name, role, company.]
- Intended reader and context: [Who reads the posts, and what decisions do they face?]
- Version: [Version and date.]
- Document owner: [Person who maintains the reference.]
- Approval: [Founder or authorized reviewer, approval date, approved version.]
- Unresolved restrictions: [What prevents use of a source or instruction?]

#### Source record (repeat for each sample)

- Sample ID: [Unique reference.]
- Source type and date: [Interview, approved post, email or other permitted material.]
- Authorship and endorsement: [Who wrote or said it? Does the founder still endorse it?]
- Exact passage or source location: [A cleared excerpt or approved internal location.]
- Internal reference permission: [What may the writer use, who authorized it, and when?]
- Public quotation permission: [Separately cleared, restricted or not obtained.]
- Exclusions: [Names, customer details or other information that must not be reused.]

### Observed language and approved choices

#### Writing choice (repeat as needed)

- Observation: [A pattern visible in the source; cite its sample ID.]
- Proposed instruction: [A usable writing choice, marked provisional.]
- Founder response: [Keep, change or reject; record their explanation.]
- Approved instruction: [The instruction a writer may now follow.]
- Useful wording and context: [Approved language and when it fits.]
- Wording to avoid and reason: [The specific issue, not an unexplained adjective.]
- Status and reviewer: [Provisional, approved or retired; reviewer and date.]

#### Tone by situation

- Routine explanation: [Suitable level of formality and detail.]
- Disagreement: [How the founder challenges an idea without inventing an opinion.]
- Sensitive communication: [Changes in tone, restrictions and additional review.]
- Other relevant situation: [Context and approved variation.]

### Attribution and factual boundaries

- First-person experiences permitted: [Specific approved experiences and source locations; leave blank if none are cleared.]
- Opinions permitted: [The actual position and its approval; do not infer beliefs from writing style.]
- Claims needing assignment-level evidence: [Numbers, outcomes, comparisons and other statements to verify.]
- Confidentiality and customer permissions: [Restrictions, clearance owner and approved source locations.]
- Specialist review: [Material requiring another reviewer and how to contact them.]
- AI-use permission: [Which cleared inputs, if any, may be used in an approved service.]
- Open question: [Question, responsible person and next action; repeat as needed.]

### Calibration and handoff

#### Passage review (repeat as needed)

- Assignment and evidence reference: [Brief ID and supporting material.]
- Draft passage: [Exact text under review.]
- Founder correction: [Exact approved change.]
- Reason: [Language preference, factual error, attribution, confidentiality or another stated reason.]
- Reusable reference change: [What should carry forward, or why this correction is assignment-specific.]
- Reviewer and date: [Who approved the decision and when.]

#### Current handoff

- Approved reference version: [Version and approval record.]
- Next writer and review owner: [Names or roles.]
- Assignment brief: [Link or location; facts belong with their evidence there.]
- Unresolved items: [Restrictions and questions the writer must retain.]
- Review trigger: [Role change, new approved samples, contradictory feedback or another relevant event.]

## Part 2: Fictional completed example

The founder, source material, permissions and review below are invented solely to demonstrate the template. They are not a Windmill client account, a statement by an actual founder or a measured result. The permissions apply only within this fictional example.

### Reference and permission

- Founder and role: Elena, founder of an illustrative finance advisory firm.
- Intended reader and context: Owners of professional-services firms considering a second office.
- Version: Example v1, November 20, 2026.
- Document owner: Editorial lead.
- Approval: Elena approves the writing instruction below for this example. Public quotation of the source interview is not cleared.
- Unresolved restrictions: No customer story or business result is authorized.

#### Source record S1

- Source type and date: Fictional founder interview note, November 19, 2026.
- Authorship and endorsement: Spoken by the fictional founder; she endorses the operating question in this example.
- Cleared internal excerpt: “Before adding another office, I want to see when the cash leaves and when it comes back.”
- Internal reference permission: The founder permits the assigned writer to use this excerpt to discuss language choices.
- Public quotation permission: Not obtained. The sentence must not be published as a quote on the basis of internal clearance.
- Exclusions: No named customer, confidential financial record or implied client outcome.

### Observed language and approved choices

- Observation: In S1, Elena asks about timing of cash movements instead of describing an ambition to grow.
- Proposed instruction: Prefer concrete operating questions to broad growth language. Initially provisional because one sample does not establish a general preference.
- Founder response: Elena approves the instruction for this reference.
- Approved instruction: Explain the operating question in plain language; keep uncertainty visible.
- Useful wording and context: “Cash commitments” and “when receipts arrive” can suit an explanation of expansion planning when factually appropriate.
- Wording to avoid and reason: Elena rejects “unlock their next chapter” because it does not identify the decision she would help examine.
- Status and reviewer: Approved by the fictional founder for Example v1.

#### Tone by situation

- Routine explanation: Direct and conversational, with enough detail to identify the operating question.
- Disagreement: Explain which assumption needs checking. No disagreement or belief is attributed to Elena without her approval.
- Sensitive communication: No incident or customer difficulty is authorized for this example. Seek approval of both substance and tone before drafting such a post.
- Other situation: Unspecified; retain as an open question rather than infer a preferred tone.

### Attribution and factual boundaries

- First-person experiences permitted: None. S1 does not establish a history of advising any particular client.
- Opinions permitted: Only the approved approach to describing the operating question. It does not authorize an opinion about a named business.
- Assignment-level evidence: Financial statements, outcomes, comparisons and claims about expansion risks require their own supporting material and review.
- Confidentiality and customer permissions: No customer material supplied or cleared.
- Specialist review: A qualified subject-matter reviewer must check financial explanations before publication.
- AI-use permission: Not granted for confidential material; use only inputs cleared under the team's approved policy.
- Open question: The editorial lead must ask whether a public source quotation may be used. Until resolved, internal-reference permission remains separate from publication permission.

### Calibration and handoff

- Assignment: A fictional LinkedIn explanation of questions an owner can examine before committing to another office. No client outcome supplied.
- Draft passage: “I've watched profitable firms fail because they expanded too fast.”
- Founder correction: “An expansion decision needs a view of cash commitments as well as revenue.”
- Reason: The draft invents first-person experience and a causal account. The source supports neither. The revised explanation still needs assignment-level factual review; it is not approved for publication by appearing here.
- Reusable reference change: Explain an operating question without inventing first-person experience. Keep the particular expansion argument in the brief.
- Reviewer: The fictional founder approves the language preference; the subject-matter reviewer and publication owner have separate responsibilities.
- Current handoff: Example v1 plus the assignment brief. Preserve restrictions on quotations, customer details and factual claims. Review the reference when the founder approves new samples or changes the instruction.
