of CS auto-resolved
Read case studySolace runs paid social across Meta, TikTok, and Google with a six-person growth team. Here's how the planner-judge-executor loop took them from weekly decisions to every six hours — without losing a night's sleep.
// the deltas
Decisions / day
Avg ROAS, paid
Time to action
Operator hours / wk
The bottleneck was the meeting, not the model
Before Magistry, every meaningful paid decision queued behind a weekly sync. A creative was fatiguing on Tuesday, but the call to cut it didn't happen until the following Monday — six days of spend the team already knew was wasted.
The constraint wasn't a lack of insight. The team knew what to do. The constraint was that doing it required a human, a meeting, and a free afternoon — and those three rarely lined up before the window closed.
What Magistry runs
The Campaign Specialist now runs a planner-judge-executor cycle every six hours across all three channels. The planner proposes budget shifts and pauses; the judge scores each against Solace's own winner floor and policy gates; the executor writes the approved moves, each stamped with its reverse op.
Crucially, the kill switch sits with the Head of Paid Media. Autonomy was granted from a position of control, not surrendered. In ninety days it's been pressed once — a precaution during a platform outage — and cleared in minutes.
The result is legibility, not just speed
Throughput went up 4.3×, but the number the team talks about is different: every decision is now a row they can point at. When finance asks why budget moved, the answer is a decision_log entry with the judge score and the evidence it cited — not a reconstruction from Slack.
The Tuesday sync is gone. The team's job shifted from making each decision to setting the policy that makes them, and auditing the rows after the fact.
The decision_log is the killer feature. Every move is a row we can audit and reverse. We replaced four spreadsheets, three Looker dashboards, and the awkward Tuesday standup with one append-only log. My CFO sleeps better.
// your story next
See your own case study in 90 days.
The fastest path to a numbers-driven story is to connect a read-only token. We'll show you exactly what the agents would have done over your last 30 days — before anything writes.
Dry-run by default · Append-only logs · One-click rollback
