Content Marketing

The Head of Content v1.0

Runs an editorial team of six plus freelancers and answers for what goes live. Wants briefs that carry the goal to the writer, a calendar that shows what is late, and an approval trail that says which version legal released — not a status anyone can flip to "approved".

The SME Marketer v1.0

Is the marketing department of a 120-person Mittelstand company and writes half the content with an AI assistant. Wants to know who owns what the model wrote, whether her drafts train it, and what the plan costs once she adds a second language and the agency as guests.

The Localisation Lead v1.0

Ships every piece in German, English and French for the DACH region and beyond. Wants locales on the field, not copies of the entry, translation status per language, and a documented export of content, model and locales — because a repository that cannot leave is a hostage, not an asset.

The Web Engineer v1.0

Builds the website and the integrations the content flows through. Wants a versioned API with published rate limits, webhooks on publish, preview environments, and a migration CLI that works in both directions — and reads "headless" as a promise about the API, not a logo.

The Data Protection Officer v1.0

Signs off every tool that stores the company's drafts, author profiles and campaign data. Wants the contracting entity and hosting region named, the subprocessor list with the AI providers on it, prompt retention in days, and training on customer content excluded in the terms rather than in a blog post.

The Skeptic v1.0

Has read "AI-powered content at scale", "one source of truth for every channel" and "no lock-in, it's headless" on every page in this category. Reads instead for the export that includes locales and history, the clause on training with customer content, and what the invoice does when the third locale and the API overage arrive.