01
You own the keys, the kill switch, and the rollback
Magistry writes to your stores and ad accounts under tokens you hold. One toggle freezes every agent; every action ships with the reverse op pre-stored.
// for founders
Hand the store the keys. Keep the kill switch.
You can't be in every channel every day — and you shouldn't have to be. Magistry's agent fleet, coordinated by the Marketing Brain, runs the catalog, paid, CS, social, and disputes loop while you pick the bets that move the company forward. Every action logged. Every action reversible. Kill switch yours.
Dry-run from day one Operator-owned kill switch No write goes live until you flip it
// why founders pick magistry
Built for the operator who has to trust it before they leave the building.
You signed every vendor, you carry every escalation, and you sleep with the phone on loud. Magistry is the only teammate you can hand the keys to and still keep the keys.
02
Reversibility is the default, not the escape hatch
Dry-run from day one. Every price change, archive, audience write, and refund lands in decision_log with its rollback op next to it — including the ones you let run live.
03
You stay across everything without sitting in everything
Otto pings you on Slack with the three rows that need a call today, not the four hundred that don't. The rest runs inside the rails you set.
04
Lean team. No headcount tax to add a channel
Catalog, paid, CS, social, disputes — one spine, one audit trail, one bill. You're not hiring three people to bolt on a TikTok account.
// this week
What Magistry did for you this week.
An illustrative week — every line like these traces to one or more rows in decision_log, every row reversible from your phone.
- Archived 14 underperformers and reshuffled Google Ads budget to your top-3 hero SKUs — net spend flat, contribution +€2,140.
- Closed 312 CS tickets end-to-end inside brand voice — 11 escalations queued for you with the full thread + suggested reply.
- Caught a Meta creative-fatigue drop on Day 6, briefed two RSAs and one static image, and waited for your green light to push.
// from your dashboard
One row. One action. One reverse op.
Every move Magistry makes is a row in decision_log, gated by evidence tier and pre-armed with its rollback. Here's an example row from a morning run on a Shopify storefront.
decision_log #84,217 ── 2026-05-25 06:14 UTC
agent catalog_specialist
action discount_test
sku linen-blazer-stone-m
evidence_tier A // shopify cost_per_item verified
prev_price EUR 148.00
next_price EUR 142.00 delta -6.00 (-4.05%)
rationale sell_through 18d ahead of plan,
margin headroom 11pts above floor,
competitor median EUR 139.
guardrails under_floor=false, cost_tier=A,
rate_limit 1/24h per sku — OK
mutation shopify.admin.productVariantUpdate
revert restore EUR 148.00 (1-click, derived)
status APPLIED (live)
operator auto (kill_switch off, gate=allow)// what you actually see
Otto pings you. You read one line. You're done.
Magistry doesn't ship you a dashboard to grade. It ships you a Slack DM with the three rows that need a founder call this week, plus the one-tap rollback if you disagree.
otto: 3 rows for your call this week.
↳ #84,217 linen blazer · –€6 · applied
↳ #84,201 archive 6 SKUs · awaiting you
↳ #84,193 spend shift to Meta · awaiting you
↳ #84,217 linen blazer · –€6 · applied
↳ #84,201 archive 6 SKUs · awaiting you
↳ #84,193 spend shift to Meta · awaiting you
// stop being the kill switch
Stop being the only kill switch in the building.
In a lot of stores the founder is the kill switch — the only person who can stop a bad price push, a bad ad spend, a bad refund. Magistry makes the kill switch a feature of the system, so you can spend your time deciding which bets to take, not which fires to put out.
// hand it the keys
Stop being the only person who can stop a bad decision.
Spin up a tenant, point Magistry at a sandbox store, and watch the decision log fill up — every row reversible, every channel logged, the kill switch in your hands.
Operator-owned kill switch · Dry-run from day one