Define brand voice without a brand agency

Ask ten team members to describe your product in one sentence. If you get ten versions, you do not have a messaging problem only — you have a voice problem. Brand voice is how you say what you already decided to stand for.

Voice is not "tone of one tweet"

Voice is stable across channels. Tone flexes by context (support vs launch vs error message). Founders confuse the two and rewrite the homepage every week chasing vibes.

The 45-minute voice workshop (solo founder edition)

Step 1: Mine customer language

Pull ten phrases from support tickets, sales calls, or Reddit threads. These are words buyers already use. Your voice should feel native to them, not imported from a corporate brand book.

Step 2: Adjective matrix

List:

• We are: three adjectives (e.g. direct, specific, calm)
• We are not: three adjectives (e.g. breathless, vague, condescending)

If "playful" and "enterprise-serious" both appear, pick a lane for this quarter.

Step 3: Write three microcopy samples

Rewrite the same idea three ways:

• Homepage hero subhead
• Onboarding welcome
• Billing receipt email

Read aloud. Cut sentences where you stumble.

Step 4: Do / don't examples

Two rows:

| Do | Don't | |----|-------| | "Export tokens to your repo in one click" | "Revolutionize your workflow" | | "We are pre-1.0 — expect rough edges" | "World-class seamless experience" |

Store in using your guidelines after you generate base voice in create your first brand.

Voice must match visual brand

Whimsical copy on a stark enterprise UI feels broken. Run brand flow so palette and typography match personality — playful products can look playful; dev tools usually should not.

Operationalize voice

• Add voice doc to onboarding for contractors
• Point Cursor rules at the same file — Cursor workflow
• Review empty states and errors quarterly — they carry more voice than the homepage

Measure voice like product

Pick one metric: support ticket sentiment, activation on onboarding copy variant, or homepage bounce rate. Change copy, hold product constant, compare.

Voice is not subjective mysticism. It is consistency you can test.

Voice vs support and sales

Support macros and sales one-pagers drift fastest because different people write them under time pressure. Point both at the same voice doc and review quarterly. Error messages and empty states carry more brand weight than the homepage — they appear when users are already frustrated.

If contractors write copy, give them three approved examples and two rejected examples, not adjectives alone. Examples beat abstract "be friendly" every time.

Brand archetypes without the fluff

Pick one primary archetype (e.g., Sage for dev tools, Creator for design products) and one secondary. Archetypes are not astrology — they are shorthand for consistent tradeoffs when you debate word choice under deadline.

Voice regression checks

Before each launch, skim five UI strings: hero, signup error, billing receipt, empty state, and one email. If any sound like a different company, fix before shipping. Voice drift is incremental; quarterly audits catch it before customers do.

Close the loop between research and repo-native brand

Research docs fail when they live apart from what ships. After you update positioning or voice, regenerate exports so the homepage, app shell, and design.md agents read stay aligned. Engineers should not guess hex values from a PDF marketing forwarded once.

Schedule a 30-minute monthly review: phrase bank, win/loss notes, and live UI screenshots side by side. If language shifted but tokens did not, you have a process gap — not a design talent gap. Majico exists to compress brief-to-repo for indie SaaS teams who cannot wait for agency timelines.

Ship one measured change per week. Research without shipping is procrastination; shipping without research is generic defaults. The balance is weekly rhythm, not quarterly workshops.

Keep a single owner for the phrase bank and the brand export path. Split ownership and the homepage reverts to template language within a month.

Sources

1. Brand voice via content marketing (Quora) — Consistency keys, mission alignment, and evolving guidelines.
2. Human brand identity with AI (Quora) — Brand archetypes and structured voice vs generic AI tone.
3. Branding session questions (Quora) — Expression pillar: personality adjectives and emotional goals.
4. Key branding guidelines (Quora) — Voice as company-wide resource, not designer-only doc.
5. One-page creative brief (Quora) — Single-minded proposition shapes verbal identity.
6. r/startups — Founders ask how to sound consistent across site, email, and support.
7. r/SaaS — Microcopy and onboarding tone threads for dev tools.
8. Mailchimp content style guide (public) — Reference example of practical voice principles and do/don't.
9. GOV.UK writing style guide — Plain language standards applicable to B2B SaaS voice.
10. NN/g: Tone of voice in UX writing — Four dimensions to document voice vs situational tone.
11. AP style consistency basics — Why documented rules reduce drift as teams grow.