# Founder ideas and voice workbook

Use one real idea. All teaching examples below are constructed, not client stories or founder quotes.

## Reader and idea brief

- Intended reader and current situation:
- Decision the reader faces:
- What the reader should understand or do:
- Your actual point of view:
- Decision rule or method:
- Evidence reference and date:
- A real detail or explicitly labeled teaching artifact:
- Conditions where the advice changes:
- Product facts to confirm:
- Material not cleared for public use:
- Useful next destination, if any:

## Voice profile

- Cleared writing or recording samples:
- Words you use for this subject:
- Sentence rhythm, with one permitted example:
- How you explain a tradeoff:
- Humor, if present:
- Formatting choices:
- Phrases you wouldn't say:
- Prior edit and why it was needed:
- Facts and stories in the samples that must not transfer to this idea:

## Capture prompt

```text
Extract an idea brief and concrete voice choices from the permitted material below.
Material: [PASTE]
Reader and situation: [PASTE]

Separate actual experience, verified product facts, opinions, and teaching examples. Preserve the person's stated point of view and the conditions where it changes. Mark missing evidence unknown.
Describe vocabulary, rhythm, explanation style, and phrases to avoid using short examples from the material. Do not infer a personality or invent a founder quote.
Ask one focused follow-up if the idea cannot yet support a useful post.
```

## LinkedIn draft prompt

```text
Draft one LinkedIn post using this idea brief and voice profile.
Brief: [PASTE]
Voice: [PASTE]

Explain the reader's situation and the person's actual decision rule. Include one supported detail or clearly labeled teaching artifact and the relevant limit.
Use only cleared facts. Do not invent a scene, customer, number, result, quote, or capability. Use plain language, Oxford commas, and no em dashes. End with a useful action, not a request for likes or comments.
If the brief needs another fact, return that question instead of inventing a finished passage.
```

## Newsletter and blog adaptation prompt

```text
Adapt the same supported idea into a newsletter outline and a blog outline.
Original brief and evidence: [PASTE]
LinkedIn draft: [PASTE]

For the newsletter, explain the context and one practical subscriber action.
For the blog, include the full method, inspectable evidence, and exceptions. Identify additional sources needed for changing external claims.
Keep the point of view and factual limits intact. Do not paste the post unchanged or invent evidence to fill a section. Sending and publication are separate actions.
```

## Source and voice review prompt

```text
Compare these drafts with the original brief, evidence, and voice samples.
Inputs: [PASTE]
Drafts: [PASTE]

List unsupported additions, facts needing confirmation, unclear passages, and voice mismatches. Suggest the smallest concrete correction. Hold any change requiring a new fact.
Check whether the reader receives a useful explanation or action. Do not certify truth from fluency or predict reach.
```

## Worked teaching brief

Reader: a service-team operations lead considering a handoff automation.
Decision: whether to automate before a receiving owner is agreed.
POV for this teaching exercise: name the receiving owner and next action before automating transfer.
Artifact: a constructed checklist with an empty owner field, not a real customer screenshot.
Boundary: a stable handoff may still need automation when repeated copying creates errors.
Unsupported material: a time saving, a failed customer deal, or a founder's personal anecdote.

LinkedIn output: explain the owner field and the decision it represents.
Newsletter output: walk through the checklist and the reader's next inspection.
Blog output: document fields, permissions, missing-data behavior, and limits with verified sources for actual product claims.

## Calendar instructions

Import content-calendar.csv. Adjust the four weekly planning rows to your schedule. Fill sources before drafting. Use status proposed, drafting, ready, scheduled, published, held, or failed. Confirm the intended account and time zone. Add a published URL only after checking the actual post. Track available reporting fields and meaningful reader questions separately from business outcomes.