The studio runs on Zaggy.
Zaggy is our business OS. Six AI agents do the reading, drafting, chasing, filing, and remembering. The humans do two things the agents never touch: taste, and the final tap that lets anything leave the building.
A company inside the company
We tell clients to automate everything except the taste. Zaggy is us taking our own advice. It started as an open-source agent framework, and we forked it, hardened it, and wired it into the way the studio actually runs.
It lives on our own machine, keeps its state in a local database, and reports to a phone. No SaaS dashboard subscription, no cloud backend, no one else's roadmap.
Six agents, one front door
Each agent has its own persona, memory, and job description.
Main
The front door
Sales
Pipeline and call prep
Ops
The document factory
Finance
The ledger
Content
Headless
Research
Headless
One front door, five specialists
Main is the only agent you talk to. It routes work to the specialists: sales reads the pipeline and preps calls, ops drafts proposals, contracts, invoices, and decks, finance keeps the ledger straight.
Two agents, content and research, have no chat channel at all. They only run work the orchestrator hands them, and their only voice back is through main. The machine does not get to freelance.
Nothing goes out without a tap
The safety spine of the whole system: no email, no message, no invoice, no proposal leaves without a human pressing an approval button. Approvals are durable, they survive restarts, and they replay safely, so a duplicate tap can never double-send or double-book.
The evening proposal drafter is the pattern in miniature. It quietly writes a complete branded proposal, then sends exactly one card asking for one tap. Until the tap, nothing exists outside the machine.
A heartbeat, not a firehose
Zaggy runs on scheduled rhythms: a morning briefing, a sales pulse before it, an evening proposal pass, a Friday money loop, a nightly encrypted backup, and a weekly self-diagnosis that checks every bot, every login, and every bridge.
Every job obeys the same contract: if there is nothing new, say nothing. A successful no-op stays silent. The phone only buzzes for genuinely new information or a failure, which is the only way an always-on system stays livable.
Every fact has exactly one home
Each agent keeps its own memory, extracted, scored, and decayed over time, with a shared tier for facts everyone needs. A cross-agent activity log lets each agent see what the team did.
Above all of it sits the rule that keeps six independent agents from corrupting each other: one datum, one home. The CRM owns sales truth, the project tool owns project truth, the business folder owns documents. Zaggy's own database holds runtime hints, never the source of truth.
The machine only interrupts you when it matters.
Local and headless, on purpose
Everything runs on our own hardware. A watchdog checks the processes and restarts anything dead. Integrations are API and command-line only, no account-tied plugins, precisely so headless agents can run unattended at three in the morning.
The result is that the studio's operational layer works the night shift, and the humans spend their hours on the one thing that cannot be delegated.
Want an operations layer like this?
We build systems like Zaggy for ourselves first, then for clients. If your team is drowning in ops, fifteen minutes will tell us if an agent layer fits.
Book a 15 minute call