How to Write a Brand Voice Guide for Your SaaS
You opened a Google Doc called "Brand Voice v1" four months ago. It still says "We are friendly, professional, and innovative." Every caption you ship sounds like ChatGPT had a panic attack. The fix is not a 40-page brand bible. It is a one-page voice guide built from your own product copy, your own customer quotes, and three rules you can recite in the shower.
This is how to write a brand voice guide for your saas without hiring an agency or staring at Notion templates for a weekend.
· · ·
Why does your saas voice sound like every other AI tool?
Because you wrote your homepage in the same week you wrote your pitch deck, and both used the same five adjectives. Founders default to category language when they are tired. You write "the modern way to manage X" because every other tool in your space said the same thing first, and you absorbed it.
The other reason: you have not separated your voice (who you sound like) from your messaging (what you say). Messaging changes per launch. Voice does not. When founders skip the voice layer and jump straight to captions, every post reads like a different person wrote it. Because a different person did. Monday-you is upbeat. Thursday-you is exhausted. Sunday-you is philosophical at 11pm.
A voice guide is the thing that makes Monday, Thursday, and Sunday sound like the same company.
· · ·
What actually goes in a saas brand voice guide?
Forget the 40-tab brand book. A working voice guide for a solo founder fits on one page and contains six things: a one-sentence pitch, three voice attributes with opposites, a do/don't list, vocabulary you use and vocabulary you ban, two or three example sentences in your voice, and a list of phrases lifted verbatim from your customers.
That last one matters more than the rest combined. Founders who quote customers verbatim sound real. Founders who paraphrase sound like analysts.
The goal is not a document for designers. It is a prompt for yourself, your contractor, and any AI tool you use to draft. If a stranger cannot write one usable caption from your guide, the guide is decoration.
The one-page test
If you cannot read your full voice guide aloud in under 90 seconds, cut it. Long guides do not get used. Short guides get pinned above the monitor.
· · ·
How do you write a brand voice guide for your saas in one sitting?
Here is the order that works. Do not skip steps. Do not start at step one with a blank doc.
- Pull 20 pieces of your existing copy. Homepage, app onboarding, your last 10 tweets, your launch post, two changelog entries, a support reply. Paste them into one doc. This is your raw voice material.
- Pull 20 customer quotes. Reddit threads, X replies, support tickets, Indie Hackers comments, churn survey answers. Verbatim, including typos. Do not clean them up.
- Highlight every sentence in your own copy that sounds like you, not like a SaaS landing page. Usually 3 to 8 sentences. Those are your voice anchors.
- Name three voice attributes from what you highlighted. Not adjectives like "friendly." Specific pairs: "blunt, not rude." "Dry, not snarky." "Technical, not academic." The opposite matters as much as the trait.
- Write a do/don't list of 5 each. Real examples. "Do quote real user complaints verbatim. Don't paraphrase pain points into bullet language."
- Build a vocabulary table. Words you use, words you ban. Ban the words your competitors all use. Add the words your customers use that the category does not.
- Write three example captions in your finished voice. One announcement, one teaching post, one reply. These are the test. If the guide produces these, it works.
The whole thing takes about two hours if you have the source material ready. Most founders stall on step two, because they have never read their own customer feedback in one sitting.
· · ·
How do you find your real voice when the homepage already sounds generic?
Look at your DMs, not your marketing site. Look at the Slack message you sent a beta user at midnight explaining why a feature broke. Look at the angry email you almost sent to a competitor. That is your voice. The homepage is your voice wearing a blazer.
A second source: voice memos to yourself. Record a 90-second explanation of what your product does, no script, talking to a friend. Transcribe it. The rhythm, the fragments, the asides, that is the raw material. Most founders write 30% worse than they speak because they think writing requires a different register. It does not.
Third source: the way you describe the product when you are frustrated with it. "It is basically a brand bible generator that does not suck." That sentence has more voice than your entire about page.
· · ·
What's the difference between voice and tone in a saas context?
Voice is constant. Tone shifts by context. Your voice might be dry and blunt across everything you ship. Your tone in a status page outage post is apologetic and specific. Your tone in a launch tweet is confident and short. Same voice. Different tone.
Most founder voice guides skip tone entirely, which is fine for the first version. Add tone guidance after you have shipped 50 posts and noticed the contexts that trip you up.
· · ·
Long brand bible vs. one-page voice guide: which wins for solo founders?
| 40-Page Brand Bible | One-Page Voice Guide |
|---|---|
| Built for design agencies and brand consultants | Built for the founder writing tonight's post |
| Covers logo, color, typography, mission, values, pillars | Covers how sentences should sound, full stop |
| Takes 3 to 6 weeks and usually a contractor | Takes 2 hours with your own copy and quotes |
| Gets opened twice, then lives in a Notion archive | Lives pinned in your drafting tool |
| Designed for a team of 8 to stay aligned | Designed for one person to stop second-guessing |
| Updated annually if at all | Updated every time a customer says something better than you did |
The brand bible is the right answer if you have a marketing team of five. If you are the founder, the writer, and the person hitting publish, the one-page guide is the only version you will actually use.
· · ·
How does Helm fit into writing your voice guide?
Helm reads your public URL and produces a working brand bible in about 12 seconds. It pulls from your homepage, your changelog, your existing copy, and gives you the voice attributes, vocabulary, and example captions back in a format you can edit. The point is not to skip the thinking. The point is to skip the blank page.
Then Helm listens in the rooms your customers actually sit in: Reddit, Hacker News, Indie Hackers, X. Live posts, not search-term scrapes. You get the verbatim quotes that should go into your vocabulary list. You get the language gap between how you describe the product and how your users do.
Then Helm reviews your marketing across 8 strategy dimensions and tells you what to work on next. Voice is one of them. Distribution is another. Most founders find out they have a voice problem only after six months of posts that did not land.
no_card_needed · works_from_any_URL · open_in_30s
· · ·
FAQ
How long should a saas brand voice guide be?
One page. Maybe two if you include example captions. Anything longer does not get read, including by you. The test: can you recite your three voice attributes from memory? If not, the guide is too long.
Do I need a brand voice guide before I start posting?
No. Post 20 things first. Read them back. Highlight what sounded like you. That becomes your guide. Writing a voice guide from zero, before you have shipped anything, produces theory. Writing one from your own existing copy produces a tool.
How often should I update my voice guide?
When a customer describes your product better than you do, add their phrasing. When you ship a post that lands and feels like you, add the structure. Otherwise leave it alone. Voice guides that get rewritten monthly are not voice guides, they are anxiety.
Can I use AI to write captions if I have a voice guide?
Yes, if the voice guide is specific. Generic guides produce generic AI output. A guide with banned terms, verbatim customer quotes, and example sentences gives any AI tool, including Helm, enough to draft something that sounds like you. Without those inputs, you get the default LinkedIn voice.
What's the biggest mistake founders make writing voice guides?
Writing in adjectives. "Friendly, professional, approachable" tells you nothing. Every SaaS in the world claims those three. Write in opposites and examples. "Blunt, not rude. Says 'this is broken' before 'we're improving the experience.'" That is usable.
Should my voice change across channels?
Your voice should not. Your format should. The same blunt founder voice fits a tweet, a Reddit reply, and a changelog. The length and structure change. The personality does not. If you sound like a different person on LinkedIn than on X, pick one and rewrite the other.
How do I keep my voice consistent when I'm tired?
Pin the one-page guide above your monitor. Before drafting, read your three voice attributes and one example caption aloud. Takes 20 seconds. It resets the register. The reason your Sunday-night posts sound off is that you skipped this step.
· · ·
Helm is free for the first 50 founders. 17 of 50 spots are taken. Paste your URL. Get your brand bible in 12 seconds. Keep the one you build.