# Subscriber Persona — [YOUR NEWSLETTER NAME]

**CUSTOMIZE THIS FILE.** Replace every section with your own audience description.
The reference version below is calibrated for Claudify Weekly (a Claude Code newsletter for developers).
The structure survives; the content is brand-specific.

---

## The audience in one sentence

[Write one sentence that describes who subscribes and why they open it.]

---

## The core writing principle

[State the single most important principle for writing for this audience. For Claudify Weekly it's:
"Technical depth and language complexity are independent dimensions. The newsletter is allowed to be deeply technical. The newsletter is NOT allowed to be linguistically complex."]

---

## Who they are

- [Describe your subscriber: their job/role, their tools, their context]
- [What do they use the thing your newsletter covers?]
- [How much time do they have for a newsletter?]
- [What do they find credible vs. what makes them unsubscribe?]

---

## The range — floor and ceiling

Every issue must land for both ends of your audience range.

### The floor reader (~40-50% of subscribers)

- Knows: [describe baseline knowledge]
- Doesn't know: [describe what they haven't encountered yet]
- Their question every issue: [what are they hoping to walk away with?]
- Their frustration: [what makes them unsubscribe?]

**Implications for writing:**
- [specific constraint derived from the floor reader]
- [specific constraint derived from the floor reader]

### The ceiling reader (~15-20% of subscribers)

- Knows: [describe advanced knowledge]
- Their question every issue: [what novelty are they hunting?]
- Their frustration: [what makes them feel the issue wasted their time?]

**Implications for writing:**
- [specific implication]
- [specific implication]

### The middle (30-40% of subscribers)

- Knows: [describe middle ground]
- Their question: [what makes an issue feel applicable?]

**Implications for writing:**
- [specific implication]

---

## What they pay attention to (and what they tune out)

### Pay attention to
- [specific signal that earns their read]
- [specific signal]
- [specific signal]

### Tune out
- [what kills trust or gets skipped]
- [what kills trust or gets skipped]

---

## What they are NOT

[Who you're explicitly NOT writing for — equally important as who you are writing for.]

---

## How to test if a sentence works for this persona

1. **Floor test:** [specific question to check against the floor reader]
2. **Ceiling test:** [specific question to check against the ceiling reader]
3. **Time test:** Could this sentence be cut without losing meaning?

---

## Changelog

[When this document changes: date + what changed + why]