Every Monday morning, five blog drafts are waiting in our Webflow CMS. Each has sources, an SEO package, a hero image and a LinkedIn post. None of them goes live until a person reads it.
That is a Claude content automation workflow, and we run one on our own blog. This article shows how it works, then how a small brand could have the same kind of thing built for product posts, newsletters or social captions. It went through the same routine and was edited by a person before it went out.
What does "Claude content automation" actually mean?
It means an AI assistant that runs a repeatable content routine on a schedule, using written rules, access to your tools and a person who approves the result. The rules are called skills, the tool access comes from connectors, and the approval is a human gate. It is not "press a button, get a blog."
What is our own pipeline, step by step?
Friday afternoon. A routine checks every existing post and every row in our content calendar, so nothing repeats. It reads a few signals, such as client requests and newsletters, and adds five planned subjects to a Notion calendar.
The weekend. A person edits a subject, an angle or a note, or skips an idea entirely.
Monday morning. A second routine takes each subject and researches it. It checks every fact and date, writes the article in the studio's voice, generates a 2K hero image, saves a draft in Webflow and keeps a full backup in Notion: the article, the SEO package, the sources, the image and a LinkedIn post. It never publishes. It sends one notification, and then it waits for us.
We built this for ourselves first, because a small studio cannot spend a day a week on blog admin. The same approach works for a brand's product posts or newsletters.
What are the four building blocks for your brand?
1. Skills. A skill is a folder of instructions, scripts and resources that Claude loads when it is relevant to the task. Anthropic's own description lists following an organization's brand guidelines as an example (Claude blog). In practice this is one file holding your brand voice, banned words, structure and checklists.
2. Connectors. These link Claude to where your content lives: a notes tool or shared drive, a website system or shop, a design tool, a customer database.
3. A schedule. Weekly, or triggered by an event such as a new product.
4. An approval gate. Drafts only. A person publishes.
Anthropic's Claude for Small Business, launched on May 13, 2026, shows the same pattern. It offers connectors for PayPal, QuickBooks, HubSpot, Canva, Docusign, Google Workspace and Microsoft 365, plus 15 ready workflows and 15 skills. One of them, a campaign runner, finds slow revenue periods, analyzes HubSpot campaign performance, drafts a promo strategy and generates Canva assets. The owner approves before anything is sent, posted or paid (Anthropic). Ready workflows save setup time, but a brand still needs its own voice skill, because no generic workflow knows how you sound.
What does it still do badly?
- Facts. They need checking. Our routine verifies every number and labels vendor claims as vendor claims, and a person still reads the result.
- Voice. It drifts if the rules are vague. Specific rules beat adjectives.
- Access. Connectors only see what their permissions allow. That is a good thing, and it needs setting up carefully.
- Images. Product images need the same checks as any AI image: label, shape, colors.
- Cost. Model and tool usage adds up, and it should be counted from the start.
Should you build it yourself or have it built?
A capable person can set up a basic version. The time goes into writing good rules, testing runs and handling failures, not into the first draft.
A studio build should include the skill files, test runs, guardrails such as draft-only and no sending, a handover, and support when tools change. For context, one vendor compilation puts mid-tier B2B content agency retainers at around $5,000 to $15,000 per month (Averi). That figure is a vendor estimate, so treat it as a rough benchmark, not a quote. We do not offer a price list; ask any provider for the build fee, the monthly support and the tool costs separately.
Practical takeaway: five questions before you automate content
- Which content repeats every week?
- Where does it live now?
- What must a person always approve?
- What would a bad output cost you?
- Who updates the rules when the brand changes?
If you can answer all five on one page, you are ready to automate the routine. If you cannot, start by writing that page, with or without a studio.
If you want to see how we work, visit 35milimetre.com.