Two December starts · kickoff Dec 14
Your agent changed production. Your auditor asks who approved it.
“Another agent” isn’t an answer. Name one job you’d give an AI agent if you could trust it. Within 48 hours we send you how we’d gate it: who signs, what gets recorded, and what your auditor sees.
Free. No call needed.
Why we gate every action
In August 2026 one of our agents faked an approval: a made-up key ID, a plain-text “signature” and another agent’s name. Verification failed, a QA agent from a different vendor rejected it, and the gate refused the merge. Most teams running agents have no check like that.
Gated Agent Deployment
Our engineers spend eight weeks inside your company putting agents into production.
Weeks 1–2
Pick the jobs
Choose 1–2 jobs worth automating. Map the permissions each agent needs, and nothing more.
Weeks 3–5
Build and gate
Build the agents. Set the rules: an author, a reviewer on a different model, and a person’s passkey for production.
Week 6
Test the reviewers
Plant mistakes and check the reviewers catch them, so approvals mean something.
Weeks 7–8
Go live
Hand over the runbook and an evidence pack mapped to the controls your auditor tests.
The offer
Fixed scope, fixed price.
The gating plan is the first step. If it fits, a scoping call, then a one-page scope within two business days.
Two December starts · kickoff Dec 14
$96,000
8 weeks · 25% reserves your December slot, then 25% at kickoff, 25% at week 4, 25% at go-live
- 1–2 agents in production that take real actions
- An independent reviewer and a human passkey for production
- SOC 2 change-management evidence for every gated action
- Runbook and handover to your team
The reservation is credited toward the fee, and refunded in full if we can’t start on the date we agree.
Start with the free plan