# Writing a Content Style Guide for Your SaaS > How to write a content style guide for a SaaS company, including voice, grammar choices, formatting, terminology, product mentions, accessibility and keeping it short enough to use. Source: https://comppound.com/blog/writing-a-content-style-guide-for-your-saas (published 2026-09-24) A content style guide documents how your company writes. It helps writers, marketers, product teams and AI-assisted workflows produce consistent content. Without one, every writer makes different choices about capitalization, terminology, tone and formatting, and readers notice the inconsistency even if they can't name it. A SaaS content style guide has an extra job: keeping product names, feature descriptions and claims accurate across every page. This guide explains what to include, how to keep the guide short enough that people use it, how to use it with AI tools and how to keep it current. It ends with a one-page starter guide you can adapt today. ## Why a SaaS company needs one Small SaaS teams often assume a style guide is something for large companies with content departments. In practice, the need appears early. The founder writes the homepage, a contractor writes blog posts, a product manager writes release notes and someone in support writes help articles. Each makes reasonable but different choices. One capitalizes feature names, another doesn't. One calls customers "users," another calls them "teams." One promises the product is "the leading" solution, another avoids claims entirely. Over time, these differences make the brand feel less trustworthy and make content harder to maintain. When a feature is renamed, nobody knows every place the old name appears. When someone asks whether a claim on the pricing page is supported, nobody knows where it came from. A style guide solves these problems with a shared set of decisions written down once. ## What to include ### Voice and tone Describe your brand voice with a few traits, such as clear, helpful and direct. Traits alone are too abstract to guide anyone, so explain what each means in practice. "Direct" might mean leading with the answer, using short sentences and avoiding hedging. "Helpful" might mean explaining why a step matters, not just what to do. Then show how tone changes by context. The voice stays the same, but a blog post can be more conversational than an error message, and a security page should be more precise than a launch announcement. A short example for each major context, such as a blog intro, a product notification and a support reply, helps writers adjust without guessing. ### Audience Describe who you write for and what they already know. A guide for a developer tool might say readers are experienced engineers who don't need basic concepts explained. A guide for a finance product might say readers are finance leads who understand accounting deeply but may not know technical terms. This section prevents writers from either over-explaining or assuming too much. ### Grammar and mechanics Make the small decisions once so writers don't make them differently every time. Decide whether headings use sentence case or title case, whether you use the Oxford comma, whether contractions are allowed, when numbers are written as words or numerals and how dates are formatted. None of these choices matters much on its own. Consistency is what matters, and readers notice when a single page mixes formats. ### Terminology This is the section that makes a SaaS style guide different. List every product and feature name exactly as it should appear, including capitalization. Write feature names the way they appear in the app, so marketing pages, help articles and the product all match. List terms to avoid, such as old feature names, internal code names or competitor terminology. And record preferred customer language, such as whether you say "customers," "teams" or "users" in marketing copy. Terminology drifts quickly in a growing product. A short, maintained list saves hours of searching and fixing later. ### Formatting Set expectations for paragraph length, heading structure, the use of bold and italics and how links are written. These rules shape how content reads on screen. A guideline as simple as preferring short paragraphs and descriptive headings will make most content easier to scan. Decide too when structured formats such as step lists or comparison tables are appropriate, so writers use them where they help rather than by habit. ### Product mentions Explain how and when to mention your product in content. Many SaaS blogs either never mention the product, which wastes the opportunity, or mention it in every paragraph, which turns useful guides into sales pages. A good rule is to mention the product where it genuinely helps the reader complete the task, and nowhere else. ### Claims and sources Set rules for statistics, citations and claims. A common standard is that every statistic links to a reputable source and that superlatives such as "best," "#1" or "leading" are not used without evidence. This protects the company's credibility and reduces legal risk. It also gives editors a clear basis for removing unsupported claims without a debate each time. ### Accessibility Include basic accessibility practices: alt text for images that conveys their meaning, descriptive link text rather than "click here," plain language and avoiding important text inside images. These practices help readers using assistive technology and usually make content clearer for everyone. ### SEO guidelines Add a few SEO conventions, such as how titles are formatted, how long meta descriptions should be and how to approach internal linking. Keep this section short and practical. Its purpose is to make sure routine SEO steps happen consistently, not to replace a full SEO strategy. ### Examples Examples are what make a style guide usable. For the most important rules, show a good and a bad version side by side. A writer can read "be direct" and still write a meandering intro, but seeing a direct intro next to a meandering one makes the difference obvious. ## Who should write it In a small SaaS company, the best author is usually the person who edits the most content, often the head of marketing or a senior writer, working with input from product and support. Product knows the correct feature names and how the product is changing. Support knows which terms confuse customers. Writing the first draft alone and then asking those teams to review the terminology section is usually faster than a long collaborative process. The founder should sign off on voice and claims, since those reflect how the company wants to be seen. ## Keep it short A long style guide rarely gets read. If the guide runs to dozens of pages, writers will skim it once and then rely on memory, which defeats the purpose. Aim for a few pages, with quick-reference sections that writers can scan while drafting. Put the most common decisions at the top. Detailed explanations can live in linked documents for anyone who wants them. ## Make it easy to find Store the guide where writers already work, such as the same workspace as your content briefs and editorial calendar. Link it in every brief, so a new contractor sees it at the moment they need it. A guide hidden in a shared drive folder that nobody visits might as well not exist. ## Use it with AI tools If your team uses AI tools to draft or edit content, include the style guide, or its most important sections, in the prompts and briefs you give those tools. A model given your terminology list, voice description and claim rules will produce drafts much closer to your standards than one working from a generic instruction. Review AI-assisted outputs against the guide just as you would any other draft. Pay particular attention to terminology and claims. AI drafts can introduce outdated feature names, generic superlatives or statistics without sources, and the style guide gives editors a clear standard to check against. ## Update it regularly Review the guide whenever something significant changes: when product names change, when positioning shifts or when you add new content types such as video scripts or in-app messages. Also schedule a regular review, perhaps every six months, with whoever writes most of your content. They'll know which rules are useful, which are ignored and which questions keep coming up. A practical habit is to add a rule whenever an editor corrects the same thing twice. Repeated corrections show where writers need guidance. Equally, remove rules that nobody follows or needs. A guide that only grows becomes the long document nobody reads. ## Common mistakes The most common mistake is making the guide too long, which guarantees it won't be used. The second is leaving out examples, so rules stay abstract. The third is letting terminology go out of date, which turns the guide into a source of errors rather than a fix for them. The fourth is having nobody own updates, so the guide slowly drifts away from how the company actually writes. ## A one-page starter guide If you have nothing today, start with a single page like the one below and expand only when real questions come up. Each line is a decision you can adopt, change or replace. For voice, write clearly, directly and helpfully. Explain things plainly and avoid hype. For headings, use sentence case, such as "How to calculate churn," rather than title case. Always capitalize the product name, and write feature names exactly as they appear in the app, such as "Scheduled reports" and "Data sources." In marketing copy, refer to "teams" or "customers" rather than "users." For numbers, use numerals for 10 and above and words for one through nine, except in metrics and tables. Contractions are allowed and encouraged. Use the Oxford comma. Every statistic links to a source, and words like "best," "#1" or "leading" are not used without evidence. For formatting, use short paragraphs and descriptive headings, and use step lists or comparison tables only where they make the content easier to follow. Mention the product where it helps the reader do the task, not in every section. Give images alt text, use descriptive link text and don't put important text inside images. Avoid words such as "leverage," "synergy," "revolutionary," "game-changing" and "seamless." That page will answer most of the questions a new writer has in their first month. Review it after a few weeks of use, and add only what real drafts show is missing. ## The takeaway A SaaS content style guide keeps writing consistent, accurate and on-brand across marketing, product and support. Cover voice and tone, audience, grammar, terminology, formatting, product mentions, claims, accessibility and basic SEO, and illustrate the key rules with examples. Keep it short, store it where writers work, include it in AI prompts and briefs, and give someone ownership of updates. A short guide that writers actually open is far more valuable than a long one that sits in a folder. ## Keep reading - [Building a Future-Proof SaaS Content Strategy: A Guide to Outlasting Algorithm Updates](/blog/building-a-future-proof-saas-content-strategy-a-guide-to-outlasting-algorithm-up) - [Measuring SEO ROI for SaaS: A Step-by-Step Guide to Proving Content's Business Impact](/blog/measuring-seo-roi-for-saas-a-step-by-step-guide-to-proving-contents-business-imp) - [Writing SaaS Content That Survives AI Summaries](/blog/writing-saas-content-that-survives-ai-summaries) ## Frequently asked questions ### What should a SaaS content style guide include? Voice, audience, grammar choices, terminology, formatting, product mentions, claims, accessibility and SEO guidelines. ### How long should a style guide be? Short enough to use regularly, often a few pages with examples. ### Should style guides be used with AI writing tools? Yes. Including the guide in prompts and reviewing outputs helps maintain consistency. ## About Comppound Comppound runs SEO and AI search for B2B SaaS companies: a person sets the plan and reviews samples and every high-risk page, and AI speeds up production. - [Check a page free](https://comppound.com/tools/seo-checker): Check one of your pages before you change anything else - [See pricing](https://comppound.com/pricing): Want the content written, reviewed and published for you?