One content engine, every channel

The blog feeds the newsletter. A guide becomes a sales one-pager, a knowledge base article, a Spanish landing page and a week of social posts. Each channel doesn’t start from a blank page; it starts from something we’ve already researched, written and checked.

Here’s what it took to build that, and what it takes to keep it running.

Start with standards, not volume

The first thing I built wasn’t a content calendar. It was a set of standards: how we research, who we write for, what every piece must answer, and how it should look. Then I turned those into briefs. A good writer brief does most of the editing in advance. It names the reader, the questions they’re asking, the competitors’ angles, the keywords and the internal experts to talk to.

Standards are also what let a team scale without losing its voice. I trained our writers to work the way I did: listen to customer calls, read sales chats, review lead queries, talk to internal subject matter experts, and answer those questions in every piece.

Build topics, not posts

Single posts rarely win. Clusters do. We organized content around our core services, with a main page supported by guides that go deeper on each question a buyer has. That structure is what built our topical authority, and it later turned out to be what AI search tools cite.

Refresh before you publish more

The most underrated work in content is maintenance. Regular audits showed us which pages were slipping, which were outdated and which could rank with more depth, better visuals or structured data. Refreshing a page that already has some authority usually beats writing a new one. Over time, that’s how one of our sites moved from an average Google position of 19 to 6, through two site migrations.

Design it to feed every channel

An in-house engine pays off when every team can draw from it:

• Sales gets one-pagers and comparison pages built from our best-performing guides.
• Support gets knowledge base articles written in the same plain language customers see before they buy.
• Lifecycle gets newsletters and onboarding emails that point to content customers actually use.
• International gets core pages to localize, with native-speaking colleagues adapting the language rather than just translating it.
• Product launches get a content cluster in place before the feature ships.

Protect the plumbing

The engine is only as good as what you can measure. During our 2025 site migrations, parts of our attribution setup were missed, and traffic started showing up in the wrong places. Along with our web developer, I caught these leakages by comparing our internal reports with Zoho CRM and GA4, then worked with web dev and IT to fix them. Now marketing is part of every rollout from the start.

What keeps it running

An in-house content engine isn’t a project with an end date. It’s a habit: regular meetings with IT, Sales and Support so we understand the product; briefs that carry the standards; audits that keep the library healthy; and data we trust. When it works, the content does the work for every team, not just for search.