Enterprise AI Measurement Guide
Agent Effectiveness
Outcome Success
What percentage of AI coding agent sessions produce a merged pull request in the selected period?
What it shows
Outcome Success measures the share of AI coding agent sessions that produce a tangible shipped output, specifically, a merged pull request. It answers the question that adoption metrics and session counts cannot: of all the time engineers spend running agent sessions, how much of it results in code that actually makes it into the codebase? An Outcome Success rate of 10% means 9 out of 10 agent sessions produce nothing that ships.
Why it matters
Session count measures activity. Outcome Success measures results. An org with 91% agent adoption and 10% Outcome Success is spending most of its agent compute on sessions that produce no shipped output, which means the effective cost per shipped outcome is roughly 10x the cost per session. For CFOs reviewing AI coding tool budgets, Outcome Success is the denominator correction that makes Cost per Outcome calculable. Without it, per-session costs significantly understate the true cost of AI-assisted engineering output.
The Larridin angle
Larridin tracks the behavioral signals that separate high-outcome sessions from low-outcome ones, including upfront planning, verification discipline, and knowledge preservation across sessions. The Outcome Success rate combined with those behavioral signals gives engineering leaders both the measurement and the explanation: not just that sessions are failing to produce outputs, but specifically which behaviors distinguish the sessions that do.
Related Agent Effectiveness Metrics
Common questions
What is Outcome Success in the context of AI coding agents?
Outcome Success measures the percentage of AI coding agent sessions that result in a merged pull request, indicating tangible shipped output.
Why is Outcome Success important for the C-suite?
Outcome Success is crucial because it measures actual results rather than just activity, helping CFOs understand the true cost per shipped outcome and make informed budget decisions.
How does Larridin help identify high-outcome sessions?
Larridin tracks behavioral signals such as upfront planning and verification discipline to distinguish between high-outcome and low-outcome sessions.
What does a 10% Outcome Success rate indicate?
A 10% Outcome Success rate means that 9 out of 10 agent sessions do not result in code that is merged into the codebase.