Quick answer: A brand voice guide is a short document that defines how a product writes: the tone, the sentence style, the vocabulary, and the words and phrases to avoid. The brand kit sets the colors and fonts; the voice guide sets the writing.

The two work together, and the voice is often the part that makes writing feel like a product.

What's in the guide

Section Content
The audience Who the reader is, and what they already know
The tone Three or four adjectives with explanations
The sentence style Length, voice, contractions, use of technical detail
The vocabulary The words the product uses, and the words it doesn't
The do and don't Before-and-after examples
The channel notes The differences between X, email, and the blog

The tone

The tone is defined with examples, not adjectives alone.

  • Direct, not blunt. Say what the product does; skip the softening.
  • Plain, not dumbed-down. A developer product stays technical; the reader is not a beginner.
  • Honest, with trade-offs. State what the product does not do.
  • Calm, not hyped. No adjectives that promise more than the product delivers.

The voice is easier to describe with a sentence than with a list of adjectives.

The vocabulary

The voice guide lists the words the product uses:

  • The official names of features.
  • The terms for the customer (user, developer, maker, team).
  • The way the product refers to itself.

It also lists the words to avoid: category buzzwords, vague adjectives, and the phrases that sound like a generic marketing template.

The before-and-after examples

The most useful section is the example bank.

Before: "We are thrilled to announce our powerful new solution."
After: "The deck exports to PowerPoint and stays editable."

The examples are the part of the guide that actually gets used by anyone writing.

Voice by channel

The voice is consistent, but the channel changes the length:

  • X: short, direct, one idea per post.
  • LinkedIn: first-person, narrative, longer.
  • Email: direct and personal.
  • Docs: precise, technical, and complete.
  • Blog: longer, with real engineering or launch detail.

The caption guide covers the channel-specific versions.

What to avoid

  • A 50-page voice document. Nobody reads it. A short guide with examples is better.
  • Tone words without examples. "Bold" and "playful" mean different things to different writers.
  • A voice that contradicts the product. A developer tool written in a casual consumer voice is unreadable.
  • A guide that's never used. The guide should be opened when a post or an email is written.

The voice guide and the launch kit

A launch kit can generate captions and posts, but the voice guide is the input. Without it, the generated text uses the default AI tone, which is why generated launch posts often sound interchangeable.

Frequently asked questions

Is the voice guide the same as the brand guidelines? It's the written section of the brand system; the guidelines also cover the visual identity.

How long is a voice guide? Two to six pages; a one-page version with examples works for a small product.

Can the voice change? The core voice is stable; the tone flexes for the channel.

How do I establish a voice? Write the twenty most common posts and emails yourself, then note the patterns; that's the voice.

Can the generated content follow the guide? It can, when the guide is supplied; Neatico writes the launch copy at the platform lengths while the founder's guide defines the voice.

Write the before-and-after examples before the adjectives. If the examples make the voice obvious, the adjectives are just decoration.