Agent Demos Are One Lucky Sample; Production Runs the Whole Distribution
Anyone picking an agent by leaderboard score is betting on a cherry-picked sample. Evaluation infrastructure now decides agent reliability costs more than model choice does, and teams that skip it will discover the 1% tail only after it has already been billing them.
Public leaderboards measure an agent's best-case ceiling: Claude Fable 5.2 completes 82.9 LiveBench 2.0 tasks, yet the best model in EON's simulated enterprise environment, Claude Opus 4.8, only clears 76.8% of tasks. The difference is a structural feature of how agents are evaluated, not a defect of any single model. A demo records the one perfect pass out of ten runs and cuts the failures, but production customers experience every run, so a 1% aberration becomes ten thousand daily incidents. Nobody measures the floor.
TechCrunch's November 11 report catalogs the repeated failure modes: strategy drift, where an agent hits the task but ignores a budget policy; multi-source entanglement, where combining three datasets stalls a flow; and long conversations that crush the context window. These compound multiplicatively when combined.
Plurai, with a $13M seed led by Team8, replicates your company's systems as a digital twin, maps every agent action path into a graph, and systematically walks the edge cases, then post-trains a custom small open-source model for each client from the simulation data. The practical floor for any team: twenty real task flows, three injected edge types, and a Wilson confidence interval on every reported success rate.
The demo-production gap is an incentive artifact: funding rounds run on quarters while production incidents run by the hour, so teams optimize the metric that pays them; tail reliability only becomes a revenue variable when customers renew on results.
Autonomous driving spent a decade learning that scenario coverage trumps mileage, and agent evaluation is replaying the same lesson at a fraction of the cost, so the window to invest in evaluation infrastructure is now.
When evaluation data doubles as post-training data, the economics flip: simulation spending stops being a quality-inspection cost and becomes a fixed asset amortized across model versions, changing which teams can afford reliable agents.
A success rate near 100% is a red flag: a hundred clean runs only demonstrate the test set is too easy, and reliability claims are believable only when the types of failures are enumerated.
The three failure modes multiplying instead of adding explains why production teams hit unreproducible 'chaos faults' that no isolated fix resolves; each fix is cheap alone, but the overlap escapes standard evaluation.