This page as Markdownllms.txtllms-full.txtservices.jsonsitemap.xml
# Agent Ops by VANDAM: We run your live agents after go-live > A monthly retainer to run your live agents. We read their traces, turn every failure into a fix and a test, re-run the eval suite whenever a model or your data changes, and send a KPI report each month and a shortlist of what to automate ne URL: https://vandam.ai/agent-ops Contact: hendrik@vibelab.be # Keep your agents working long after go-live. A monthly retainer to run your live agents. We read their traces, turn every failure into a fix and a test, re-run the eval suite whenever a model or your data changes, and send a KPI report each month and a shortlist of what to automate next each quarter. [Discuss the project](mailto:hendrik@vibelab.be?subject=VANDAM%20/%20Agent%20Ops) **$3,200/mo** monthly · six-month minimum ## Most teams run agents in production. About half test them. - **57%** of organizations have agents running in production. [LangChain](https://www.langchain.com/state-of-agent-engineering), State of Agent Engineering, survey of 1,340 professionals. - **52%** run offline evaluations on test sets, and 37% run online evals on real-world performance. [LangChain](https://www.langchain.com/state-of-agent-engineering), same survey. - **32%** name quality as a top barrier to production, the most cited barrier in the survey. [LangChain](https://www.langchain.com/state-of-agent-engineering). > Turn on tracing first. Traces = receipts of every action (tool calls, Salesforce pings, web searches, dead ends). > > Alex Lieberman, Co-founder, Tenex, September 2026, [Source](https://x.com/businessbarista/status/2099565601312166157) The trace shows where it went wrong, usually a few steps before the error. ## Agents drift after launch. Someone has to own them. An agent that worked in its first week meets new cases every week after. A supplier changes its invoice layout, a model version is retired, a field in the CRM gets renamed. The agent keeps running while some of its results quietly get worse, and without someone reading the traces, the first sign is a customer or a controller finding the mistake. Agent Ops is that someone. We review the traces of every run, the record of each step and tool call, and catch failures, loops and slow drift. Each failure becomes a fix and a new case in the eval suite, so the same mistake cannot come back unnoticed. When a model or a data source changes, the whole suite runs again before the change reaches your team. “Who owns a build after it’s deployed?” is on the list of questions [Alex Lieberman](https://x.com/businessbarista/status/2077143133049995619)’s team hears most from enterprise executives. Many companies will hire for it. [Aaron Levie](https://x.com/levie/status/2043883641366032638) describes the role as an agent deployer and manager who “manages evals and reviews after any major model or data change, and runs and manages the agents on an ongoing basis tracking KPIs.” Until that person is in place, you can rent the job by the month, and hand it over when they start. > The more enterprises I talk to about AI agent transformation, the more it’s clear that there is going to be a new type of role in most enterprises going forward. The job is to be the agent deployer and manager in teams. > > Aaron Levie, CEO, Box, April 2026, [Source](https://x.com/levie/status/2043883641366032638) ## How a month of Agent Ops runs. 1. Read the traces: Tracing is switched on for every agent we run, in your own observability tool or in one we set up in your environment. We review runs every working day, flag failures, loops and cost spikes, and keep a log of what we found. 2. Fix and test: Each failure is traced to its cause: a prompt, a tool, a data change or a model change. We write the fix, add the failing case to the eval suite and re-run the suite before the fix goes live through your release process. 3. Report and look ahead: At the end of each month you receive the KPI report per agent: runs, completion rate, failures, time to fix and hours saved. Each quarter we bring a ranked shortlist of what to automate next, with the expected gain. ## Run by us. Yours to take in-house. The six-month minimum gives the eval suite and the runbook time to cover the cases your agents actually meet. Everything lives in your environment: traces, evals, fixes and the runbook. When you hire your own agent manager, we hand it over and train them. - Trace review: Runs read every working day, failures logged with their trace. - Eval re-runs: The full suite run after every model, prompt or data change. - KPI report: Monthly, per agent, next to the month before. - Handover: Runbook, evals and training for the person who takes over in-house. [Ask about Agent Ops](mailto:hendrik@vibelab.be?subject=VANDAM%20/%20Agent%20Ops%20care) ## What you receive. - Trace review: Every agent run read for failures, loops and quiet errors. - Failure-to-fix loop: Each failure traced, fixed and added to the eval suite. - Eval re-runs: The full suite re-run after any model, prompt or data change. - KPI report: Runs, completion rate, time to fix and hours saved, per agent. $3,200/mo monthly · six-month minimum An indication from past projects. The final price can move a little with the size and complexity of your company, and we agree it in writing before we start. For operations and IT leads with agents in production. Useful once an agent runs every day and nobody has time to watch it. [hendrik@vibelab.be](mailto:hendrik@vibelab.be?subject=VANDAM%20/%20Agent%20Ops) ## Where Agent Ops leads. Each next step has its own service. ### Eval Suite Tests a new model on your own cases before it reaches the live agents. **$12,800** ### Token Ledger What every live agent costs, next to what it produced. **$9,600 + $1,600/mo** ### Agent Attack Audit A yearly red-team of the agents we run and their connections. **$6,400** > Right now nobody knows which of their agents are actually good and which ones are quietly wasting money. > > Greg Isenberg, CEO, Late Checkout, April 2026, [Source](https://x.com/gregisenberg/status/2048381278953603406) ## Before you ask. ### Which agents can you run? Agents we built and agents built by your team or another partner, as long as tracing can be switched on and the agent can run against an eval suite. If there is no suite yet, building one is part of the first month. ### Do you need access to production? Read access to traces and logs, and a test environment for the evals. Fixes go live through your own release process, with your sign-off. ### What counts as a failure? A run that ended in an error, produced a wrong result, looped or cost far more than usual. We agree the thresholds per agent in the first month. ### What happens when a model is updated? The eval suite runs on the new version before your agents switch. You see the result next to the current version and decide.