web analytics
Back to blog

How I built editorial standards from zero (and why it was the most strategic thing I did all year)

Extractable summary

Editorial standards are the documented infrastructure that determines how a specific company writes, what it values in its content, and what quality floor every piece must clear. This article walks through how I built editorial standards from zero at a B2B SaaS company, what they covered, what changed downstream once they were in place, and why they turned out to be the single most strategically valuable thing I built all year, above the AEO/LLMO framework, the multi-persona content strategy, and the GTM pivot work.

Editorial standards are the most strategic document a content team can write, because they set the quality floor for everything that comes after them, and most B2B companies don’t have them. When I built them from zero at a B2B SaaS company serving 200+ higher education institutions, review cycles went from two weeks to three days and the blog, LinkedIn, product pages and sales materials started sounding like the same company. The stakes are bigger than tidiness: in the 2024 Edelman-LinkedIn B2B Thought Leadership Impact Report, 73% of 3,500 B2B decision-makers said thought leadership is a more trustworthy basis than marketing materials for judging a company’s competence. The catch is that standards take time to build, and my first draft was too long and too much about my own taste.

Stat card: review cycles dropped from two weeks to three days after editorial standards were introduced at a B2B SaaS company serving higher education.

When I joined that company, I audited the existing content within my first two weeks: blog posts, product pages, whitepapers, landing pages, social content and sales materials. The pattern jumped out in a few hours, and it was the same mess I’d later find in the 40+ off-brand assets at an eMobility company. Different posts spelled the product name differently, sales materials contradicted the website on specific capabilities, and pages flipped between “our platform”, “the platform” and “the product” inside the same funnel. Two whitepapers made contradictory claims about the same integration, and one landing page carried a statistic nobody could source when I asked.

None of it was anyone’s fault: different people had written the content at different times with no shared reference, and when there’s no standard, writers default to their own instincts, which never add up to one brand voice. So I built the standards.

What do editorial standards cover?

Editorial standards cover how a specific company writes and what it values, which goes much further than a style guide. A style guide tells you which dictionary to use and whether to capitalise job titles; the standards capture one company’s editorial personality in enough detail that someone else can reproduce it. Mailchimp’s public content style guide is a good example of the bigger version, with voice and tone, a word list and rules for each kind of content, built so its teams write clearly and consistently across every channel.

Style guideBrand guidelinesEditorial standards
What it settlesSpelling, punctuation, capitalisationLogo, colours, type, taglineHow this company writes, and what it’ll claim
Who it’s forAnyone writingDesigners, agenciesEveryone producing content, human or AI
Specific to the company?Mostly genericYes, visuallyYes, in voice, vocabulary, evidence and positioning
What breaks without itInconsistent mechanicsAn off-brand lookContradictory claims, voice drift, unsourced stats

The standards I built covered six areas:

  1. Voice and tone rules for how the brand sounds in practice. I wrote each rule with examples, a sentence in our voice next to one that wasn’t, and a line on what made the difference, because voice is only useful once it’s concrete enough that someone else can copy it without guessing.
  2. Prohibited phrases, banned regardless of context: “cutting-edge”, “seamless”, “best-in-class”, “industry-leading” and a longer list of corporate-speak that had crept in over the years. Once a phrase means nothing from overuse, cutting it is faster than trying to rehabilitate it.
  3. Competitive positioning guardrails for how we talked about competitors, adjacent platforms and the wider market: which claims we could make directly, which needed careful framing and which were off-limits. Overstepping created legal exposure, and the opposite problem, underselling what made us different, left pipeline on the table, so the guardrails made the line visible.
  4. Evidence standards, which defined what counted as a verifiable claim. Every statistic needed a documented source and comparative statements needed evidence before publication, while the account owner had to sign off any customer outcome. The rule was simple: trace every claim to a source or cut it, and I’ve written about why that verification discipline is a competitive moat separately.
  5. Formatting and structure across every format: headline length, paragraph length, heading hierarchy, lists, FAQ formatting and CTA placement. These seem minor until you notice they’re the difference between a blog post that reads like a blog post and one that reads like whatever the writer felt like that day.
  6. Instructions by content type, since product pages, LinkedIn posts, whitepapers and sales enablement each carry their own tone. I gave each format its own sub-section, so nobody writing a LinkedIn post was guessing how it should differ from a blog post.
Card listing the six areas of editorial standards: voice and tone, prohibited phrases, competitive guardrails, evidence standards, formatting and structure, and rules by content type.

How do you build editorial standards from scratch?

You build them by listening first, auditing what exists, drafting, testing the draft on live work and wiring it into the workflow. It took me about three weeks of focused work, spread over roughly six weeks of real time because I was producing content alongside it.

  • Stakeholder interviews came first. I talked to sales, product, leadership and customer-facing roles about how the company wanted to sound against how it actually sounded, which brought out the gap between the aspirational voice (“confident and expert”) and the content (“cautious and generic”). People also felt strongly about specific words, and my job was to synthesise rather than collect, so some of those inputs made it in and others didn’t.
  • The content audit gave me ammunition: I catalogued every inconsistency across a large sample of existing content (spelling variations, voice drift, contradictory claims, unsourced statistics, competitive overreach), so the standards could point at concrete examples. Instead of “avoid corporate-speak”, I could write “avoid the following phrases that appear across our content”, with the list.
  • Category research gave me a reference point: I looked at how adjacent B2B SaaS companies handled tone, comparative claims and evidence thresholds, to see the range of positions on offer before choosing ours.
  • Iterative drafting is where I learned the most: the first version was too long and too prescriptive, and it leaned far too much on my own preferences. Stakeholders’ feedback made the second better, but it still missed cases that came up in day-to-day writing, and the third version worked because I’d tested it on actual production by then.
  • Integration into the workflow was the hardest part, because the document was the easy bit. I built the standards into content briefs, review checklists and onboarding material, and quoted them in review feedback (“this breaks rule 3.2, here’s the fix”) until they became the default answer to any question about how content should be written.
Timeline of building editorial standards: interviews, a content audit, category research, drafting through three versions and workflow integration, taking about three weeks of work across six weeks.

What changed once I enforced the editorial standards?

Once I enforced them, production got faster, reviews got shorter, every channel started to match, and editorial decisions stopped being questions of taste. That’s where they stopped being a documentation exercise.

Production got faster, which surprised me, because I’d expected more rules to slow writers down; instead, clear rules meant less time second-guessing what to call a feature, how to reference an integration or what tone suited an audience. The standards took hundreds of micro-decisions out of every piece and left the thinking time for the parts that needed it.

Review cycles shrank. Before the standards, feedback was mostly “this doesn’t quite feel right” with vague suggestions. Afterwards, it looked like this:

“This breaks the evidence standards: please source or cut.”

“This uses a prohibited phrase: replace with [alternative].”

Clear feedback resolves faster than vague feedback, and two-week review cycles became three-day ones; it’s the same editing muscle I argue for in why the best content marketers are editors first. With 39+ LinkedIn posts a quarter going out alongside blog content, whitepapers and sales enablement, days saved on every review were the difference between hitting targets and falling behind.

Channels started matching. Within a few months, you could put a blog post, a LinkedIn campaign, a product page and a sales one-pager side by side and see they came from the same company, which most B2B SaaS companies can’t do. That consistency held up the multi-persona content strategy I was running, because five personas getting content that sounded like five companies would have wrecked the brand.

Annotated example comparing vague review feedback with feedback that cites an editorial standard and gives the fix, such as sourcing a claim or replacing a prohibited phrase.

Brand voice stopped being a question of taste. When someone asked why our content sounded the way it did, I had a documented answer instead of an opinion, so editorial calls traced back to principles. That counts for a lot when you have to push back on a stakeholder request that would hurt quality, and it’s what makes the kind of ownership I wrote about in why companies say they want ownership and then punish it concrete.

Onboarding got easier. When I worked with freelancers or briefed colleagues, the document did half the onboarding: instead of explaining the voice out of my head, I sent the standards, and people arrived already knowing the basics.

Why are editorial standards strategic infrastructure?

Editorial standards are strategic infrastructure because they set the quality floor for every piece of content, including the pieces written by people who aren’t your best writer on their best day, since otherwise quality is whatever each writer happens to bring. With standards, everyone starts from the same rules, so the best writers spend their energy above that line instead of on it. Kristina Halvorson put governance into the definition of the discipline back in 2008:

“Content strategy plans for the creation, publication, and governance of useful, usable content.”

Kristina Halvorson, A List Apart

Standards are the governance part, and buyers notice when it’s missing: the same Edelman-LinkedIn study found only 15% of decision-makers rated the thought leadership they read as very good or excellent, so a company whose content holds together across channels is already ahead of most of what its buyers see. The longer argument for why so much B2B content blurs together is in why B2B content sounds the same.

They’re also an AI readiness play, which I didn’t fully appreciate at the time, because standards specific enough for a freelancer are specific enough for a model: word lists, sentence length limits, evidence rules and formatting rules dropped straight into AI prompts and agent instructions, which is the core of context engineering for content marketers. The gap shows in the data: in the Content Marketing Institute’s 2026 B2B research, 89% of B2B marketers used AI to create content, and CMI’s research release reported that fewer than four in ten said it had improved performance. Feed a model “keep it conversational” and it writes like everyone else, which is why your standards document is the most useful brief you can give it.

Comparison of a vague AI instruction, keep it conversational, with specific rules taken from editorial standards: an approved word list, a sentence length limit, sourced statistics and standalone FAQ answers.

And they’re trust infrastructure: once writers, reviewers, sales and leadership know editorial decisions follow principles, people trust that the standards were followed instead of debating whether a piece is “good”, which is a far easier conversation to have every week. When I was running content for five buyer personas, the standards kept all five sounding like one company even though tone, technical depth and pain points differed across them.

How do you get buy-in for editorial standards nobody asked for?

You get buy-in by framing the standards as risk and efficiency rather than creativity, and by building them before you ask. Nobody asks for them: the CEO isn’t requesting documented writing rules, sales isn’t complaining about voice drift and engineering has other priorities, so the content marketer who wants them has to make the case.

The risks are what land: inconsistent claims across channels confuse prospects, unsourced statistics create credibility problems and competitive overreach creates legal exposure, and any Head of Marketing recognises those faster than “our content would be more consistent”. The efficiency gains come with them: faster reviews, shorter production cycles and onboarding that takes half as long.

I also built them before asking for permission: they never had a line in anyone’s budget, and they existed because I prioritised them alongside everything else, so once they were producing visible results, they’d shown their value without me having to argue it. Getting buy-in afterwards, with evidence, beats asking upfront for infrastructure nobody can picture yet, and it’s how I approached the wider content system too. The AEO/LLMO framework I built later only worked at speed because the standards already existed, and most companies won’t give you the time to build them before demanding output, which is exactly why waiting for permission is the wrong move.

Frequently asked questions

A style guide covers generic writing conventions, like which dictionary to use, whether to capitalise job titles and how to handle commas. Editorial standards go further by documenting how one specific company writes and what it values: voice rules with examples, prohibited phrases, competitive positioning guardrails, evidence standards that trace every claim to a source, and instructions for each content type. Style guides are largely interchangeable between companies, while editorial standards capture one company’s editorial personality and work as both quality control and strategic infrastructure.

Building editorial standards from scratch took me about three weeks of focused work, spread over roughly six weeks of real time while I kept producing content. The process runs through stakeholder interviews, an audit of existing content, research into how comparable companies handle tone and claims, at least three drafts tested against live production, and integration into briefs, review checklists and onboarding. Expect the first draft to be too long and too prescriptive; mine needed three versions before it worked.

Editorial standards become the instructions for AI-assisted content workflows, because rules specific enough for a freelancer are specific enough for a model: word lists, sentence length limits, evidence requirements, formatting rules and prohibited phrases. The Content Marketing Institute’s 2026 research found 89% of B2B marketers using AI to create content, but fewer than four in ten said it had improved performance. A company with documented standards can give its AI tools concrete rules instead of vague instructions like “keep it conversational”, which gives the output a chance of sounding like the company.

The most reliable way to get leadership behind the standards is to frame them as a risk and efficiency fix and to show results before asking for formal approval. Inconsistent claims, unsourced statistics and competitive overreach are risks any Head of Marketing recognises, and faster reviews and onboarding are gains they can measure. Building a first version alongside regular work, then pointing to shorter review cycles and consistent channels, is easier to approve than a proposal for infrastructure nobody can picture yet.

How did this land?No reactions yet
Solange Rainha
Solange Rainha
Content Marketing Manager | 10+ Years B2B SaaS & AEO/LLMO