Case Study 04 · AI Build

Mojo: A Campaign Sprint
In Under An Hour

Built Solo7 Agents + OrchestratorLive On Client Work

Creative sprints for Konvert.Media took about five days, and most of that was coordination, not creative work. Mojo is the seven-agent system I built to run the whole sprint from one WhatsApp message, with a human approving every major handoff.

Sprint Time

<1 hr

Per campaign sprint

Down from a ~5-day cycle

Run Cost

<$1

Per sprint

Whole stack on one VPS for <$40/month

Build Time

36 hrs

Idea to first live sprint

7 agents · 175+ languages

01 · The Problem

Creative agencies move slowly. A typical production cycle — research, strategy, copy, production, localization — takes around 5 days. Most of that time isn't creative work. It's coordination, handoffs, status meetings, and rework.

The bottleneck isn't talent. It's orchestration.

02 · What I Built

Mojo is a 7-agent orchestration system that coordinates the entire sprint. Each agent owns a discipline — research, strategy, copywriting, production direction, localization, ops — with its own knowledge base, protocols, and learning loop.

Built from scratch in 36 hours. Runs on OpenClaw. Coordinated through WhatsApp. Outputs to Google Drive. Tracked on Google Sheets. Designed with HITL gates so a human approves every major handoff.

Same sprint scope. Minutes instead of days.

03 · How It Works

7 Steps,
End To End

01

Brief intake

Mojo (the orchestrator) receives the client brief via WhatsApp and structures it into a sprint plan.

02

Scout runs deep research

Perplexity for narrative intel, Apify for structured data extraction.

03

Strategist maps the thesis

Positioning, audience, and narrative thesis synthesized from Scout's findings.

04

Writer produces the creative

Ad scripts, hooks, headlines, taglines — with a HITL gate before approval.

05

Producer directs production

Production briefs and visual direction. Asset generation roadmap lands in Month 2.

06

Babel localizes

Outputs adapted for additional markets and languages — 175+ supported.

07

Ops packages delivery

Final deliverables packaged into a client-ready Google Drive folder. Every action logged.

04 · Proof

Build time36 hours, idea to first live sprint
Sprint durationUnder an hour vs a 5-day campaign cycle
Cost per sprintUnder $1
Agents in production7 specialized agents + 1 orchestrator
Languages supported175+ via the Babel agent
VisibilityEvery action visible across WhatsApp + Google Sheets

05 · The Stack

OrchestrationOpenClaw multi-agent framework
ModelsGPT-5.4 (1M context) · Claude Sonnet
Web intelligencePerplexity Search API · Apify (structured scraping)
CoordinationWhatsApp Business API
Output layerGoogle Drive · Google Sheets (via gog CLI)
InfrastructureHostinger VPS (32 GB) · systemd-managed

Markdown-first agent definitions, no vendor lock-in, full observability at every layer, and the whole thing runs on a single VPS for under $40/month.

06 · What’s Next

  • Month 2 — Production tool integrations (Higgsfield, Freepik, HeyGen for asset generation), a single manifest file for the entire system, and n8n integration for deterministic ops workflows.
  • Month 3–4 — Vertical agent systems for adjacent verticals (lead generation, market research, outreach) using the same architecture.
  • The bigger bet: agent systems that can be packaged and deployed for specific verticals — small businesses, founders, indie creators — where Apify + AI + domain knowledge unlocks workflows that previously required full teams.

07 · Takeaway

The bottleneck in creative work was never talent; it was orchestration. Mojo turns an operator's playbook, who does what, in what order, with which checks, into a system that runs it every time.