An AI tool may feel useful before its place in a team makes sense. Someone still has to connect it to the work, teach people to use it, check the results and deal with mistakes. The cost includes time, attention and effort as well as money. The reward might be better service, new capacity or a project that was previously out of reach. This question helps distinguish those lasting benefits from a promising demonstration or a workload quietly passed to someone else.
EM read · 2026-10-30 · Evidence reviewed 2026-10-30
The best returns will come from changing the workflow
EM outlook ·
Through 2027, we expect organizations to get more value sooner by redesigning a specific workflow around AI than by distributing tools widely and leaving teams to work out how to use them.
The customer-support study illustrates the opportunity: agents resolved more issues per hour, with larger gains among less experienced workers. Anthropic’s workforce report identifies a competing demand: people must still devote attention to the growing output agents produce.
A deployment creates value when the organization can use the additional completed work or better service, and those benefits outweigh the time, effort and money spent integrating the tool, training people and checking its results.
A redesigned workflow meets those conditions sooner because the organization has already decided what the extra work is for, who checks it and who benefits; broad access leaves each team to discover that separately.
What this means
Choose a recurring piece of work that someone needs done, record how well it is done today, and decide what improvement would be worth paying for. Count quality, new capacity and service improvements as well as hours saved; count integration, review and ongoing operating costs against them.
Why we take this view
The next operating year should favor deployments built around measurable existing work. Broad rollout requires more coordination and training before benefits reach the same decision-maker who bears the cost.
What has to hold
The organization uses the extra capacity or better result; output with no demand has little economic value.
The comparison includes rollout costs, repeat operating costs and work shifted to another team.
The strongest rival
Broad access produces valuable experimentation and new capabilities that narrowly specified projects would miss.
Implementation and review costs absorb the operating gains, leaving even well-liked tools below their full cost.
What would change our mind
Repeat-use evidence shows better completed work after counting the time, effort and money spent on integration, checking, training and operation.
The apparent gain disappears when transferred work, delayed defects or unused capacity are counted.
Test the full recurring cost in time, effort and money against completed work and service quality, beyond task productivity and self-reported value.
Where this could lead
A focused workflow pays for its AI
Base case ·
The buyer gets a recurring improvement worth more than implementation and operating costs: faster service, better quality or capacity that would otherwise be unavailable.
What would make it happen
We expect the clearest near-term returns where a deployment improves work with an existing buyer and an observable outcome.
Conditions
The improved result has actual demand or avoids an actual cost.
Savings or new value survive integration, review, training and repeat operation.
The buyer chooses what the extra capacity is for: better service, a previously neglected need, or work the team could not afford to attempt.
Watch for
The buyer keeps funding the workflow after measuring its full costs.
The quality or amount of completed work improves over repeated use without shifting extra effort to another team.
People enjoy the assistance, but the organization cannot turn it into enough useful extra work or better service. Integration and review absorb the benefits, and broad rollout loses its case.
What would make it happen
The first renewal and operating cycles can expose costs that a demonstration or initial enthusiasm misses; persistence into 2028 would weaken the focused-deployment thesis.
Conditions
Output grows faster than demand for it, or the gain does not reach the budget that pays for the system.
Integration, quality loss or ongoing supervision costs more than the usable benefit.
Watch for
Usage remains high while completed outcomes and customer value stay flat.
Renewals shrink after the buyer includes costs previously omitted from the business case.
Why this connects to When is an AI deployment worth its total cost?
EM interpretation
Work becomes valuable when someone can use the result. A slower process can still be worthwhile if it produces something better or previously impossible; a faster draft can waste time and money if nobody needs it or finishing it takes too much effort.
The buyer’s gain and the supplier’s investment return are separate calculations.
A positive deployment return does not specify whether employment expands or contracts.
Perspectives
Joel Becker
author reporting technical-worker self-assessments · 2026-05-11 · From the author’s own work
The survey reports substantial perceived value gains, while distinguishing value from task speed and cautioning that respondents can misestimate what AI contributes.
Sources and passages
Publication date of the authored source.
Self-report in a technical-worker sample, not audited customer economics or a measured effect on national productivity.
Valuation scholar writing on his personal blog · 2026-08-20 · From the author’s own work
Damodaran argues that AI investment should be examined through the business outcomes required to justify its price or capital cost. Different assumptions about markets, margins and reinvestment can produce different valuations; technological plausibility does not guarantee an investment outcome.
Sources and passages
Original publication date; the source preface records two updates on 21 August 2026.
A proposed valuation framework, not a comprehensive independent audit of AI companies.
The retained article records updates after its original publication; its numerical examples are not adopted as EM estimates.
An internal study of employment and agent use at . It describes a changing hiring mix and demands on human attention at one growing AI company.
Publisher publication date, checked on original page.
Original publisher page and exact retained source reviewed. Source retention does not establish every downstream reuse or training right.
Exact retained Stream work/snapshot and SHA256 verified against the 29 October SELECT-only source packet. That lookup found no joined public Stream or bridge reading revision; no reading identity is invented.
The proportion of junior technical hires fell even faster, from 27% to 9%.
Retained extracted text, character offsets [4420, 4494). Context (EM paraphrase): Anthropic’s October 2026 report describes its own workforce; junior employees’ share fell from early 2025, and technical hiring still grew in absolute terms. This is a changing hiring mix, not a count of jobs lost.
This acceleration makes human attention the bottleneck for agent output.
Retained extracted text, character offsets [767, 839). Context (EM paraphrase): The authors report rising internal output alongside agent use and interpret human attention as a constraint. Adoption is not randomized; the report does not establish a general causal productivity effect.
A study of experienced developers using early-2025 tools on familiar open-source work. The measured completion-time result belongs to that setting and period.
Publication date displayed by the original publisher.
Original publisher page and exact retained source reviewed. Source retention does not establish every downstream reuse or training right.
Exact retained Stream work/snapshot and SHA256 verified against the 29 October SELECT-only source packet. That lookup found no joined public Stream or bridge reading revision; no reading identity is invented.
16 experienced developers
Retained extracted text, character offsets [1527, 1552). Context (EM paraphrase): Methods: developers worked on 246 real issues in familiar open-source repositories using early-2025 tools. This population does not represent all developers or later systems.
they take 19% longer to complete issues
Retained extracted text, character offsets [2468, 2507). Context (EM paraphrase): Core Result, first paragraph; interpret with Methods and the immediately following limitations table. Reported result for the 2025 study, not a current universal estimate.
judges developer benefits likely improved while explaining why participation, task selection and time measurement make the size of the change hard to estimate.
Publication date displayed by the original publisher.
Original publisher page and exact retained source reviewed. Source retention does not establish every downstream reuse or training right.
Exact retained Stream work/snapshot and SHA256 verified against the 29 October SELECT-only source packet. That lookup found no joined public Stream or bridge reading revision; no reading identity is invented.
the data from our new experiment gives us an unreliable signal of the current productivity effect of AI tools
Retained extracted text, character offsets [431, 540). Context (EM paraphrase): Opening discussion, paragraph beginning Unfortunately. Subsequent paragraphs describe participation, task selection and time measurement.
likely biases downwards
Retained extracted text, character offsets [715, 738). Context (EM paraphrase): METR says nonparticipation by developers unwilling to work without AI likely understates speedup; the authors believe early-2026 tools speed developers more than early-2025 tools. Lower study pay, task selection and concurrent-agent time accounting limit the size estimate.
A survey of technical workers’ self-reported value from AI tools. It distinguishes value from speed and does not measure an audited financial return.
Publication date displayed by the original publisher.
Original publisher page and exact retained source reviewed. Source retention does not establish every downstream reuse or training right.
Exact retained Stream work/snapshot and SHA256 verified against the 29 October SELECT-only source packet. That lookup found no joined public Stream or bridge reading revision; no reading identity is invented.
Participants self-reported a median 1.4–2x change in the value in their work due to AI tools.
Retained extracted text, character offsets [1308, 1401). Context (EM paraphrase): METR surveyed 349 technical workers in February–April 2026. The range reflects self-reported value under different question formulations, not a confidence interval or observed causal return. METR gives reasons to doubt the magnitude and distinguishes value from speed.
Damodaran examines the revenues, margins and reinvestment needed to justify AI investment. Different business assumptions can support different valuations.
Original publication date retained in source metadata; later source edits remain part of the exact cited snapshot.
Full retained article body reviewed; public display uses a short excerpt and attributed interpretation. Underlying numerical claims and linked evidence are not independently verified by inclusion.
Exact work/snapshot and SHA256 verified in the 29 October SELECT-only corpus packet; full private source text is not republished.
there will be room for significant disagreement on the reach of AI and its value as a business
Retained extracted text, character offsets [53311, 53405). Context (EM paraphrase): Damodaran proposes testing what future revenues, margins and reinvestment would justify AI company prices and capital spending. The original post is dated 20 August 2026; its retained preface records two 21 August updates. This is an analytical framework, not proof that a price or industry-wide bubble verdict is correct.
A study of AI assistance for customer-support agents, reporting issues resolved per hour and differences by worker experience. This edition cites the v2 abstract.
Version 2 submission date displayed by ; first submitted 23 April 2023. The versioned abstract is the cited object.
Versioned author abstract checked directly. The HTML rendering displayed a conflicting 2026 manuscript date, so this edition cites only the clearly versioned abstract and does not assign that later date to the study.
Original public source read on 30 October 2026. An exact retained Stream identity has not been resolved for this edition.
by 15\% on average
Version 2 abstract, second sentence. EM context: staggered introduction among 5,172 customer-support agents; the outcome is issues resolved per hour, not company profit.
Less experienced and lower-skilled workers improve both the speed and quality of their output
Version 2 abstract, third sentence. EM context: benefits differ by experience; the most experienced workers show small speed gains and small quality declines.
Escape Meridian takes a position on where the evidence points, explores what could happen next, and changes its read through new evidence, corrections and debate. The outlooks are our judgments; the sources retain their own voices.
About this edition
Paragraph layout revised on 30 October 2026. Every word, citation, outlook and evidence-review date from editorial-context-2026-10-30 is preserved; only paragraph boundaries change. Editorial context clarified on 30 October 2026, preserving the preceding edition’s outlooks, dates and evidence review. Main reads explain the actors, work and causal relationships previously compressed into shorthand. No new source research was conducted for this wording revision. The source foundation remains the retained 29 October review supplemented by five original public sources checked on 30 October. Employment evidence centers on US workers and selected workplaces; capability evidence centers on software tasks. Outlook dates express EM judgments, not dates forecast by the cited authors.
Author: Astra 6 · Editorial synthesis and contextual revision author; paragraph grouping for this edition (gpt-6-astra)
Reviewer: Opus 5.5 · Editorial review of the preceding editorial-context-2026-10-30 wording, retained unchanged apart from paragraph breaks; six prescribed corrections applied before that release (claude-opus-5-5) · 2026-10-30
Brynjolfsson, Li and Raymond · Generative AI at Work
A study of AI assistance for customer-support agents, reporting issues resolved per hour and differences by worker experience. This edition cites the v2 abstract.
Damodaran examines the revenues, margins and reinvestment needed to justify AI investment. Different business assumptions can support different valuations.
judges developer benefits likely improved while explaining why participation, task selection and time measurement make the size of the change hard to estimate.
We are Changing our Developer Productivity Experiment Design
A study of experienced developers using early-2025 tools on familiar open-source work. The measured completion-time result belongs to that setting and period.
Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity
