The Cheaper AI Model That Costs You More with Rayan Krishnan, Vals AI

High-level model-card benchmarks mask a "jagged frontier" of inconsistent model performance across domains, tasks, and cost structures; building rigorous, ta

By Sean Weldon

The Cheaper AI Model That Costs You More: Jagged Frontiers and the ROI Gap in Enterprise AI Evaluation

Abstract

Aggregate benchmark scores published on model cards systematically misrepresent the performance that enterprises actually obtain from frontier language models. This synthesis examines evidence that model capability forms a jagged frontier: rankings invert across domains, task subsets, harnesses, and cost-optimization regimes, such that a model leading an aggregate index may fall off the cost-performance Pareto frontier entirely on a specific subtask. Drawing on domain benchmarks in finance, legal, coding, and healthcare, the analysis documents a counterintuitive cost inversion in which a model with lower per-token pricing incurred 14x higher task cost while scoring 3% worse. It further presents a benchmark design framework (validity, reliability, discriminability), catalogues agentic evaluation failure modes including reward hacking and rubric gaming, and reports a case study in which eval-driven model routing reduced coding spend by approximately 90%. The central implication is that task-specific evaluation, not vendor benchmarking, is the mechanism by which enterprise AI return on investment (ROI) becomes measurable.

1. Introduction

Enterprise expenditure on artificial intelligence is approximately doubling year over year, and roughly 90% of workers report regular use of AI tools. Yet only 7% of companies report established ROI from that spend. This synthesis argues that the gap is primarily an instrumentation failure: organizations lack the measurement apparatus to connect model selection to task-level cost and task-level quality.

Two terms require definition. An eval (evaluation) is a structured task set paired with a scoring rubric, executed against a model or agent to produce quantitative performance estimates. The jagged frontier denotes the empirical observation that relative model capability is non-monotonic across tasks - a model's aggregate rank does not predict its rank on any particular workload.

The central thesis is that high-level model-card benchmarks mask this jaggedness, and that rigorous, task-specific evals are the key unlock for measuring real ROI, right-sizing AI spend, and codifying institutional knowledge. Section 2 establishes the benchmarking context. Section 3 analyzes jaggedness, the ROI gap, cost inversion, and Pareto structure. Section 4 presents benchmark design and agentic failure modes. Sections 5 and 6 discuss implications and strategic applications.

2. Background and Related Work

The Vals Index compiles benchmark results across finance, legal, coding, and healthcare into a composite intended to approximate economic impact rather than academic capability. Domain-specific instruments underlying such aggregation include a Finance Agent Benchmark, an Excel Modeling Benchmark, and a Tax Agent Benchmark.

Aggregation is itself a source of the problem it attempts to solve. A composite score is a weighted average over heterogeneous tasks; the weights encode an implicit workload that matches no individual firm's actual usage pattern. Consequently, an index can be informative about the frontier in general while being uninformative about the frontier for a given deployment. This motivates analysis via Pareto curves plotting cost-per-task against performance, which preserve the trade-off structure that scalar scores discard, and which form the analytical basis for the findings in Section 3.

3. Core Analysis

3.1 Jaggedness Across Domains and Harnesses

Within finance alone, rankings across the finance agent, Excel modeling, and tax agent benchmarks are inconsistent: the same set of models occupies first, second, and third position in different orders depending on the instrument used. Jaggedness intensifies at finer granularity - custom benchmarks constructed for specific repositories or programming languages exhibit markedly more fragmented performance than public suites. Two additional variance sources compound the effect. First, the harness - the scaffolding, tool definitions, and control loop surrounding the model - materially alters measured performance, so cross-model comparisons conducted under different harnesses are not directly comparable. Second, whether a provider has optimized a given model variant for cost/latency versus raw capability changes its position on any given leaderboard independent of underlying model quality.

3.2 The Cost Inversion Problem

The clearest demonstration of jaggedness interacting with pricing structure is the comparison between Opus 5.5 and Fable 5.1 on a tax agent benchmark. Opus 5.5 is priced lower per token ($4 input / $20 output) than Fable 5.1 ($10 input / $50 output). On a per-token basis, Opus 5.5 appears to be the economical choice. In practice, it incurred approximately 14x higher total cost on the benchmark, because its lower effective intelligence caused it to consume substantially more tokens completing the same task - through longer reasoning chains, retries, or verbose intermediate output. It additionally scored 3% lower than Fable 5.1 on the same benchmark. The combined effect is a model that is simultaneously more expensive and less accurate in realized use, despite appearing cheaper on the model card. As the source material states, "you would have spent less and got a better performance, but that intuition isn't directly available for people who are using the models in practice." This finding generalizes: per-token pricing is not a reliable proxy for per-task cost, because task cost is the product of price and token consumption, and token consumption is itself a function of model capability.

3.3 Pareto Frontiers and Subtask Divergence

The Excel Modeling Benchmark demonstrates that even a correctly constructed cost-performance Pareto curve for an aggregate task category can misrepresent performance on a specific subtask. Plotting cost-per-task against performance for the full benchmark produces one frontier; restricting the same analysis to the leveraged buyout (LBO) subcategory produces a frontier that sits strictly below the overall frontier. Fable 5.1, the best overall performer on the aggregate benchmark, falls off the Pareto frontier entirely when the analysis is restricted to LBO tasks. A firm selecting Fable 5.1 on the basis of its aggregate ranking, but deploying it primarily for LBO modeling, would be "massively overpaying for what is no longer the state of the art model for that category." This establishes that task-subset analysis, not category-level analysis, is the appropriate unit of evaluation for procurement decisions.

4. Technical Insights

Benchmark construction itself introduces measurement artifacts that must be controlled for before cost-performance comparisons are meaningful.

5. Discussion

The token-maxing case study illustrates the financial stakes of unmeasured AI usage: a 10-12 person engineering team given unrestricted token access spent $1.5 million on tokens in one month, roughly 10 times the team's salary spend for that period. This outcome motivated the construction of internal eval tooling (subsequently productized as Val Smith), which used historical GitHub pull requests - issues paired with their human-authored resolutions - as a ground-truth task set against which agent performance could be benchmarked directly against prior human output. In this evaluation, GPT-5.6 Soul outperformed self-hosted Kimiko 3 by 2% while costing $2.50 versus $11 and running twice as fast, directly contradicting the common assumption that self-hosted open-source models are the cost-saving option.

Applying the resulting eval-driven recommendations on tool procurement, usage limits, and per-task model routing reduced costs by approximately 90% while maintaining output quality. This suggests that the primary lever for enterprise AI cost control is not model selection in the abstract but routing - assigning the correct model to each task based on task-specific evaluation rather than organization-wide defaults.

A broader open question concerns where the historical record required to construct such evals exists outside of software engineering. GitHub provides a ready-made, labeled corpus of tasks and accepted solutions; legal and finance work rarely has an equivalent centralized, labeled record, often residing instead in email, SharePoint, or data platforms such as Databricks, encoding a "standard of excellence" that is tacit rather than documented.

6. Conclusion

This analysis demonstrates that the gap between aggregate benchmark performance and realized enterprise ROI is attributable to the jaggedness of model capability across domains, task subsets, and cost regimes, combined with the absence of task-specific measurement infrastructure. Evals that satisfy validity, reliability, and discriminability criteria, and that are robust to reward hacking and rubric gaming, provide the mechanism by which firms can right-size usage, negotiate vendor pricing, build model routers, and validate post-training approaches. The practical takeaway is that procurement and deployment decisions should be made against Pareto curves computed for the specific task subset a firm performs, not against aggregate index rankings, and that firms lacking a labeled historical record of prior work face a prerequisite data-curation problem before task-specific evals can be constructed at all.


Sources


About the Author

Sean Weldon is an AI engineer and systems architect specializing in autonomous systems, agentic workflows, and applied machine learning. He builds production AI systems that automate complex business operations.

LinkedIn | Website | GitHub

Sean Weldon builds apps and custom software at 22Atlas.

Start your build

More about Sean