Brand Voice

Voice and tone are not the same thing

The two words get used interchangeably, and the distinction is the useful part. Voice is constant: it is who the company sounds like, and it should be recognisable in a support reply, a pricing page and a changelog entry alike. Tone is situational: the same voice is warmer in a welcome email than in an incident notice, in the same way a person's character does not change when their mood does.

That matters because most brand-voice documents fail by describing a mood rather than a character. A list like friendly, professional and innovative describes something any writer can perform for one paragraph and nobody can check afterwards. A voice becomes legible in the specific choices a writer makes over and over, which is where a usable definition has to start.

What actually defines a voice

Strip away the adjectives and a voice is a small set of repeated decisions. These are the ones that show up on the page:

• Vocabulary — the words you reach for and, more tellingly, the ones you refuse. A company that never once says *solution* has made a voice decision, whether or not it wrote it down.
• Formality and person — whether you write *we* or *I*, whether the reader is addressed as *you*, whether contractions are allowed. These are invisible individually and unmistakable in aggregate.
• Sentence rhythm — short and declarative reads as confident, long and qualified reads as careful. Both are real voices. Alternating between them at random reads as no voice at all.
• Claim posture — how far you will go beyond what you can evidence. This is the most recognisable trait a company has and the first one lost when writing gets distributed.
• What you find funny, if anything — humour is optional, but its presence or absence is never neutral. A voice with no jokes in it is still a deliberate voice.

Why it stopped being a branding exercise

Voice used to be enforced by headcount. Two or three people wrote everything a company published, they sat near each other, and consistency arrived for free. That is no longer the normal case. A founder drafts the landing page, a contractor writes the blog, a support tool suggests replies, and an AI assistant produces a first pass of most of it. Every additional writer pulls the output toward the average of everything ever written on the subject, which is exactly the generic register readers have trained themselves to skim past.

So voice has become an operating constraint rather than a page in a brand deck: it holds only if it is written down in a form another writer, human or otherwise, can actually follow. First-hand note from building AgentCeres — the AI Growth Officer at agentceres.com. When we set a new customer up, we extract voice *samples* from their existing site and uploaded material rather than asking them to choose adjectives, because a sample is something a draft can be compared against and an adjective is not. Our own voice is partly enforced by a test that fails the build when a page uses one of a short list of phrases we have decided never to use, most of them over-claims about what software does without a person involved. A voice rule that can be checked mechanically is the only kind that survives a growing number of writers.

How to document one that survives

A voice guide earns its keep when a new writer can produce something recognisable from it on the first attempt. That standard rules out most of what usually goes into one:

• Samples, not adjectives — five to ten sentences you would publish and five you would not, taken from real pages. Show first, explain second.
• A do-not-say list — the specific words, claims and formats that are out. Prohibitions travel between writers far more reliably than aspirations do.
• Rules that are checkable — anything expressible as a rule should be expressed as one and checked where the writing is produced. Whatever is left is a judgement call and should be labelled as one.
• A worked example per format — a landing page, a support reply and a social post in the same voice, side by side. Most voice failures are format failures: people who write the site well go generic the moment the box changes shape.