OpenAI Pushes 'Useful Work Per Dollar' Framework for Enterprise AI Measurement

OpenAI published a four-dimension AI ROI scorecard — useful work, cost per successful task, dependability, and return on compute — promoted by CFO Sarah Friar and targeted at enterprise finance audiences. [1][2] A Cars24 case study supplies the concrete output numbers the scorecard is designed to track: 1 million monthly conversation minutes, 50% improvement in customer support resolution rates, and 80% reduction in workflow turnaround time. [3] Coverage has spread broadly across enterprise and finance outlets. [5][6][7][8] Against this, Simon Willison endorsing Nik Suresh argues that financial incentive alignment between vendor and customer executives structurally sustains unrealistic AI productivity claims and suppresses honest assessment. [4]

OpenAI's framework reframes AI evaluation around output value — a framing that favors agentic, higher-cost deployments where OpenAI competes, and one whose definitions OpenAI as the vendor controls. The Willison/Suresh counter identifies a structural problem: the same financial incentives driving enterprise AI adoption also make honest measurement institutionally difficult to sustain.

OpenAI published two pieces within three days in mid-July 2026, arguing that standard business metrics — cost per seat, token prices, headcount saved — do not capture what enterprises receive from AI deployments. The first, a general advisory, frames the right lens as 'useful work per dollar': measuring the value of outputs rather than the price of inputs. [1] The follow-up, authored by CFO Sarah Friar, formalizes this into a named scorecard with four dimensions: useful work (volume and quality of tasks completed), cost per successful task (spend normalized to completed work), dependability (consistency and error rate), and return on compute (value extracted per unit of compute invested). [2] Friar's byline is deliberate — the content is aimed at finance and executive audiences rather than technical buyers.

A companion case study on Cars24, an Indian used-car marketplace, provides the concrete numbers OpenAI is asking enterprises to track: over 1 million monthly conversation minutes handled by AI agents, a 50% increase in customer support resolution rates, 12% recovery of previously dropped seller leads, and an 80% reduction in turnaround time across key workflows. [3] ChatGPT Enterprise and Codex reached 85–90% daily active usage across approximately 600 employees, spreading from engineering into finance, legal, marketing, and operations. OpenAI presents this as evidence that AI can move from pilots to production when tied to specific business workflows — exactly the output-value story the scorecard is designed to justify.

Against this, Simon Willison endorsed a sharply critical account by Nik Suresh of what corporate AI measurement actually looks like in practice. [4] Suresh describes executives producing AI-centered technical strategies without ever having used an AI tool, engineers running AI rewrites of codebases solely to inflate token usage leaderboards, and a culture of silence around AI productivity claims. The silence, Suresh argues, is not accidental: when customer executives publicly claim 100x productivity gains, any vendor representative who disputes those claims risks being seen as undermining the customer's credibility and inviting contract cancellation. The dominant force sustaining unrealistic numbers is financial incentive alignment, not genuine belief.

Both OpenAI pieces are openly promotional and neither references independent measurement research or third-party audits. The scorecard has drawn broad media coverage across enterprise and finance outlets, but the coverage so far consists of amplification rather than independent analysis or counter-argument. [5][6][7][8] IBM has published its own piece on measuring GenAI productivity in the enterprise, which could represent an independent vendor perspective, but its substantive content has not been extracted. [9] Willison and Suresh's account, if accurate, describes an institutional environment where even a well-designed measurement framework faces a headwind: the organizations most eager to adopt output-value metrics are also the ones with the strongest incentives to report favorable results.