Case Study — Multi-Agent System Design

ContentOps Squad: orchestrating 10 AI specialists for a one-person social media operation

A multi-agent system that replaced the always-on manual grind of running social media solo — trend research, content drafting, comment triage, reporting, pricing intelligence — with a single conversational entry point.

Problem

One operator, a dozen full-time jobs

The brand this was built for runs its entire social presence with no dedicated team — one person doing trend research, content drafting, comment moderation, competitor tracking, and performance reporting, all at once, every day.

None of that work is optional, and none of it is occasional — it's the daily floor every account needs just to stay alive, before anything strategic gets attempted. The question wasn't "can AI write a caption," it was: can a system absorb the repetitive, always-on parts of this job well enough that the operator's limited hours go to judgment calls instead of manual data pulls.

Architecture

One orchestrator, ten specialists, one shared brain

A single entry point routes every request to the right station — or several, in parallel — while a shared knowledge base keeps judgment consistent across all ten.

%%{init: {'theme':'base', 'themeVariables': {
  'background':'#14161c','primaryColor':'#22262f','primaryTextColor':'#ecedf1',
  'primaryBorderColor':'#3a3f4c','lineColor':'#5b6270','secondaryColor':'#1b1e26',
  'tertiaryColor':'#1b1e26','fontFamily':'ui-monospace, Consolas, monospace','fontSize':'13px',
  'clusterBkg':'#1b1e26','clusterBorder':'#2b2f3a','edgeLabelBackground':'#14161c'
}}}%%
flowchart TB
  T["'let's cook ...' request"] --> HC{{"Head Chef — orchestrator"}}
  SC(["Sous Chef — strategic peer\n(campaign planning)"]) -. hands off paid execution .-> HC

  subgraph RESEARCH["Research stations"]
    direction LR
    TS["Trend Scout"]
    NS["News Scout"]
    CoS["Competitor Scout"]
    CmS["Community Scout"]
  end

  subgraph PRODUCE["Production & ops stations"]
    direction LR
    CD["Content Drafter"]
    CT["Comment Triage"]
    OR["Ops Reporter"]
    TK["Timekeeper"]
  end

  subgraph GROWTH["Growth stations"]
    direction LR
    GM["Growth Marketer"]
    PS["Price Scout"]
  end

  HC --> RESEARCH
  HC --> PRODUCE
  HC --> GROWTH
  TS -->|"digest feeds"| CD
  NS -->|"digest feeds"| CD

  KB[("Shared knowledge base\ncompany · audience · patterns")]
  KB --- RESEARCH
  KB --- PRODUCE
  KB --- GROWTH

  OR -->|"performance data"| KB

  CD --> APPROVE{{"Human approval"}}
  APPROVE --> POST["schedule & post\n(mechanical layer)"]

  classDef station fill:#22262f,stroke:#3a3f4c,color:#ecedf1;
  classDef hub fill:#e8873a,stroke:#e8873a,color:#1b120a,font-weight:bold;
  classDef kb fill:#1b1e26,stroke:#e8873a,color:#e8873a,stroke-dasharray: 3 3;
  class TS,NS,CoS,CmS,CD,CT,OR,TK,GM,PS,POST station;
  class HC,APPROVE hub;
  class KB kb;

Request Flow

What happens between a request and a result

1. 01

   Receive

   A natural-language request comes in via a fixed wake phrase — no need to remember exact agent names or commands.

2. 02

   Decompose & route

   Works out which station(s) the request maps to, using a routing table of request signals — never guesses silently when a request doesn't clearly match one.

3. 03

   Sequence

   Independent subtasks run in parallel in a single dispatch; known dependencies (content drafting needs a fresh trend digest) run in order automatically.

4. 04

   Delegate

   Each station reads the shared knowledge base — brand context, audience behavior, proven content patterns — before producing anything, so judgment stays consistent across all ten.

5. 05

   Aggregate

   Results merge into one coherent response. Anything needing a human call — an urgent complaint, a credential about to expire — gets surfaced explicitly, not buried.

6. 06

   Learn

   The reporting station critically analyzes why content performed, not just what the numbers were, and writes validated findings back into the shared knowledge base — every future run starts a little smarter than the last.

The Stations

Ten specialists, one job each

Engineering Decisions

Judgment calls that shaped the system

Capabilities

What this required, in general terms

Case study by Marvel Sutantio · brand names and internal identifiers genericized for confidentiality · architecture, decisions, and system logic unmodified.