Agency content work depends on keeping each client's brand, sources, assets and review decisions together. When they are scattered, every new piece starts by rebuilding the same context.
The Studio organises that context per brand and connects repeated production steps through n8n and application code, so a team can move from a brief to content without redesigning the process for each client.
The problem
Agencies either publish unchecked AI text or lose days reviewing it, and each client's brand rules live in someone's head. The work needs separation between clients, quality checks and a clear point where a person decides.
What the system does
- One workspace per brand, with its own database, profile, connections and settings. A module never reads another module's tables.
- Blog, carousel and reel modules, plus SEO research, sharing one control plane for sign-in, permissions and a per-brand Live switch.
- Autopilot recipes that research a topic, draft, fact-check, score and revise, with a held state when a check fails.
- A single delivery service is the only part that sends or schedules anything, so publication has one gate.
A representative journey
- Step 1: Choose the brandPick a workspace. Its profile, past posts and connections are separate from every other brand's.
- Step 2: Brief and researchStart from a topic or an approved plan. Research and sources are attached to the job, not typed into a chat.
- Step 3: Draft per formatBlog post, carousel slides or reel script are produced as separate drafts from the same brief.
- Step 4: Check and reviseFact-check and quality scoring run first. A flagged claim holds the piece and shows the reviewer the sentence and reason.
- Step 5: Approve and deliverA person approves, or the brand's policy allows automatic delivery. Only the Live switch lets the delivery service send.
- Step 6: Keep the historyEach job keeps its versions, decisions and spend, so a reviewer can see what happened and what it cost.
Studio · fictional workspace
Brand ABrand BBrand CBrand brief · Brand A
Voice: warm, practical. Never promise results. Facts only from the approved list.
Live switch: off · connections: none
Draft 3
- Blog: spring routine
- Carousel: 5 tips
- Reel script: before and after
In review 1
- Blog: ingredient guide, 1 claim held
Approved 1
- Carousel: myth vs fact, scheduled Tue 09:00
Working prototypeUse a small working version of this on invented data, the way a person would.
Try the prototypeInspect the system
This anatomy is a proposed description of how such a system is put together. It is not an audit of a specific deployment.
Inspect the system
How Content operations studio for agencies is put together
- What it is
- Control planeSign-in, workspaces, grants, signed capabilities and the Live switch.
- What flows through it
- A user signs in and picks a brand. The plane issues a signed grant for that workspace and its modules.
- The decision
- Permissions are checked by signed capability, not trusted from the screen.
Read the whole system as a list
- Control plane. Sign-in, workspaces, grants, signed capabilities and the Live switch. Flow: A user signs in and picks a brand. The plane issues a signed grant for that workspace and its modules. Decision: Permissions are checked by signed capability, not trusted from the screen.
- Brand workspace. A per-brand database, profile and connections. Flow: Brand voice, past content and approved facts are read when a job starts. Decision: One database per company, so one brand's data cannot leak into another's.
- Production modules. Blog, visuals (carousels) and reels, plus SEO research, each with its own storage and worker. Flow: A brief goes in. Format-specific drafts come out with their sources. Decision: Modules do not read each other's tables. They talk through contracts.
- Checks and revision. Fact-check, scoring and a revision loop before a piece is ready. Flow: A draft goes in. A score, flagged claims and a revised draft come out. Decision: A failed check holds the piece and shows the reviewer the sentence and reason.
- Delivery service. The only component that publishes or schedules. Flow: An approved piece and a destination go in. A scheduled or published post and a record come out. Decision: Nothing sends unless the brand's Live switch is on and no stop is in force.
Key decisions
One database per company
A mistake in one client's workspace cannot leak into another's. It costs more to operate, which is the right trade for client work.
A single sender
Delivery is a separate capability behind a Live switch and an emergency stop. Modules cannot publish on their own.
Held, not silently fixed
When a fact-check flags a claim the piece is held and the reviewer is shown why, with keep or remove answers. A tool that quietly rewrites a claim hides the error.
Free providers first
Model and search providers are optional connections that stay off until a person connects them, which keeps cost visible.
Outcomes and limits
We publish no measured outcomes for this project, because we have none we can evidence. The description above is of what the system does, not of results it has produced.
- The current local build is not deployed. External providers are off until connected.
- Free model quotas were the practical bottleneck in recent testing. Throughput on a paid plan is untested here.
- Not every format or provider is claimed as in production use. Carousel, reel and publishing adapters are not claimed as delivered.
Guardrail
Nothing is delivered unless the brand's Live switch is on, and a failed fact-check holds the piece for a person.
Technical detail
Technology named in the portfolio for this kind of system. Which parts a given engagement used is not stated.
- n8n
- PostgreSQL
- Node.js
- Docker
- WordPress and social adapters
- Model and search APIs