AI's capability improvements haven't come from it getting less affordable

· Source: Redwood Research blog · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Data Science & Analytics · Depth: Advanced, long

Summary

An analysis of METR's time horizon data indicates that the rising inference costs of frontier AI models do not signify increasing expense relative to human labor, but rather reflect models completing longer tasks. The study defines "cost ratio" as AI inference cost divided by human cost for the same task, finding that this ratio at a model's 50% reliability time horizon has not increased across successive frontier models. Furthermore, longer tasks do not exhibit higher cost ratios than shorter ones among successfully completed tasks. The analysis also demonstrates that capping AI spending per task at a fraction of human cost (e.g., 1/32x) barely slows time horizon trends, which continue to double approximately every three months. This contradicts a previous conclusion by Toby Ord, whose methodology is argued to significantly overestimate hourly model costs by conflating per-task budget with the 50% time horizon.

Key takeaway

For CTOs and VPs of Engineering evaluating AI automation strategies, the data suggests that increasing AI capabilities are not being offset by rising relative costs. You should confidently plan for broader AI deployment, as models can affordably complete tasks at 50% or 80% reliability horizons with cost ratios around 3% of human labor. This implies that even with retries for failures, automation remains profitable, and investing in higher inference compute for specific domains could further accelerate capability milestones.

Key insights

AI automation costs are not rising relative to human labor, enabling continued rapid capability expansion.

Principles

Method

The study calculates cost ratio by estimating AI inference cost from token count (using OpenRouter pricing) and dividing by human task cost, analyzing trends at 50% and 80% reliability time horizons.

In practice

Topics

Code references

Best for: CTO, VP of Engineering/Data, Executive, AI Scientist, Director of AI/ML, Consultant

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by Redwood Research blog.