This page is for the engineer who saw Runback work and needs to bring it to a VP, CTO, or CISO. The business case is below. The pre-written email is at the bottom. Copy it, fill in the [ ] parts, and send it.
When an agent fails in production today, your logs show what happened — not why. The model's reasoning, the context it received, the step it went wrong on: none of that is in a log. The on-call engineer spends hours guessing. Runback gives you the exact run, step by step, in under 5 minutes. See the MTTR proof →
Without a release gate backed by real production replay, a model update can quietly break customer-facing behavior and you won't know until a customer tells you. Runback's CI gate replays a dataset of real captured steps before every deploy — a red row stops the build.
A teammate, a customer, a regulator, or an auditor will ask. “The model did it” is not an answer. Runback keeps a signed, tamper-evident record of every agent decision — replayable on demand, inside your own perimeter.
Your VP isn't worried about MTTR. They're worried about the conversation with their risk committee when an agent makes a decision they can't explain. These are the three things they need to be able to say.
Free Community edition, self-hosted, one agent, one sprint. No procurement, no data leaving your network, no sales call.
Growth tier — 10 seats, golden suite, 60-day retention. One avoided incident covers months of cost.
MTTR reduction from hours to minutes. At $120/hr, 12 incidents/yr, 3 engineers per incident: ~$60k/yr in recovered engineering time.
These numbers use common defaults. Model your own on the exposure calculator →
This is a real email, written for a real VP. It explains the problem, the solution, the data-residency posture, and the ask. Fill in the blanks and send it — or use it as the starting point for your own.
Subject: AI agent observability — want your take before we go further Hi [Name], We've started shipping AI agents into [product / area] and I've been looking at how to make them production-safe without burning half a sprint every time one misbehaves. I found a tool called Runback (runback.dev) that does something I haven't seen elsewhere: instead of just logging what the agent did, it lets you re-run the exact decision — same context, same tools — so you can reproduce a failure in minutes instead of digging through logs. The three things that stood out: 1. Reproducible incidents. Root-cause in ~4 minutes instead of hours in logs. The MTTR proof is on their site if you want the specifics. 2. CI release gate. Catches a regression before it ships — a red row stops the deploy. We'd never find out in production what a model change silently broke. 3. Signed audit trail. Every agent decision is a replayable, tamper-evident record. Useful now; essential if we hit CPS 230 or EU AI Act territory. The free Community edition runs in our own VPC — no data leaves our perimeter, so it should clear security review quickly. I think it's worth a look before we have [number] agents in production with no way to reproduce what they did. Happy to set up 30 minutes to walk through what I found. [Your name]
We'll join your security review, answer your risk team's questions directly, and help you land value on one agent before any procurement conversation.