Case Study
Agency OS — Company Suite
A client-services agency's operating workflows packaged as one installable Claude plugin: fifteen named automations across growth, onboarding, delivery, client success, finance, and internal ops. Documented handoffs, config-driven setup, and no sends without human approval.
System Summary
Packaged a client-services agency's operating workflows as Agency OS: fifteen named automations that Claude Cowork runs against the tools a company already connects, installable together as a single Claude plugin.
Business Problem
Agency operations depend on playbooks that live in people's heads. Leads wait, onboarding gets improvised, status reports and renewals slip, and single-task automation tools never cover the operating loop that connects them.
What Czar Studios Built
Fifteen workflow kits across six pillars (growth, onboarding, delivery, client success, finance, internal ops), each with an executable playbook, a documented handoff contract, reusable templates, and its own config; setup and board utility skills; seven n8n companion specs for the scheduled workflows; a zero-dependency verifier; and a no-build control board showing pillars, handoffs, and setup state.
Architecture and Data Flow
One plugin installs the suite. Each workflow consumes and produces named artifacts along a documented handoff spine, from lead intake through proposal, onboarding, delivery, reporting, billing, renewal, and retrospective, with learnings routed back into qualification. Company specifics bind through a single placeholder config, and connector language is capability-based (CRM, chat, email, files, meetings) so the same kits run on different stacks.
Integrations
Claude Cowork and Claude Code skills, n8n for the scheduled companions, and HubSpot, Slack, Gmail, Google Drive, and Zoom as the reference connector bindings.
Permissions, Guardrails, and Human Review
Draft-first everywhere: no email leaves, nothing posts externally, and no CRM record changes without human approval. Scheduled companions are notify-only, and every kit carries dedupe-before-create and no-invented-facts rules.
Testing and Verification
A repository verifier checks the manifests, all fifteen kits, trigger-phrase uniqueness, companion-spec syntax, board data, and internal links, and passes with zero failures; the control board is render-verified in light and dark themes.
Practical Outcome
An agency can fork the repository, fill one config file, connect its tools, and run the same fifteen workflows. The package installs from the public repository in two commands.
Privacy-Safe Proof Notes
Public repository with every kit, the verifier, and the control board; screenshots show the board and the handoff map. Configs ship as placeholders, so no client data exists in the project. Claude assisted the implementation; Czar Studios owned the architecture, workflow design, guardrail rules, verification, and release.
Project Gallery
