For agencies · studios · fractional teams
You are accountable for tag managers you do not own, that clients edit behind your back, and that nobody has a history of. You get one digest across the lot, and a write boundary the client controls.
Same service as everywhere else on this site, at fleet scale: $1,500 a month for up to 25 client containers, checked daily, with a change report per client you can forward without an editing pass. One person runs it — me — and the reports go out under your name.
The problem, at your scale
A single-site team has one container to lose track of. You have one per client, each with its own history of departed contractors, and the client’s own marketing hire has edit access to every one of them.
What you get
Everything in the Monitoring service applies to every container on the account. These are the parts that only start to mean something once there is more than one.
01 / Fleet digest
One run across every container the account can read, one block each. A container with nothing to say is a single line; the one that changed since the last run carries its changelog underneath it.
Twenty-five clients should cost you the thirty seconds it takes to read the exceptions, not twenty-five inboxes to check.
KillsChanges you didn’t make, found before the client finds them.
02 / Forwardable reports
The monthly change report and the audit are written for the person who approves the work, not the person who built the container — which means they leave your hands and go to the client without an editing pass.
An outage arrives priced, against a weekday-adjusted baseline with the assumptions printed. That is the artifact that answers “what did we pay you for this month.”
KillsHaving nothing to show in a quiet month.
03 / Fenced per client
An allowlist names exactly which containers automation may write to. Anything outside it fails closed — a refusal, not a warning to click past — and read access is a different grant from write access.
That is the answer that lets a client principal say yes: their container is not on the list until they put it there, and taking it off is one line.
KillsThe delegation problem, at the only layer where it can actually be solved.
The exceptions digest
A container with nothing to report gets a heading and nothing else, so the one that changed is the only thing with body text under it. You read the exceptions and close the tab.
The run below is real output over the three containers this service account can read — the site you are on, a demonstration container, and one other. One drifted since the previous run; the other two are quiet, and being quiet takes one line each.
GTM-WJSNBN47 project5.ai DRIFT
GTM-W44B54PP Project5 Demo CLEAN
GTM-N9HGRC5Z Rustfish.com CLEAN
Real output from the drift check over this account’s own three containers. At twenty-five the shape is the same and the reading time barely moves, because quiet containers stay one line.
The part nobody says out loud
The container audit is free and it is read-only, which makes it the cheapest piece of pre-pitch research available to you. Walk into the room already knowing what is broken in their measurement, and open with the finding instead of the credentials slide.
Real output from the audit tool, run against a demonstration container.
Straight answers
You are about to put client containers on a single-founder service. Here is the part of the pitch that usually gets left out.
Pricing
$1,500 a month covers up to 25 client containers. Against that: one broken checkout tag on one client, caught a month late, costs more than the annual bill — and the reports come back to you as something you can bill for.
$600/mo
Up to 10 containers
$1,500/mo
Up to 25 containers, white-label
Custom
25+ containers
Goes to the request form on the home page. No sales call to book, no third-party processor.