Skip to content

Publish everywhere from writing once

New content in → LinkedIn, newsletter, and threads out.

You will recognise at least one of these

  • Content gets written then never distributed
  • Repurposing is somebody's Friday afternoon job
  • Your best material lives in one channel
  • Publishing depends on a person remembering

Most teams publish once and move on. When you are selling into several African markets at once, the same message has to land differently in Lagos and Cape Town, and doing that by hand is what stops teams publishing at all.

What we actually build

An n8n pipeline monitors your CMS for new publications. On trigger, Claude AI generates three repurposed formats: a LinkedIn post, newsletter snippet, and Twitter thread. Each is routed to the right team member in Slack for one-click approval before auto-scheduling.

The stack

  • n8n
  • Claude AI
  • Slack
  • Buffer
  • CMS Webhook

Every system ships documented and built to run without us. The goal is that you do not need Zuun after 90 days.

What changes

  • Content output 3x with same team size
  • Distribution time per piece: 3 hours → 14 minutes
  • Newsletter open rate +22% from consistency

Real numbers from real builds are on the case studies. We do not quote figures that did not happen.

Content Automation, answered

Does the AI write the posts?

It drafts. A person approves in Slack before anything schedules. Fully autonomous publishing is how brands end up apologising, and we do not build it that way.

What if we do not publish often enough to need this?

Then you probably do not need it yet. This pays off when you are already producing content and losing value because it only ever reaches one channel.

Which channels does it cover?

Usually LinkedIn, a newsletter and a thread format. The pipeline is not channel specific, so adding one later is a config change rather than a rebuild.

The other four

Ready to build this?

We scope it on a call and start building. No decks, no six week discovery phase.