# Brand Voice

> Brand voice and tone — how a brand communicates verbally. Covers voice definition, tone modulation across contexts, messaging frameworks, vocabulary systems, and content guidelines. The verbal execution layer that translates positioning into words.

- Skill: `npbuilds/brand-voice` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add npbuilds/brand-voice`
- Raw SKILL.md: https://api.skillmd.com/api/skills/npbuilds/brand-voice/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: npbuilds (https://skillmd.com/u/npbuilds)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/npbuilds/brand-voice

---


# Brand Voice — How the Brand Speaks

The verbal counterpart to visual identity. While visual identity is how the brand looks, brand voice is how it sounds in every piece of written and spoken communication.

## Voice vs Tone

**Voice** is consistent — it's the brand's personality expressed through language. It doesn't change.
**Tone** modulates — it's how the voice adapts to different contexts. Same personality, different situations.

| | Voice (constant) | Tone (varies) |
|---|---|---|
| Analogy | Your personality | Your mood |
| Example | "We're direct and warm" | Error message: direct + empathetic. Marketing: direct + enthusiastic |
| Changes? | No — it's who we are | Yes — adapts to context, audience, and content type |

## Defining Voice

### The Voice Attributes Framework
Define your voice with 3-4 attributes, each on a spectrum:

**Format:**
> We are [attribute], not [opposite].
> This means we [do this], not [that].

**Example for a developer tools brand:**
> - We are **precise**, not verbose. We say what's needed in the fewest words.
> - We are **direct**, not aggressive. We respect the reader's intelligence without being blunt.
> - We are **helpful**, not patronizing. We explain when useful, not when obvious.
> - We are **human**, not corporate. We use contractions, humor when appropriate, and first-person.

### Voice from Brand Personality
| Brand Personality | Voice Direction |
|---|---|
| High sincerity | Conversational, inclusive, first-person plural ("we"), warm |
| High excitement | Short sentences, action verbs, exclamation-adjacent energy (without actual exclamation marks everywhere) |
| High competence | Structured, evidence-backed, confident without boasting |
| High sophistication | Curated vocabulary, understated, fewer words with more weight |
| High ruggedness | Direct, imperative mood, no hedge words, concrete |

### The "We'd Never Say" List
Equally important to defining what you sound like is defining what you'd never say:

| Voice Attribute | We'd Never Say | Why |
|---|---|---|
| Precise | "Basically, what this does is..." | Filler undermines precision |
| Direct | "We would like to suggest perhaps considering..." | Hedging undermines directness |
| Helpful | "Simply do X" or "Just click Y" | "Simply" and "just" are patronizing |
| Human | "The user shall proceed to..." | Third-person passive is robotic |

## Tone Modulation

### The Tone Matrix
Map tone across two dimensions for each content type:

| Content Type | Formality (casual ↔ formal) | Energy (calm ↔ energetic) |
|---|---|---|
| Marketing landing page | Casual | Energetic |
| Product documentation | Moderate | Calm |
| Error messages | Casual | Calm (empathetic) |
| Legal/compliance | Formal | Calm |
| Social media | Very casual | Energetic |
| Customer support | Moderate | Calm (patient) |
| Internal comms | Casual | Varies |

### Error Message Tone (Special Case)
Error messages are where brand voice is tested most. Bad error messages erode trust faster than any marketing can build it.

**Framework:**
1. **Say what happened** (not technical jargon)
2. **Say why it matters** (impact on the user)
3. **Say what to do next** (actionable step)

| Bad | Good | Why |
|---|---|---|
| "Error 403: Forbidden" | "You don't have access to this page. Ask your admin for permission." | Explains the situation and gives a next step |
| "An unexpected error occurred" | "Something went wrong on our end. Try again in a minute — if it persists, contact support." | Takes responsibility, gives timeline and escalation |
| "Invalid input" | "That email address doesn't look right. Check for typos?" | Specific, non-blaming, suggests a fix |

## Messaging Framework

### The Message Hierarchy
Every brand needs messages at different levels of detail:

| Level | Length | Use Case | Example |
|---|---|---|---|
| Tagline | 3-7 words | Logo lockup, memorability | "Think different" |
| Elevator pitch | 1-2 sentences | Quick introductions | What you'd say if someone asked "What do you do?" |
| Value propositions | 3-5 bullet points | Landing pages, sales materials | One per key benefit |
| Detailed narrative | 1-2 paragraphs | About page, investor materials | The full story |
| Proof points | Supporting evidence per claim | Case studies, testimonials | Data, quotes, results |

### Value Proposition Formula
For each key benefit:

> **[Benefit headline]** — [One sentence explaining what it means for the user]. [One sentence of proof or specificity].

**Example:**
> **Ship faster without breaking things** — Our CI/CD pipeline catches errors before they reach production, so your team can deploy with confidence. Teams using our platform deploy 3x more frequently with 60% fewer rollbacks.

## Vocabulary Systems

### Word Lists
Define preferred and avoided vocabulary:

| Category | Prefer | Avoid | Reason |
|---|---|---|---|
| The product | "platform", "tool" | "solution", "offering" | "Solution" is meaningless corporate-speak |
| Users | "you", "your team" | "the user", "end user", "client" | Direct address is more human |
| Problems | "challenge", "friction" | "pain point", "problem" | "Pain point" is jargon |
| Actions | "build", "create", "set up" | "leverage", "utilize", "onboard" | Concrete verbs over abstract ones |
| Results | "faster", "simpler", "clearer" | "optimized", "streamlined", "best-in-class" | Specific over superlative |

### Jargon Policy
- **Internal jargon**: Define it on first use, then use freely
- **Industry jargon**: Use only if your audience uses it daily
- **Marketing jargon**: Never. "Synergy," "leverage," "best-in-class" — delete on sight.
- **Technical jargon**: Match the audience's technical level. A developer docs site can say "API endpoint." A consumer app should say "connection."

## Content Guidelines

### Formatting Conventions
| Element | Guideline | Rationale |
|---|---|---|
| Headings | Sentence case, not title case | More natural, less shouty |
| Lists | Parallel structure, consistent punctuation | Professionalism |
| Numbers | Spell out one-nine, use digits for 10+ | Standard editorial convention |
| Dates | March 22, 2026 (not 03/22/2026) | Unambiguous, international-friendly |
| CTAs | Start with a verb, max 4 words | "Start free trial" not "Click here to get started with our free trial" |
| Punctuation | One exclamation mark per page maximum | Exclamation inflation devalues enthusiasm |

### Writing Principles
1. **Front-load value** — the most important information goes first. Don't bury the lead.
2. **One idea per paragraph** — if a paragraph has "also" or "additionally," split it.
3. **Active voice by default** — "We shipped the feature" not "The feature was shipped"
4. **Short sentences for clarity** — under 25 words. If you need a comma, consider a period.
5. **Cut ruthlessly** — if removing a word doesn't change the meaning, remove it.

## Anti-Patterns

- **Voice guidelines nobody reads** — if the guide is 40 pages, nobody follows it. Keep to 2-3 pages.
- **Tone-deaf consistency** — using the same enthusiastic tone in a data breach notification as a product launch
- **Copycat voice** — sounding like Mailchimp because they're famous for good voice. Your brand isn't Mailchimp.
- **No examples** — abstract guidelines ("be friendly") without concrete examples ("say X, not Y") are useless
- **Voice by committee** — when 6 stakeholders edit copy, the voice becomes beige. One voice owner per brand.
- **Ignoring internal communications** — brand voice that only applies to marketing but not support, docs, or internal comms is incomplete

## Cross-Domain Connections

- **Writing/sentence-craft/style-dna**: Brand voice IS style-dna applied to an organization instead of an author. Both define consistent identity through measurable traits — sentence length, vocabulary range, formality level. Style-dna provides the analytical toolkit; brand-voice provides the strategic framework.