Good posts take hours, and two brands need two voices

Good blog posts take hours of research and writing, and two brands need two distinct voices.

Copying drafts into the website and fixing formatting by hand is slow, and a mistaken update to a live post is hard to undo.

We wanted one place to go from a chosen topic to a published post, quickly and safely, with a person approving every word that goes live.

Write, discuss, preview, publish

The blog workflow takes a chosen topic to a published post for our two brands. It was built for our own companies, BinaryBits and TheDataHQ, and it is used every day.

The product screen, shown with test data. Real screens use the same layout.
✍️
A writer per brand
Each writes in its brand's voice and researches the topic fresh.
💬
Discuss the draft
A person can discuss and revise the draft with the AI in the app, like working with a writer.
👁
Preview
The post shown as it will look before anything goes live.
⬆️
Publish from the app
One click, by a person only.
💾
Backups and undo
A copy is kept before every publish or update, so any change can be undone.
🖼️
Images handled for the web
Cover options, and images optimised and uploaded with the post.

From brief to live post

AI agentAutomated stepPersonData or serviceChosen topic & brieffrom the SEO strategistWriter per brandresearch and writeDraftDiscuss & reviseperson with the AIPreviewexactly as it will lookA person clicks PublishBackupbefore every changeLive websitebriefdraftrevisionsreadyapprovedpublishgoes live
Separate writers keep each brand's voice. The AI never publishes: only a person's click does, and a backup comes first.
1
A topic and its brief come from the strategist
The AI SEO strategist hands over the chosen topic and a brief for the writer.
2
The brand's writer researches and drafts
Each brand has its own writer, with its own voice, audience and facts. Research is fresh for every post.
3
A person discusses changes
The person asks for changes in the app, and the writer revises the draft.
4
Preview
The post is shown exactly as it will look on the site.
5
A person publishes
One click, by a person. The AI never publishes on its own.
6
A backup is kept automatically
A copy is taken before every publish or update, so any change can be undone.

Two writers, one person approving

Separate writers per brand keep the voices distinct. The AI never publishes; only the person's click does. Research is fresh per post, not template-based. The agents run on Anthropic's Claude, through Claude Code skills.

WhoWhat it does
Writer for Brand A (AI)Researches and writes in the first brand's voice.
Writer for Brand B (AI)Researches and writes in the second brand's voice.
Preview, backup and publishing (automated)Shows the post as it will look, keeps a backup before every change, and publishes when the person clicks.
A personDiscusses the draft, checks the preview and clicks Publish.
Distinct voices

A separate writer per brand, each with its own voice and facts.

Safe publishing

An automatic backup before every publish or update means any change can be undone.

People stay in control

Nothing goes live unseen. Only a person can click Publish.

Fast

In-app discussion and preview remove the copy-and-paste step.

Technologies used

Our own Python code, an HTML preview, a website publishing integration, and AI agents built on Anthropic's Claude.

Python Claude agents HTML preview Website publishing integration

Challenges and how we solved them

❌ Challenge
Two brands sounding the same.
✓ What we did
A separate writer per brand, each with its own voice and facts.
Result: Distinct posts.
❌ Challenge
Safe publishing.
✓ What we did
An automatic backup before every publish or update.
Result: Any change can be undone.
❌ Challenge
Keeping a person in control without slowing down.
✓ What we did
In-app discussion and preview, with a one-click publish.
Result: Fast, and nothing goes live unseen.

Both brands, published through one workflow

2
Brands, each in its own voice
Daily
In daily use
Every change
Backed up first

Posts for both brands are written and published through this workflow, and it is in daily use. Business results will be added here once they are measured.

Last updated: November 2026

What this means for you

The same workflow suits any team that publishes for more than one brand or client.

  • A multi-brand content workflow. One place to research, write, review and publish, with each brand in its own voice.
  • An agency managing several client blogs. A writer per client, with the agency approving every post.
  • Brand-safe AI writing with approval. Drafts and revisions by AI, publishing by a person, backups before every change.

For a client we would connect it to your CMS (WordPress, a headless CMS or your own), with roles and approvals. For client systems we build on PostgreSQL, MySQL, MongoDB or Redis, and cloud data warehouses where needed, chosen for the project's scale and team. See our AI agent development services.

Frequently asked questions

Does the AI publish on its own?

No. A person reviews, previews and clicks publish.

How do you keep each brand's voice?

Each brand has its own writer with its own voice, audience and facts.

What if a published change is wrong?

A backup is taken before every publish or update, so it can be undone.

Can it work with our CMS?

Yes. We integrate with your CMS and approval flow.