Why Resolve AI: Token Efficiency at Scale
Token usage has become a scoreboard across the industry, largely because nobody agreed on how to evaluate what AI actually delivers. Varun makes the case that this is the wrong measure entirely. Tokens only represent how hard a model is working. What matters is the outcome on the other side.
In this video he defines token efficiency as the number of tokens burned to reach an outcome, whether that is investigating an alert or getting to a root cause, and explains why Resolve AI focuses on it: to keep cost predictable and quality high at the same time.
The place that game is won or lost is context. Varun uses a detective analogy to explain it. A dumb detective takes the first answer and closes the case. A nervous detective interviews the whole town and never reaches a conclusion. A smart detective asks the right questions and works across code, infrastructure, and telemetry to reach a precise answer.
Plotted out, agent quality against context looks like a hill, with low quality at both extremes and a peak in the middle. Getting to the top of that hill is a research problem, and it is the reason Resolve AI charges customers on outcomes rather than tokens.
Resolve AI is the first agentic interface for engineers to operate their production systems. Using natural language, engineers can work across their code, infrastructure, telemetry, and team knowledge all in one place.

See the agents that run and fix software in action
Join our engineering leads for "Behind the Build", a webinar series deep-dive into how we built agents that run software.
Related Post

Claude Sonnet 4.6: Testing adaptive thinking on AI agents for prod
We benchmarked Claude Sonnet 4.6's adaptive thinking on production incident investigations. Sonnet 4.6 at medium effort came close to Opus 4.6 at a fraction of the cost.

6 Pillars of an Agentic Harness needed to run and fix software
A frontier model can produce a thousand coherent answers. Most enterprise work needs exactly one correct one, and closing that gap is not a bigger model. It is the agent architecture around it. Here are the six layers that turn open-ended capability into a defined outcome, and why production incidents are the hardest test of whether they work.

Why I joined Resolve AI
Announcing my new role at Resolve AI to lead marketing - joining a mission-driven team reimagining software operations with Agentic AI and building a category-defining company.