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.
From brief to live post
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.
| Who | What 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 person | Discusses the draft, checks the preview and clicks Publish. |
A separate writer per brand, each with its own voice and facts.
An automatic backup before every publish or update means any change can be undone.
Nothing goes live unseen. Only a person can click Publish.
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.
Challenges and how we solved them
Both brands, published through one workflow
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.