Founder of Erudience. Head of AI at Absolute Intelligence UK. Ships production n8n and voice AI systems for UK and international teams.
One automation serves multiple brands by storing each business's tone of voice, topics, target audience, and platform mix as a data profile, then feeding that profile into the same content generation and publishing pipeline on a schedule. This means adding a new client is a configuration change, not a new workflow, and the human effort concentrates only on approvals and long-form publishing that genuinely need a person.
Managing content creation, scheduling, and posting across multiple businesses and multiple platforms is a full time job on its own if done manually. The pattern that makes one automation serve many clients without becoming an unmanageable pile of per-client scripts is a stored brand profile, not a hardcoded workflow per business.
This is the architecture behind a system covering content for several businesses across three platforms from a single pipeline.
The brand profile is what makes this scale
Each business has a stored profile, tone of voice, topics, target audience, platform mix, in a database. On a recurring schedule per business, an automation pulls the relevant brand profile and sends it to an AI model, which generates platform specific content variations. The workflow logic is identical across every client; only the profile data changes.
This is the difference between a system that scales to ten clients and one that needs a new workflow built for each one. Onboarding a new business is filling in a profile, not writing new automation logic.
Approval as a dial, not a fixed step
Generated content can route through a lightweight human approval step before publishing, or run fully hands off, depending on the business's risk tolerance. This is configured per client, not fixed globally. A regulated or reputation-sensitive business gets the approval gate; a lower-stakes account can run unattended once the tone and quality have been validated over a few cycles.
Platform specific publishing
Facebook and Instagram posts go out through an official publishing and scheduling tool built for those platforms. LinkedIn posts, short form and company page content, go out through the LinkedIn focused automation layer. Each platform's own API constraints and best practices are respected rather than forcing one generic publishing mechanism across all three.
The one piece that stays deliberately manual
LinkedIn's public API does not support publishing long form articles through any third party tool, so this piece is deliberately semi automated: the AI drafts the article and a person pastes and publishes it manually, which takes minutes rather than hours of writing. This is a case where fighting a platform limitation is not worth it; the automation still removes the slow part (writing from scratch) and leaves the fast part (pasting and clicking publish) to a human.
- ·A stored brand profile per client, not a workflow per client, is what makes one automation serve many businesses without multiplying maintenance work.
- ·Onboarding a new client becomes a data entry task rather than a development task.
- ·Human approval should be a per-client setting based on risk tolerance, not a single global policy applied to every account.
- ·Respect each platform's actual API constraints rather than forcing one publishing mechanism across all of them.
- ·Where a platform limitation makes full automation impractical, as with LinkedIn long form articles, automate the slow part and leave the fast part to a human rather than forcing a workaround.
Frequently asked
How many brands can one pipeline realistically manage?+
The pattern itself does not impose a hard limit since it is data-driven, not workflow-per-client. Practical limits come from review capacity for clients on the approval gate, not from the automation itself.
What AI model generates the content?+
This build uses Claude via the Claude API for content generation, prompted with each brand's stored profile to produce platform specific variations.
Why can't LinkedIn long form articles be fully automated?+
LinkedIn's public API does not expose an endpoint for publishing long form articles through third party tools, only shorter posts and company page updates. Full automation of that specific format is not currently possible without violating platform terms.
How is quality controlled across many brands without reviewing everything manually?+
Through the per-client approval setting for higher-risk accounts, combined with the stored brand profile keeping tone and topic consistent, which reduces the odds of an off-brand generation in the first place.
Further reading and references
Related work on this site, and the tools and profiles referenced above.
Get new guides like this one
Whatever I ship next, straight to your inbox. No noise, unsubscribe any time.
